From report at bugs.python.org  Wed Oct  1 01:09:02 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 30 Sep 2014 23:09:02 +0000
Subject: [docs] [issue22465] Number agreement error in section 3.2 of web
	docs
In-Reply-To: <1411415613.69.0.707690037263.issue22465@psf.upfronthosting.co.za>
Message-ID: <20140930230855.23211.60924@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 63dc1e32b715 by Terry Jan Reedy in branch '2.7':
Issue 22465: grammar, number agreement.
https://hg.python.org/cpython/rev/63dc1e32b715

New changeset 4848e0c6b342 by Terry Jan Reedy in branch '3.4':
Issue 22465: grammar, number agreement.
https://hg.python.org/cpython/rev/4848e0c6b342

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

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

From report at bugs.python.org  Wed Oct  1 01:09:52 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 30 Sep 2014 23:09:52 +0000
Subject: [docs] [issue22465] Number agreement error in section 3.2 of web
	docs
In-Reply-To: <1411415613.69.0.707690037263.issue22465@psf.upfronthosting.co.za>
Message-ID: <1412118592.84.0.71541225255.issue22465@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Thanks for the report.

----------
nosy: +terry.reedy
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed Oct  1 01:34:10 2014
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 30 Sep 2014 23:34:10 +0000
Subject: [docs] [issue16155] Some minor doc fixes in Doc/faq
In-Reply-To: <1349562552.07.0.641735051076.issue16155@psf.upfronthosting.co.za>
Message-ID: <1412120050.69.0.840012428219.issue16155@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag
stage:  -> patch review
versions: +Python 3.5 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Wed Oct  1 03:27:35 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Oct 2014 01:27:35 +0000
Subject: [docs] [issue21739] Add hint about expression in list
	comprehensions	(https://docs.python.org/2/tutorial/datastructures.html#list-comprehensions)
In-Reply-To: <1402600679.26.0.179499997563.issue21739@psf.upfronthosting.co.za>
Message-ID: <20141001012727.74997.18214@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 84895d037258 by R David Murray in branch '3.4':
#21739: mention subtle difference between loops and listcomps in tutorial.
https://hg.python.org/cpython/rev/84895d037258

New changeset 8279017436a2 by R David Murray in branch 'default':
Merge #21739: mention subtle difference between loops and listcomps in tutorial.
https://hg.python.org/cpython/rev/8279017436a2

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

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

From report at bugs.python.org  Wed Oct  1 03:28:52 2014
From: report at bugs.python.org (R. David Murray)
Date: Wed, 01 Oct 2014 01:28:52 +0000
Subject: [docs] [issue21739] Add hint about expression in list
	comprehensions	(https://docs.python.org/2/tutorial/datastructures.html#list-comprehensions)
In-Reply-To: <1402600679.26.0.179499997563.issue21739@psf.upfronthosting.co.za>
Message-ID: <1412126932.0.0.97577293729.issue21739@psf.upfronthosting.co.za>


R. David Murray added the comment:

The only demure I got on this was from Ezio, who objected that the concept of 'scope' hadn't been introduced yet in the tutorial.  So I reworded it to avoid the word 'scope'.

Thanks, Rose.

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

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

From report at bugs.python.org  Wed Oct  1 13:34:53 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 01 Oct 2014 11:34:53 +0000
Subject: [docs] [issue22001] containers "same" does not always mean "__eq__".
In-Reply-To: <1405625961.78.0.30088981548.issue22001@psf.upfronthosting.co.za>
Message-ID: <1412163293.8.0.474984901406.issue22001@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/issue22001>
_______________________________________

From report at bugs.python.org  Wed Oct  1 17:47:18 2014
From: report at bugs.python.org (Friedrich Spee von Langenfeld)
Date: Wed, 01 Oct 2014 15:47:18 +0000
Subject: [docs] [issue22528] Missing hint to source code
In-Reply-To: <1412106340.24.0.431957287455.issue22528@psf.upfronthosting.co.za>
Message-ID: <1412178438.78.0.487806047688.issue22528@psf.upfronthosting.co.za>


Friedrich Spee von Langenfeld added the comment:

Excuse me, but it would be nice to fix the documentation of the modules symtable and compileall too. Thanks.

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

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

From report at bugs.python.org  Wed Oct  1 20:33:49 2014
From: report at bugs.python.org (Ryan)
Date: Wed, 01 Oct 2014 18:33:49 +0000
Subject: [docs] [issue19622] Default buffering for input and output pipes
	in	subprocess module
In-Reply-To: <1384579334.66.0.612676075589.issue19622@psf.upfronthosting.co.za>
Message-ID: <1412188429.32.0.413609727208.issue19622@psf.upfronthosting.co.za>


Ryan added the comment:

This is not fixed. The documentation may be more correct now, but the behavior still does not match Python 2 as purported.

The default bufsize changed in 3.3.1 is incorrect, at least when tested in 3.4.0 and 3.4.1.

Here is a test for systems with cat available.

    import subprocess
    proc = subprocess.Popen('cat', stdin=subprocess.PIPE)
    proc.stdin.write('test\n'.encode('utf8'))

This test will succeed in Python 2.x and Python 3.0 - 3.3.0, but fail on 3.4.x. This is a regression as the documentation states "did not match the behavior of Python 2 as most code expected", while the current behavior definitely does not match Python 2.

----------
nosy: +lunixbochs
versions:  -Python 3.2

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

From report at bugs.python.org  Wed Oct  1 22:58:47 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Wed, 01 Oct 2014 20:58:47 +0000
Subject: [docs] [issue9274] code.InteractiveInterpreter fails to change
	locals when	invoked in a function
In-Reply-To: <1279300874.85.0.408315798568.issue9274@psf.upfronthosting.co.za>
Message-ID: <1412197127.44.0.985418016681.issue9274@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

@Eric can you provide a doc patch for this?

----------
nosy: +BreamoreBoy
versions: +Python 3.4, Python 3.5 -Python 2.6, Python 3.1, Python 3.2

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

From report at bugs.python.org  Thu Oct  2 00:56:07 2014
From: report at bugs.python.org (paul j3)
Date: Wed, 01 Oct 2014 22:56:07 +0000
Subject: [docs] [issue22401] argparse: 'resolve' conflict handler damages
	the actions	of the parent parser
In-Reply-To: <1410673598.78.0.274465754789.issue22401@psf.upfronthosting.co.za>
Message-ID: <1412204167.18.0.738196184941.issue22401@psf.upfronthosting.co.za>


paul j3 added the comment:

A simpler solution is to make a copy of each Action when importing a parent parser.  The current practice is to just copy references.  With a copy, an Action will belong to only one group and parser, and the 'resolve' handler will operate without problems.

In the attached patch, I added a `.copy` method to Action.  I believe '.option_strings' is the only attribute that needs special handling, since it is a list, and 'resolve' operates on it.  The other attributes are strings, or objects that the user defines (e.g. 'default', 'choices').

The other change is in '_add_container_actions', the method which imports parents.  Here I make the copy action contingent on a 'action_copy' attribute of the conflict handler object (a function).  I also define this attribute for the 'resolve' handler.  I've made this copy contingent just to be safe w/r to backward compatibility, even though, I can't think of a reason for preferring the existing copy by reference.

In another Stackoverflow question, a poster wanted to use the same parent for 2 subparsers, but give the 2 actions different defaults.  This copy approach solves that issue.

This patch needs testing and documentation changes.

----------
keywords: +patch
Added file: http://bugs.python.org/file36773/patch_1.diff

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

From report at bugs.python.org  Thu Oct  2 02:21:23 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Thu, 02 Oct 2014 00:21:23 +0000
Subject: [docs] [issue17799] settrace docs are wrong about "c_call" events
In-Reply-To: <1366428980.14.0.538502026896.issue17799@psf.upfronthosting.co.za>
Message-ID: <1412209282.97.0.813398853049.issue17799@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

@Ned can you provide a patch for this?

----------
nosy: +BreamoreBoy
type:  -> behavior
versions: +Python 3.4, Python 3.5 -Python 3.3

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

From report at bugs.python.org  Thu Oct  2 03:00:41 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Thu, 02 Oct 2014 01:00:41 +0000
Subject: [docs] [issue19342] Improve grp module docstrings
In-Reply-To: <1382432303.67.0.186570774383.issue19342@psf.upfronthosting.co.za>
Message-ID: <1412211641.13.0.0878070369735.issue19342@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

The patch only changes six lines.  At a quick glance it seems fine to me so can we have a formal review please.

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

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

From report at bugs.python.org  Thu Oct  2 04:07:56 2014
From: report at bugs.python.org (Martin Panter)
Date: Thu, 02 Oct 2014 02:07:56 +0000
Subject: [docs] [issue19622] Default buffering for input and output pipes
	in	subprocess module
In-Reply-To: <1384579334.66.0.612676075589.issue19622@psf.upfronthosting.co.za>
Message-ID: <1412215675.99.0.435791701535.issue19622@psf.upfronthosting.co.za>


Martin Panter added the comment:

I agree that it is misleading to say it matches Python 2 behaviour, as I said in my original post. Do you think I should reopen this and get that bit removed from the documentation?

I don?t see an easy way to make the behaviour consistent in all cases. My understanding is Python 2 always defaulted to unbuffered pipe readers and writers, but they were always ?greedy?, meaning the read() and write() methods only succeed after transferring all the data. This is basically the API for BufferedIOBase.read() and BufferedIOBase.write(). In Python 3, unbuffered pipe readers and writers implement the RawIOBase API and may succeed before all the data is transfered.

If you really wanted to change the behaviour to be consistent with Python 2, you could make Popen always return BufferedIOBase pipes (unless universal_newlines=True). But BufferedReader and BufferedWriter don?t seem to accept buffer_size=0. For a pipe reader, maybe BufferedReader(buffer_size=1) would work, but you would either have to hack the BufferedWriter class, or implement a new GreedyWriter class. However I suspect this would introduce deadlocks in programs that access more than one pipe at once (probably also a problem in Python 2).

Perhaps the best thing is to document the problems and then explicitly pass in whatever ?bufsize? value is appropriate for your usage.

----------

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

From report at bugs.python.org  Thu Oct  2 05:09:34 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 02 Oct 2014 03:09:34 +0000
Subject: [docs] [issue22537] Failure building 2.7 docs on Windows
Message-ID: <1412219374.89.0.582755946661.issue22537@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

I was able to build docs of all versions with the old system.  When 3.4 was changed to the new system, 'pip install sphinx' installed everything needed so that 'sphinx-build -bhtml . build/html'  in .../Doc (Devguide 7.5.2) works for 3.4 (and 3.5).  "PYTHON=C:\programs\python27\python.exe" does not seem to matter.

After the recent conversion for 2.7, that command and 'make html' (devguide 7.5.1) do not work for 2.7. The devguide instructions are version-independent, but the reality does not seem to be.  Both commands give this.

Running Sphinx v1.2.2

Configuration error:
There is a syntax error in your configuration file: invalid syntax (patchlevel.py, line 71)
Did you change the syntax from 2.x to 3.x?

tools/patchlevel.py. line 71, is "print x'.  When I added ()s, this error goes away and I get

Running Sphinx v1.2.2

Exception occurred:
  File "F:\Python\dev\2\py27\Doc\tools\pyspecific.py", line 247, in <module>
    import suspicious
  File "F:\Python\dev\2\py27\Doc\tools\suspicious.py", line 57
    detect_all = re.compile(ur'''
    ::(?=[^=])|            # two :: (but NOT ::=)
    :[a-zA-Z][a-zA-Z0-9]+| # :foo
    `|                     # ` (seldom used by itself)
    (?<!\.)\.\.[ \t]*\w+:  # .. foo: (but NOT ... else:)
    ''', re.UNICODE | re.VERBOSE).finditer

      ^
SyntaxError: invalid syntax

I expect the problem is the 'ur' prefix, invalid in 3.4+.

I tried to install a 2.7 version of sphinx, but pip refuses.

C:\Programs\Python27>pip install sphinx
Requirement already satisfied (use --upgrade to upgrade): sphinx in c:\programs\python34\lib\site-packages

So I don't know how to sensibly proceed without disabling 3.x builds.

----------
assignee: docs at python
components: Devguide, Documentation
messages: 228152
nosy: docs at python, ezio.melotti, georg.brandl, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Failure building 2.7 docs on Windows
type: behavior
versions: Python 2.7

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

From report at bugs.python.org  Thu Oct  2 05:34:34 2014
From: report at bugs.python.org (Ned Deily)
Date: Thu, 02 Oct 2014 03:34:34 +0000
Subject: [docs] [issue22537] Failure building 2.7 docs on Windows
In-Reply-To: <1412219374.89.0.582755946661.issue22537@psf.upfronthosting.co.za>
Message-ID: <1412220874.82.0.903452422223.issue22537@psf.upfronthosting.co.za>


Ned Deily added the comment:

Your analysis is correct: you now do need to use a 2.7 sphinx to build 2.7 docs.  It looks like you may be using a 3.4 version of pip.  However you invoke python2.7, try "python -m pip install sphinx".

----------
nosy: +ned.deily

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

From report at bugs.python.org  Thu Oct  2 08:07:57 2014
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 02 Oct 2014 06:07:57 +0000
Subject: [docs] [issue22537] Failure building 2.7 docs on Windows
In-Reply-To: <1412219374.89.0.582755946661.issue22537@psf.upfronthosting.co.za>
Message-ID: <1412230077.23.0.65369121036.issue22537@psf.upfronthosting.co.za>


Georg Brandl added the comment:

> you now do need

You always did :)

However, it should not be a problem to make the extensions 2.x and 3.x compatible in both branches.

----------

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

From report at bugs.python.org  Thu Oct  2 08:27:25 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 06:27:25 +0000
Subject: [docs] [issue22537] Failure building 2.7 docs on Windows
In-Reply-To: <1412219374.89.0.582755946661.issue22537@psf.upfronthosting.co.za>
Message-ID: <20141002062722.75005.5180@mail.hg.python.org>


Roundup Robot added the comment:

New changeset fd2530294d50 by Georg Brandl in branch '2.7':
Closes #22537: Make sphinx extensions compatible with Python 2 or 3, like in the 3.x branches
https://hg.python.org/cpython/rev/fd2530294d50

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Oct  2 08:32:13 2014
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 02 Oct 2014 06:32:13 +0000
Subject: [docs] [issue19342] Improve grp module docstrings
In-Reply-To: <1382432303.67.0.186570774383.issue19342@psf.upfronthosting.co.za>
Message-ID: <1412231533.81.0.739810405596.issue19342@psf.upfronthosting.co.za>


Georg Brandl added the comment:

LGTM.

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

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

From report at bugs.python.org  Thu Oct  2 08:35:40 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 06:35:40 +0000
Subject: [docs] [issue19342] Improve grp module docstrings
In-Reply-To: <1382432303.67.0.186570774383.issue19342@psf.upfronthosting.co.za>
Message-ID: <20141002063537.74995.72887@mail.hg.python.org>


Roundup Robot added the comment:

New changeset e2b757baaef1 by Georg Brandl in branch '3.4':
Closes #19342: improve docstrings in grp module.
https://hg.python.org/cpython/rev/e2b757baaef1

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Oct  2 08:37:01 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 06:37:01 +0000
Subject: [docs] [issue19342] Improve grp module docstrings
In-Reply-To: <1382432303.67.0.186570774383.issue19342@psf.upfronthosting.co.za>
Message-ID: <20141002063659.86183.18803@mail.hg.python.org>


Roundup Robot added the comment:

New changeset de0ca868d44f by Georg Brandl in branch '2.7':
Closes #19342: improve docstrings in grp module.
https://hg.python.org/cpython/rev/de0ca868d44f

----------

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

From report at bugs.python.org  Thu Oct  2 08:40:07 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 06:40:07 +0000
Subject: [docs] [issue22528] Missing hint to source code
In-Reply-To: <1412106340.24.0.431957287455.issue22528@psf.upfronthosting.co.za>
Message-ID: <20141002064004.74985.367@mail.hg.python.org>


Roundup Robot added the comment:

New changeset b51742cb1685 by Georg Brandl in branch '3.4':
closes #22528: add source links to symtable and compileall
https://hg.python.org/cpython/rev/b51742cb1685

New changeset 5144c7d0ef29 by Georg Brandl in branch '2.7':
closes #22528: add source links to symtable and compileall
https://hg.python.org/cpython/rev/5144c7d0ef29

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

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

From report at bugs.python.org  Thu Oct  2 12:26:01 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Thu, 02 Oct 2014 10:26:01 +0000
Subject: [docs] [issue19434] Wrong documentation of MIMENonMultipart class
In-Reply-To: <1383061890.83.0.167475194564.issue19434@psf.upfronthosting.co.za>
Message-ID: <1412245561.46.0.789104835365.issue19434@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

The patch is a one line change, can we have a commit review please.

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

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

From report at bugs.python.org  Thu Oct  2 12:36:06 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 10:36:06 +0000
Subject: [docs] [issue19434] Wrong documentation of MIMENonMultipart class
In-Reply-To: <1383061890.83.0.167475194564.issue19434@psf.upfronthosting.co.za>
Message-ID: <20141002103600.74995.14371@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 41f46f7f2722 by Georg Brandl in branch '3.4':
Closes #19434: fix copy-paste error in MIMENonMultipart docstring.
https://hg.python.org/cpython/rev/41f46f7f2722

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Oct  2 12:36:19 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 10:36:19 +0000
Subject: [docs] [issue19434] Wrong documentation of MIMENonMultipart class
In-Reply-To: <1383061890.83.0.167475194564.issue19434@psf.upfronthosting.co.za>
Message-ID: <20141002103618.121785.30237@mail.hg.python.org>


Roundup Robot added the comment:

New changeset a53f2cf4b556 by Georg Brandl in branch '2.7':
Closes #19434: fix copy-paste error in MIMENonMultipart docstring.
https://hg.python.org/cpython/rev/a53f2cf4b556

----------

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

From report at bugs.python.org  Thu Oct  2 12:39:20 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Oct 2014 10:39:20 +0000
Subject: [docs] [issue18729] In unittest.TestLoader.discover doc select the
	name of	load_tests function
In-Reply-To: <1376418287.73.0.835584535115.issue18729@psf.upfronthosting.co.za>
Message-ID: <20141002103914.86179.4052@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 1e0156aef491 by Georg Brandl in branch '3.4':
Closes #18729: minor markup improvement.
https://hg.python.org/cpython/rev/1e0156aef491

----------
nosy: +python-dev
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Oct  2 13:38:30 2014
From: report at bugs.python.org (Artur de Sousa Rocha)
Date: Thu, 02 Oct 2014 11:38:30 +0000
Subject: [docs] [issue22539] Table formatting errors in pydoc
Message-ID: <1412249910.15.0.577492255731.issue22539@psf.upfronthosting.co.za>


New submission from Artur de Sousa Rocha:

Tables in pydoc are formatted incorrectly -- some lines are missing. Example in Python 3.4.1:

>>> help('TUPLES')
...
+----------------------------+----------------------------------+------------+
| Operation                  | Result                           | Notes      |
+============================+==================================+============+
| "x in s"                   | "True" if an item of *s* is      | (1)        |
+----------------------------+----------------------------------+------------+
| "x not in s"               | "False" if an item of *s* is     | (1)        |
+----------------------------+----------------------------------+------------+
| "s + t"                    | the concatenation of *s* and *t* | (6)(7)     |
+----------------------------+----------------------------------+------------+
| "s * n" or "n * s"         | *n* shallow copies of *s*        | (2)(7)     |
+----------------------------+----------------------------------+------------+
| "s[i]"                     | *i*th item of *s*, origin 0      | (3)        |
+----------------------------+----------------------------------+------------+
| "s[i:j]"                   | slice of *s* from *i* to *j*     | (3)(4)     |
+----------------------------+----------------------------------+------------+
| "s[i:j:k]"                 | slice of *s* from *i* to *j*     | (3)(5)     |
+----------------------------+----------------------------------+------------+
+----------------------------+----------------------------------+------------+
+----------------------------+----------------------------------+------------+
+----------------------------+----------------------------------+------------+
| "s.index(x[, i[, j]])"     | index of the first occurrence of | (8)        |
+----------------------------+----------------------------------+------------+
+----------------------------+----------------------------------+------------+


Older version of the same table in Python 3.2.5 in Cygwin console:

+--------------------+----------------------------------+------------+
| Operation          | Result                           | Notes      |
+====================+==================================+============+
| ``x in s``         | ``True`` if an item of *s* is    | (1)        |
|                    | equal to *x*, else ``False``     |            |
+--------------------+----------------------------------+------------+
| ``x not in s``     | ``False`` if an item of *s* is   | (1)        |
|                    | equal to *x*, else ``True``      |            |
+--------------------+----------------------------------+------------+
| ``s + t``          | the concatenation of *s* and *t* | (6)        |
+--------------------+----------------------------------+------------+
| ``s * n, n * s``   | *n* shallow copies of *s*        | (2)        |
|                    | concatenated                     |            |
+--------------------+----------------------------------+------------+
| ``s[i]``           | *i*th item of *s*, origin 0      | (3)        |
+--------------------+----------------------------------+------------+
| ``s[i:j]``         | slice of *s* from *i* to *j*     | (3)(4)     |
+--------------------+----------------------------------+------------+
| ``s[i:j:k]``       | slice of *s* from *i* to *j*     | (3)(5)     |
|                    | with step *k*                    |            |
+--------------------+----------------------------------+------------+
| ``len(s)``         | length of *s*                    |            |
+--------------------+----------------------------------+------------+
| ``min(s)``         | smallest item of *s*             |            |
+--------------------+----------------------------------+------------+
| ``max(s)``         | largest item of *s*              |            |
+--------------------+----------------------------------+------------+
| ``s.index(i)``     | index of the first occurence of  |            |
|                    | *i* in *s*                       |            |
+--------------------+----------------------------------+------------+
| ``s.count(i)``     | total number of occurences of    |            |
|                    | *i* in *s*                       |            |
+--------------------+----------------------------------+------------+

----------
assignee: docs at python
components: Documentation
messages: 228217
nosy: Artur.de.Sousa.Rocha, docs at python
priority: normal
severity: normal
status: open
title: Table formatting errors in pydoc
type: behavior
versions: Python 3.4

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

From report at bugs.python.org  Thu Oct  2 18:24:54 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 02 Oct 2014 16:24:54 +0000
Subject: [docs] [issue22537] Failure building 2.7 docs on Windows
In-Reply-To: <1412219374.89.0.582755946661.issue22537@psf.upfronthosting.co.za>
Message-ID: <1412267094.22.0.672402727416.issue22537@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Works great. Thanks.

----------

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

From report at bugs.python.org  Thu Oct  2 23:00:18 2014
From: report at bugs.python.org (Ned Deily)
Date: Thu, 02 Oct 2014 21:00:18 +0000
Subject: [docs] [issue22539] Table formatting errors in pydoc
In-Reply-To: <1412249910.15.0.577492255731.issue22539@psf.upfronthosting.co.za>
Message-ID: <1412283618.25.0.624505415783.issue22539@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct  3 00:56:48 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Thu, 02 Oct 2014 22:56:48 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
In-Reply-To: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>
Message-ID: <1412290608.71.0.774650133002.issue19477@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

@Stefan can you provide a patch for this?

----------
nosy: +BreamoreBoy
versions: +Python 3.5 -Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Fri Oct  3 01:01:23 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Thu, 02 Oct 2014 23:01:23 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1412290883.91.0.22833961372.issue19489@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

If this is referring to the box on docs.python.org shouldn't this be logged elsewhere?

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

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

From report at bugs.python.org  Fri Oct  3 01:17:04 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 02 Oct 2014 23:17:04 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1412291824.5.0.959645401756.issue19489@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct  3 01:49:37 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Thu, 02 Oct 2014 23:49:37 +0000
Subject: [docs] [issue19472] inspect.getsource() raises a wrong exception
	type
In-Reply-To: <1383306863.35.0.879382426433.issue19472@psf.upfronthosting.co.za>
Message-ID: <1412293777.14.0.147548743549.issue19472@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

@Yury do you agree with this?

----------
nosy: +BreamoreBoy, yselivanov

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

From report at bugs.python.org  Fri Oct  3 02:52:26 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 03 Oct 2014 00:52:26 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
In-Reply-To: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>
Message-ID: <1412297546.53.0.257340681394.issue19477@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Fri Oct  3 10:07:34 2014
From: report at bugs.python.org (Florent Rougon)
Date: Fri, 03 Oct 2014 08:07:34 +0000
Subject: [docs] [issue11975] Fix referencing of built-in types (list, int,
	...)
In-Reply-To: <1304281262.53.0.265979216697.issue11975@psf.upfronthosting.co.za>
Message-ID: <1412323654.81.0.224865124318.issue11975@psf.upfronthosting.co.za>


Changes by Florent Rougon <frougon at users.sourceforge.net>:


----------
nosy: +frougon

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

From report at bugs.python.org  Fri Oct  3 11:31:18 2014
From: report at bugs.python.org (Tommy Andersen)
Date: Fri, 03 Oct 2014 09:31:18 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
Message-ID: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>


New submission from Tommy Andersen:

The format documentation for the Format Specification Mini-Language for python 3.3 (perhaps newer and older as well) at: https://docs.python.org/3.3/library/string.html 

States for type '' (for floating point numbers):

    Similar to 'g', except with at least one digit past the decimal point and a default precision of 12. This is intended to match str(), except you can add the other format modifiers.

This appears not to be true, the following code example, run in Python 3.3.2:

>>> '{}'.format(3.14159265358979323846264338327950288419)
'3.141592653589793'

As it can be seen form the output the default precision appears to be 15.

----------
assignee: docs at python
components: Documentation
messages: 228318
nosy: Barium, docs at python
priority: normal
severity: normal
status: open
title: Wrong default precision in documentation for format
versions: Python 3.3

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

From report at bugs.python.org  Fri Oct  3 13:03:04 2014
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 03 Oct 2014 11:03:04 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412334184.1.0.69396138327.issue22546@psf.upfronthosting.co.za>


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


----------
nosy: +eric.smith, mark.dickinson

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

From report at bugs.python.org  Fri Oct  3 13:06:13 2014
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 03 Oct 2014 11:06:13 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412334373.25.0.771586169729.issue22546@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

I think this is a result of changing the precision of str() to match repr().

2.7 prints:
'3.14159265359'

----------

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

From Scott.Hinton at Honeywell.com  Thu Oct  2 17:25:09 2014
From: Scott.Hinton at Honeywell.com (Hinton, Scott (ESEA Space))
Date: Thu, 2 Oct 2014 15:25:09 +0000
Subject: [docs] typos in docs
Message-ID: <63EC325C5190FF4CBC44EB63354C987E22639FAC@az18ex3002.global.ds.honeywell.com>

Hello,

I was reading in the multiprocessing module section today
https://docs.python.org/2/library/multiprocessing.html#all-platforms
and noticed a few minor errors:
"Remember also that non-daemonic processes will be automatically be joined."
That sentence has the word 'be' twice.  The word wrap must have got somebody.
Then a few lines later it says:
"A fix here would be to swap the last two lines round (or simply remove the p.join() line)."
Though most people probably understand this because 'round' is a slang-ish way to say 'around', we should probably change this to use the proper spelling.

Scott Hinton
Honeywell Aerospace
Engineer I Systems

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

From Scott.Hinton at Honeywell.com  Thu Oct  2 19:33:46 2014
From: Scott.Hinton at Honeywell.com (Hinton, Scott (ESEA Space))
Date: Thu, 2 Oct 2014 17:33:46 +0000
Subject: [docs] another minor typo
Message-ID: <63EC325C5190FF4CBC44EB63354C987E2263A110@az18ex3002.global.ds.honeywell.com>

Hello,

There is a minor misspelling in the documentation in section
https://docs.python.org/2/library/multiprocessing.html#miscellaneous
The line says:
"Calling this has the side affect of "joining" any processes which have already finished."
But in this case I believe that affect is incorrect and effect should be used instead.


Scott Hinton
Honeywell Aerospace
Engineer I Systems

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

From zachary.ware+pydocs at gmail.com  Fri Oct  3 17:57:42 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Fri, 3 Oct 2014 10:57:42 -0500
Subject: [docs] typos in docs
In-Reply-To: <63EC325C5190FF4CBC44EB63354C987E22639FAC@az18ex3002.global.ds.honeywell.com>
References: <63EC325C5190FF4CBC44EB63354C987E22639FAC@az18ex3002.global.ds.honeywell.com>
Message-ID: <CAKJDb-PQOjQc2rCty2g2X4ai0xszDh5jRkn=bcYWDLOWfDMXUQ@mail.gmail.com>

On Thu, Oct 2, 2014 at 10:25 AM, Hinton, Scott (ESEA Space)
<Scott.Hinton at honeywell.com> wrote:
> Hello,
>
> I was reading in the multiprocessing module section today
>
> https://docs.python.org/2/library/multiprocessing.html#all-platforms
>
> and noticed a few minor errors:
>
> ?Remember also that non-daemonic processes will be automatically be joined.?
>
> That sentence has the word ?be? twice.  The word wrap must have got
> somebody.
>
> Then a few lines later it says:
>
> ?A fix here would be to swap the last two lines round (or simply remove the
> p.join() line).?
>
> Though most people probably understand this because ?round? is a slang-ish
> way to say ?around?, we should probably change this to use the proper
> spelling.

Thanks for the report!

These (and the one you reported in another message) have been fixed
and will be live soon.

Regards,
-- 
Zach

From report at bugs.python.org  Fri Oct  3 22:23:18 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 03 Oct 2014 20:23:18 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412367798.18.0.799214799623.issue22546@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

"The precision is a decimal number indicating how many digits should be displayed ... before and after the decimal point for a floating point value formatted with 'g' or 'G'. It seems that str, repr, and '' are using precision 16, and the doc should be changed to match.

>>>str(.314159265358979323846264338327950288419)
'0.3141592653589793' # 16, not counting 0.

>>> '{}'.format(3.14159265358979323846264338327950288419)
'3.141592653589793'
>>> '{:.16g}'.format(3.14159265358979323846264338327950288419)
'3.141592653589793'
>>> str(3.14159265358979323846264338327950288419)
'3.141592653589793'  # 16

But I discovered this 'anomaly' (bug?)
>>> str(31.4159265358979323846264338327950288419)
'31.41592653589793'
>>> str(33.14159265358979323846264338327950288419)
'33.1415926535898'  # precision 15
I expected this last to be
'33.14159265358979'
as 32... rounds down, not up.

repr and '{}'.format act the same.

----------
nosy: +terry.reedy
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.4, Python 3.5 -Python 3.3

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

From report at bugs.python.org  Fri Oct  3 22:28:34 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 03 Oct 2014 20:28:34 +0000
Subject: [docs] [issue16700] Document that bytes OS API can returns unusable
	results	on Windows
In-Reply-To: <1355677117.39.0.191453655217.issue16700@psf.upfronthosting.co.za>
Message-ID: <1412368114.04.0.659227321667.issue16700@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

As #13247 has been closed "not a bug" and #16656 "won't fix" shouldn't this be done sooner rather than later?

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

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

From report at bugs.python.org  Fri Oct  3 23:17:09 2014
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 03 Oct 2014 21:17:09 +0000
Subject: [docs] [issue19472] inspect.getsource() raises a wrong exception
	type
In-Reply-To: <1383306863.35.0.879382426433.issue19472@psf.upfronthosting.co.za>
Message-ID: <1412371029.51.0.69513110279.issue19472@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

> @Yury do you agree with this?

I think it's a perfectly normal behaviour. OSError is raised for valid kind of objects, and TypeError is raised when you're passing something weird. That's a pretty common practice is Python.

----------

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

From report at bugs.python.org  Fri Oct  3 23:17:18 2014
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 03 Oct 2014 21:17:18 +0000
Subject: [docs] [issue19472] inspect.getsource() raises a wrong exception
	type
In-Reply-To: <1383306863.35.0.879382426433.issue19472@psf.upfronthosting.co.za>
Message-ID: <1412371038.72.0.788998533137.issue19472@psf.upfronthosting.co.za>


Changes by Yury Selivanov <yselivanov at gmail.com>:


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

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

From report at bugs.python.org  Sat Oct  4 00:21:21 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 03 Oct 2014 22:21:21 +0000
Subject: [docs] [issue19796] urllib2.HTTPError.reason is not documented as
	"Added in	2.7"
In-Reply-To: <1385459958.78.0.648544615764.issue19796@psf.upfronthosting.co.za>
Message-ID: <1412374881.67.0.288626467347.issue19796@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

The patch just adds the version added tag to urllib2.rst.  Can someone commit this please.

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

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

From report at bugs.python.org  Sat Oct  4 02:22:59 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 04 Oct 2014 00:22:59 +0000
Subject: [docs] [issue18043] No mention of `match.regs` in `re` documentation
In-Reply-To: <1369308537.81.0.515783227267.issue18043@psf.upfronthosting.co.za>
Message-ID: <1412382179.47.0.75409390711.issue18043@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

@Ram Rachum can you provide a patch for this?

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

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

From report at bugs.python.org  Sat Oct  4 02:42:28 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Oct 2014 00:42:28 +0000
Subject: [docs] [issue19796] urllib2.HTTPError.reason is not documented as
	"Added in	2.7"
In-Reply-To: <1385459958.78.0.648544615764.issue19796@psf.upfronthosting.co.za>
Message-ID: <1412383348.86.0.361410181032.issue19796@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag
stage:  -> patch review

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

From report at bugs.python.org  Sat Oct  4 02:42:56 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Oct 2014 00:42:56 +0000
Subject: [docs] [issue13211] urllib2.HTTPError does not have 'reason'
	attribute.
In-Reply-To: <1318943168.93.0.520705450261.issue13211@psf.upfronthosting.co.za>
Message-ID: <1412383376.47.0.554612164333.issue13211@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct  4 06:37:21 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Oct 2014 04:37:21 +0000
Subject: [docs] [issue19796] urllib2.HTTPError.reason is not documented as
	"Added in	2.7"
In-Reply-To: <1385459958.78.0.648544615764.issue19796@psf.upfronthosting.co.za>
Message-ID: <1412397441.64.0.599603722155.issue19796@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct  4 09:03:58 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 04 Oct 2014 07:03:58 +0000
Subject: [docs] [issue18043] No mention of `match.regs` in `re` documentation
In-Reply-To: <1369308537.81.0.515783227267.issue18043@psf.upfronthosting.co.za>
Message-ID: <1412406238.87.0.832564642393.issue18043@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I'm wondering what "regs" is supposed to stand for.  It might be for "regions", but that term is used nowhere else.  It should really be named "spans" to be consistent.

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

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

From report at bugs.python.org  Sat Oct  4 09:20:24 2014
From: report at bugs.python.org (Ram Rachum)
Date: Sat, 04 Oct 2014 07:20:24 +0000
Subject: [docs] [issue18043] No mention of `match.regs` in `re` documentation
In-Reply-To: <1369308537.81.0.515783227267.issue18043@psf.upfronthosting.co.za>
Message-ID: <1412407224.16.0.405038719878.issue18043@psf.upfronthosting.co.za>


Ram Rachum added the comment:

Mark, I prefer to leave this to someone else.

----------

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

From report at bugs.python.org  Sat Oct  4 09:55:57 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 04 Oct 2014 07:55:57 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412409357.0.0.662259976559.issue22546@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

> It seems that str, repr, and '' are using precision 16

None of them is using a fixed precision: they're all using David Gay's implementation of the "shortest string" algorithm (? la Burger and Dybvig).   For repr, this is the case since Python 3.1 / 2.7; for str and formatting with no type specifier, since Python 3.2.  The docs definitely do need updating here.

> I expected this last to be
> '33.14159265358979'

'33.1415926535898' is shorter, and rounds back to the same floating-point number, so that's what Gay's algorithm gives here.

----------

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

From report at bugs.python.org  Sat Oct  4 10:03:39 2014
From: report at bugs.python.org (Tommy Andersen)
Date: Sat, 04 Oct 2014 08:03:39 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412409819.54.0.802300833619.issue22546@psf.upfronthosting.co.za>


Changes by Tommy Andersen <andersentommy at gmail.com>:


----------
versions: +Python 3.3

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

From report at bugs.python.org  Sat Oct  4 10:18:31 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 04 Oct 2014 08:18:31 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412410711.51.0.63216894722.issue22546@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Here's a proposed fix.

----------
keywords: +patch
Added file: http://bugs.python.org/file36798/missing_type_specifier.patch

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

From report at bugs.python.org  Sat Oct  4 10:25:12 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 04 Oct 2014 08:25:12 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412411112.61.0.782757368925.issue22546@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Hmm;  it's only outputs in non-scientific notation that are guaranteed to have a decimal point.  Patch updated.

----------
Added file: http://bugs.python.org/file36799/missing_type_specifier2.patch

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

From report at bugs.python.org  Sat Oct  4 18:00:47 2014
From: report at bugs.python.org (Eric Fulton)
Date: Sat, 04 Oct 2014 16:00:47 +0000
Subject: [docs] [issue22553] Diagram issue
Message-ID: <1412438447.77.0.331037308598.issue22553@psf.upfronthosting.co.za>


New submission from Eric Fulton:

I believe the diagram showing how slices works from https://docs.python.org/2/tutorial/introduction.html is incorrect.  There should be no 6.  

>>> word = 'Python'
>>> word[6]
IndexError: string index out of range


Original:
 +---+---+---+---+---+---+
 | P | y | t | h | o | n |
 +---+---+---+---+---+---+
 0   1   2   3   4   5   6
-6  -5  -4  -3  -2  -1

What it should be:
 +---+---+---+---+---+---+
 | P | y | t | h | o | n |
 +---+---+---+---+---+---+
 0   1   2   3   4   5   
-6  -5  -4  -3  -2  -1


--------------------------

One way to remember how slices work is to think of the indices as pointing between characters, with the left edge of the first character numbered 0. Then the right edge of the last character of a string of n characters has index n, for example:

 +---+---+---+---+---+---+
 | P | y | t | h | o | n |
 +---+---+---+---+---+---+
 0   1   2   3   4   5   6
-6  -5  -4  -3  -2  -1

----------
assignee: docs at python
components: Documentation
messages: 228464
nosy: Eric.Fulton, docs at python
priority: normal
severity: normal
status: open
title: Diagram issue

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

From report at bugs.python.org  Sat Oct  4 18:05:33 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 04 Oct 2014 16:05:33 +0000
Subject: [docs] [issue22553] Diagram issue
In-Reply-To: <1412438447.77.0.331037308598.issue22553@psf.upfronthosting.co.za>
Message-ID: <1412438733.37.0.285591317814.issue22553@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Hi Eric,

this paragraph is about slices, where you *can* do

>>> word[0:6]
'Python'

As such, the paragraph is correct.

----------
nosy: +georg.brandl
resolution:  -> not a bug
status: open -> closed

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

From report at bugs.python.org  Sat Oct  4 19:51:21 2014
From: report at bugs.python.org (Matthew Barnett)
Date: Sat, 04 Oct 2014 17:51:21 +0000
Subject: [docs] [issue18043] No mention of `match.regs` in `re` documentation
In-Reply-To: <1369308537.81.0.515783227267.issue18043@psf.upfronthosting.co.za>
Message-ID: <1412445081.23.0.941899460347.issue18043@psf.upfronthosting.co.za>


Matthew Barnett added the comment:

There's an interesting bit of history here:

http://www.gossamer-threads.com/lists/python/dev/236584

----------

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

From report at bugs.python.org  Sat Oct  4 19:58:06 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 04 Oct 2014 17:58:06 +0000
Subject: [docs] [issue18043] No mention of `match.regs` in `re` documentation
In-Reply-To: <1369308537.81.0.515783227267.issue18043@psf.upfronthosting.co.za>
Message-ID: <1412445486.83.0.526044020358.issue18043@psf.upfronthosting.co.za>


Georg Brandl added the comment:

IOW: it was already intentionally undocumented back then, and only added for compatibility reasons.

Probably should be deprecated and removed at some point.

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

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

From report at bugs.python.org  Sat Oct  4 23:15:14 2014
From: report at bugs.python.org (Francis MB)
Date: Sat, 04 Oct 2014 21:15:14 +0000
Subject: [docs] [issue8481] doc: ctypes no need to explicitly allocate
	writable	memory with Structure
In-Reply-To: <1271834227.47.0.0148350492358.issue8481@psf.upfronthosting.co.za>
Message-ID: <1412457314.56.0.0328670441734.issue8481@psf.upfronthosting.co.za>


Changes by Francis MB <francismb at email.de>:


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

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

From report at bugs.python.org  Sun Oct  5 00:26:51 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 04 Oct 2014 22:26:51 +0000
Subject: [docs] [issue14201] Documented caching for shared library's
	__getattr__ and	__getitem__ is incorrect
In-Reply-To: <1330957421.08.0.5889949548.issue14201@psf.upfronthosting.co.za>
Message-ID: <20141004222649.52973.15187@mail.hg.python.org>


Roundup Robot added the comment:

New changeset ae64614b66b7 by R David Murray in branch '2.7':
#14201: Update ctypes docs to match behavior changed from 214b28d7a999.
https://hg.python.org/cpython/rev/ae64614b66b7

New changeset 5518aa0fbc06 by R David Murray in branch '3.4':
#14201: Update ctypes docs to match behavior changed from 214b28d7a999.
https://hg.python.org/cpython/rev/5518aa0fbc06

New changeset dfdcc3fad3aa by R David Murray in branch 'default':
Merge: #14201: Update ctypes docs to match behavior changed from 214b28d7a999.
https://hg.python.org/cpython/rev/dfdcc3fad3aa

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

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

From report at bugs.python.org  Sun Oct  5 00:27:59 2014
From: report at bugs.python.org (R. David Murray)
Date: Sat, 04 Oct 2014 22:27:59 +0000
Subject: [docs] [issue14201] Documented caching for shared library's
	__getattr__ and	__getitem__ is incorrect
In-Reply-To: <1330957421.08.0.5889949548.issue14201@psf.upfronthosting.co.za>
Message-ID: <1412461679.29.0.267489472836.issue14201@psf.upfronthosting.co.za>


R. David Murray added the comment:

Committed.  See also issue 22552.

----------
nosy: +r.david.murray
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Oct  5 01:53:46 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 04 Oct 2014 23:53:46 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412466826.5.0.888024936069.issue22546@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I see now that my expectation, based on decimal rounding rather than binary conversion and rounding, was wrong ;-)
>>> 33.14159265358979323846264338327950288419 == 33.1415926535898
True
>>> 33.14159265358979323846264338327950288419 == 33.14159265358979
False
>>> format(33.14159265358979323846264338327950288419, '.18')
'33.1415926535897967'

Tommy: 3.3 only gets security fixes.  When a core developer (indicated by the blue and yellow snake symbol) resets Versions, you should leave them alone or ask before changing.

As for the patch: 'non-scientific' == 'fixed-point', the expression already used in the table. The rewrite omits the fact the exception is to match str and that g and str are otherwise the same except for fixed versus 'as needed' precision.  I note that '' = 'd' for integers also makes '' for integers similar to str() as modified by the preceding options.  An alternate rewrite:

Similar to 'g', except that fixed-point notation, when used, has at least one digit past the decimal point.  The default precision is as high as needed to represent the particular value. The overall effect is to match the output of str() as altered by the other format modifiers.

--
The following in the examples could be fixed in the same patch
>>> '{:+f}; {:+f}'.format(3.14, -3.14)  # show it always
'+3.140000; -3.140000'

add to the comment 'it always displays a sign'.

----------
versions:  -Python 3.3

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

From report at bugs.python.org  Sun Oct  5 02:38:51 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sun, 05 Oct 2014 00:38:51 +0000
Subject: [docs] [issue20997] Wrong URL fragment identifier in search result
In-Reply-To: <1395327003.08.0.0901954371896.issue20997@psf.upfronthosting.co.za>
Message-ID: <1412469531.14.0.22584593937.issue20997@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

What's the verdict on this guys?

----------
nosy: +BreamoreBoy
status: pending -> open

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

From report at bugs.python.org  Sun Oct  5 05:03:32 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 05 Oct 2014 03:03:32 +0000
Subject: [docs] [issue21072] Python docs and downloads not available for
	Egypt
In-Reply-To: <1395872823.34.0.614292416852.issue21072@psf.upfronthosting.co.za>
Message-ID: <1412478212.67.0.629999606915.issue21072@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Is this problem still occurring?

There were recently some problems in other regions with *.python.org getting caught up in national IP filters, which our CDN provider has now resolved by providing us with dedicated IP addresses. These aren't shared with any other users, and hence shouldn't be subject to IP filtering.

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

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

From report at bugs.python.org  Sun Oct  5 10:23:35 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 05 Oct 2014 08:23:35 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412497415.3.0.144361360793.issue22546@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Terry: your rewrite looks fine to me.  +1 for committing that.

----------

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

From report at bugs.python.org  Sun Oct  5 11:52:25 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 05 Oct 2014 09:52:25 +0000
Subject: [docs] [issue20997] Wrong URL fragment identifier in search result
In-Reply-To: <1395327003.08.0.0901954371896.issue20997@psf.upfronthosting.co.za>
Message-ID: <1412502745.11.0.957639401041.issue20997@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Not a Python issue.

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

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

From report at bugs.python.org  Sun Oct  5 12:55:29 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 Oct 2014 10:55:29 +0000
Subject: [docs] [issue22297] 2.7 json encoding broken for enums
In-Reply-To: <1409310034.91.0.63329091583.issue22297@psf.upfronthosting.co.za>
Message-ID: <1412506529.08.0.820851220181.issue22297@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
stage: test needed -> 
status: open -> pending

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

From report at bugs.python.org  Sun Oct  5 15:05:37 2014
From: report at bugs.python.org (Friedrich Spee von Langenfeld)
Date: Sun, 05 Oct 2014 13:05:37 +0000
Subject: [docs] [issue22558] Missing hint to source code - complete
Message-ID: <1412514337.47.0.069385783283.issue22558@psf.upfronthosting.co.za>


New submission from Friedrich Spee von Langenfeld:

As mentioned in Issue22528, in some modules? documentation, the link to their source code is missing. To check the stdlib, I?ve written the script missing_hint.py.
It seems that in the following module entries, there aren?t a link to their source code (the last part of output of missing_hint.py):
https://docs.python.org/3/library/aifc.html
https://docs.python.org/3/library/base64.html
https://docs.python.org/3/library/binhex.html
https://docs.python.org/3/library/bz2.html
https://docs.python.org/3/library/cgi.html
https://docs.python.org/3/library/cgitb.html
https://docs.python.org/3/library/chunk.html
https://docs.python.org/3/library/code.html
https://docs.python.org/3/library/codecs.html
https://docs.python.org/3/library/codeop.html
https://docs.python.org/3/library/configparser.html
https://docs.python.org/3/library/copy.html
https://docs.python.org/3/library/copyreg.html
https://docs.python.org/3/library/csv.html
https://docs.python.org/3/library/datetime.html
https://docs.python.org/3/library/decimal.html
https://docs.python.org/3/library/difflib.html
https://docs.python.org/3/library/doctest.html
https://docs.python.org/3/library/fnmatch.html
https://docs.python.org/3/library/formatter.html
https://docs.python.org/3/library/ftplib.html
https://docs.python.org/3/library/getpass.html
https://docs.python.org/3/library/glob.html
https://docs.python.org/3/library/hashlib.html
https://docs.python.org/3/library/imaplib.html
https://docs.python.org/3/library/imp.html
https://docs.python.org/3/library/io.html
https://docs.python.org/3/library/locale.html
https://docs.python.org/3/library/lzma.html
https://docs.python.org/3/library/macpath.html
https://docs.python.org/3/library/mailbox.html
https://docs.python.org/3/library/mimetypes.html
https://docs.python.org/3/library/nntplib.html
https://docs.python.org/3/library/numbers.html
https://docs.python.org/3/library/os.html
https://docs.python.org/3/library/pathlib.html
https://docs.python.org/3/library/pickle.html
https://docs.python.org/3/library/plistlib.html
https://docs.python.org/3/library/poplib.html
https://docs.python.org/3/library/profile.html
https://docs.python.org/3/library/pydoc.html
https://docs.python.org/3/library/py_compile.html
https://docs.python.org/3/library/quopri.html
https://docs.python.org/3/library/re.html
https://docs.python.org/3/library/sched.html
https://docs.python.org/3/library/selectors.html
https://docs.python.org/3/library/shelve.html
https://docs.python.org/3/library/shutil.html
https://docs.python.org/3/library/smtplib.html
https://docs.python.org/3/library/sndhdr.html
https://docs.python.org/3/library/socket.html
https://docs.python.org/3/library/ssl.html
https://docs.python.org/3/library/stat.html
https://docs.python.org/3/library/stringprep.html
https://docs.python.org/3/library/struct.html
https://docs.python.org/3/library/subprocess.html
https://docs.python.org/3/library/telnetlib.html
https://docs.python.org/3/library/tempfile.html
https://docs.python.org/3/library/timeit.html
https://docs.python.org/3/library/traceback.html
https://docs.python.org/3/library/tracemalloc.html
https://docs.python.org/3/library/turtle.html
https://docs.python.org/3/library/uuid.html
https://docs.python.org/3/library/xdrlib.html

Is it possible to add the specific source code link to all of this entries?

----------
assignee: docs at python
components: Documentation
files: missing_hint.py
messages: 228563
nosy: Friedrich.Spee.von.Langenfeld, docs at python
priority: normal
severity: normal
status: open
title: Missing hint to source code - complete
Added file: http://bugs.python.org/file36812/missing_hint.py

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

From report at bugs.python.org  Sun Oct  5 15:14:21 2014
From: report at bugs.python.org (SilentGhost)
Date: Sun, 05 Oct 2014 13:14:21 +0000
Subject: [docs] [issue22558] Missing hint to source code - complete
In-Reply-To: <1412514337.47.0.069385783283.issue22558@psf.upfronthosting.co.za>
Message-ID: <1412514860.99.0.959015598466.issue22558@psf.upfronthosting.co.za>


SilentGhost added the comment:

Your code produces many false positives, would you care to reduce this list to only those modules that actually do not have a Source code link?

----------
nosy: +SilentGhost

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

From report at bugs.python.org  Sun Oct  5 16:15:26 2014
From: report at bugs.python.org (Stefan Behnel)
Date: Sun, 05 Oct 2014 14:15:26 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
In-Reply-To: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>
Message-ID: <1412518526.47.0.792030483363.issue19477@psf.upfronthosting.co.za>


Stefan Behnel added the comment:

Sure.

----------
keywords: +patch
Added file: http://bugs.python.org/file36813/undocument_tp_print.patch

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

From report at bugs.python.org  Sun Oct  5 16:28:45 2014
From: report at bugs.python.org (Stefan Behnel)
Date: Sun, 05 Oct 2014 14:28:45 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
In-Reply-To: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>
Message-ID: <1412519325.41.0.389290079314.issue19477@psf.upfronthosting.co.za>


Changes by Stefan Behnel <scoder at users.sourceforge.net>:


Removed file: http://bugs.python.org/file36813/undocument_tp_print.patch

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

From report at bugs.python.org  Sun Oct  5 16:28:59 2014
From: report at bugs.python.org (Stefan Behnel)
Date: Sun, 05 Oct 2014 14:28:59 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
In-Reply-To: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>
Message-ID: <1412519339.62.0.0660075861695.issue19477@psf.upfronthosting.co.za>


Changes by Stefan Behnel <scoder at users.sourceforge.net>:


Added file: http://bugs.python.org/file36815/undocument_tp_print.patch

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

From report at bugs.python.org  Sun Oct  5 16:38:12 2014
From: report at bugs.python.org (R. David Murray)
Date: Sun, 05 Oct 2014 14:38:12 +0000
Subject: [docs] [issue22558] Missing hint to source code - complete
In-Reply-To: <1412514337.47.0.069385783283.issue22558@psf.upfronthosting.co.za>
Message-ID: <1412519892.53.0.789656431717.issue22558@psf.upfronthosting.co.za>


R. David Murray added the comment:

And that have source code.

That said, some modules may have been consciously omitted.

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

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

From report at bugs.python.org  Sun Oct  5 16:38:37 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Oct 2014 14:38:37 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
In-Reply-To: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>
Message-ID: <20141005143831.82427.3036@mail.hg.python.org>


Roundup Robot added the comment:

New changeset bead459ccce8 by Georg Brandl in branch '3.4':
Closes #19477: remove outdated documentation of tp_print type object slot.
https://hg.python.org/cpython/rev/bead459ccce8

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Oct  5 17:09:03 2014
From: report at bugs.python.org (Friedrich Spee von Langenfeld)
Date: Sun, 05 Oct 2014 15:09:03 +0000
Subject: [docs] [issue22558] Missing hint to source code - complete
In-Reply-To: <1412514337.47.0.069385783283.issue22558@psf.upfronthosting.co.za>
Message-ID: <1412521743.55.0.103024871132.issue22558@psf.upfronthosting.co.za>


Friedrich Spee von Langenfeld added the comment:

I decremented the shown number of modules by 25. Here is the new list:

https://docs.python.org/3/library/base64.html
https://docs.python.org/3/library/binhex.html
https://docs.python.org/3/library/bz2.html
https://docs.python.org/3/library/cgitb.html
https://docs.python.org/3/library/chunk.html
https://docs.python.org/3/library/code.html
https://docs.python.org/3/library/codecs.html
https://docs.python.org/3/library/codeop.html
https://docs.python.org/3/library/configparser.html
https://docs.python.org/3/library/copy.html
https://docs.python.org/3/library/copyreg.html
https://docs.python.org/3/library/csv.html
https://docs.python.org/3/library/datetime.html
https://docs.python.org/3/library/decimal.html
https://docs.python.org/3/library/difflib.html
https://docs.python.org/3/library/doctest.html
https://docs.python.org/3/library/formatter.html
https://docs.python.org/3/library/getpass.html
https://docs.python.org/3/library/imp.html
https://docs.python.org/3/library/io.html
https://docs.python.org/3/library/locale.html
https://docs.python.org/3/library/lzma.html
https://docs.python.org/3/library/macpath.html
https://docs.python.org/3/library/mailbox.html
https://docs.python.org/3/library/numbers.html
https://docs.python.org/3/library/os.html
https://docs.python.org/3/library/pathlib.html
https://docs.python.org/3/library/pickle.html
https://docs.python.org/3/library/re.html
https://docs.python.org/3/library/selectors.html
https://docs.python.org/3/library/socket.html
https://docs.python.org/3/library/stat.html   # false positive
https://docs.python.org/3/library/stringprep.html
https://docs.python.org/3/library/struct.html
https://docs.python.org/3/library/subprocess.html
https://docs.python.org/3/library/traceback.html
https://docs.python.org/3/library/tracemalloc.html
https://docs.python.org/3/library/turtle.html
https://docs.python.org/3/library/uuid.html

@R. David Murray: I will try to look at the source code for each module, but I have updated the list to make it possible to work on this subject in the meantime.

PS: Is it possible for me to edit my own contributions (comments, files) after uploading?

----------
Added file: http://bugs.python.org/file36817/missing_hint_v2.py

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

From report at bugs.python.org  Sun Oct  5 17:48:01 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Oct 2014 15:48:01 +0000
Subject: [docs] [issue16518] add "buffer protocol" to glossary
In-Reply-To: <1353477807.87.0.204584648831.issue16518@psf.upfronthosting.co.za>
Message-ID: <20141005154755.64895.19454@mail.hg.python.org>


Roundup Robot added the comment:

New changeset e7e8a218737a by R David Murray in branch 'default':
#16518: Bring error messages in harmony with docs ("bytes-like object")
https://hg.python.org/cpython/rev/e7e8a218737a

----------

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

From report at bugs.python.org  Sun Oct  5 18:15:14 2014
From: report at bugs.python.org (R. David Murray)
Date: Sun, 05 Oct 2014 16:15:14 +0000
Subject: [docs] [issue16518] add "buffer protocol" to glossary
In-Reply-To: <1353477807.87.0.204584648831.issue16518@psf.upfronthosting.co.za>
Message-ID: <1412525714.51.0.795192963059.issue16518@psf.upfronthosting.co.za>


R. David Murray added the comment:

Committed the message changes to 3.5 only, since it will probably cause tests to fail in various projects, despite messages not being a formal part of the python API.  

Per IRC conversation with Ezio and Antoine, I posted a note to python-dev to let people know we now have a consistent terminology in the docs and error messages, and to provide a last opportunity for objections (it is easy enough to back the patch out if there is an outcry, but I don't expect one).

----------
nosy: +r.david.murray
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Oct  5 19:27:53 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sun, 05 Oct 2014 17:27:53 +0000
Subject: [docs] [issue14303] Incorrect documentation for socket.py on linux
In-Reply-To: <1331744298.15.0.025379356395.issue14303@psf.upfronthosting.co.za>
Message-ID: <1412530073.36.0.956957489413.issue14303@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

Shane, there are major differences between the makefile docs versions 2 and 3, so could you prepare a patch for this addressed at version 2 only?

----------
nosy: +BreamoreBoy
versions:  -Python 2.6

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

From report at bugs.python.org  Sun Oct  5 19:40:56 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 Oct 2014 17:40:56 +0000
Subject: [docs] [issue16518] add "buffer protocol" to glossary
In-Reply-To: <1353477807.87.0.204584648831.issue16518@psf.upfronthosting.co.za>
Message-ID: <1412530856.49.0.29315089778.issue16518@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

There are other unfixed messages (may be introduced after 3.3):

>>> b''.join([''])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: sequence item 0: expected bytes, bytearray, or an object with the buffer interface, str found
>>> str(42, 'utf8')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: coercing to str: need bytes, bytearray or buffer-like object, int found
>>> import array; array.array('B').frombytes(array.array('I'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: string/buffer of bytes required.
>>> import socket; print(socket.socket.sendmsg.__doc__)
sendmsg(buffers[, ancdata[, flags[, address]]]) -> count

Send normal and ancillary data to the socket, gathering the
non-ancillary data from a series of buffers and concatenating it into
a single message.  The buffers argument specifies the non-ancillary
data as an iterable of buffer-compatible objects (e.g. bytes objects).
The ancdata argument specifies the ancillary data (control messages)
as an iterable of zero or more tuples (cmsg_level, cmsg_type,
cmsg_data), where cmsg_level and cmsg_type are integers specifying the
protocol level and protocol-specific type respectively, and cmsg_data
is a buffer-compatible object holding the associated data.  The flags
argument defaults to 0 and has the same meaning as for send().  If
address is supplied and not None, it sets a destination address for
the message.  The return value is the number of bytes of non-ancillary
data sent.

And there are several mentions of "buffer-like" or "buffer-compatible" in the documentation.

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

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

From report at bugs.python.org  Sun Oct  5 20:02:37 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sun, 05 Oct 2014 18:02:37 +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: <1412532157.04.0.623972033462.issue12957@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

@Michael can you provide a patch to this effect?

----------
nosy: +BreamoreBoy
versions: +Python 3.5 -Python 3.3

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

From report at bugs.python.org  Sun Oct  5 20:34:00 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sun, 05 Oct 2014 18:34:00 +0000
Subject: [docs] [issue18494] PyType_GenericSet/GetDict functions misnamed in
	docs?
In-Reply-To: <1374174654.87.0.00339141994483.issue18494@psf.upfronthosting.co.za>
Message-ID: <1412534040.85.0.161560505093.issue18494@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

Can someone with knowledge of the C code associated with the object/type system comment on this please.

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

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

From report at bugs.python.org  Sun Oct  5 21:03:48 2014
From: report at bugs.python.org (eryksun)
Date: Sun, 05 Oct 2014 19:03:48 +0000
Subject: [docs] [issue18494] PyType_GenericSet/GetDict functions misnamed in
	docs?
In-Reply-To: <1374174654.87.0.00339141994483.issue18494@psf.upfronthosting.co.za>
Message-ID: <1412535828.01.0.888408462508.issue18494@psf.upfronthosting.co.za>


eryksun added the comment:

See changeset 78f93eb7dd75. The names in the docs are wrong.

----------
nosy: +eryksun

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

From report at bugs.python.org  Mon Oct  6 03:21:11 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 01:21:11 +0000
Subject: [docs] [issue18494] PyType_GenericSet/GetDict functions misnamed in
	docs?
In-Reply-To: <1374174654.87.0.00339141994483.issue18494@psf.upfronthosting.co.za>
Message-ID: <20141006012101.52977.7570@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 9dbd7d34cbcf by Benjamin Peterson in branch '3.4':
PyObject not PyType (closes #18494)
https://hg.python.org/cpython/rev/9dbd7d34cbcf

New changeset ec3077e23b7d by Benjamin Peterson in branch 'default':
merge 3.4 (#18494)
https://hg.python.org/cpython/rev/ec3077e23b7d

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 08:05:09 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 06:05:09 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <20141006060506.52967.40191@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 041d0752171a by Terry Jan Reedy in branch '3.4':
Issue #22546: update doc for mini-language float None presentation type.
https://hg.python.org/cpython/rev/041d0752171a

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

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

From report at bugs.python.org  Mon Oct  6 08:06:23 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Oct 2014 06:06:23 +0000
Subject: [docs] [issue22546] Wrong default precision in documentation for
	format
In-Reply-To: <1412328678.8.0.959126948842.issue22546@psf.upfronthosting.co.za>
Message-ID: <1412575583.38.0.3481310215.issue22546@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Tommy, thanks for reporting this.

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

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

From report at bugs.python.org  Mon Oct  6 12:54:22 2014
From: report at bugs.python.org (Lars Buitinck)
Date: Mon, 06 Oct 2014 10:54:22 +0000
Subject: [docs] [issue22565] missing const in declaration of PyErr_WarnEx in
	C-API	docs
Message-ID: <1412592862.35.0.877932125102.issue22565@psf.upfronthosting.co.za>


New submission from Lars Buitinck:

The declaration for PyErr_WarnEx in Doc/c-api/exceptions.rst is missing a const compared to Include/warnings.h.

----------
assignee: docs at python
components: Documentation
files: pyerr_warnex_const.patch
keywords: patch
messages: 228657
nosy: docs at python, larsmans
priority: normal
severity: normal
status: open
title: missing const in declaration of PyErr_WarnEx in C-API docs
versions: Python 3.5
Added file: http://bugs.python.org/file36824/pyerr_warnex_const.patch

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

From report at bugs.python.org  Mon Oct  6 12:58:45 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 10:58:45 +0000
Subject: [docs] [issue22565] missing const in declaration of PyErr_WarnEx in
	C-API	docs
In-Reply-To: <1412592862.35.0.877932125102.issue22565@psf.upfronthosting.co.za>
Message-ID: <20141006105841.82443.42233@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 554152c317b4 by Georg Brandl in branch '3.4':
Closes #22565: fix argument types of PyErr_WarnEx.
https://hg.python.org/cpython/rev/554152c317b4

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 16:20:05 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 14:20:05 +0000
Subject: [docs] [issue10031] Withdraw anti-recommendation of relative
	imports from	documentation
In-Reply-To: <1286309891.2.0.339569302596.issue10031@psf.upfronthosting.co.za>
Message-ID: <20141006141925.52963.47309@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 8c33440d1f64 by Georg Brandl in branch '3.4':
Closes #10031: overhaul the "imports" section of the programming FAQ.
https://hg.python.org/cpython/rev/8c33440d1f64

----------
nosy: +python-dev
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 16:21:56 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 14:21:56 +0000
Subject: [docs] [issue10031] Withdraw anti-recommendation of relative
	imports from	documentation
In-Reply-To: <1286309891.2.0.339569302596.issue10031@psf.upfronthosting.co.za>
Message-ID: <20141006142125.64915.77902@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 9d321235f1f9 by Georg Brandl in branch '2.7':
Closes #10031: overhaul the "imports" section of the programming FAQ.
https://hg.python.org/cpython/rev/9d321235f1f9

----------

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

From report at bugs.python.org  Mon Oct  6 16:25:25 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 06 Oct 2014 14:25:25 +0000
Subject: [docs] [issue16518] add "buffer protocol" to glossary
In-Reply-To: <1353477807.87.0.204584648831.issue16518@psf.upfronthosting.co.za>
Message-ID: <1412605525.06.0.665543025896.issue16518@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Please open a new issue for those.

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

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

From report at bugs.python.org  Mon Oct  6 16:37:04 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 14:37:04 +0000
Subject: [docs] [issue14303] Incorrect documentation for socket.py on linux
In-Reply-To: <1331744298.15.0.025379356395.issue14303@psf.upfronthosting.co.za>
Message-ID: <20141006143630.52983.9510@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 6e2a72e05b4f by Georg Brandl in branch '2.7':
Closes #14303: socket.makefile() does not call dup() anymore on the socket fd.
https://hg.python.org/cpython/rev/6e2a72e05b4f

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 16:38:36 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 06 Oct 2014 14:38:36 +0000
Subject: [docs] [issue21784] __init__.py can be a directory
In-Reply-To: <1402973312.89.0.00365270476425.issue21784@psf.upfronthosting.co.za>
Message-ID: <1412606316.43.0.6358603449.issue21784@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I agree, closing.

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

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

From report at bugs.python.org  Mon Oct  6 16:40:56 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 06 Oct 2014 14:40:56 +0000
Subject: [docs] [issue13101] Module Doc viewer closes when browser window
	closes on	Windows 8
In-Reply-To: <1317753409.09.0.358970019617.issue13101@psf.upfronthosting.co.za>
Message-ID: <1412606456.16.0.452692117268.issue13101@psf.upfronthosting.co.za>


Georg Brandl added the comment:

pydoc.gui() no longer exists in supported versions.

----------
nosy: +georg.brandl
resolution:  -> out of date
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 16:48:50 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 14:48:50 +0000
Subject: [docs] [issue21782] hashable documentation error: shouldn't mention
	id
In-Reply-To: <1402943814.73.0.280307813498.issue21782@psf.upfronthosting.co.za>
Message-ID: <20141006144844.64915.33143@mail.hg.python.org>


Roundup Robot added the comment:

New changeset bfaf434a6f10 by Georg Brandl in branch '3.4':
Closes #21782: the default hash(x) is not exactly id(x) but derived from it.
https://hg.python.org/cpython/rev/bfaf434a6f10

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 16:57:11 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 14:57:11 +0000
Subject: [docs] [issue12148] Clarify "or-ing together" doctest option flags
In-Reply-To: <1306058966.52.0.456848115548.issue12148@psf.upfronthosting.co.za>
Message-ID: <20141006145707.64909.19857@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 1439619daf42 by Georg Brandl in branch '3.4':
Closes #12148: clarify "or's together option flags" in doctest docs.
https://hg.python.org/cpython/rev/1439619daf42

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 17:13:50 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 06 Oct 2014 15:13:50 +0000
Subject: [docs] [issue21072] Python docs and downloads not available for
	Egypt
In-Reply-To: <1395872823.34.0.614292416852.issue21072@psf.upfronthosting.co.za>
Message-ID: <1412608430.38.0.0729856578601.issue21072@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
status: open -> pending

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

From report at bugs.python.org  Mon Oct  6 17:47:00 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 15:47:00 +0000
Subject: [docs] [issue17057] Data model documentation grammar
In-Reply-To: <1359332657.03.0.048046509713.issue17057@psf.upfronthosting.co.za>
Message-ID: <20141006154648.64911.33021@mail.hg.python.org>


Roundup Robot added the comment:

New changeset b6fab5c89ca9 by Georg Brandl in branch '2.7':
Closes #17057: fix grammar in old-style vs new-style class docs.
https://hg.python.org/cpython/rev/b6fab5c89ca9

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 17:51:56 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 15:51:56 +0000
Subject: [docs] [issue16155] Some minor doc fixes in Doc/faq
In-Reply-To: <1349562552.07.0.641735051076.issue16155@psf.upfronthosting.co.za>
Message-ID: <20141006155151.52957.27415@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 09782fad1825 by Georg Brandl in branch '2.7':
Closes #16155: fix a few errors in doctest output of the FAQ pages.
https://hg.python.org/cpython/rev/09782fad1825

----------
nosy: +python-dev
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 17:52:06 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 15:52:06 +0000
Subject: [docs] [issue16155] Some minor doc fixes in Doc/faq
In-Reply-To: <1349562552.07.0.641735051076.issue16155@psf.upfronthosting.co.za>
Message-ID: <20141006155159.82427.77798@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 96eab476d45e by Georg Brandl in branch '3.4':
Closes #16155: fix a few errors in doctest output of the FAQ pages.
https://hg.python.org/cpython/rev/96eab476d45e

----------

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

From report at bugs.python.org  Mon Oct  6 17:52:18 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 06 Oct 2014 15:52:18 +0000
Subject: [docs] [issue16155] Some minor doc fixes in Doc/faq
In-Reply-To: <1349562552.07.0.641735051076.issue16155@psf.upfronthosting.co.za>
Message-ID: <1412610738.09.0.854493233667.issue16155@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks!

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

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

From report at bugs.python.org  Mon Oct  6 18:01:11 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 Oct 2014 16:01:11 +0000
Subject: [docs] [issue19071] Documentation on what self is for module-level
	functions	is misleading/wrong.
In-Reply-To: <1379849996.18.0.35390897499.issue19071@psf.upfronthosting.co.za>
Message-ID: <20141006160107.52969.70938@mail.hg.python.org>


Roundup Robot added the comment:

New changeset 59fe0ff02c90 by Georg Brandl in branch '2.7':
Closes #19071: "self" argument is not the module for module functions in 2.x.
https://hg.python.org/cpython/rev/59fe0ff02c90

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Oct  6 18:30:52 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 06 Oct 2014 16:30:52 +0000
Subject: [docs] [issue10583] Encoding issue with chm help in 2.7.1
In-Reply-To: <1291060108.22.0.631034667944.issue10583@psf.upfronthosting.co.za>
Message-ID: <1412613052.7.0.0303813315782.issue10583@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Agreed, closing.

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

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

From report at bugs.python.org  Mon Oct  6 22:23:24 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Oct 2014 20:23:24 +0000
Subject: [docs] [issue22571] Remove import * recommendations and examples in
	doc?
Message-ID: <1412627004.13.0.564055290321.issue22571@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

PEP 8 recommends against 'from mod import *' because it makes reading harder and is bad for code analysis.  My experience with retrofitting tests to idlelib modules with tkinter * imports is that it also makes testing harder since the testing strategy depends on the specific tkinter objects actually used.  So either an explicit list ('from tkinter import x, y, z') or a searchable prefix ('tk.') makes testing easier.  

Some time ago, 'from tkinter import *' was changed to 'import tkinter as tk' in the tkinter doc examples, though *not* the text.  ##10031 changed the import section of the FAQ to "remove the advice to use "from ... import *" with some modules" (from the commit message).  Should we finish the job?  Or leave the issue to individual chapter authors?

Here is the edited result of grepping 'import *' in ...\py34\Doc\*.rst with Idle.

F:\Python\dev\4\py34\Doc\distutils\apiref.rst: 1289: This module is safe to use in ``from ... import *`` mode; it only exports
F:\Python\dev\4\py34\Doc\library\cmd.rst: 234:     from turtle import *
F:\Python\dev\4\py34\Doc\library\collections.abc.rst: 14:    from collections import *
F:\Python\dev\4\py34\Doc\library\collections.rst: 11:     from collections import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 54:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 86:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 320:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 562:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 671:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 695:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 714:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 914:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 1074:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\ctypes.rst: 1122:    >>> from ctypes import *
F:\Python\dev\4\py34\Doc\library\decimal.rst: 20:    from decimal import *
F:\Python\dev\4\py34\Doc\library\decimal.rst: 56:      >>> from decimal import *
F:\Python\dev\4\py34\Doc\library\decimal.rst: 125:    >>> from decimal import *
F:\Python\dev\4\py34\Doc\library\difflib.rst: 13:    from difflib import *
F:\Python\dev\4\py34\Doc\library\itertools.rst: 12:    from itertools import *
F:\Python\dev\4\py34\Doc\library\stat.rst: 104:    from stat import *
F:\Python\dev\4\py34\Doc\library\statistics.rst: 13:    from statistics import *
F:\Python\dev\4\py34\Doc\library\struct.rst: 313:    >>> from struct import *
F:\Python\dev\4\py34\Doc\library\tkinter.rst: 63:    from tkinter import *
F:\Python\dev\4\py34\Doc\library\tkinter.rst: 580:    from tkinter import *
F:\Python\dev\4\py34\Doc\library\tkinter.tix.rst: 60:       from tkinter.constants import *
F:\Python\dev\4\py34\Doc\library\tkinter.ttk.rst: 38:    from tkinter import *
F:\Python\dev\4\py34\Doc\library\tkinter.ttk.rst: 39:    from tkinter.ttk import *
F:\Python\dev\4\py34\Doc\library\turtle.rst: 11:    from turtle import *

F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 102:    >>> from fibo import *
F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 461: Now what happens when the user writes ``from sound.effects import *``?  Ideally,
F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 470: list of module names that should be imported when ``from package import *`` is
F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 479: This would mean that ``from sound.effects import *`` would import the three
F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 482: If ``__all__`` is not defined, the statement ``from sound.effects import *``
F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 493:    from sound.effects import *
F:\Python\dev\4\py34\Doc\tutorial\modules.rst: 501: patterns when you use ``import *``, it is still considered bad practise in
F:\Python\dev\4\py34\Doc\tutorial\stdlib2.rst: 372:    >>> from decimal import *

I removed the reference hits that simply explain.  I have not looked at whether the tutorial goes beyond explanation, but should this even be mentioned in so many places?

----------
assignee: docs at python
components: Documentation
messages: 228734
nosy: docs at python, georg.brandl, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Remove import * recommendations and examples in doc?
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue Oct  7 01:25:43 2014
From: report at bugs.python.org (Leo Butcher)
Date: Mon, 06 Oct 2014 23:25:43 +0000
Subject: [docs] [issue21072] Python docs and downloads not available for
	Egypt
In-Reply-To: <1395872823.34.0.614292416852.issue21072@psf.upfronthosting.co.za>
Message-ID: <1412637943.0.0.748845840458.issue21072@psf.upfronthosting.co.za>


Leo Butcher added the comment:

Yes, all subdomains are working now for me

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

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

From report at bugs.python.org  Tue Oct  7 01:31:53 2014
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 06 Oct 2014 23:31:53 +0000
Subject: [docs] [issue21072] Python docs and downloads not available for
	Egypt
In-Reply-To: <1395872823.34.0.614292416852.issue21072@psf.upfronthosting.co.za>
Message-ID: <1412638313.14.0.145606748008.issue21072@psf.upfronthosting.co.za>


Changes by Benjamin Peterson <benjamin at python.org>:


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

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

From report at bugs.python.org  Tue Oct  7 10:40:23 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 07 Oct 2014 08:40:23 +0000
Subject: [docs] [issue22571] Remove import * recommendations and examples in
	doc?
In-Reply-To: <1412627004.13.0.564055290321.issue22571@psf.upfronthosting.co.za>
Message-ID: <1412671223.26.0.549365804442.issue22571@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

I think it's fine to recommend using (for example) `>>> from decimal import *` at the command-line prompt when experimenting with a module.  It's a quick way to get yourself into a state where you can easily experiment with that module and its features.

That's not the same as recommending that scripts using the decimal module start with "from decimal import *", of course.

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

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

From report at bugs.python.org  Tue Oct  7 17:33:18 2014
From: report at bugs.python.org (Andy Maier)
Date: Tue, 07 Oct 2014 15:33:18 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1412695998.2.0.233983907387.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

Just wanted to say that i will continue working on this, working in the comments made so far...
Andy

----------

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

From report at bugs.python.org  Tue Oct  7 17:50:44 2014
From: report at bugs.python.org (Edward O)
Date: Tue, 07 Oct 2014 15:50:44 +0000
Subject: [docs] [issue22297] 2.7 json encoding broken for enums
In-Reply-To: <1409310034.91.0.63329091583.issue22297@psf.upfronthosting.co.za>
Message-ID: <1412697044.6.0.654907662008.issue22297@psf.upfronthosting.co.za>


Edward O added the comment:

The arguments for fixing:

* int subclasses overriding str is a very common usecase for enums (so much so that it was added to stdlib in 3.4).

* json supporting a standard type of a subsequent python version, though not mandatory, would be beneficial to Py2/Py3 compatibility.

* fixing this cannot break existing code

* the fix could theoretically be done to 3.0-3.3 if Ethan's argument is deemed important.

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

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

From report at bugs.python.org  Tue Oct  7 19:34:20 2014
From: report at bugs.python.org (Martijn Pieters)
Date: Tue, 07 Oct 2014 17:34:20 +0000
Subject: [docs] [issue22575] bytearray documentation confuses string for
	unicode	objects
Message-ID: <1412703260.19.0.077276076378.issue22575@psf.upfronthosting.co.za>


New submission from Martijn Pieters:

The Python 2 version of the bytearray() documentation appears to be copied directly from its Python 3 counterpart and states that when passing in a string an encoding is required:

* If it is a string, you must also give the encoding (and optionally, errors) parameters; bytearray() then converts the string to bytes using str.encode().

(from https://docs.python.org/2/library/functions.html#bytearray).

This obviously doesn't apply to Python 2 str() objects, but would only apply to unicode() objects.

Can this be corrected? The current wording is confusing new users (see http://stackoverflow.com/questions/26230745/how-to-convert-python-str-to-bytearray).

----------
assignee: docs at python
components: Documentation
messages: 228771
nosy: docs at python, mjpieters
priority: normal
severity: normal
status: open
title: bytearray documentation confuses string for unicode objects
versions: Python 2.7

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

From leal2608 at poli.ufrj.br  Mon Oct  6 19:29:14 2014
From: leal2608 at poli.ufrj.br (=?UTF-8?Q?Pedro_Batista_C=C3=A2mara_Leal?=)
Date: Mon, 6 Oct 2014 14:29:14 -0300
Subject: [docs] Documentation: Broken link
Message-ID: <CAMHt0dyOCnX0Zv00Bc5xCjw7vpZ8A4Y4P6C+mMJrGakNKAjPKA@mail.gmail.com>

Hello,

I was looking through the documentation and on
*https://docs.python.org/2/using/windows.html
<https://docs.python.org/2/using/windows.html>*, the hyperlink ?A Byte of
Python? by Swaroop C H, 2003 is redirecting to a website not related to
Python.

Thank you for your time,

Pedro Leal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141006/01c1737b/attachment.html>

From report at bugs.python.org  Tue Oct  7 22:34:38 2014
From: report at bugs.python.org (Derek Kurth)
Date: Tue, 07 Oct 2014 20:34:38 +0000
Subject: [docs] [issue22576] ftplib documentation gives a wrong argument
	name for	storbinary
Message-ID: <1412714078.21.0.80330944433.issue22576@psf.upfronthosting.co.za>


New submission from Derek Kurth:

The Python 3 documentation for ftplib gives the storbinary method signature as:

FTP.storbinary(cmd, file, blocksize=8192, callback=None, rest=None)

However, the parameter named "file" is actually named "fp" in the code, so if you do something like this:

ftp.storbinary(cmd="RETR something.txt", file=f)

then you will get a TypeError: storbinary() got an unexpected keyword argument 'file'.  

I think the documentation should be updated to call that argument "fp" instead of "file."

----------
assignee: docs at python
components: Documentation
messages: 228773
nosy: Derek.Kurth, docs at python
priority: normal
severity: normal
status: open
title: ftplib documentation gives a wrong argument name for storbinary
versions: Python 3.3

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

From report at bugs.python.org  Wed Oct  8 12:15:51 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 08 Oct 2014 10:15:51 +0000
Subject: [docs] [issue22576] ftplib documentation gives a wrong argument
	name for	storbinary
In-Reply-To: <1412714078.21.0.80330944433.issue22576@psf.upfronthosting.co.za>
Message-ID: <20141008101526.99286.29951@psf.io>


Roundup Robot added the comment:

New changeset 4cc584d47c7d by Berker Peksag in branch '3.4':
Issue #22576: Fix signatures of FTP.storbinary() and FTP.storlines() methods.
https://hg.python.org/cpython/rev/4cc584d47c7d

New changeset f21f0de30544 by Berker Peksag in branch 'default':
Issue #22576: Fix signatures of FTP.storbinary() and FTP.storlines() methods.
https://hg.python.org/cpython/rev/f21f0de30544

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

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

From report at bugs.python.org  Wed Oct  8 12:16:52 2014
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 08 Oct 2014 10:16:52 +0000
Subject: [docs] [issue22576] ftplib documentation gives a wrong argument
	name for	storbinary
In-Reply-To: <1412714078.21.0.80330944433.issue22576@psf.upfronthosting.co.za>
Message-ID: <1412763412.27.0.0379439625848.issue22576@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Fixed. Thanks for the report, Derek.

----------
assignee: docs at python -> berker.peksag
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.4, Python 3.5 -Python 3.3

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

From report at bugs.python.org  Wed Oct  8 18:18:21 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 08 Oct 2014 16:18:21 +0000
Subject: [docs] [issue22581] Other mentions of the buffer protocol
Message-ID: <1412785100.97.0.773176507587.issue22581@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

In addition to issue16518. There are other non-fixed messages (may be introduced after 3.3):

>>> b''.join([''])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: sequence item 0: expected bytes, bytearray, or an object with the buffer interface, str found
>>> str(42, 'utf8')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: coercing to str: need bytes, bytearray or buffer-like object, int found
>>> import array; array.array('B').frombytes(array.array('I'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: string/buffer of bytes required.
>>> import socket; print(socket.socket.sendmsg.__doc__)
sendmsg(buffers[, ancdata[, flags[, address]]]) -> count

Send normal and ancillary data to the socket, gathering the
non-ancillary data from a series of buffers and concatenating it into
a single message.  The buffers argument specifies the non-ancillary
data as an iterable of buffer-compatible objects (e.g. bytes objects).
The ancdata argument specifies the ancillary data (control messages)
as an iterable of zero or more tuples (cmsg_level, cmsg_type,
cmsg_data), where cmsg_level and cmsg_type are integers specifying the
protocol level and protocol-specific type respectively, and cmsg_data
is a buffer-compatible object holding the associated data.  The flags
argument defaults to 0 and has the same meaning as for send().  If
address is supplied and not None, it sets a destination address for
the message.  The return value is the number of bytes of non-ancillary
data sent.

And there are several mentions of "buffer-like" or "buffer-compatible" in the documentation.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 228799
nosy: chris.jerdonek, docs at python, eric.araujo, ezio.melotti, flox, georg.brandl, pitrou, python-dev, r.david.murray, rhettinger, serhiy.storchaka, skrah, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Other mentions of the buffer protocol

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

From report at bugs.python.org  Thu Oct  9 18:50:50 2014
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 09 Oct 2014 16:50:50 +0000
Subject: [docs] [issue22586] urljoin allow_fragments doesn't work
In-Reply-To: <1412870433.46.0.862767853703.issue22586@psf.upfronthosting.co.za>
Message-ID: <1412873450.95.0.997316479978.issue22586@psf.upfronthosting.co.za>


Georg Brandl added the comment:

The "not allowed" should be clarified.  What is meant is that if allow_fragments is false, a fragment is parsed as part of the path.

This doesn't make a difference for urljoin if the fragment is part of the second part.  It does make a difference for the first part:

>>> urljoin('http://www.example.com/#frag/', 'foo#bar', allow_fragments=True)
'http://www.example.com/foo#bar'

>>> urljoin('http://www.example.com/#frag/', 'foo#bar', allow_fragments=False)
'http://www.example.com/#frag/foo#bar'

For reference, the urlparse() results:

>>> urlparse('http://www.example.com/#frag/', allow_fragments=True)
ParseResult(scheme='http', netloc='www.example.com', path='/', params='', query='', fragment='frag/')

>>> urlparse('http://www.example.com/#frag/', allow_fragments=False)
ParseResult(scheme='http', netloc='www.example.com', path='/#frag/', params='', query='', fragment='')

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, georg.brandl, orsenthil
versions: +Python 2.7, Python 3.5

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

From manuel.dominguez at altertechnology.com  Wed Oct  8 13:41:00 2014
From: manuel.dominguez at altertechnology.com (Manuel Dominguez Alvarez)
Date: Wed, 8 Oct 2014 13:41:00 +0200
Subject: [docs] error 404 - Download Python 3.4.2 Documentation
Message-ID: <754FCD159662C648BE0C4258E49F35F1069FDABC@tl2kco04.tecnologica.tlc>

Dear Sirs,

 

It seems that there is an error in the page https://docs.python.org/3/download.html when I try to download the documentation https://docs.python.org/3/archives/python-3.4.2-docs-pdf-a4.zip

 

Thanks in advance for your support,

 

Best regards,

Manuel Dom?nguez

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141008/adf46483/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3841 bytes
Desc: image001.png
URL: <http://mail.python.org/pipermail/docs/attachments/20141008/adf46483/attachment-0001.png>

From Matt.funke at VPGSensors.com  Wed Oct  8 17:25:14 2014
From: Matt.funke at VPGSensors.com (Funke, Matt)
Date: Wed, 8 Oct 2014 15:25:14 +0000
Subject: [docs] Erroneous links in downloadable documentation page
Message-ID: <2876D4BDA747384DAAD36E18FDE0689108B05C@WSWD43.vishaypg.com>

The links on this page:

https://docs.python.org/3/download.html

... point to files that don't exist.  Has the downloadable documentation for version 3.4.2 been finalized?  (I note that the release candidate documentation is in that location.)

Matt Funke
Senior Programmer/Analyst | VPG
951 Wendell Blvd | Wendell, NC 27591 USA
Office: 919-374-5553
Mobile: 919-628-9261
Fax: 919-374-5248
vpgsensors.com<http://vpgsensors.com/>
[http://vpgweb.vpgsensors.com/MarCom/REBRANDING%20%20%20Templates%20Forms%20and%20Logos/VPG-Corporate-Email-Signature-Image/VPG-Corporate-email-signagure-small.jpg]<http://www.vpgsensors.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141008/5581cd90/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 12328 bytes
Desc: image001.jpg
URL: <http://mail.python.org/pipermail/docs/attachments/20141008/5581cd90/attachment-0001.jpg>

From P.J.Turner at student.bradford.ac.uk  Wed Oct  8 19:11:59 2014
From: P.J.Turner at student.bradford.ac.uk (Pete Turner)
Date: Wed, 8 Oct 2014 17:11:59 +0000
Subject: [docs] Documentation links broken
Message-ID: <1412788318745.73686@student.bradford.ac.uk>

Hi,


The download links at https://docs.python.org/3/download.html? all give a "404 not found" error


Regards


Peter Turner MSc

Doctoral Student
Archaeological Sciences
University of Bradford
Bradford
West Yorkshire BD7 1DP
UK
Email: p.j.turner at student.bradford.ac.uk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141008/00d1b4dd/attachment.html>

From report at bugs.python.org  Thu Oct  9 23:33:48 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Oct 2014 21:33:48 +0000
Subject: [docs] [issue18176] Builtins documentation refers to old version of
	UCD.
In-Reply-To: <1370823303.7.0.563688972804.issue18176@psf.upfronthosting.co.za>
Message-ID: <20141009213331.42882.71635@psf.io>


Roundup Robot added the comment:

New changeset fd7994909c2d by R David Murray in branch '3.4':
#18176: updated stdtypes UCD link, added reminder to makeunicodedata.
https://hg.python.org/cpython/rev/fd7994909c2d

New changeset 2551bdfff335 by R David Murray in branch 'default':
Merge: #18176: updated stdtypes UCD link, added reminder to makeunicodedata.
https://hg.python.org/cpython/rev/2551bdfff335

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

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

From report at bugs.python.org  Thu Oct  9 23:44:19 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Oct 2014 21:44:19 +0000
Subject: [docs] [issue18176] Builtins documentation refers to old version of
	UCD.
In-Reply-To: <1370823303.7.0.563688972804.issue18176@psf.upfronthosting.co.za>
Message-ID: <20141009214410.22020.89835@psf.io>


Roundup Robot added the comment:

New changeset 303861ce9ead by R David Murray in branch '3.4':
#18176: fix another reference and add it to the makeunicodedata comment.
https://hg.python.org/cpython/rev/303861ce9ead

New changeset e9ec8d622a30 by R David Murray in branch 'default':
Merge: #18176: fix another reference and add it to the makeunicodedata comment.
https://hg.python.org/cpython/rev/e9ec8d622a30

----------

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

From report at bugs.python.org  Thu Oct  9 23:46:45 2014
From: report at bugs.python.org (R. David Murray)
Date: Thu, 09 Oct 2014 21:46:45 +0000
Subject: [docs] [issue18176] Builtins documentation refers to old version of
	UCD.
In-Reply-To: <1370823303.7.0.563688972804.issue18176@psf.upfronthosting.co.za>
Message-ID: <1412891205.13.0.325845785826.issue18176@psf.upfronthosting.co.za>


R. David Murray added the comment:

I committed the stdtypes, lexical_analysis, and Tools changes, updating the version number appropriately in the doc fixes.

I'm closing this, and will open a new issue for the PropList.txt problem.

----------
nosy: +r.david.murray
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Oct 10 02:48:00 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Oct 2014 00:48:00 +0000
Subject: [docs] [issue18176] Builtins documentation refers to old version of
	UCD.
In-Reply-To: <1370823303.7.0.563688972804.issue18176@psf.upfronthosting.co.za>
Message-ID: <20141010004754.77406.64809@psf.io>


Roundup Robot added the comment:

New changeset 73a6f121e51a by R David Murray in branch '3.4':
#18176: Change generic UCD PropList link to version specific link.
https://hg.python.org/cpython/rev/73a6f121e51a

New changeset b04b7af14910 by R David Murray in branch 'default':
Merge: #18176: Change generic UCD PropList link to version specific link.
https://hg.python.org/cpython/rev/b04b7af14910

----------

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

From report at bugs.python.org  Fri Oct 10 03:13:37 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 10 Oct 2014 01:13:37 +0000
Subject: [docs] [issue18176] Builtins documentation refers to old version of
	UCD.
In-Reply-To: <1370823303.7.0.563688972804.issue18176@psf.upfronthosting.co.za>
Message-ID: <1412903617.41.0.813891074402.issue18176@psf.upfronthosting.co.za>


R. David Murray added the comment:

I changed my mind and decided to "fix" the PropList reference to also be version specific, since that solves the immediate problem.  I opened a new issue for automating the changes, since there are three locations and four URLs, now.

----------

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

From report at bugs.python.org  Fri Oct 10 03:38:23 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 10 Oct 2014 01:38:23 +0000
Subject: [docs] [issue7061] Improve turtle module documentation
In-Reply-To: <1254717274.49.0.570691979968.issue7061@psf.upfronthosting.co.za>
Message-ID: <1412905103.15.0.578314072037.issue7061@psf.upfronthosting.co.za>


R. David Murray added the comment:

If there *is* anything left to do here, new issues should be opened.

----------
nosy: +r.david.murray
resolution: accepted -> fixed
stage: commit review -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Oct 10 09:48:05 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 10 Oct 2014 07:48:05 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
Message-ID: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The regex module is purposed as a replacement of standard re module. Of course we fix re bugs, but for now regex is more bugfree. Even after fixing all open re bugs, regex will remain more featured. It would be good to add a link to regex in re documentation (as there are links to other GUI libraries in Tkinter documentation).

----------
assignee: docs at python
components: Documentation, Regular Expressions
keywords: easy
messages: 228961
nosy: docs at python, ezio.melotti, mrabarnett, pitrou, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Add a link to the regex module in re documentation
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Oct 10 16:20:55 2014
From: report at bugs.python.org (=?utf-8?q?Francisco_Fern=C3=A1ndez_Casta=C3=B1o?=)
Date: Fri, 10 Oct 2014 14:20:55 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
Message-ID: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>


New submission from Francisco Fern?ndez Casta?o:

>From the code example at https://docs.python.org/3/library/contextlib.html#contextlib.ContextDecorator

"logging.info('Entering: {}'.format(name))
NameError: name 'name' is not defined"

name is referenced instead of self.name

----------
assignee: docs at python
components: Documentation
files: doctypo.patch
keywords: patch
messages: 229000
nosy: Francisco.Fern?ndez.Casta?o, docs at python
priority: normal
severity: normal
status: open
title: Fix a typo in the contextlib docs
type: crash
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file36867/doctypo.patch

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

From report at bugs.python.org  Fri Oct 10 17:08:29 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 10 Oct 2014 15:08:29 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <1412953709.77.0.846491082623.issue22603@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +ncoghlan
stage:  -> commit review
type: crash -> enhancement

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

From report at bugs.python.org  Fri Oct 10 18:43:30 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 10 Oct 2014 16:43:30 +0000
Subject: [docs] [issue22558] Missing hint to source code - complete
In-Reply-To: <1412514337.47.0.069385783283.issue22558@psf.upfronthosting.co.za>
Message-ID: <1412959410.3.0.250484724053.issue22558@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Messages and patches can be unlinked from an issue (and that action recorded in the history list) but not edited.  Proofread before clicking.

Originally, only a few module docs had a source code link where the source code was thought to be especially useful.  When these links were determined to be useful, more have gradually been added as some developer thought of it or as some user requested, as you did in #22528.  I don't know if any requests have been denied.  I also don't know if there is a written policy anywhere.  To me, it might be easier to link all python sources and be done with the issue.

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

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

From report at bugs.python.org  Fri Oct 10 19:03:19 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Oct 2014 17:03:19 +0000
Subject: [docs] [issue22575] bytearray documentation confuses string for
	unicode	objects
In-Reply-To: <1412703260.19.0.077276076378.issue22575@psf.upfronthosting.co.za>
Message-ID: <20141010170312.58883.34968@psf.io>


Roundup Robot added the comment:

New changeset 0c75819f1d86 by Terry Jan Reedy in branch '2.7':
Issue #22575: Revise bytearray entry for 2.7.
https://hg.python.org/cpython/rev/0c75819f1d86

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

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

From report at bugs.python.org  Fri Oct 10 19:06:42 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 10 Oct 2014 17:06:42 +0000
Subject: [docs] [issue22575] bytearray documentation confuses string for
	unicode	objects
In-Reply-To: <1412703260.19.0.077276076378.issue22575@psf.upfronthosting.co.za>
Message-ID: <1412960802.54.0.863796647748.issue22575@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I changed the line to 
* If it is unicode, you must also give the encoding (and optionally, errors) parameters; bytearray() then converts the unicode to bytes using unicode.encode().

Thank you for the report, and for your work answering questions on SO

----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type:  -> behavior

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

From report at bugs.python.org  Fri Oct 10 21:54:22 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 10 Oct 2014 19:54:22 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <1412970862.29.0.983712778527.issue22603@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy
type: enhancement -> behavior
versions:  -Python 3.2, Python 3.3

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

From report at bugs.python.org  Fri Oct 10 22:02:08 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Oct 2014 20:02:08 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <20141010200058.39544.50116@psf.io>


Roundup Robot added the comment:

New changeset b81443d9c64a by Terry Jan Reedy in branch '3.4':
Issue 22603: add missing 'self'.  Patch by Francisco Fern?ndez Casta?o.
https://hg.python.org/cpython/rev/b81443d9c64a

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

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

From report at bugs.python.org  Fri Oct 10 22:09:21 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 10 Oct 2014 20:09:21 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <1412971761.32.0.141972482947.issue22603@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Thanks. Should you be alphabetized in our ACKS file under Ca... or Fe...?

----------
resolution:  -> fixed
stage: commit review -> resolved

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

From report at bugs.python.org  Fri Oct 10 22:12:06 2014
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 10 Oct 2014 20:12:06 +0000
Subject: [docs] [issue15414] os.path.join behavior on Windows (ntpath.join)
	is	unexpected and not well documented
In-Reply-To: <1342903268.21.0.193498975528.issue15414@psf.upfronthosting.co.za>
Message-ID: <1412971926.19.0.745105403312.issue15414@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Dave, your patch is a significant improvement on the accuracy of the current doc, but the whole paragraph seems somewhat haphazard and confusing to me.  Here's my own attempt to clean it up, though I'm not certain just how much improvement it is :)

----------
nosy: +zach.ware
Added file: http://bugs.python.org/file36872/issue15414.diff

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

From report at bugs.python.org  Fri Oct 10 22:13:13 2014
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 10 Oct 2014 20:13:13 +0000
Subject: [docs] [issue15414] os.path.join behavior on Windows (ntpath.join)
	is not	well documented
In-Reply-To: <1342903268.21.0.193498975528.issue15414@psf.upfronthosting.co.za>
Message-ID: <1412971993.37.0.88051358931.issue15414@psf.upfronthosting.co.za>


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


----------
title: os.path.join behavior on Windows (ntpath.join) is unexpected and not well documented -> os.path.join behavior on Windows (ntpath.join) is not well documented

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

From report at bugs.python.org  Fri Oct 10 22:21:53 2014
From: report at bugs.python.org (=?utf-8?q?Francisco_Fern=C3=A1ndez_Casta=C3=B1o?=)
Date: Fri, 10 Oct 2014 20:21:53 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <1412972513.51.0.00946516989746.issue22603@psf.upfronthosting.co.za>


Francisco Fern?ndez Casta?o added the comment:

Under Fern?ndez it's ok.

----------

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

From report at bugs.python.org  Fri Oct 10 22:24:53 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 10 Oct 2014 20:24:53 +0000
Subject: [docs] [issue15414] os.path.join behavior on Windows (ntpath.join)
	is not	well documented
In-Reply-To: <1342903268.21.0.193498975528.issue15414@psf.upfronthosting.co.za>
Message-ID: <1412972693.2.0.383114705168.issue15414@psf.upfronthosting.co.za>


R. David Murray added the comment:

I'd say it was definitely an improvement in terms of comprehensibility.

----------

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

From report at bugs.python.org  Fri Oct 10 22:54:20 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Oct 2014 20:54:20 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <20141010205416.19948.37101@psf.io>


Roundup Robot added the comment:

New changeset 50bedeffec2f by Terry Jan Reedy in branch '3.4':
Issue 22603: add Francisco Fern?ndez Casta?o to ACKS.
https://hg.python.org/cpython/rev/50bedeffec2f

----------

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

From report at bugs.python.org  Fri Oct 10 22:55:03 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 10 Oct 2014 20:55:03 +0000
Subject: [docs] [issue22603] Fix a typo in the contextlib docs
In-Reply-To: <1412950855.37.0.697609134038.issue22603@psf.upfronthosting.co.za>
Message-ID: <1412974503.43.0.287869263151.issue22603@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 10 23:06:24 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Oct 2014 21:06:24 +0000
Subject: [docs] [issue15414] os.path.join behavior on Windows (ntpath.join)
	is not	well documented
In-Reply-To: <1342903268.21.0.193498975528.issue15414@psf.upfronthosting.co.za>
Message-ID: <20141010210615.58877.64719@psf.io>


Roundup Robot added the comment:

New changeset 05274a517b37 by Zachary Ware in branch '2.7':
Issue #15414: Clean and correct the os.path.join docs.
https://hg.python.org/cpython/rev/05274a517b37

New changeset c9c6082d4f9b by Zachary Ware in branch '3.4':
Issue #15414: Clean and correct the os.path.join docs.
https://hg.python.org/cpython/rev/c9c6082d4f9b

New changeset e57f93c681a6 by Zachary Ware in branch 'default':
Closes #15414: Merge with 3.4
https://hg.python.org/cpython/rev/e57f93c681a6

----------
nosy: +python-dev
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Oct 10 23:10:01 2014
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 10 Oct 2014 21:10:01 +0000
Subject: [docs] [issue15414] os.path.join behavior on Windows (ntpath.join)
	is not	well documented
In-Reply-To: <1342903268.21.0.193498975528.issue15414@psf.upfronthosting.co.za>
Message-ID: <1412975400.93.0.931396504123.issue15414@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Committed, with better line wrapping.

Thank you Dave Sawyer for the initial patch, and RDM for the review.

----------

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

From report at bugs.python.org  Sat Oct 11 01:51:14 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 10 Oct 2014 23:51:14 +0000
Subject: [docs] [issue16728] Missing cross-reference in sequence glossary
	entry
In-Reply-To: <1355919289.81.0.186820029813.issue16728@psf.upfronthosting.co.za>
Message-ID: <1412985074.56.0.811686699493.issue16728@psf.upfronthosting.co.za>


R. David Murray added the comment:

Looks like this was left open for post-commit review, but since no one has objected (and it looks fine to me) I'm going to close it.

----------
nosy: +r.david.murray
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Oct 11 10:02:00 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 11 Oct 2014 08:02:00 +0000
Subject: [docs] [issue22001] containers "same" does not always mean "__eq__".
In-Reply-To: <1405625961.78.0.30088981548.issue22001@psf.upfronthosting.co.za>
Message-ID: <1413014520.88.0.755655422388.issue22001@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> Ah... "be the same object or compare equal" sounds much better.

Yes, the plain language is clear and reads nicely.

> We can't say "will normally", since we don't know about 
> the infinite  number of possible container types that people 
> might create. The most we can say is that *builtin* container 
> types will [assuming that this is  the intent] or that general 
> containers *may*.

"general containers may" is most accurate.  

> Several suggested changes:

Jim, can you propose a much more minimal edit?

As you pointed-out, the underlying logic is "containers are permitted to (and generally do) read "same as" as "is or __eq__".   I don't think we should say much more than that in the section on expressions.

Any notes on NaNs should probably be in a section talking about the float type.  The weirdness of NaNs is a feature of the NaNs, not a feature of the entire language.  We definitely don't want a NaN note added to the documentation of every container.

----------

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

From report at bugs.python.org  Sat Oct 11 12:26:52 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 11 Oct 2014 10:26:52 +0000
Subject: [docs] [issue21061] Is contextlib.redirect_stdout reentrant or not?
In-Reply-To: <1395740166.01.0.738234296915.issue21061@psf.upfronthosting.co.za>
Message-ID: <1413023212.63.0.846144254285.issue21061@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Here is a simple patch to correct the redirect_stdout documentation.

----------
keywords: +patch
nosy: +berker.peksag
stage:  -> patch review
Added file: http://bugs.python.org/file36877/issue21061.diff

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

From report at bugs.python.org  Sat Oct 11 14:39:31 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 11 Oct 2014 12:39:31 +0000
Subject: [docs] [issue15569] Doc doc: incorrect description of some roles
	as	format-only
In-Reply-To: <1344302647.18.0.307450045197.issue15569@psf.upfronthosting.co.za>
Message-ID: <20141011123924.39526.88859@psf.io>


Roundup Robot added the comment:

New changeset bef3ddfe5d09 by Georg Brandl in branch 'default':
Closes #15569: some roles do create more than formatting
https://hg.python.org/devguide/rev/bef3ddfe5d09

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Oct 11 14:39:36 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 11 Oct 2014 12:39:36 +0000
Subject: [docs] [issue15569] Doc doc: incorrect description of some roles
	as	format-only
In-Reply-To: <1344302647.18.0.307450045197.issue15569@psf.upfronthosting.co.za>
Message-ID: <1413031176.36.0.409540146123.issue15569@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks!

----------
nosy: +georg.brandl
resolution: fixed -> 
stage: resolved -> needs patch
status: closed -> open

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

From report at bugs.python.org  Sat Oct 11 14:47:23 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 11 Oct 2014 12:47:23 +0000
Subject: [docs] [issue18959] Create a "Superseded modules" section in
	standard	library ToC
In-Reply-To: <1378559362.61.0.726437189184.issue18959@psf.upfronthosting.co.za>
Message-ID: <1413031643.48.0.2574183007.issue18959@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks for the patch.

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

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

From report at bugs.python.org  Sat Oct 11 14:50:09 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 11 Oct 2014 12:50:09 +0000
Subject: [docs] [issue15569] Doc doc: incorrect description of some roles
	as	format-only
In-Reply-To: <1344302647.18.0.307450045197.issue15569@psf.upfronthosting.co.za>
Message-ID: <1413031809.77.0.0421465739197.issue15569@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 11 14:51:24 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 11 Oct 2014 12:51:24 +0000
Subject: [docs] [issue21189] Broken link to patch
In-Reply-To: <1397050976.2.0.0354182649484.issue21189@psf.upfronthosting.co.za>
Message-ID: <1413031884.38.0.843377295491.issue21189@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Ping?

----------

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

From report at bugs.python.org  Sat Oct 11 15:08:29 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 11 Oct 2014 13:08:29 +0000
Subject: [docs] [issue18959] Create a "Superseded modules" section in
	standard	library ToC
In-Reply-To: <1378559362.61.0.726437189184.issue18959@psf.upfronthosting.co.za>
Message-ID: <20141011130826.58891.48154@psf.io>


Roundup Robot added the comment:

New changeset 7276bc0b0318 by Georg Brandl in branch '3.4':
Closes #18959: move optparse and imp to new "superseded modules" chapter
https://hg.python.org/cpython/rev/7276bc0b0318

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Oct 11 15:08:29 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 11 Oct 2014 13:08:29 +0000
Subject: [docs] [issue21687] Py_SetPath: Path components separated by colons
In-Reply-To: <1402154292.52.0.48898043171.issue21687@psf.upfronthosting.co.za>
Message-ID: <20141011130826.58891.19767@psf.io>


Roundup Robot added the comment:

New changeset 2d150c01bf7e by Georg Brandl in branch '3.4':
Closes #21687: delimiter in Py_SetPath is platform dependent
https://hg.python.org/cpython/rev/2d150c01bf7e

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Oct 11 15:08:29 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 11 Oct 2014 13:08:29 +0000
Subject: [docs] [issue21675] Library - Introduction - paragraph 5 - wrong
	ordering
In-Reply-To: <1402025432.44.0.956815380297.issue21675@psf.upfronthosting.co.za>
Message-ID: <20141011130826.58891.92580@psf.io>


Roundup Robot added the comment:

New changeset 52b9d79f6bfa by Georg Brandl in branch '3.4':
Closes #21675: fix ordering of description in library intro
https://hg.python.org/cpython/rev/52b9d79f6bfa

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Oct 11 16:28:31 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 11 Oct 2014 14:28:31 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1413037711.14.0.816402936864.issue22594@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

+1

----------

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

From report at bugs.python.org  Sat Oct 11 16:38:19 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 11 Oct 2014 14:38:19 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1413038299.81.0.681912179161.issue22594@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 11 16:39:09 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 11 Oct 2014 14:39:09 +0000
Subject: [docs] [issue15569] Doc doc: incorrect description of some roles
	as	format-only
In-Reply-To: <1344302647.18.0.307450045197.issue15569@psf.upfronthosting.co.za>
Message-ID: <1413038349.59.0.237230691443.issue15569@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 11 19:11:07 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 11 Oct 2014 17:11:07 +0000
Subject: [docs] [issue21061] Is contextlib.redirect_stdout reentrant or not?
In-Reply-To: <1395740166.01.0.738234296915.issue21061@psf.upfronthosting.co.za>
Message-ID: <1413047467.26.0.92302312319.issue21061@psf.upfronthosting.co.za>


Changes by Raymond Hettinger <raymond.hettinger at gmail.com>:


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

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

From report at bugs.python.org  Sat Oct 11 19:20:47 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 11 Oct 2014 17:20:47 +0000
Subject: [docs] [issue21061] Is contextlib.redirect_stdout reentrant or not?
In-Reply-To: <1395740166.01.0.738234296915.issue21061@psf.upfronthosting.co.za>
Message-ID: <1413048047.86.0.652145710766.issue21061@psf.upfronthosting.co.za>


Changes by Raymond Hettinger <raymond.hettinger at gmail.com>:


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

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

From udiedric at cisco.com  Sat Oct 11 11:26:36 2014
From: udiedric at cisco.com (Ute Diedrichsen (udiedric))
Date: Sat, 11 Oct 2014 09:26:36 +0000
Subject: [docs] Chapter 3: Informal Introduction does not work
Message-ID: <D05EC3E4.2E4BA%udiedric@cisco.com>

Hi all,

This links seems not work properly:

https://docs.python.org/2/tutorial/introduction.html

Thanks!

Regards



Ute Diedrichsen

ENGINEER.NETWORK CONSULTING
Cisco Services
udiedric at cisco.com
Phone: +49 811 559 5521
Mobile: +49 151 12522815


Cisco Systems GmbH
85399 Hallbergmoos
Amtsgericht M?nchen, HRB 102605
Gesch?ftsf?hrer: Norbert Spinner, Iris Slaby

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141011/91265a5f/attachment-0001.html>

From jacko21 at aliceadsl.fr  Sat Oct 11 23:12:31 2014
From: jacko21 at aliceadsl.fr (Jacques)
Date: Sat, 11 Oct 2014 23:12:31 +0200
Subject: [docs] Python documentation : some points requiring attention
Message-ID: <54399D3F.5030503@aliceadsl.fr>


Hello,

First, I want to thank you for the useful and clear documentation of 
Python.

Beeing a fanatic reader of it, sometimes I encounter some mistake (or it 
seems to me it is such). If this could bring some help, you will find in 
the attached file a list of points requiring attention.

All the comments concern the official standard documentation of Python 
3.4.0.

With regards.

Jacques Ducasse
FRANCE

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PythonDocErreurs141010.pdf
Type: application/pdf
Size: 84795 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20141011/706d6106/attachment-0001.pdf>

From zachary.ware+pydocs at gmail.com  Sat Oct 11 23:52:12 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Sat, 11 Oct 2014 16:52:12 -0500
Subject: [docs] Chapter 3: Informal Introduction does not work
In-Reply-To: <D05EC3E4.2E4BA%udiedric@cisco.com>
References: <D05EC3E4.2E4BA%udiedric@cisco.com>
Message-ID: <CAKJDb-O-ao-BmbwR4h=sPP3svvKOoWLHE8Vsn7k91YuEJSq3mg@mail.gmail.com>

Hi,

On Sat, Oct 11, 2014 at 4:26 AM, Ute Diedrichsen (udiedric)
<udiedric at cisco.com> wrote:
> Hi all,
>
> This links seems not work properly:
>
> https://docs.python.org/2/tutorial/introduction.html

It's working fine for me, is it still not working for you?

Regards,
-- 
Zach

From report at bugs.python.org  Sun Oct 12 00:17:23 2014
From: report at bugs.python.org (Zachary Ware)
Date: Sat, 11 Oct 2014 22:17:23 +0000
Subject: [docs] [issue22613] Several minor doc issues
Message-ID: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>


New submission from Zachary Ware:

>From docs@:

"""
Hello,

First, I want to thank you for the useful and clear documentation of Python.

Beeing a fanatic reader of it, sometimes I encounter some mistake (or it seems to me it is such). If this could bring some help, you will find in the attached file a list of points requiring attention.

All the comments concern the official standard documentation of Python 3.4.0.

With regards.

Jacques Ducasse
"""

----------
assignee: docs at python
components: Documentation
files: PythonDocErreurs141010.pdf
keywords: easy
messages: 229104
nosy: docs at python, zach.ware
priority: normal
severity: normal
status: open
title: Several minor doc issues
type: enhancement
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file36883/PythonDocErreurs141010.pdf

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

From report at bugs.python.org  Sun Oct 12 00:17:48 2014
From: report at bugs.python.org (Zachary Ware)
Date: Sat, 11 Oct 2014 22:17:48 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <1413065868.47.0.406535227037.issue22613@psf.upfronthosting.co.za>


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


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

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

From zachary.ware+pydocs at gmail.com  Sun Oct 12 00:22:19 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Sat, 11 Oct 2014 17:22:19 -0500
Subject: [docs] Python documentation : some points requiring attention
In-Reply-To: <54399D3F.5030503@aliceadsl.fr>
References: <54399D3F.5030503@aliceadsl.fr>
Message-ID: <CAKJDb-Mnf-=bECWF33iLTHzqo2cMrpj3BYtD9HrTCOHhqCb=bw@mail.gmail.com>

Hi,

On Sat, Oct 11, 2014 at 4:12 PM, Jacques <jacko21 at aliceadsl.fr> wrote:
>
> Hello,
>
> First, I want to thank you for the useful and clear documentation of Python.
>
> Beeing a fanatic reader of it, sometimes I encounter some mistake (or it
> seems to me it is such). If this could bring some help, you will find in the
> attached file a list of points requiring attention.
>
> All the comments concern the official standard documentation of Python
> 3.4.0.

Thanks for the report!  I've created
https://bugs.python.org/issue22613 to keep track of it.

-- 
Zach

From report at bugs.python.org  Sun Oct 12 02:25:59 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 12 Oct 2014 00:25:59 +0000
Subject: [docs] [issue21061] Is contextlib.redirect_stdout reentrant or not?
In-Reply-To: <1395740166.01.0.738234296915.issue21061@psf.upfronthosting.co.za>
Message-ID: <20141012002552.50009.47291@psf.io>


Roundup Robot added the comment:

New changeset dafbd78ac15b by Nick Coghlan in branch '3.4':
Issue #21061: correctly note redirect_stdout is reentrant
https://hg.python.org/cpython/rev/dafbd78ac15b

New changeset 83540d7b7366 by Nick Coghlan in branch 'default':
Merge issue #21061 fix from 3.4
https://hg.python.org/cpython/rev/83540d7b7366

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

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

From report at bugs.python.org  Sun Oct 12 02:27:41 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 12 Oct 2014 00:27:41 +0000
Subject: [docs] [issue21061] Is contextlib.redirect_stdout reentrant or not?
In-Reply-To: <1395740166.01.0.738234296915.issue21061@psf.upfronthosting.co.za>
Message-ID: <1413073661.4.0.157301103767.issue21061@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Thanks folks - the outdated cross reference has been updated as Berker suggested.

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

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

From report at bugs.python.org  Sun Oct 12 03:55:07 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 12 Oct 2014 01:55:07 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <1413078907.71.0.555709822731.issue22613@psf.upfronthosting.co.za>


Berker Peksag added the comment:

> Repr.repr_TYPE()

This is already fixed in issue 14824.

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

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

From report at bugs.python.org  Sun Oct 12 04:11:08 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 12 Oct 2014 02:11:08 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <20141012021105.19964.97988@psf.io>


Roundup Robot added the comment:

New changeset 7659f06a3648 by Berker Peksag in branch '3.4':
Issue #22613: Fix reprlib.Repr subclass example on Python 3.
https://hg.python.org/cpython/rev/7659f06a3648

New changeset 7394e5f85284 by Berker Peksag in branch 'default':
Issue #22613: Fix reprlib.Repr subclass example on Python 3.
https://hg.python.org/cpython/rev/7394e5f85284

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

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

From report at bugs.python.org  Sun Oct 12 07:23:09 2014
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sun, 12 Oct 2014 05:23:09 +0000
Subject: [docs] [issue22571] Remove import * recommendations and examples in
	doc?
In-Reply-To: <1412627004.13.0.564055290321.issue22571@psf.upfronthosting.co.za>
Message-ID: <1413091389.06.0.439054519871.issue22571@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/issue22571>
_______________________________________

From report at bugs.python.org  Sun Oct 12 07:24:27 2014
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sun, 12 Oct 2014 05:24:27 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1413091467.1.0.324097084957.issue22594@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/issue22594>
_______________________________________

From report at bugs.python.org  Sun Oct 12 09:19:47 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 12 Oct 2014 07:19:47 +0000
Subject: [docs] [issue22571] Remove import * recommendations and examples in
	doc?
In-Reply-To: <1412627004.13.0.564055290321.issue22571@psf.upfronthosting.co.za>
Message-ID: <1413098387.26.0.301328025264.issue22571@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Many of these (such as collections, collections.abc, decimal, and itertools) use import * as part of the doctest setup and are not part of the generated page shown to users.

Also, I don't think you should be aggressive about removing the other example that are visible users.   The "import *" construct is part of the language and will be encountered occasionally.

For similar reasons, the decimal module was specifically designed for be easily usable with "import *" because of the numerous exceptions and rounding flags and constants.

There are also some examples such the one in cmd.rst that I put there on-purpose.  Changing it would distract from the focus of the example.

With respect to Tkinter (and other gui toolkits as well), I believe that "import *" is a standard or common practice, in part because there are so many widget names names and widget options.  Changing the example might make it more pep8-ish but would result in a good deal of clutter that isn't the normal practice.


>  Should we finish the job?  Or leave the issue to
> individual chapter authors?

I vote for leaving any changes to the chapter authors who are in a better position to know that they were trying to communicate or who were just setting up the doctests.   As discussed above some of the import * are there for a reason.

We really need to start thinking of PEP 8 as something we do to our own code rather than something that gets inflicted on other people's code.

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

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

From report at bugs.python.org  Sun Oct 12 16:14:26 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 12 Oct 2014 14:14:26 +0000
Subject: [docs] [issue22586] urljoin allow_fragments doesn't work
In-Reply-To: <1412870433.46.0.862767853703.issue22586@psf.upfronthosting.co.za>
Message-ID: <20141012141424.50011.92600@psf.io>


Roundup Robot added the comment:

New changeset 9eed2e7fa764 by Georg Brandl in branch '3.4':
Closes #22586: clarify meaning of allow_fragments in urlparse.
https://hg.python.org/cpython/rev/9eed2e7fa764

New changeset c2eda29a8ccb by Georg Brandl in branch '2.7':
Closes #22586: clarify meaning of allow_fragments in urlparse.
https://hg.python.org/cpython/rev/c2eda29a8ccb

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Oct 12 16:56:53 2014
From: report at bugs.python.org (R. David Murray)
Date: Sun, 12 Oct 2014 14:56:53 +0000
Subject: [docs] [issue22618] urllib.parse.parse_qsl different results
	after	urllib.parse.unquote
In-Reply-To: <1413122181.37.0.728502828464.issue22618@psf.upfronthosting.co.za>
Message-ID: <1413125813.26.0.000382242482925.issue22618@psf.upfronthosting.co.za>


R. David Murray added the comment:

Isn't it obvious that you have to parse before you unquote?  That's the purpose of quoting, after all.  I suppose that is one of those "beginner mind" things that is obvious only because I'm an experienced programmer...and that there are web servers that do it wrong. 

The docs could definitely use some improvement, since they don't mention that parse_qs automatically unquotes the values...it is implicit in the fact that urlencode with doseq=true is the inverse, and it encodes them, but it should be made explicit.

You also might want to take note of the 'keep_blank_values' attribute, which could also use a doc improvement (it isn't obvious from the text what 'blank values' are):

>>> parse_qs('a=1&b=2&b=1&a%3Donly_appears_after_unquote', keep_blank_values=True)
{'a': ['1'], 'b': ['2', '1'], 'a=only_appears_after_unquote': ['']}

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

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

From report at bugs.python.org  Sun Oct 12 16:59:44 2014
From: report at bugs.python.org (R. David Murray)
Date: Sun, 12 Oct 2014 14:59:44 +0000
Subject: [docs] [issue22618] urllib.parse.parse_qsl different results
	after	urllib.parse.unquote
In-Reply-To: <1413122181.37.0.728502828464.issue22618@psf.upfronthosting.co.za>
Message-ID: <1413125984.72.0.0743476460595.issue22618@psf.upfronthosting.co.za>


R. David Murray added the comment:

Eh, that "Isn't it obvious" comment was uncalled for.  Of course it isn't obvious, especially when the docs are unclear.

----------

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

From report at bugs.python.org  Sun Oct 12 17:29:56 2014
From: report at bugs.python.org (Alex Vaystikh)
Date: Sun, 12 Oct 2014 15:29:56 +0000
Subject: [docs] [issue22618] urllib.parse.parse_qsl different results
	after	urllib.parse.unquote
In-Reply-To: <1413122181.37.0.728502828464.issue22618@psf.upfronthosting.co.za>
Message-ID: <1413127796.55.0.677960129357.issue22618@psf.upfronthosting.co.za>


Alex Vaystikh added the comment:

It is much clearer after your insight:
- I wasn't aware that 'parse_qs' unquotes values. That's most helpful!
- I had no idea what 'keep_blank_values' were before your example, but now it couldn't be more obvious. I know that adding that example to docs would've helped me a lot! Maybe others?

Thank you for the help!

----------

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

From report at bugs.python.org  Mon Oct 13 05:07:46 2014
From: report at bugs.python.org (Martin Panter)
Date: Mon, 13 Oct 2014 03:07:46 +0000
Subject: [docs] [issue22001] containers "same" does not always mean "__eq__".
In-Reply-To: <1405625961.78.0.30088981548.issue22001@psf.upfronthosting.co.za>
Message-ID: <1413169666.4.0.932748908917.issue22001@psf.upfronthosting.co.za>


Martin Panter added the comment:

Issue 12067 has a large patch in progress that would conflict with the changes suggested here. However most of the concerns here may already be addressed there, if the patch ever goes ahead.

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

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

From report at bugs.python.org  Mon Oct 13 05:09:18 2014
From: report at bugs.python.org (Martin Panter)
Date: Mon, 13 Oct 2014 03:09:18 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413169758.61.0.26245852666.issue12067@psf.upfronthosting.co.za>


Martin Panter added the comment:

Maybe it would be wise to split this task up and commit the bits that don?t need any more work. I think the existing patch might already solve Issue 22001.

----------

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

From udiedric at cisco.com  Mon Oct 13 08:20:17 2014
From: udiedric at cisco.com (Ute Diedrichsen (udiedric))
Date: Mon, 13 Oct 2014 06:20:17 +0000
Subject: [docs] Chapter 3: Informal Introduction does not work
In-Reply-To: <CAKJDb-O-ao-BmbwR4h=sPP3svvKOoWLHE8Vsn7k91YuEJSq3mg@mail.gmail.com>
References: <D05EC3E4.2E4BA%udiedric@cisco.com>
 <CAKJDb-O-ao-BmbwR4h=sPP3svvKOoWLHE8Vsn7k91YuEJSq3mg@mail.gmail.com>
Message-ID: <D0613ACB.2E5A4%udiedric@cisco.com>

Hi Zach, 

Thanks for your reply.

#### with firefox ####
I can open 
https://docs.python.org/2/tutorial/
without any problems. I can open section 2 and section 4. But section 3
does not work.

### with Safari ####
Section 3 works fine.

Regards
Ute


Ute Diedrichsen

ENGINEER.NETWORK CONSULTING
Cisco Services
udiedric at cisco.com
Phone: +49 811 559 5521
Mobile: +49 151 12522815


Cisco Systems GmbH
85399 Hallbergmoos
Amtsgericht M?nchen, HRB 102605
Gesch?ftsf?hrer: Norbert Spinner, Iris Slaby

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html

This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is strictly prohibited. If you are not the intended recipient
(or authorized to receive for the recipient), please contact the sender by
reply email and delete all copies of this message.





On 10/11/14 11:52 PM, "Zachary Ware" <zachary.ware+pydocs at gmail.com> wrote:

>Hi,
>
>On Sat, Oct 11, 2014 at 4:26 AM, Ute Diedrichsen (udiedric)
><udiedric at cisco.com> wrote:
>> Hi all,
>>
>> This links seems not work properly:
>>
>> https://docs.python.org/2/tutorial/introduction.html
>
>It's working fine for me, is it still not working for you?
>
>Regards,
>-- 
>Zach


From zachary.ware+pydocs at gmail.com  Mon Oct 13 08:59:27 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Mon, 13 Oct 2014 01:59:27 -0500
Subject: [docs] Chapter 3: Informal Introduction does not work
In-Reply-To: <D0613ACB.2E5A4%udiedric@cisco.com>
References: <D05EC3E4.2E4BA%udiedric@cisco.com>
 <CAKJDb-O-ao-BmbwR4h=sPP3svvKOoWLHE8Vsn7k91YuEJSq3mg@mail.gmail.com>
 <D0613ACB.2E5A4%udiedric@cisco.com>
Message-ID: <CAKJDb-OihVbZM7uE1PDrFN8L2DETNquj4qmo-hPZe1zeandmhQ@mail.gmail.com>

Hi Ute,

On Mon, Oct 13, 2014 at 1:20 AM, Ute Diedrichsen (udiedric)
<udiedric at cisco.com> wrote:
> Hi Zach,
>
> Thanks for your reply.
>
> #### with firefox ####
> I can open
> https://docs.python.org/2/tutorial/
> without any problems. I can open section 2 and section 4. But section 3
> does not work.
>
> ### with Safari ####
> Section 3 works fine.

That is very strange; section 3 ("An Informal Introduction to Python")
works fine in Firefox for me.  I'm not sure what to suggest,
especially in the absence of error messages.  It might be a good idea
to make sure you don't have any addons causing issues (though I'm not
sure what kind of addon could cause an issue with that page).

Sorry I can't be of any more help,
-- 
Zach

From georg at python.org  Mon Oct 13 09:02:24 2014
From: georg at python.org (Georg Brandl)
Date: Mon, 13 Oct 2014 09:02:24 +0200
Subject: [docs] Chapter 3: Informal Introduction does not work
In-Reply-To: <D0613ACB.2E5A4%udiedric@cisco.com>
References: <D05EC3E4.2E4BA%udiedric@cisco.com>
 <CAKJDb-O-ao-BmbwR4h=sPP3svvKOoWLHE8Vsn7k91YuEJSq3mg@mail.gmail.com>
 <D0613ACB.2E5A4%udiedric@cisco.com>
Message-ID: <543B7900.6070001@python.org>

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

Hi,

this is strange.  Can you describe a bit more what the failure is?
Do you get a 404 error, or a corrupted page?

Since we don't see a problem from our ends, is it possible that you
are behind a proxy server that cached the page incorrectly and needs
a refresh, or some kind of content filter?

cheers,
Georg

On 10/13/2014 08:20 AM, Ute Diedrichsen (udiedric) wrote:
> Hi Zach,
> 
> Thanks for your reply.
> 
> #### with firefox #### I can open https://docs.python.org/2/tutorial/ 
> without any problems. I can open section 2 and section 4. But section 3 
> does not work.
> 
> ### with Safari #### Section 3 works fine.
> 
> Regards Ute

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlQ7eQAACgkQN9GcIYhpnLAPsACfVDG1CgyJTL5fN4+uFP5dkI1X
VnsAn3msl+D5AS5+wFqAcx+EBvesNsmx
=H/Gi
-----END PGP SIGNATURE-----

From report at bugs.python.org  Mon Oct 13 09:04:31 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 13 Oct 2014 07:04:31 +0000
Subject: [docs] [issue9311] os.access can return bogus values when run as
	superuser
In-Reply-To: <1279591357.64.0.139129514793.issue9311@psf.upfronthosting.co.za>
Message-ID: <1413183871.08.0.521794788541.issue9311@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Oct 13 09:41:47 2014
From: report at bugs.python.org (Andy Maier)
Date: Mon, 13 Oct 2014 07:41:47 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413186107.66.0.356207968302.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

@Guido:
Agree to all you said in your #msg226496.

There is additional information about comparison in:
- Tutorial (5.8. Comparing Sequences and Other Types),
- Library Reference (5.3. Comparisons),
- Language Reference (3.3.1. Basic customization)
that needs to be reviewed in light of this patch.

I'm just not sure I want to make this patch even larger as it is already, and tend to do that in a follow on issue and patch (unless directed otherwise).

Andy

----------

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

From report at bugs.python.org  Mon Oct 13 10:01:47 2014
From: report at bugs.python.org (Andy Maier)
Date: Mon, 13 Oct 2014 08:01:47 +0000
Subject: [docs] [issue22001] containers "same" does not always mean "__eq__".
In-Reply-To: <1405625961.78.0.30088981548.issue22001@psf.upfronthosting.co.za>
Message-ID: <1413187307.84.0.377842387934.issue22001@psf.upfronthosting.co.za>


Andy Maier added the comment:

I reviewed the issues discussed here and believe that the patch for #Issue 12067 adresses all of them (and yes, it is large, unfortunately).
It became large because I think that more needed to be fixed. May I suggest to review that patch.

Andy

----------
nosy: +andymaier

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

From report at bugs.python.org  Mon Oct 13 11:07:28 2014
From: report at bugs.python.org (Andy Maier)
Date: Mon, 13 Oct 2014 09:07:28 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413191245.93.0.124257369361.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

Uploading v10 of the patch, which addresses all review comments made on v9.

There is one open question back to Martin Panter about which different types of byte sequences can be compared in Py 3.4.

I also believe this patch addresses all of Issue 22001. Let me know if you find that that is not the case.

If we continue to scope this patch to only the comparison chapter of the language reference, then I think we are done (see msg229229 about other places that need review and possibly updates).

Please review the patch v10.

----------
Added file: http://bugs.python.org/file36896/issue12067-expressions-py34_v10.diff

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

From report at bugs.python.org  Mon Oct 13 13:46:17 2014
From: report at bugs.python.org (Andy Maier)
Date: Mon, 13 Oct 2014 11:46:17 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413200777.67.0.296409802617.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

Here is the delta between v9 and v10 of the patch, if people want to see just that.

----------
Added file: http://bugs.python.org/file36897/issue12067-expressions-py34_delta-v9-v10.diff

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

From report at bugs.python.org  Mon Oct 13 16:10:17 2014
From: report at bugs.python.org (Martin Panter)
Date: Mon, 13 Oct 2014 14:10:17 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413209417.8.0.10095945243.issue12067@psf.upfronthosting.co.za>


Martin Panter added the comment:

About the byte sequence comparisons, I wondered if it was misleading to say that a list(), tuple() or range() can only be compared to the same type, without mentioning that bytes() and bytearray() can be compared to each other.

BTW just noticed you say range() supports lexicographical ordering, which I think is incorrect.

----------

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

From andreas.r.maier at gmx.de  Mon Oct 13 11:09:12 2014
From: andreas.r.maier at gmx.de (andreas.r.maier at gmx.de)
Date: Mon, 13 Oct 2014 09:09:12 -0000
Subject: [docs] Doc: remove errors about mixed-type comparisons. (issue
	12067)
Message-ID: <20141013090912.24542.41335@psf.upfronthosting.co.za>


http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst
File Doc/reference/expressions.rst (right):

http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst#newcode1087
Doc/reference/expressions.rst:1087: The behavior of the default equality
comparison that instances with different
On 2014/08/27 07:56:54, vadmium wrote:
> Needs a comma between ?comparison, that?

Done.

http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst#newcode1096
Doc/reference/expressions.rst:1096: otherwise, :exc:`TypeError` is
raised:
> Everything is an instance of the built-in type ?object?, and ?subtypes
of each
> other? does not make much sense to me.

I plan to change that in the next version of the patch to "if they are
of the same type or one is a subtype of the other".
 
> I think the cases where TypeError is
> raised or not by default are already described above. Would it hurt to
just drop
> the second sentence?

Where do you see that it is stated above ? At the begin of the chapter,
it is stated that types do not need to be the same to be compared, which
is the general statement that is then refined by the sentence you
commented on, for built-in types. So I'd like to keep the second
sentence.

http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst#newcode1120
Doc/reference/expressions.rst:1120: Strings cannot directly be compared
with binary sequences, and vice versa!
> I think the "be" is misplaced in this sentence (it should be "cannot
be directly
> compared").
My german English ... sorry for that...

> Further, the "and" conjunction seemed so jarring to me I wasn't sure
it was even
> grammatical (though after further consideration I understand it now).
I'd
> suggest dropping the whole "vice versa" clause, since the ability to
be compared
> is symmetric (even if the comparisons themselves are not). It wouldn't
make
> sense to say that A can be compared to B if B cannot be compared to A.
I agree.
Just to explain myself: My original motivation was driven by the fact
that the rich comparison methods are all unsymmetrical (they are defined
on the left hand operand and turning the comparison expression around
invokes the other method if both have one, which might be implemented
inconsistently. Now, because strings and sequences are both built-in
types, we know what their implementations do, and so using a language
that is based on the theoretical capability that it could have been
different, is just adding complexity.

> And finally, the exclamation mark at the end is a bit overemphatic!!1!
:-)

> tldr, make this sentence: "Strings and binary sequences cannot be
directly
> compared."
Done.

http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst#newcode1149
Doc/reference/expressions.rst:1149: each other), have the same length,
and each pair of corresponding elements
> Again, ?subtypes of each other? does not make sense. Maybe just say
you cannot
> compare between lists, tuples, and ranges [and byte sequences and text
strings]
> this way. [I understand comparing the different kinds of byte
sequences is meant
> to work though.]
I had the sentence about subtypes only to cover the case of user-defined
collections derived from the built-in collections. However, because this
section is about the behavior of built-in collections, that scope should
be maintained consistently. And because all built-in collections inherit
directly from object, the case of subtypes between them does not exist.
I have removed the phrase "or subtypes of each other)".

One point still to clarify, though: Which different types of byte
sequences can be compared in Py 3.4?

http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst#newcode1156
Doc/reference/expressions.rst:1156: * Mappings (instances of
:class:`dict`) are compared lexicographically using
On 2014/08/27 07:56:54, vadmium wrote:
> Not sure ?lexicographical comparison? makes sense unless the items
have an
> order. Maybe the original wording was better?
The original text said "same (key, value) pairs" without pointing out
that that does not mean "same object", plus it did not point out that
reflexivity is enforced on both key and value. I'll come up with
something that addresses your comment and still clarifies that.

http://bugs.python.org/review/12067/diff/12409/Doc/reference/expressions.rst#newcode1216
Doc/reference/expressions.rst:1216: sequences and mappings, but not to
sets). See also the
> Perhaps drop ?mappings?; even OrderedDict does not do ordering
comparisons for
> me
Agreed, we explicitly state that 'dict' mappings do not support
ordering.

http://bugs.python.org/review/12067/

From andreas.r.maier at gmx.de  Mon Oct 13 11:17:23 2014
From: andreas.r.maier at gmx.de (andreas.r.maier at gmx.de)
Date: Mon, 13 Oct 2014 09:17:23 -0000
Subject: [docs] Doc: remove errors about mixed-type comparisons. (issue
	12067)
Message-ID: <20141013091723.24542.64075@psf.upfronthosting.co.za>


http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst
File Doc/reference/expressions.rst (right):

http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst#newcode1093
Doc/reference/expressions.rst:1093: otherwise, :exc:`TypeError` is
raised:
After thinking again about Martin Panter's comment to the previous patch
set, that the subtype statement here does not make much sense, I have
realized that the second sentence above really only covers the case of
numeric types (everything else is not a subtype of each other), and for
numeric types we are explicit about which of them can be compared.

So in the next round of updating the patch, I intend to remove the
second sentence in the paragraph above.

http://bugs.python.org/review/12067/

From andreas.r.maier at gmx.de  Mon Oct 13 11:19:43 2014
From: andreas.r.maier at gmx.de (andreas.r.maier at gmx.de)
Date: Mon, 13 Oct 2014 09:19:43 -0000
Subject: [docs] Doc: remove errors about mixed-type comparisons. (issue
	12067)
Message-ID: <20141013091943.24542.23550@psf.upfronthosting.co.za>


http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst
File Doc/reference/expressions.rst (right):

http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst#newcode1174
Doc/reference/expressions.rst:1174: 
Should we move the remainder of this section to 3.3.1. "Basic
customization" of the Language Reference?

http://bugs.python.org/review/12067/

From vadmium+py at gmail.com  Mon Oct 13 15:17:35 2014
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Mon, 13 Oct 2014 13:17:35 -0000
Subject: [docs] Doc: remove errors about mixed-type comparisons. (issue
	12067)
Message-ID: <20141013131735.24542.44144@psf.upfronthosting.co.za>


http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst
File Doc/reference/expressions.rst (right):

http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst#newcode1093
Doc/reference/expressions.rst:1093: otherwise, :exc:`TypeError` is
raised:
Fine by me. In the previous patch I was referring to two paragraphs up,
that already says ?A default order comparision . . . raises
:exc:`TypeError` ?.

http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst#newcode1100
Doc/reference/expressions.rst:1100: also between different types (for
example, ``1 == 1.0`` is true).
This sounds like 1 and 1.0 were considered unequal before 3.2. Perhaps
you were trying to say that Decimal and Fraction couldn?t be compared
with other types before 3.2?

http://bugs.python.org/review/12067/diff/13054/Doc/reference/expressions.rst#newcode1174
Doc/reference/expressions.rst:1174: 
Not sure. It might also be useful to people using the operators without
implementing them.

http://bugs.python.org/review/12067/

From report at bugs.python.org  Mon Oct 13 18:32:51 2014
From: report at bugs.python.org (anupama srinivas murthy)
Date: Mon, 13 Oct 2014 16:32:51 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1413217970.96.0.239836292861.issue22594@psf.upfronthosting.co.za>


anupama srinivas murthy added the comment:

I have added the link and attached the patch below. Could you review it?

Thank you

----------
components:  -Regular Expressions
keywords: +patch
nosy: +anupama.srinivas.murthy
Added file: http://bugs.python.org/file36900/regex-link.patch

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

From report at bugs.python.org  Mon Oct 13 18:44:30 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 13 Oct 2014 16:44:30 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1413218670.14.0.705739243185.issue22594@psf.upfronthosting.co.za>


Georg Brandl added the comment:

"currently more bugfree and intended to replace re"

The first part is spreading FUD if not explained in more detail.  The second is probably never going to happend :(

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

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

From jimjjewett at gmail.com  Mon Oct 13 21:25:44 2014
From: jimjjewett at gmail.com (jimjjewett at gmail.com)
Date: Mon, 13 Oct 2014 19:25:44 -0000
Subject: [docs] Doc: remove errors about mixed-type comparisons. (issue
	12067)
Message-ID: <20141013192544.16240.51477@psf.upfronthosting.co.za>

Despite my comments suggesting further improvements, I believe it would
be helpful to commit the test case changes relatively soon.  

Refactoring (or adding) test cases at the last minute is risky, but
documentation tweaks can be made at any time -- and more people are
confident about committing them.


https://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py
File Lib/test/test_compare.py (right):

https://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py#newcode100
Lib/test/test_compare.py:100: class Class_none(object):
Is there a reason that these all inherit directly from object, as
opposed to ProxyCompare or something that takes care of the __init__,
and __str__ methods and documents the meth sequence?  I kept looking to
see what the differences were, and not finding any.

https://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py#newcode123
Lib/test/test_compare.py:123: def __eq__(self, other):
Do you need some way of verifying that *this* __eq__ was called, or is
that another set of tests?

https://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py#newcode297
Lib/test/test_compare.py:297: return False
I would like to see this simplified to do fewer isinstance checks, but
I'm not sure I should trust my intuition.

At the moment, I would do something like:

    isa1=isinstance(i1, t)
    isa2=isinstance(i2, t)
    if isa1 and isa2: ... # will do a return
    if isa1 or isa2:  return False

https://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py#newcode325
Lib/test/test_compare.py:325: test quality; the tests do not have a
functional dependency on that.
Why not?  It does seem like something that should be explicitly tested.

Or do you just mean that that not all tests do that?  If so, adding the
word "some" up above might help.

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

From report at bugs.python.org  Mon Oct 13 21:53:44 2014
From: report at bugs.python.org (Alex Gaynor)
Date: Mon, 13 Oct 2014 19:53:44 +0000
Subject: [docs] [issue22626] Documentation should point people to bugs. over
	HTTPS
Message-ID: <1413230024.39.0.966950626463.issue22626@psf.upfronthosting.co.za>


New submission from Alex Gaynor:

Very simple patch.

----------
assignee: docs at python
components: Documentation
files: https.diff
keywords: patch
messages: 229266
nosy: alex, docs at python
priority: normal
severity: normal
status: open
title: Documentation should point people to bugs. over HTTPS
versions: Python 3.5
Added file: http://bugs.python.org/file36903/https.diff

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

From report at bugs.python.org  Mon Oct 13 21:55:38 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 13 Oct 2014 19:55:38 +0000
Subject: [docs] [issue22626] Documentation should point people to bugs. over
	HTTPS
In-Reply-To: <1413230024.39.0.966950626463.issue22626@psf.upfronthosting.co.za>
Message-ID: <20141013195534.16336.95605@psf.io>


Roundup Robot added the comment:

New changeset b3bd4a65b45b by Alex Gaynor in branch 'default':
issue22626: Use https:// for a link to the bug tracker
https://hg.python.org/cpython/rev/b3bd4a65b45b

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

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

From report at bugs.python.org  Mon Oct 13 21:55:51 2014
From: report at bugs.python.org (Alex Gaynor)
Date: Mon, 13 Oct 2014 19:55:51 +0000
Subject: [docs] [issue22626] Documentation should point people to bugs. over
	HTTPS
In-Reply-To: <1413230024.39.0.966950626463.issue22626@psf.upfronthosting.co.za>
Message-ID: <1413230151.19.0.474448089321.issue22626@psf.upfronthosting.co.za>


Changes by Alex Gaynor <alex.gaynor at gmail.com>:


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

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

From report at bugs.python.org  Mon Oct 13 22:34:15 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 13 Oct 2014 20:34:15 +0000
Subject: [docs] [issue22626] Documentation should point people to bugs. over
	HTTPS
In-Reply-To: <1413230024.39.0.966950626463.issue22626@psf.upfronthosting.co.za>
Message-ID: <20141013203410.16324.60105@psf.io>


Roundup Robot added the comment:

New changeset 552f2d558e78 by Alex Gaynor in branch '3.4':
issue22626: Use https:// for a link to the bug tracker
https://hg.python.org/cpython/rev/552f2d558e78

----------

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

From report at bugs.python.org  Mon Oct 13 22:36:01 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 13 Oct 2014 20:36:01 +0000
Subject: [docs] [issue22626] Documentation should point people to bugs. over
	HTTPS
In-Reply-To: <1413230024.39.0.966950626463.issue22626@psf.upfronthosting.co.za>
Message-ID: <20141013203545.115605.89291@psf.io>


Roundup Robot added the comment:

New changeset 7bb901d68be0 by Alex Gaynor in branch '2.7':
issue22626: Use https:// for a link to the bug tracker
https://hg.python.org/cpython/rev/7bb901d68be0

----------

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

From report at bugs.python.org  Mon Oct 13 23:33:36 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 13 Oct 2014 21:33:36 +0000
Subject: [docs] [issue22626] Documentation should point people to bugs. over
	HTTPS
In-Reply-To: <1413230024.39.0.966950626463.issue22626@psf.upfronthosting.co.za>
Message-ID: <1413236016.17.0.723006166104.issue22626@psf.upfronthosting.co.za>


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


----------
stage:  -> resolved
type:  -> enhancement

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

From report at bugs.python.org  Tue Oct 14 11:05:54 2014
From: report at bugs.python.org (Ben Mather)
Date: Tue, 14 Oct 2014 09:05:54 +0000
Subject: [docs] [issue22630]
	`concurrent.futures.Future.set_running_or_notify_cancel`	does
	not notify cancel
Message-ID: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za>


New submission from Ben Mather:

The documentation for the `set_running_or_notify_cancel` method on `concurrent.futures.Future` states that it will notify waiting threads and trigger callbacks after the `Future` has been cancelled, however currently this is done immediately by the call to `cancel`.

Oddly waiters (private interface used to implement `wait` and `as_completed`) do follow the behaviour documented for callbacks (they are called in `set_running_or_notify_cancel`) which means that they are not equivalent to setting a callback on each future.


I have attached three possible patches:
 1) "change-callbacks.patch" - this changes the behaviour to match the documentation.
 2) "change-docs.patch" - this fixes the documentation to match the current behaviour.
 3) "change-docs-and-waiters.patch" - in addition to fixing the documentation, this also fixes the inconsistency between waiters and callbacks by invoking waiters' `add_cancelled` method in `cancel`.

I believe moving to the documented behaviour (1) would be a mistake as currently `set_running_or_notify_cancel` and the `RUNNING` state can be skipped entirely allowing Futures to be used just as a way to send results.

Should mention that I have a separate patch (which I will submit separately (or here?)) that re-implements `wait` and `as_completed` using only publicly exposed methods.  This makes it possible to extend or replace `Future` without having to preserve its private interface.  Unfortunately this slightly breaks compatibility due to the difference between waiters and callbacks.  I thought it would be best to discuss this issue first as I don't believe the current behaviour is as intended.

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: change-callbacks.patch
keywords: patch
messages: 229282
nosy: bwhmather, docs at python
priority: normal
severity: normal
status: open
title: `concurrent.futures.Future.set_running_or_notify_cancel` does not notify cancel
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file36908/change-callbacks.patch

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

From report at bugs.python.org  Tue Oct 14 11:06:31 2014
From: report at bugs.python.org (Ben Mather)
Date: Tue, 14 Oct 2014 09:06:31 +0000
Subject: [docs] [issue22630]
	`concurrent.futures.Future.set_running_or_notify_cancel`	does
	not notify cancel
In-Reply-To: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za>
Message-ID: <1413277591.82.0.243640067947.issue22630@psf.upfronthosting.co.za>


Changes by Ben Mather <bwhmather at bwhmather.com>:


Added file: http://bugs.python.org/file36909/change-docs.patch

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

From report at bugs.python.org  Tue Oct 14 11:07:07 2014
From: report at bugs.python.org (Ben Mather)
Date: Tue, 14 Oct 2014 09:07:07 +0000
Subject: [docs] [issue22630]
	`concurrent.futures.Future.set_running_or_notify_cancel`	does
	not notify cancel
In-Reply-To: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za>
Message-ID: <1413277627.7.0.965983832731.issue22630@psf.upfronthosting.co.za>


Changes by Ben Mather <bwhmather at bwhmather.com>:


Added file: http://bugs.python.org/file36910/change-docs-and-waiters.patch

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

From report at bugs.python.org  Tue Oct 14 16:38:34 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 14:38:34 +0000
Subject: [docs] [issue12965] longobject: documentation improvements
In-Reply-To: <1315846670.45.0.93309834122.issue12965@psf.upfronthosting.co.za>
Message-ID: <1413297514.09.0.227956415439.issue12965@psf.upfronthosting.co.za>


Stefan Krah added the comment:

This seems like too much trouble for 2.7. Closing, since I was the
one who opened the issue (just reopen if you think it is still worth
it).

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

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

From report at bugs.python.org  Tue Oct 14 17:00:50 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 15:00:50 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1413298850.26.0.95091807247.issue13124@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 17:12:57 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 15:12:57 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413299577.72.0.297997505472.issue13918@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 17:20:01 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 15:20:01 +0000
Subject: [docs] [issue21227] Decimal class error messages for integer
	division aren't	good
In-Reply-To: <1397520159.39.0.440264883295.issue21227@psf.upfronthosting.co.za>
Message-ID: <1413300001.14.0.917032195487.issue21227@psf.upfronthosting.co.za>


Stefan Krah added the comment:

I guess there's not much to be done here.

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

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

From report at bugs.python.org  Tue Oct 14 17:22:04 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 15:22:04 +0000
Subject: [docs] [issue22581] Other mentions of the buffer protocol
In-Reply-To: <1412785100.97.0.773176507587.issue22581@psf.upfronthosting.co.za>
Message-ID: <1413300124.96.0.139853413845.issue22581@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 17:45:55 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 15:45:55 +0000
Subject: [docs] [issue15849] PEP 3121, 384 Refactoring applied to xx module
In-Reply-To: <1346596353.57.0.974507844943.issue15849@psf.upfronthosting.co.za>
Message-ID: <1413301555.75.0.704259464342.issue15849@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 18:13:29 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 16:13:29 +0000
Subject: [docs] [issue18841] math.isfinite fails with Decimal sNAN
In-Reply-To: <1377531520.63.0.106544243675.issue18841@psf.upfronthosting.co.za>
Message-ID: <1413303209.38.0.75505877703.issue18841@psf.upfronthosting.co.za>


Stefan Krah added the comment:

"Wont fix" sounds good to me.

----------

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

From report at bugs.python.org  Tue Oct 14 18:21:09 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 16:21:09 +0000
Subject: [docs] [issue19412] Add docs for test.support.requires_docstrings
	decorator
In-Reply-To: <1382809267.31.0.380635405032.issue19412@psf.upfronthosting.co.za>
Message-ID: <1413303669.29.0.586451907913.issue19412@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 18:37:06 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 16:37:06 +0000
Subject: [docs] [issue21510] fma documentation should provide better example.
In-Reply-To: <1400131145.93.0.338142878224.issue21510@psf.upfronthosting.co.za>
Message-ID: <1413304626.07.0.396791651264.issue21510@psf.upfronthosting.co.za>


Stefan Krah added the comment:

I have no strong opinion, except that the docs appear clear:

"Return self*other+third with no rounding of the intermediate product self*other."

----------

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

From report at bugs.python.org  Tue Oct 14 18:48:33 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 14 Oct 2014 16:48:33 +0000
Subject: [docs] [issue21510] fma documentation should provide better example.
In-Reply-To: <1400131145.93.0.338142878224.issue21510@psf.upfronthosting.co.za>
Message-ID: <1413305313.4.0.782918563586.issue21510@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Just for the record, I think that an example also helps educate a non-expert reader (such as me ;-)) about the rounding problem.

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

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

From report at bugs.python.org  Tue Oct 14 19:01:02 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 17:01:02 +0000
Subject: [docs] [issue21929] Rounding properly
In-Reply-To: <1404729306.28.0.45044219182.issue21929@psf.upfronthosting.co.za>
Message-ID: <1413306062.41.0.83556649695.issue21929@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 19:04:05 2014
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 Oct 2014 17:04:05 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1413306245.1.0.582877550543.issue22237@psf.upfronthosting.co.za>


St?phane Wirtel added the comment:

For this issue, I have read the source code of "sorted" and "list.sort" to be sure they use the same algorithm (not sure). But in the builtin_sorted function, I read PyId_sort, but when I grep the code, I don't find it. Where can I find the reference of this function?

Thank you.

----------
nosy: +matrixise

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

From report at bugs.python.org  Tue Oct 14 19:58:02 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 14 Oct 2014 17:58:02 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1295653779.62.0.836506069174.issue10977@psf.upfronthosting.co.za>
Message-ID: <1413309482.51.0.912525051727.issue10977@psf.upfronthosting.co.za>


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


----------
nosy:  -skrah

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

From report at bugs.python.org  Tue Oct 14 20:16:13 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 14 Oct 2014 18:16:13 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1413310573.16.0.551126321604.issue22237@psf.upfronthosting.co.za>


Georg Brandl added the comment:

PyId_sort is not a function, it's a somewhat complicated way of getting a Python string "sort" (in this case, for looking up a method using PyObject_GetAttrId).  The string object is cached, with is faster than constructing one every time with PyObject_GetAttrString.

----------

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

From report at bugs.python.org  Tue Oct 14 20:17:16 2014
From: report at bugs.python.org (Andy Maier)
Date: Tue, 14 Oct 2014 18:17:16 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413310633.16.0.870328726631.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

I have addressed the comments by Jim Jewett, Martin Panter and of myself in a new version v11, which got posted.

For the expression.rst doc file, this version of the patch has its diff sections in a logical order, so that the original text and the patched text are close by each other.

Please review.

----------
Added file: http://bugs.python.org/file36920/issue12067-expressions-py34_v11.diff

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

From report at bugs.python.org  Tue Oct 14 20:27:43 2014
From: report at bugs.python.org (Andy Maier)
Date: Tue, 14 Oct 2014 18:27:43 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413311263.33.0.881982263856.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

I also made sure in both files that the line length of any changed or new lines is max 80. Sorry if that creates extra changes when looking at deltas between change sets.

----------

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

From report at bugs.python.org  Tue Oct 14 20:28:52 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 14 Oct 2014 18:28:52 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
Message-ID: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

WWW address (http://www.python.org/idle/) mentioned in "About IDLE" dialog window is no longer valid.

----------
assignee: docs at python
components: Documentation, IDLE
messages: 229329
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, kbk, roger.serwy, serhiy.storchaka, terry.reedy
priority: normal
severity: normal
status: open
title: Official IDLE web page address is not valid
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue Oct 14 20:59:35 2014
From: report at bugs.python.org (Ned Deily)
Date: Tue, 14 Oct 2014 18:59:35 +0000
Subject: [docs] [issue22630]
	`concurrent.futures.Future.set_running_or_notify_cancel`	does
	not notify cancel
In-Reply-To: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za>
Message-ID: <1413313175.72.0.771645670791.issue22630@psf.upfronthosting.co.za>


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


----------
nosy: +bquinlan

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

From report at bugs.python.org  Tue Oct 14 21:18:00 2014
From: report at bugs.python.org (Ned Deily)
Date: Tue, 14 Oct 2014 19:18:00 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413314280.47.0.993722098511.issue22632@psf.upfronthosting.co.za>


Ned Deily added the comment:

For the record, on the legacy web site, that URI (which you can still see as http://legacy.python.org/idle/) redirected to the Python 2 IDLE page in the Standard Library docs:  https://docs.python.org/2/library/idle.html.

----------
nosy: +ned.deily

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

From report at bugs.python.org  Tue Oct 14 21:19:26 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 14 Oct 2014 19:19:26 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413314366.48.0.478608410667.issue22632@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I guess a redirect could be added again.

----------
nosy: +benjamin.peterson

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

From report at bugs.python.org  Tue Oct 14 21:22:18 2014
From: report at bugs.python.org (Ned Deily)
Date: Tue, 14 Oct 2014 19:22:18 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413314538.53.0.774921308331.issue22632@psf.upfronthosting.co.za>


Ned Deily added the comment:

It could but to which page, e.g. which version of the docs?

----------

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

From report at bugs.python.org  Tue Oct 14 21:22:39 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 14 Oct 2014 19:22:39 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413314366.48.0.478608410667.issue22632@psf.upfronthosting.co.za>
Message-ID: <4504156.TugVfcEz9r@raxxla>


Serhiy Storchaka added the comment:

Should we add /idle3/ redirection for 3.x?

----------

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

From report at bugs.python.org  Tue Oct 14 21:29:00 2014
From: report at bugs.python.org (Ned Deily)
Date: Tue, 14 Oct 2014 19:29:00 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413314940.16.0.765539419853.issue22632@psf.upfronthosting.co.za>


Ned Deily added the comment:

The URI in "About IDLE" is redundant in that the same information on the doc page is also available in text format in the IDLE Help menu and there is also a link there to the full HTML docs.  Perhaps the URI should just be removed from About IDLE going forward; we could still add a redirect for the benefit of IDLEs already released.

----------

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

From report at bugs.python.org  Tue Oct 14 21:29:45 2014
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 14 Oct 2014 19:29:45 +0000
Subject: [docs] [issue21189] Broken link to patch
In-Reply-To: <1397050976.2.0.0354182649484.issue21189@psf.upfronthosting.co.za>
Message-ID: <1413314985.3.0.776635422094.issue21189@psf.upfronthosting.co.za>


Barry A. Warsaw added the comment:

I changed the link to point here: https://docs.python.org/devguide/patch.html

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

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

From report at bugs.python.org  Tue Oct 14 22:51:23 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 14 Oct 2014 20:51:23 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413319883.16.0.675931611454.issue22632@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Idle's Help system needs a thorough review.  Current issues include 
16893, 21995, 17583, and a few more in my head, including revising About.

In the meanwhile, I am replacing the dead link with 
'https://docs.python.org/' + sys.version[:3] + '/library/idle.html'
(It cannot be copied to be pasted; making it clickable would be part of revising About.)

I suggest redirecting the current dead link http://www.python.org/idle/ to https://docs.python.org/3/library/idle.html.  People can always select a different version from there.

----------

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

From report at bugs.python.org  Tue Oct 14 22:54:32 2014
From: report at bugs.python.org (Ned Deily)
Date: Tue, 14 Oct 2014 20:54:32 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413320072.59.0.972894038951.issue22632@psf.upfronthosting.co.za>


Ned Deily added the comment:

OK, the redirect should now be in place.

----------

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

From report at bugs.python.org  Tue Oct 14 22:57:30 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 14 Oct 2014 20:57:30 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <20141014205727.1825.40534@psf.io>


Roundup Robot added the comment:

New changeset d411dff4e3d4 by Terry Jan Reedy in branch '2.7':
Issue #22632: replace dead link with version-specific doc link.
https://hg.python.org/cpython/rev/d411dff4e3d4

New changeset db5e431125b1 by Terry Jan Reedy in branch '3.4':
Issue #22632: replace dead link with version-specific doc link.
https://hg.python.org/cpython/rev/db5e431125b1

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

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

From report at bugs.python.org  Tue Oct 14 22:59:44 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 14 Oct 2014 20:59:44 +0000
Subject: [docs] [issue22632] Official IDLE web page address is not valid
In-Reply-To: <1413311332.96.0.42616641652.issue22632@psf.upfronthosting.co.za>
Message-ID: <1413320384.62.0.341273091286.issue22632@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

verified

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

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

From report at bugs.python.org  Tue Oct 14 23:23:52 2014
From: report at bugs.python.org (R. David Murray)
Date: Tue, 14 Oct 2014 21:23:52 +0000
Subject: [docs] [issue22635] subprocess.getstatusoutput changed behavior in
	3.4	(maybe 3.3.4?)
In-Reply-To: <1413320958.05.0.462062330084.issue22635@psf.upfronthosting.co.za>
Message-ID: <1413321832.56.0.885166414962.issue22635@psf.upfronthosting.co.za>


R. David Murray added the comment:

You are right, it did change in 3.3.4 (see issue 10197).  That change should not have been applied to 3.3, and obviously there was a missing test concerning the return code format.

At this point I think we are stuck with changing the documentation.  The new return code is both more convenient and more consistent with the rest of the subprocess module.  It is very unfortunate that it did not follow our normal backward compatibility rules, but we are stuck with the mistake now.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, r.david.murray

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

From report at bugs.python.org  Tue Oct 14 23:31:45 2014
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 14 Oct 2014 21:31:45 +0000
Subject: [docs] [issue22635] subprocess.getstatusoutput changed behavior in
	3.4	(maybe 3.3.4?)
In-Reply-To: <1413320958.05.0.462062330084.issue22635@psf.upfronthosting.co.za>
Message-ID: <1413322305.72.0.501359540324.issue22635@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> You are right, it did change in 3.3.4 (see issue 10197).  That change should not have been applied to 3.3, ...

The purpose of the issue #10197 was to fix a bug on Windows: getoutput() didn't work.

----------

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

From report at bugs.python.org  Tue Oct 14 23:34:02 2014
From: report at bugs.python.org (R. David Murray)
Date: Tue, 14 Oct 2014 21:34:02 +0000
Subject: [docs] [issue22635] subprocess.getstatusoutput changed behavior in
	3.4	(maybe 3.3.4?)
In-Reply-To: <1413320958.05.0.462062330084.issue22635@psf.upfronthosting.co.za>
Message-ID: <1413322442.95.0.483229530867.issue22635@psf.upfronthosting.co.za>


R. David Murray added the comment:

But it was also a feature addition: getoutput had not been *intended* to work on Windows.  I understand why the mistake was made (the argument that it was a bug has weight), but the fact that a versionchanged was needed mentioning 3.3.4 indicates it wasn't really a bug fix.

----------

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

From report at bugs.python.org  Wed Oct 15 01:36:11 2014
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Tue, 14 Oct 2014 23:36:11 +0000
Subject: [docs] [issue22635] subprocess.getstatusoutput changed behavior in
	3.4	(maybe 3.3.4?)
In-Reply-To: <1413320958.05.0.462062330084.issue22635@psf.upfronthosting.co.za>
Message-ID: <1413329771.74.0.347721821629.issue22635@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Wed Oct 15 03:58:18 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 15 Oct 2014 01:58:18 +0000
Subject: [docs] [issue20386] socket.SocketType enum overwrites import
	of	_socket.SocketType
In-Reply-To: <1390603701.84.0.039670998795.issue20386@psf.upfronthosting.co.za>
Message-ID: <20141015015814.107234.20280@psf.io>


Roundup Robot added the comment:

New changeset 613c30ffd344 by Ethan Furman in branch '3.4':
Issue20386: SocketType is again socket.socket; the IntEnum SOCK constants are SocketKind
https://hg.python.org/cpython/rev/613c30ffd344

New changeset ef24851f340f by Ethan Furman in branch 'default':
Issue20386: SocketType is again socket.socket; the IntEnum SOCK constants are SocketKind
https://hg.python.org/cpython/rev/ef24851f340f

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

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

From report at bugs.python.org  Wed Oct 15 04:02:05 2014
From: report at bugs.python.org (Ethan Furman)
Date: Wed, 15 Oct 2014 02:02:05 +0000
Subject: [docs] [issue20386] socket.SocketType enum overwrites import
	of	_socket.SocketType
In-Reply-To: <1390603701.84.0.039670998795.issue20386@psf.upfronthosting.co.za>
Message-ID: <1413338525.74.0.241875050775.issue20386@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Oct 15 10:38:26 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 15 Oct 2014 08:38:26 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1413362306.77.0.971452150785.issue22237@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

> when I grep the code, I don't find it

The non-greppability is due to preprocessor evil. The culprit is this macro from Include/object.h:

  #define _Py_IDENTIFIER(varname) _Py_static_string(PyId_##varname, #varname)

along with the declaration

  _Py_IDENTIFIER(sort);

earlier in bltinmodule.c.

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

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

From report at bugs.python.org  Wed Oct 15 10:42:00 2014
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 Oct 2014 08:42:00 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1413362306.77.0.971452150785.issue22237@psf.upfronthosting.co.za>
Message-ID: <C32AFF1B-9E0D-46B3-8F52-9D12F4695DE9@wirtel.be>


St?phane Wirtel added the comment:

Hi Mark,

Without your explanation, I was really lost.

Thank you.

----------

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

From report at bugs.python.org  Wed Oct 15 10:56:15 2014
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 15 Oct 2014 08:56:15 +0000
Subject: [docs] [issue20386] socket.SocketType enum overwrites import
	of	_socket.SocketType
In-Reply-To: <1390603701.84.0.039670998795.issue20386@psf.upfronthosting.co.za>
Message-ID: <1413363375.24.0.229299542449.issue20386@psf.upfronthosting.co.za>


Berker Peksag added the comment:

+ self.assertTrue(socket.SocketType is _socket.socket)

You can use assertIs instead of assertTrue.

----------
nosy: +berker.peksag
versions: +Python 3.5

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

From report at bugs.python.org  Wed Oct 15 11:02:53 2014
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 Oct 2014 09:02:53 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1413363773.9.0.832373242521.issue22237@psf.upfronthosting.co.za>


St?phane Wirtel added the comment:

My patch for the documentation of Python 3.5, just need a small feedback.

If you agree with this patch, I will provide the same patch for 2.7 and 3.4

Thank you

----------
keywords: +patch
Added file: http://bugs.python.org/file36933/issue22237.patch

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

From report at bugs.python.org  Wed Oct 15 12:20:36 2014
From: report at bugs.python.org (koobs)
Date: Wed, 15 Oct 2014 10:20:36 +0000
Subject: [docs] [issue20386] socket.SocketType enum overwrites import
	of	_socket.SocketType
In-Reply-To: <1390603701.84.0.039670998795.issue20386@psf.upfronthosting.co.za>
Message-ID: <1413368434.5.0.70226522682.issue20386@psf.upfronthosting.co.za>


koobs added the comment:

This change looks to be implicated in a buildbot breakage on koobs-freebsd9 (3.4).

I couldn't reproduce the test failure by re-running the build, so possibly intermittent or non-deterministic.

Full build log attached.

I'll leave the issue closed for now, please re-open if verified.

======================================================================
ERROR: test_pickling (test.test_multiprocessing_fork.WithProcessesTestPicklingConnections)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.4.koobs-freebsd9/build/Lib/test/_test_multiprocessing.py", line 2590, in test_pickling
    self.assertEqual(new_conn.recv(), msg.upper())
  File "/usr/home/buildbot/python/3.4.koobs-freebsd9/build/Lib/multiprocessing/connection.py", line 250, in recv
    buf = self._recv_bytes()
  File "/usr/home/buildbot/python/3.4.koobs-freebsd9/build/Lib/multiprocessing/connection.py", line 416, in _recv_bytes
    buf = self._recv(4)
  File "/usr/home/buildbot/python/3.4.koobs-freebsd9/build/Lib/multiprocessing/connection.py", line 389, in _recv
    raise EOFError
EOFError

----------
nosy: +koobs
Added file: http://bugs.python.org/file36937/koobs-freebsd9-py34-build-553.txt

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

From report at bugs.python.org  Wed Oct 15 20:09:30 2014
From: report at bugs.python.org (panos black)
Date: Wed, 15 Oct 2014 18:09:30 +0000
Subject: [docs] [issue22646] Set SMTPHandler's "credentials"
	through	"logging.config.dictConfig".
Message-ID: <1413396570.86.0.25871256892.issue22646@psf.upfronthosting.co.za>


New submission from panos black:

If you configure logging using a JSON file, then, after you parse it and you pass it to logging.config.dictConfig(), you realize that when you define an SMTPHandler you can't set "credentials", or, more precisely, whether you set it or not the credentials value is ignored.

This happens because SMTPHandler's __init__ has the following code

        if isinstance(credentials, tuple):
            self.username, self.password = credentials
        else:
            self.username = None

while "credentials" inside dictConfig() is a "ConvertingList" and not a "tuple". As a result, username is set to None. 

I think that this is a problem because:

a) "credentials" is allowed to be specified in the configuration file (i.e. if you have an identifier that SMTPHandler's __init__, knows nothing about then you get an exception).
b) Other fields like, "timeout", and "toaddrs" work as expected (i.e. you can set them just fine)
c) This behaviour is not documented and you end up with improperly configured logging.

I guess that similar problems exist in other handlers too, but I haven't checked them one by one.

I think that it would make sense to be able to set all __init__ arguments in the Handlers section, or at least, if this is not desirable, to document this behaviour.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 229488
nosy: docs at python, panos.black, vinay.sajip
priority: normal
severity: normal
status: open
title: Set SMTPHandler's "credentials" through "logging.config.dictConfig".
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Wed Oct 15 23:52:25 2014
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 15 Oct 2014 21:52:25 +0000
Subject: [docs] [issue22646] Set SMTPHandler's "credentials"
	through	"logging.config.dictConfig".
In-Reply-To: <1413396570.86.0.25871256892.issue22646@psf.upfronthosting.co.za>
Message-ID: <1413409945.44.0.513186587312.issue22646@psf.upfronthosting.co.za>


Changes by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
assignee: docs at python -> vinay.sajip
versions:  -Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Oct 16 09:18:19 2014
From: report at bugs.python.org (Steve)
Date: Thu, 16 Oct 2014 07:18:19 +0000
Subject: [docs] [issue11176] give more meaningful argument names in
	argparse	documentation
In-Reply-To: <1297352937.46.0.470038569364.issue11176@psf.upfronthosting.co.za>
Message-ID: <1413443898.76.0.033412837006.issue11176@psf.upfronthosting.co.za>


Steve added the comment:

I came here to file a bug against the argparse documentation because reading through the documentation I didn't realize a good usecase for the `epilog` argument to the `ArgumentParser()` class until I started noticing that some commandline tools end with examples of usage.

I found this bug and so thought it would be better to just leave a comment here instead.

I glaced through the submitted patches and noticed that the pizza making example has `epilog="Remember: select a good combination to ensure maximum tastiness` ...which while good, still might not immediately convey the usefulness of the epilog parameter (just IMHO). I think, the example would be better served by something like:

>>> pizza_parser = argparse.ArgumentParser(
...     description='Make a pizza out of ingredients and toppings',
...     epilog="""Examples: Create a Python Lovers pizza using the command::
...     ./makepizz.py spam ham eggs
...     """)

Of course this example would then also require passing a formatter_class argument to handle the wrapping ...but in essence the point of my comment is that the examples might be more useful if a 'real-world' usage is demonstrated.

----------
nosy: +lonetwin

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

From report at bugs.python.org  Thu Oct 16 10:55:55 2014
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 16 Oct 2014 08:55:55 +0000
Subject: [docs] [issue22651] Python 2: Open file in a+ mode on Windows
	doesn't go to	the end
In-Reply-To: <1413446231.99.0.734842825619.issue22651@psf.upfronthosting.co.za>
Message-ID: <1413449755.52.0.171002053762.issue22651@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This is a somewhat unfortunate difference between the major C libs and Python's new IO, but probably too late to change.

What's left to do is to document the behavior properly.

----------
assignee:  -> docs at python
components: +Documentation -IO, Windows
nosy: +docs at python, georg.brandl

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

From report at bugs.python.org  Thu Oct 16 11:29:22 2014
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 16 Oct 2014 09:29:22 +0000
Subject: [docs] [issue22651] Python 2: Open file in a+ mode on Windows
	doesn't go to	the end
In-Reply-To: <1413446231.99.0.734842825619.issue22651@psf.upfronthosting.co.za>
Message-ID: <1413451762.78.0.437531284517.issue22651@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> This is a somewhat unfortunate difference between the major C libs and Python's new IO, but probably too late to change.

Well, it's easy to workaround it: just all file.seek(0, 2) after open() to always to the end ;-) (or file.seek(0) to always go the beginning).

----------

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

From report at bugs.python.org  Thu Oct 16 14:38:41 2014
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Thu, 16 Oct 2014 12:38:41 +0000
Subject: [docs] [issue22651] Python 2: Open file in a+ mode doesn't go to
	the end
In-Reply-To: <1413446231.99.0.734842825619.issue22651@psf.upfronthosting.co.za>
Message-ID: <1413463121.59.0.722515390438.issue22651@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever
title: Python 2: Open file in a+ mode on Windows doesn't go to the end -> Python 2: Open file in a+ mode doesn't go to the end
versions: +Python 2.7 -Python 3.4

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

From report at bugs.python.org  Thu Oct 16 14:53:09 2014
From: report at bugs.python.org (=?utf-8?b?0JLQsNGB0LjQu9C40Lkg0JzQsNC60LDRgNC+0LI=?=)
Date: Thu, 16 Oct 2014 12:53:09 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1413463989.47.0.564011689579.issue15204@psf.upfronthosting.co.za>


??????? ??????? added the comment:

open() documentation is probably broken a little now. Here is what one can see at the end of open() description:
"...
Deprecated since version 3.4, will be removed in version 4.0.

The 'U' mode."

Reader may assume open() function is what will be removed. Which is frightening :)

----------
nosy: +???????.???????

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

From report at bugs.python.org  Fri Oct 17 05:19:19 2014
From: report at bugs.python.org (eryksun)
Date: Fri, 17 Oct 2014 03:19:19 +0000
Subject: [docs] [issue22651] Open file in a+ mode reads from end of file in
	Python 3.4
In-Reply-To: <1413446231.99.0.734842825619.issue22651@psf.upfronthosting.co.za>
Message-ID: <1413515959.74.0.033015340901.issue22651@psf.upfronthosting.co.za>


Changes by eryksun <eryksun at gmail.com>:


----------
title: Python 2: Open file in a+ mode doesn't go to the end -> Open file in a+ mode reads from end of file in Python 3.4
versions: +Python 3.4, Python 3.5 -Python 2.7

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

From vadmium+py at gmail.com  Wed Oct 15 02:15:54 2014
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Wed, 15 Oct 2014 00:15:54 -0000
Subject: [docs] Doc: remove errors about mixed-type comparisons. (issue
	12067)
Message-ID: <20141015001554.13057.37285@psf.upfronthosting.co.za>

Patch v11 looks pretty good I think


http://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py
File Lib/test/test_compare.py (right):

http://bugs.python.org/review/12067/diff/13054/Lib/test/test_compare.py#newcode100
Lib/test/test_compare.py:100: class Class_none(object):
I guess Jim is suggesting to factor out your own base class, maybe like:

class ProxyCompare:
    def __init__(self, x=None): ...
    def __str__(self): ...
class Class_none(ProxyCompare):
    meth = ()
class Class_eq(ProxyCompare):
    meth = ("eq",)
    def __eq__(self, other): ...

http://bugs.python.org/review/12067/

From report at bugs.python.org  Fri Oct 17 09:52:39 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 17 Oct 2014 07:52:39 +0000
Subject: [docs] [issue22646] Set SMTPHandler's "credentials"
	through	"logging.config.dictConfig".
In-Reply-To: <1413396570.86.0.25871256892.issue22646@psf.upfronthosting.co.za>
Message-ID: <20141017075234.115078.51223@psf.io>


Roundup Robot added the comment:

New changeset 3ba23c6f7986 by Vinay Sajip in branch '2.7':
Issue #22646: Accept list as well as tuple to support initialisation via dictConfig().
https://hg.python.org/cpython/rev/3ba23c6f7986

New changeset d15708f13266 by Vinay Sajip in branch '3.4':
Issue #22646: Accept list as well as tuple to support initialisation via dictConfig().
https://hg.python.org/cpython/rev/d15708f13266

New changeset bcc3f167a30b by Vinay Sajip in branch 'default':
Closes #22646: Accept list as well as tuple to support initialisation via dictConfig().
https://hg.python.org/cpython/rev/bcc3f167a30b

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Oct 17 11:32:12 2014
From: report at bugs.python.org (=?utf-8?q?C=C3=A9dric_Krier?=)
Date: Fri, 17 Oct 2014 09:32:12 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413538332.5.0.646146954763.issue13918@psf.upfronthosting.co.za>


C?dric Krier added the comment:

So what about this patch?
It adds a delocalize method while keeping the atof func parameter for backward compatibility.

----------
Added file: http://bugs.python.org/file36955/delocalize.patch

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

From report at bugs.python.org  Fri Oct 17 15:37:52 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 17 Oct 2014 13:37:52 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413553072.12.0.501406770909.issue13918@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
assignee: docs at python -> 
components: +Library (Lib) -Documentation
stage:  -> patch review
versions: +Python 3.5 -Python 2.7, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Oct 17 15:38:34 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 17 Oct 2014 13:38:34 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413553114.52.0.901092754378.issue13918@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

The patch's approach looks reasonable to me.

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

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

From report at bugs.python.org  Fri Oct 17 16:54:54 2014
From: report at bugs.python.org (Douglas Naphas)
Date: Fri, 17 Oct 2014 14:54:54 +0000
Subject: [docs] [issue22657] Bad link to packages specification in language
	reference	2.x sec 6.12
Message-ID: <1413557694.48.0.952625223829.issue22657@psf.upfronthosting.co.za>


New submission from Douglas Naphas:

Section 6.12 of the Python 2.x language reference (https://docs.python.org/2/reference/simple_stmts.html#the-import-statement) has a link to "The original specification for packages" to http://www.python.org/doc/essays/packages.html, which is not found.

----------
assignee: docs at python
components: Documentation
messages: 229574
nosy: docs at python, douglasnaphas
priority: normal
severity: normal
status: open
title: Bad link to packages specification in language reference 2.x sec 6.12
versions: Python 2.7

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

From report at bugs.python.org  Fri Oct 17 17:07:46 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 17 Oct 2014 15:07:46 +0000
Subject: [docs] [issue22657] Bad link to packages specification in language
	reference	2.x sec 6.12
In-Reply-To: <1413557694.48.0.952625223829.issue22657@psf.upfronthosting.co.za>
Message-ID: <20141017150730.93088.3016@psf.io>


Roundup Robot added the comment:

New changeset dae99db70336 by Benjamin Peterson in branch '2.7':
remove link to the 'original package specification'; I doubt it's useful anymore (closes #22657)
https://hg.python.org/cpython/rev/dae99db70336

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Oct 17 18:16:35 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 17 Oct 2014 16:16:35 +0000
Subject: [docs] [issue22186] Typos in .py files
In-Reply-To: <1407862651.37.0.513368911737.issue22186@psf.upfronthosting.co.za>
Message-ID: <1413562595.89.0.0747654321585.issue22186@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag
stage:  -> commit review

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

From report at bugs.python.org  Fri Oct 17 18:46:30 2014
From: report at bugs.python.org (James Goodwin)
Date: Fri, 17 Oct 2014 16:46:30 +0000
Subject: [docs] [issue22658] IMAP4 Example lacking host information
Message-ID: <1413564390.73.0.387636698685.issue22658@psf.upfronthosting.co.za>


New submission from James Goodwin:

The IMAP4 Example for Python 3.4 (Section 21.15.2) does not show the appropriate host information for the example to work.  

Suggested fix would be to change the line "M = imaplib.IMAP4()" to "M = imaplib.IMAP4('localhost')"  This will bring the example inline with the poplib example (Section 21.14.2).

----------
assignee: docs at python
components: Documentation
messages: 229581
nosy: James.Goodwin, docs at python
priority: normal
severity: normal
status: open
title: IMAP4 Example lacking host information
versions: Python 3.4

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

From report at bugs.python.org  Fri Oct 17 18:50:10 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 17 Oct 2014 16:50:10 +0000
Subject: [docs] [issue22658] IMAP4 Example lacking host information
In-Reply-To: <1413564390.73.0.387636698685.issue22658@psf.upfronthosting.co.za>
Message-ID: <1413564610.51.0.933739137446.issue22658@psf.upfronthosting.co.za>


R. David Murray added the comment:

I think this is actually a bug, rather than a doc bug.  See issue 18540.  if you agree, we'll close this as a duplicate of that one.

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

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

From report at bugs.python.org  Fri Oct 17 19:01:15 2014
From: report at bugs.python.org (James Goodwin)
Date: Fri, 17 Oct 2014 17:01:15 +0000
Subject: [docs] [issue22658] IMAP4 Example lacking host information
In-Reply-To: <1413564390.73.0.387636698685.issue22658@psf.upfronthosting.co.za>
Message-ID: <1413565275.42.0.519405847226.issue22658@psf.upfronthosting.co.za>


James Goodwin added the comment:

I do see that.  I agree that this is a duplicate of that one.

----------

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

From report at bugs.python.org  Fri Oct 17 19:16:27 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 17 Oct 2014 17:16:27 +0000
Subject: [docs] [issue16802] fileno argument to socket.socket() undocumented
In-Reply-To: <1356711151.76.0.423836721045.issue16802@psf.upfronthosting.co.za>
Message-ID: <1413566187.02.0.739698065263.issue16802@psf.upfronthosting.co.za>


Berker Peksag added the comment:

The actual signature is now

    socket.socket(family=AF_INET, type=SOCK_STREAM, proto=0, fileno=None)

but, the fileno argument still needs to be documented.

----------
nosy: +berker.peksag
stage: needs patch -> patch review
versions: +Python 3.5 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Fri Oct 17 20:00:53 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 17 Oct 2014 18:00:53 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
Message-ID: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

The current ssl documentation has a number of statements which may need updating, particularly wrt. SSLv3.

----------
assignee: docs at python
components: Documentation
messages: 229590
nosy: alex, christian.heimes, docs at python, dstufft, giampaolo.rodola, janssen, pitrou
priority: normal
severity: normal
stage: needs patch
status: open
title: Review ssl docs for security recommendations
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Oct 17 20:42:57 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 17 Oct 2014 18:42:57 +0000
Subject: [docs] [issue22658] IMAP4 Example lacking host information
In-Reply-To: <1413564390.73.0.387636698685.issue22658@psf.upfronthosting.co.za>
Message-ID: <1413571378.0.0.670271288495.issue22658@psf.upfronthosting.co.za>


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


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> imaplib.IMAP4() ends with "Name or service not known" on Fedora 18

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

From report at bugs.python.org  Fri Oct 17 21:54:55 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 17 Oct 2014 19:54:55 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413575695.46.0.17878013613.issue17401@psf.upfronthosting.co.za>


R. David Murray added the comment:

I think the information from the following line of the 'open' docs should be added to the doc patch:

"If a filename is given closefd has no effect and must be True (the default)."

Otherwise it looks fine to me.

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

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

From report at bugs.python.org  Sat Oct 18 00:22:27 2014
From: report at bugs.python.org (Ethan Furman)
Date: Fri, 17 Oct 2014 22:22:27 +0000
Subject: [docs] [issue7186] Document specialness of __doc__,
	and possibly other "special" attributes
In-Reply-To: <1256240855.61.0.550470965616.issue7186@psf.upfronthosting.co.za>
Message-ID: <1413584547.48.0.0760331448553.issue7186@psf.upfronthosting.co.za>


Ethan Furman added the comment:

Patch attached for the __doc__ attribute.

----------
keywords: +patch
nosy: +ethan.furman
stage: needs patch -> patch review
Added file: http://bugs.python.org/file36956/issue7186.stoneleaf.01.patch

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

From report at bugs.python.org  Sat Oct 18 00:29:36 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 17 Oct 2014 22:29:36 +0000
Subject: [docs] [issue7186] Document specialness of __doc__,
	and possibly other "special" attributes
In-Reply-To: <1256240855.61.0.550470965616.issue7186@psf.upfronthosting.co.za>
Message-ID: <1413584976.57.0.410125369665.issue7186@psf.upfronthosting.co.za>


R. David Murray added the comment:

Looks fine to me.

----------

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

From report at bugs.python.org  Sat Oct 18 02:39:22 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 18 Oct 2014 00:39:22 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <20141018003900.64059.72958@psf.io>


Roundup Robot added the comment:

New changeset a1500e4a159a by Robert Collins in branch 'default':
Issue #17401: document closefd in io.FileIO docs and add to repr
https://hg.python.org/cpython/rev/a1500e4a159a

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

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

From report at bugs.python.org  Sat Oct 18 07:26:13 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 18 Oct 2014 05:26:13 +0000
Subject: [docs] [issue7186] Document specialness of __doc__,
	and possibly other "special" attributes
In-Reply-To: <1256240855.61.0.550470965616.issue7186@psf.upfronthosting.co.za>
Message-ID: <20141018052605.109745.89430@psf.io>


Roundup Robot added the comment:

New changeset 7c183c782401 by Ethan Furman in branch '3.4':
Issue7186: document that __doc__ is not inherited by subclasses
https://hg.python.org/cpython/rev/7c183c782401

New changeset cb8606fc84df by Ethan Furman in branch 'default':
Issue7186: document that __doc__ is not inherited by subclasses
https://hg.python.org/cpython/rev/cb8606fc84df

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

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

From report at bugs.python.org  Sat Oct 18 07:28:40 2014
From: report at bugs.python.org (Ethan Furman)
Date: Sat, 18 Oct 2014 05:28:40 +0000
Subject: [docs] [issue7186] Document specialness of __doc__,
	and possibly other "special" attributes
In-Reply-To: <1256240855.61.0.550470965616.issue7186@psf.upfronthosting.co.za>
Message-ID: <1413610120.35.0.981295167097.issue7186@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 18 07:28:54 2014
From: report at bugs.python.org (Ethan Furman)
Date: Sat, 18 Oct 2014 05:28:54 +0000
Subject: [docs] [issue7186] Document specialness of __doc__,
	and possibly other "special" attributes
In-Reply-To: <1256240855.61.0.550470965616.issue7186@psf.upfronthosting.co.za>
Message-ID: <1413610134.42.0.358382608778.issue7186@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 18 09:46:29 2014
From: report at bugs.python.org (Martin Panter)
Date: Sat, 18 Oct 2014 07:46:29 +0000
Subject: [docs] [issue21228] Missing enumeration of HTTPResponse Objects
	methods of	urllib.request.urlopen's http.client.HTTPResponse?
In-Reply-To: <1397520483.48.0.224250148615.issue21228@psf.upfronthosting.co.za>
Message-ID: <1413618389.07.0.772451036238.issue21228@psf.upfronthosting.co.za>


Martin Panter added the comment:

Is there anything else that needs doing to get this committed and resolved? My patch is just a trivial reordering of Evens?s, with about one sentence deleted.

----------

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

From report at bugs.python.org  Sat Oct 18 15:13:19 2014
From: report at bugs.python.org (=?utf-8?q?C=C3=A9dric_Krier?=)
Date: Sat, 18 Oct 2014 13:13:19 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413637999.39.0.241571013402.issue13918@psf.upfronthosting.co.za>


C?dric Krier added the comment:

A new version with unittest.

----------
Added file: http://bugs.python.org/file36960/delocalize.patch

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

From report at bugs.python.org  Sat Oct 18 18:50:34 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 18 Oct 2014 16:50:34 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413651034.07.0.618812178786.issue13918@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Thanks for the updated patch, C?dric. Just some remarks:

- the documentation should mention that the return value is still a string
- the documentation needs a "versionadded" marker next to the new function
- have you already signed the contributor's agreement? otherwise you should sign it at https://www.python.org/psf/contrib/contrib-form/

----------

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

From report at bugs.python.org  Sat Oct 18 20:35:15 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 18 Oct 2014 18:35:15 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <1413657314.89.0.597972174273.issue22660@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Here is a patch.

----------
keywords: +patch
Added file: http://bugs.python.org/file36961/ssldoc.patch

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

From report at bugs.python.org  Sat Oct 18 23:08:33 2014
From: report at bugs.python.org (=?utf-8?q?C=C3=A9dric_Krier?=)
Date: Sat, 18 Oct 2014 21:08:33 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1413666513.28.0.282195773961.issue13918@psf.upfronthosting.co.za>


C?dric Krier added the comment:

Add return value is string in doc
Add versionadded
And yes I signed the agreement.

----------
Added file: http://bugs.python.org/file36964/delocalize.patch

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

From gabcap1 at gmail.com  Sat Oct 18 21:42:36 2014
From: gabcap1 at gmail.com (Gabriella Capone)
Date: Sat, 18 Oct 2014 15:42:36 -0400
Subject: [docs] Typo
Message-ID: <CADSfYbf8BoOkpsZBt4sPQ7aDNQp9kUpL+CpfNoD02nYeQ1kc3A@mail.gmail.com>

https://docs.python.org/2/library/re.html

In explanation of "\W" last sentence reads "classied" instead of
"classified."

-- 
Gabriella Capone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141018/21d2dd89/attachment.html>

From zachary.ware+pydocs at gmail.com  Sun Oct 19 08:10:25 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Sun, 19 Oct 2014 01:10:25 -0500
Subject: [docs] Typo
In-Reply-To: <CADSfYbf8BoOkpsZBt4sPQ7aDNQp9kUpL+CpfNoD02nYeQ1kc3A@mail.gmail.com>
References: <CADSfYbf8BoOkpsZBt4sPQ7aDNQp9kUpL+CpfNoD02nYeQ1kc3A@mail.gmail.com>
Message-ID: <CAKJDb-Okpa9XU3t7hfD=kvJ8P6KZHbnsY+uUQ78RPJVJ5DC_yg@mail.gmail.com>

On Sat, Oct 18, 2014 at 2:42 PM, Gabriella Capone <gabcap1 at gmail.com> wrote:
> https://docs.python.org/2/library/re.html
>
> In explanation of "\W" last sentence reads "classied" instead of
> "classified."

Thanks for the report!  This has now been fixed.

-- 
Zach

From report at bugs.python.org  Sun Oct 19 11:35:52 2014
From: report at bugs.python.org (gigaplastik)
Date: Sun, 19 Oct 2014 09:35:52 +0000
Subject: [docs] [issue22671] Typo in class io.BufferedIOBase docs
Message-ID: <1413711352.27.0.0253692424247.issue22671@psf.upfronthosting.co.za>


New submission from gigaplastik:

The online documentation for class io.BufferedIOBase states the following:

"Besides, the read() method does not have a default implementation that defers to readinto()."

According to the documentation for class io.RawIOBase (which the statement compares with) read() method actually defers to readall(), NOT readinto() as misleadingly stated.
The same typo is present in help('io.BufferedIOBase') output and, very likely, in all 3.X line docs for this class.

----------
assignee: docs at python
components: Documentation
messages: 229677
nosy: docs at python, gigaplastik
priority: normal
severity: normal
status: open
title: Typo in class io.BufferedIOBase docs
type: enhancement
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Sun Oct 19 17:06:07 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 19 Oct 2014 15:06:07 +0000
Subject: [docs] [issue22186] Typos in .py files
In-Reply-To: <1407862651.37.0.513368911737.issue22186@psf.upfronthosting.co.za>
Message-ID: <20141019150601.109739.61762@psf.io>


Roundup Robot added the comment:

New changeset 98f16237e1e2 by Berker Peksag in branch '3.4':
Issue #22186: Fix typos in Lib/.
https://hg.python.org/cpython/rev/98f16237e1e2

New changeset 57b19af3d71b by Berker Peksag in branch 'default':
Issue #22186: Fix typos in Lib/.
https://hg.python.org/cpython/rev/57b19af3d71b

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

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

From report at bugs.python.org  Sun Oct 19 17:09:23 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Oct 2014 15:09:23 +0000
Subject: [docs] [issue22186] Typos in .py files
In-Reply-To: <1407862651.37.0.513368911737.issue22186@psf.upfronthosting.co.za>
Message-ID: <1413731363.9.0.430473040185.issue22186@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch, F?vry.

----------
assignee: rhettinger -> berker.peksag
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed
versions: +Python 3.4, Python 3.5

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

From report at bugs.python.org  Sun Oct 19 20:33:08 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Oct 2014 18:33:08 +0000
Subject: [docs] [issue21949] Document the Py_SIZE() macro.
In-Reply-To: <1404935084.68.0.420259951718.issue21949@psf.upfronthosting.co.za>
Message-ID: <1413743588.39.0.820252069667.issue21949@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Oct 19 22:20:15 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 19 Oct 2014 20:20:15 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1413750015.24.0.154409154702.issue15204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Please open new issue for this.

----------

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

From report at bugs.python.org  Mon Oct 20 01:13:05 2014
From: report at bugs.python.org (Robert Collins)
Date: Sun, 19 Oct 2014 23:13:05 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413760385.98.0.317922213442.issue17401@psf.upfronthosting.co.za>


Changes by Robert Collins <robertc at robertcollins.net>:


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

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

From report at bugs.python.org  Mon Oct 20 03:14:41 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 20 Oct 2014 01:14:41 +0000
Subject: [docs] [issue16893] Generate Idle help from Doc/library/idle.rst
In-Reply-To: <1357663512.19.0.739336896498.issue16893@psf.upfronthosting.co.za>
Message-ID: <1413767681.62.0.325397019555.issue16893@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I have avoided editing the Idle docs because of this issue, but idle.rst needs some corrections and updates now, and will soon need some additions.  I want to only edit idle.rst. So I want to resolve this issue soon.

As I mentioned before, I think the best idea is Ned's: copy Doc/build/html/library/idle.html to idlelib (as help.html for now) and change the 'IDLE Help' code to display it in a browser.  This will be easy and will end the duplication and DRY violation that is the goal of this issue.

Zach, can you produce a makefiles.v4 patch (without .rst changes) that patches the makefiles to add a target do the copying?  The same patch (or another) should add idlelib/help.html to .hgignore so idle developers and testers can 'make' the new target without committing it.  Georg can then update PEP 101 with the new release step.

This change will provide a nicely formatted, always-available local copy that should match the installed micro-version.  Because of PEP 434, later online versions of the doc may contain changes that do not apply to the installed version.

After this is done, and anything in help.txt but not in idle.rst is moved, help.txt will be deleted.

issue16893.v3.diff mixes together changes for this issue and a separate issue of editing idle.rst.  I will separately apply some of your mising changes, but I don't think I like adding the new separators and even more whitespace.  Also, I assume that 'Control' in .txt was changed to 'C' in .rst because OSX uses 'Command' instead of 'Control' and 'C' stands for either.  That is aside from the issue of abbreviating something used repeatedly.  Anyway, I think this is a discussion for another tracker issue.

----------
stage:  -> needs patch
title: Create IDLE help.txt from Doc/library/idle.rst -> Generate Idle help from Doc/library/idle.rst

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

From report at bugs.python.org  Mon Oct 20 04:20:05 2014
From: report at bugs.python.org (R. David Murray)
Date: Mon, 20 Oct 2014 02:20:05 +0000
Subject: [docs] [issue22673] document the special features (eg:
	fdclose=False) of the	standard streams
In-Reply-To: <1413745258.02.0.518044907787.issue22673@psf.upfronthosting.co.za>
Message-ID: <1413771605.7.0.260750479899.issue22673@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation -IO
nosy: +docs at python
stage:  -> needs patch
title: Incorrect fileno for CONOUT$ / stdout -> document the special features (eg: fdclose=False) of the standard streams
versions: +Python 3.4, Python 3.5

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

From report at bugs.python.org  Mon Oct 20 06:20:56 2014
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 20 Oct 2014 04:20:56 +0000
Subject: [docs] [issue16893] Generate Idle help from Doc/library/idle.rst
In-Reply-To: <1357663512.19.0.739336896498.issue16893@psf.upfronthosting.co.za>
Message-ID: <1413778856.03.0.61745100916.issue16893@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Sure; here's a patch.  I suspect we may want to try giving Sphinx some different options to clean up the output a bit, but I'm not experienced enough with Sphinx to have any specific suggestions.

----------
Added file: http://bugs.python.org/file36975/issue16893-v4.diff

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

From report at bugs.python.org  Mon Oct 20 10:02:29 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 20 Oct 2014 08:02:29 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413792149.47.0.0945880162279.issue17401@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

FileIO repr now looks confusing:

>>> sys.stdout.buffer.raw
<_io.FileIO name='<stdout>' mode='wb' closefd='0'>

The closefd attribute is not a string '0' or '1', it is boolean value True or False. Here is a patch which fixes a repr.

And I think that documentation part of the patch should be backported.

----------
nosy: +serhiy.storchaka
resolution: fixed -> 
stage:  -> patch review
status: closed -> open
versions: +Python 3.5 -Python 3.2, Python 3.3
Added file: http://bugs.python.org/file36977/io_fileio_repr_closefd.patch

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

From report at bugs.python.org  Mon Oct 20 10:20:39 2014
From: report at bugs.python.org (Robert Collins)
Date: Mon, 20 Oct 2014 08:20:39 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413793239.47.0.426722891479.issue17401@psf.upfronthosting.co.za>


Robert Collins added the comment:

Yeah thats nicer. I'll apply that later unless you can.

----------

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

From report at bugs.python.org  Mon Oct 20 11:26:32 2014
From: report at bugs.python.org (Andy Maier)
Date: Mon, 20 Oct 2014 09:26:32 +0000
Subject: [docs] [issue12067] Doc: remove errors about mixed-type comparisons.
In-Reply-To: <1305237573.86.0.646542413513.issue12067@psf.upfronthosting.co.za>
Message-ID: <1413797191.73.0.259018740513.issue12067@psf.upfronthosting.co.za>


Andy Maier added the comment:

I have posted v12 of the patch, which addresses all comments since v11.

This Python 3.4 patch can be applied to the "default" (3.5 dev) branch as well.

I will start working on a similar patch for Python 2.7 now.

----------
Added file: http://bugs.python.org/file36978/issue12067-expressions-py34_v12.diff

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

From report at bugs.python.org  Mon Oct 20 12:48:47 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 20 Oct 2014 10:48:47 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413802127.01.0.95301763555.issue17401@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

May be include closefd in the repr only when it is False? By default closefd is True and in common case the repr will be more compact.

----------
Added file: http://bugs.python.org/file36979/io_fileio_repr_closefd_2.patch

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

From report at bugs.python.org  Mon Oct 20 16:22:52 2014
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Mon, 20 Oct 2014 14:22:52 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413814972.82.0.536386957873.issue17401@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Mon Oct 20 16:26:21 2014
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Mon, 20 Oct 2014 14:26:21 +0000
Subject: [docs] [issue22673] document the special features (eg:
	fdclose=False) of the	standard streams
In-Reply-To: <1413745258.02.0.518044907787.issue22673@psf.upfronthosting.co.za>
Message-ID: <1413815181.18.0.178557277834.issue22673@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Mon Oct 20 16:41:09 2014
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Mon, 20 Oct 2014 14:41:09 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <1413816069.81.0.440478705605.issue22660@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Mon Oct 20 23:39:42 2014
From: report at bugs.python.org (Robert Collins)
Date: Mon, 20 Oct 2014 21:39:42 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413841182.83.0.405565741182.issue17401@psf.upfronthosting.co.za>


Robert Collins added the comment:

Showing it only when False would have higher cognitive load. Showing it always is simple and clear.

----------

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

From robertc at robertcollins.net  Mon Oct 20 23:48:30 2014
From: robertc at robertcollins.net (robertc at robertcollins.net)
Date: Mon, 20 Oct 2014 21:48:30 -0000
Subject: [docs] io.FileIO closefd parameter is not documented nor shown
 in repr (issue 17401)
Message-ID: <20141020214830.18263.64113@psf.upfronthosting.co.za>

Patch set 1 looks fine to me.

http://bugs.python.org/review/17401/

From report at bugs.python.org  Tue Oct 21 00:16:30 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 20 Oct 2014 22:16:30 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <20141020221624.128344.8510@psf.io>


Roundup Robot added the comment:

New changeset 230889852e17 by Antoine Pitrou in branch '3.4':
Issue #22660: update various mentions in the ssl module documentation.
https://hg.python.org/cpython/rev/230889852e17

New changeset 9015f502ac06 by Antoine Pitrou in branch 'default':
Issue #22660: update various mentions in the ssl module documentation.
https://hg.python.org/cpython/rev/9015f502ac06

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

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

From report at bugs.python.org  Tue Oct 21 00:32:32 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 20 Oct 2014 22:32:32 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <1413844351.94.0.371703274267.issue22660@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

This is done in 3.x. Alex, do you want to backport it to 2.7?

----------
stage: needs patch -> commit review

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

From report at bugs.python.org  Tue Oct 21 00:36:55 2014
From: report at bugs.python.org (Alex Gaynor)
Date: Mon, 20 Oct 2014 22:36:55 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <1413844615.62.0.901077241636.issue22660@psf.upfronthosting.co.za>


Alex Gaynor added the comment:

Yes, that would be good. Need to make sure all the changes are completely applicable -- the SSLv3 change wasn't backported.

----------

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

From berker.peksag at gmail.com  Tue Oct 21 02:35:21 2014
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Tue, 21 Oct 2014 00:35:21 -0000
Subject: [docs] io.FileIO closefd parameter is not documented nor shown
 in repr (issue 17401)
Message-ID: <20141021003521.27951.64214@psf.upfronthosting.co.za>

io_fileio_repr_closefd.patch LGTM, too.

http://bugs.python.org/review/17401/

From report at bugs.python.org  Tue Oct 21 02:35:33 2014
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Oct 2014 00:35:33 +0000
Subject: [docs] [issue17401] io.FileIO closefd parameter is not documented
	nor shown	in repr
In-Reply-To: <1363057927.36.0.00381165430664.issue17401@psf.upfronthosting.co.za>
Message-ID: <1413851733.17.0.938070435192.issue17401@psf.upfronthosting.co.za>


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


----------
stage: patch review -> commit review

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

From robertc at robertcollins.net  Mon Oct 20 23:50:16 2014
From: robertc at robertcollins.net (robertc at robertcollins.net)
Date: Mon, 20 Oct 2014 21:50:16 -0000
Subject: [docs] io.FileIO closefd parameter is not documented nor shown
 in repr (issue 17401)
Message-ID: <20141020215016.13766.6127@psf.upfronthosting.co.za>


http://bugs.python.org/review/17401/diff/13116/Modules/_io/fileio.c
File Modules/_io/fileio.c (right):

http://bugs.python.org/review/17401/diff/13116/Modules/_io/fileio.c#newcode1059
Modules/_io/fileio.c:1059: self->fd, mode_string(self), self->closefd ?
"" : " closefd=False");
So this will work, but its more complex for folk to reason about.

http://bugs.python.org/review/17401/diff/13116/Modules/_io/fileio.c#newcode1064
Modules/_io/fileio.c:1064: nameobj, mode_string(self), self->closefd ?
"" : " closefd=False");
OTOH this code path here may make sense to hide closefd altogether,
since closefd cannot be specified with file names (rather than fds) -
its always treated as True.

http://bugs.python.org/review/17401/

From report at bugs.python.org  Tue Oct 21 12:23:42 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 21 Oct 2014 10:23:42 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <20141021102335.53366.49411@psf.io>


Roundup Robot added the comment:

New changeset 6f6e56bb10aa by Antoine Pitrou in branch '2.7':
Issue #22660: update various mentions in the ssl module documentation.
https://hg.python.org/cpython/rev/6f6e56bb10aa

----------

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

From report at bugs.python.org  Tue Oct 21 12:23:56 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 21 Oct 2014 10:23:56 +0000
Subject: [docs] [issue22660] Review ssl docs for security recommendations
In-Reply-To: <1413568853.31.0.251861459385.issue22660@psf.upfronthosting.co.za>
Message-ID: <1413887036.57.0.929718125697.issue22660@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Wed Oct 22 07:08:23 2014
From: report at bugs.python.org (James)
Date: Wed, 22 Oct 2014 05:08:23 +0000
Subject: [docs] [issue22691] A Better Help File
Message-ID: <1413954503.13.0.720826050231.issue22691@psf.upfronthosting.co.za>


New submission from James:

Just the General Help that is in Python, doesn't really help.  Here's what would help, if every Module, had an example in code of how it was used instead of the Trees.  I mean, word trees, well that's what the writing reminds me of, is word trees like you'd produce in an English class.  But, a short working piece of code, does allot more for me, than a lecture, you'd have to take a course to understand because of it's use of it's own writing style.  It doesn't help to type help() and hit enter.

----------
assignee: docs at python
components: Documentation
messages: 229796
nosy: FCK, docs at python
priority: normal
severity: normal
status: open
title: A Better Help File
type: enhancement
versions: Python 2.7

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

From report at bugs.python.org  Wed Oct 22 07:23:04 2014
From: report at bugs.python.org (James)
Date: Wed, 22 Oct 2014 05:23:04 +0000
Subject: [docs] [issue22691] A Better Help File
In-Reply-To: <1413954503.13.0.720826050231.issue22691@psf.upfronthosting.co.za>
Message-ID: <1413955384.52.0.376426289997.issue22691@psf.upfronthosting.co.za>


James added the comment:

Just the General Help that is in Python, doesn't really help.  Here's what would help, if every Module, had an example in code of how it was used instead of the Trees.  I mean, word trees, well that's what the writing reminds me of, is word trees like you'd produce in an English class.  But, a short working piece of code, does allot more for me, than a lecture, you'd have to take a course to understand because of it's use of it's own writing style.  It doesn't help to type help() and hit enter.

Honestly, the old old version of Quick Basic, that once came with every version of windows back in the 90s.  It's help, is a template that I think Python, should follow.

----------

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

From report at bugs.python.org  Wed Oct 22 09:50:21 2014
From: report at bugs.python.org (=?utf-8?b?0JLQsNGB0LjQu9C40Lkg0JzQsNC60LDRgNC+0LI=?=)
Date: Wed, 22 Oct 2014 07:50:21 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
Message-ID: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>


New submission from ??????? ???????:

Python 3 open() documentation ( https://docs.python.org/3/library/functions.html#open ) is probably broken. Here is what one can see at the end of open() description:
"...
Deprecated since version 3.4, will be removed in version 4.0.

The 'U' mode."

Reader may assume the open() function is what will be removed, which is wrong AFAIK

----------
assignee: docs at python
components: Documentation
messages: 229802
nosy: docs at python, ???????.???????
priority: normal
severity: normal
status: open
title: open() declared deprecated in python 3 docs
type: behavior
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Wed Oct 22 09:57:58 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 22 Oct 2014 07:57:58 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <20141022075755.76747.60017@psf.io>


Roundup Robot added the comment:

New changeset a2ecc284eaa7 by Victor Stinner in branch '3.4':
Issue #22695: Fix syntax of open() doc
https://hg.python.org/cpython/rev/a2ecc284eaa7

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

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

From report at bugs.python.org  Wed Oct 22 09:58:37 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 22 Oct 2014 07:58:37 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <1413964716.96.0.865241751453.issue22695@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Reader may assume the open() function is what will be removed, which is wrong AFAIK

It looks like an issue with the reST syntax in the documentation. Wait until the doc is regenerated (in a few hours) and then check again the doc please, to confirm that the issue is fixed.

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

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

From report at bugs.python.org  Wed Oct 22 11:01:56 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 22 Oct 2014 09:01:56 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <1413968516.43.0.142203963962.issue22695@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

There are other "deprecated-removed" instructions without following empty line in the docs. Should they be changed?

However the "deprecated" instruction works without following empty line. It looks as there is a bug in the implementation of the "deprecated-removed" instruction.

----------
nosy: +georg.brandl, serhiy.storchaka
versions:  -Python 3.2, Python 3.3, Python 3.6

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

From report at bugs.python.org  Wed Oct 22 11:03:04 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 22 Oct 2014 09:03:04 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <1413968584.05.0.408373379276.issue22695@psf.upfronthosting.co.za>


STINNER Victor added the comment:

"However the "deprecated" instruction works without following empty line. It looks as there is a bug in the implementation of the "deprecated-removed" instruction."

Agreed, we can maybe enhance that. At least emit a warning?

----------

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

From report at bugs.python.org  Wed Oct 22 15:25:07 2014
From: report at bugs.python.org (R. David Murray)
Date: Wed, 22 Oct 2014 13:25:07 +0000
Subject: [docs] [issue22691] A Better Help File
In-Reply-To: <1413954503.13.0.720826050231.issue22691@psf.upfronthosting.co.za>
Message-ID: <1413984307.46.0.20814971819.issue22691@psf.upfronthosting.co.za>


R. David Murray added the comment:

The help isn't targeted at teaching you to use the module.  The help is targeted at *reminding* you how to use the module after you've read the full documentation, which usually does contain examples (though generally not at the top of the page...they are usually at the bottom or interspersed...it is a *reference* guide after all, the tutorial is a separate thing with yet a different target).  I'm afraid, though, that if you find the help to be a wall of words, you'll find the library reference worse.  You might be best serve by checking out the book/website "Python Module of the Week" (pymotw.com), which has a more tutorial style and more examples.

I've never see the Quick Basic style docs.  I don't know if that style would be applicable to Python modules.

Bottom line right now, though, is that this isn't really a useful issue for the bug tracker.  If you want to discuss strategies for making overall improvements in the documentation, that's something that should be done with the group of people who focus on documentation.  Their mailing list is docs at python.org if you want to join the team and advocate for a change (your suggestion has already been posted to that mailing list by the bug tracker, FYI).

----------
nosy: +r.david.murray
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed Oct 22 15:34:13 2014
From: report at bugs.python.org (R. David Murray)
Date: Wed, 22 Oct 2014 13:34:13 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <1413984853.24.0.947120819698.issue22695@psf.upfronthosting.co.za>


R. David Murray added the comment:

Presumably we can fix it.  The code is in Docs/tools/pyspecific.py.  Probably just need to figure out how it is different from the regular Sphinx deprecated tag implementation.

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

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

From report at bugs.python.org  Wed Oct 22 22:57:56 2014
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Oct 2014 20:57:56 +0000
Subject: [docs] [issue11260] smtpd-as-a-script feature should be documented
	and	should use argparse
In-Reply-To: <1298232231.08.0.088023732748.issue11260@psf.upfronthosting.co.za>
Message-ID: <1414011476.11.0.296884523569.issue11260@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag
stage:  -> patch review

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

From report at bugs.python.org  Wed Oct 22 23:03:45 2014
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Oct 2014 21:03:45 +0000
Subject: [docs] [issue16863] Python 2 error in Argparse tutorial
In-Reply-To: <1357317464.45.0.840404790237.issue16863@psf.upfronthosting.co.za>
Message-ID: <1414011825.69.0.066923273548.issue16863@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +berker.peksag
stage:  -> needs patch

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

From report at bugs.python.org  Wed Oct 22 23:45:54 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 22 Oct 2014 21:45:54 +0000
Subject: [docs] [issue16863] Python 2 error in Argparse tutorial
In-Reply-To: <1357317464.45.0.840404790237.issue16863@psf.upfronthosting.co.za>
Message-ID: <1414014353.95.0.659933956309.issue16863@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Since the author of the tutorial agrees with my idea, and no one has come forward with anything else, I will make the change.

----------
assignee:  -> terry.reedy

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

From report at bugs.python.org  Thu Oct 23 00:00:16 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 22 Oct 2014 22:00:16 +0000
Subject: [docs] [issue16863] Python 2 error in Argparse tutorial
In-Reply-To: <1357317464.45.0.840404790237.issue16863@psf.upfronthosting.co.za>
Message-ID: <20141022220008.76751.17376@psf.io>


Roundup Robot added the comment:

New changeset e7428d7f641f by Terry Jan Reedy in branch '2.7':
Issue #16863: Explain difference between text and 2.7 behavior.
https://hg.python.org/cpython/rev/e7428d7f641f

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

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

From report at bugs.python.org  Thu Oct 23 00:04:46 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 22 Oct 2014 22:04:46 +0000
Subject: [docs] [issue16863] Python 2 error in Argparse tutorial
In-Reply-To: <1357317464.45.0.840404790237.issue16863@psf.upfronthosting.co.za>
Message-ID: <1414015486.35.0.830207724906.issue16863@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Once this discrepancy is explained
(3.x) prog.py: error: the following arguments are required: echo
(2.7) prog.py: error: too few arguments
I agree with leaving the 3.x version in the tutorial.  A normal output discrepany might be a different matter.

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

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

From report at bugs.python.org  Thu Oct 23 00:52:47 2014
From: report at bugs.python.org (Ned Deily)
Date: Wed, 22 Oct 2014 22:52:47 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1414018367.22.0.161770443289.issue22702@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation -Macintosh
nosy: +docs at python -ned.deily, ronaldoussoren
versions: +Python 3.4 -Python 3.3

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

From report at bugs.python.org  Thu Oct 23 06:00:41 2014
From: report at bugs.python.org (Josh Rosenberg)
Date: Thu, 23 Oct 2014 04:00:41 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1414036841.79.0.140420200232.issue22702@psf.upfronthosting.co.za>


Josh Rosenberg added the comment:

Seems awfully verbose relative to the standards of the other built-in methods. Can you explain what improvements you feel this provides? str.join isn't a particularly complex method, relative to the other str methods that have inline usage examples (e.g. the *strip methods, where it needs to be made clear that it's stripping by character, not string matching, or the interaction of arguments in str.split).

----------
nosy: +josh.r

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

From report at bugs.python.org  Thu Oct 23 06:21:24 2014
From: report at bugs.python.org (Van Ly)
Date: Thu, 23 Oct 2014 04:21:24 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1414038084.48.0.166834079265.issue22702@psf.upfronthosting.co.za>


Van Ly added the comment:

The improvement on the original (doc v.2.7.5) lies in the removal of the repeated 'iterable' in the first sentence, and I have also shortened it to deliver only what is returned by the builtin method which was what I wanted to know without knowing how. I wrote up this reformulation as I would have like to read it. I believe the word "concatenation" is off putting to beginners without a formal background or wanting to acquire that, and there are people like me who prefer plain and simple words. "concatenation" could be used in a footnote to guide readers to more depth if that is something they want to have. The inline usage example serves to confirm what has been described/claimed.

--original: doc v.2.7.5

str.join(iterable)

Return a string which is the concatenation of the strings in the iterable iterable. The separator between elements is the string providing this method.

----------

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

From report at bugs.python.org  Thu Oct 23 06:35:55 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 23 Oct 2014 04:35:55 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1414038955.65.0.42696785964.issue22702@psf.upfronthosting.co.za>


Changes by Raymond Hettinger <raymond.hettinger at gmail.com>:


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

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

From report at bugs.python.org  Thu Oct 23 06:42:14 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 23 Oct 2014 04:42:14 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1414039334.15.0.728145592222.issue22702@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

At least the "iterable iterable" should be fixed.  However, as Josh said, the proposed wording is verbose.  Aim for the smallest number of words that gets the job done.

----------

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

From report at bugs.python.org  Thu Oct 23 06:51:02 2014
From: report at bugs.python.org (Van Ly)
Date: Thu, 23 Oct 2014 04:51:02 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1414039862.36.0.932235639963.issue22702@psf.upfronthosting.co.za>


Van Ly added the comment:

Aim for the fewest syllables in the words without losing meaning or good taste.

----------

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

From report at bugs.python.org  Thu Oct 23 13:01:38 2014
From: report at bugs.python.org (James)
Date: Thu, 23 Oct 2014 11:01:38 +0000
Subject: [docs] [issue22691] A Better Help File
In-Reply-To: <1413984307.46.0.20814971819.issue22691@psf.upfronthosting.co.za>
Message-ID: <B54E7D1ED25F41088994268763F268E5@JamesPCX>


James added the comment:

I've written several languages, I'm no novice but, I also know when to brush 
up.Its just how I started, it looks like an opening for others.

-----Original Message----- 
From: R. David Murray
Sent: Wednesday, October 22, 2014 6:25 AM
To: geek.moses at gmail.com
Subject: [issue22691] A Better Help File

R. David Murray added the comment:

The help isn't targeted at teaching you to use the module.  The help is 
targeted at *reminding* you how to use the module after you've read the full 
documentation, which usually does contain examples (though generally not at 
the top of the page...they are usually at the bottom or interspersed...it is 
a *reference* guide after all, the tutorial is a separate thing with yet a 
different target).  I'm afraid, though, that if you find the help to be a 
wall of words, you'll find the library reference worse.  You might be best 
serve by checking out the book/website "Python Module of the Week" 
(pymotw.com), which has a more tutorial style and more examples.

I've never see the Quick Basic style docs.  I don't know if that style would 
be applicable to Python modules.

Bottom line right now, though, is that this isn't really a useful issue for 
the bug tracker.  If you want to discuss strategies for making overall 
improvements in the documentation, that's something that should be done with 
the group of people who focus on documentation.  Their mailing list is 
docs at python.org if you want to join the team and advocate for a change (your 
suggestion has already been posted to that mailing list by the bug tracker, 
FYI).

----------
nosy: +r.david.murray
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

----------

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

From report at bugs.python.org  Thu Oct 23 14:57:26 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 12:57:26 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
Message-ID: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

I just noticed that access to the normal distutils docs has become difficult. They are hidden as "legacy" while a link to the packaging user guide (https://packaging.python.org/en/latest/) is prominently displayed.

The problem is that the packaging user guide is an unreadable mess of recommandations, which is both tedious and unhelpful when you want a detailed documentation of e.g. the setup() function.

I would ask to revert to the "old" distutils docs until the packaging guide becomes up to the task.

----------
assignee: docs at python
components: Documentation
messages: 229871
nosy: docs at python, dstufft, eric.araujo, ncoghlan, pitrou
priority: normal
severity: normal
status: open
title: "legacy" distutils docs better than packaging guide
versions: Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Oct 23 17:05:30 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Oct 2014 15:05:30 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414076730.27.0.475205620617.issue22711@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

The old distutils docs are actively wrong in some areas, which is why they have been moved from their previous location.

They can't be deleted yet because they contain info that needs to be moved to either the distutils module docs, the setuptools docs, or the Python Packaging User Guide (although the latter is generally not the right place for detailed API references).

Assistance salvaging the information that still needs to be retained out of the middle of the now deprecated legacy docs would be greatly appreciated.

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

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

From report at bugs.python.org  Thu Oct 23 17:06:28 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 15:06:28 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414076788.74.0.246321966777.issue22711@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

> The old distutils docs are actively wrong in some areas

Yet they are actively useful in others.

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

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

From report at bugs.python.org  Thu Oct 23 17:19:14 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Oct 2014 15:19:14 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414077554.0.0.0015429509824.issue22711@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

For reference, issue #19407 covered the PEP 453 docs updates.

I tried fixing them in place, and judged it utterly impractical to do so - moving them out of the way, but keeping them available (including via existing deep links) was the resulting compromise.

If you're prepared to help extract the needed data, great, but putting them back where they were is *not* going to happen.

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

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

From report at bugs.python.org  Thu Oct 23 17:20:20 2014
From: report at bugs.python.org (Martijn Pieters)
Date: Thu, 23 Oct 2014 15:20:20 +0000
Subject: [docs] [issue13769] json.dump(ensure_ascii=False) return str
	instead of	unicode
In-Reply-To: <1326300079.82.0.279410736545.issue13769@psf.upfronthosting.co.za>
Message-ID: <1414077620.43.0.00543201920471.issue13769@psf.upfronthosting.co.za>


Martijn Pieters added the comment:

I'd say this is a bug in the library, not the documentation. The library varies the output type, making it impossible to use `json.dump()` with a `io.open()` object as the library will *mix data type* when writing. That is *terrible* behaviour.

----------
nosy: +mjpieters

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

From report at bugs.python.org  Thu Oct 23 17:25:18 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 15:25:18 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414077918.9.0.0111314513902.issue22711@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Ok, can you stop closing this issue?

> I tried fixing them in place, and judged it utterly impractical to do so

Why?

> If you're prepared to help extract the needed data, great, but putting them back where they were is *not* going to happen.

Why?

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

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

From report at bugs.python.org  Thu Oct 23 19:20:09 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 23 Oct 2014 17:20:09 +0000
Subject: [docs] [issue13769] json.dump(ensure_ascii=False) return str
	instead of	unicode
In-Reply-To: <1326300079.82.0.279410736545.issue13769@psf.upfronthosting.co.za>
Message-ID: <1414084808.95.0.532084502914.issue13769@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

The revised doc admits the problem: "If *ensure_ascii* is False, some chunks written to *fp* may be unicode instances.  Unless fp.write() explicitly understands unicode (as in codecs.getwriter) this is likely to cause an error."

Making text be unicode in 3.x is our attempt at a generic fix to the problems resulting from the bug-prone 2.x 'text may be bytes or unicode' design.  Since continued 2.7 support is aimed at supporting legacy code, we are very reluctant to make behavior changes that could break working code.

----------

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

From report at bugs.python.org  Thu Oct 23 22:09:54 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 23 Oct 2014 20:09:54 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1414094994.16.0.196113688813.issue22594@psf.upfronthosting.co.za>


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


----------
components: +Regular Expressions

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

From report at bugs.python.org  Thu Oct 23 22:49:43 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 20:49:43 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1414097382.9.0.12152798214.issue13918@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Thank you! The patch looks good to me, I'm going to apply it.

----------

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

From report at bugs.python.org  Thu Oct 23 22:52:52 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 23 Oct 2014 20:52:52 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <20141023205237.76753.88741@psf.io>


Roundup Robot added the comment:

New changeset aee097e5a2b2 by Antoine Pitrou in branch 'default':
Issue #13918: Provide a locale.delocalize() function which can remove
https://hg.python.org/cpython/rev/aee097e5a2b2

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

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

From report at bugs.python.org  Thu Oct 23 22:53:30 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 20:53:30 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1414097610.12.0.543091312135.issue13918@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Done. Thank you for your contribution!

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

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

From report at bugs.python.org  Thu Oct 23 22:58:17 2014
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 23 Oct 2014 20:58:17 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1414097897.04.0.118042042666.issue13918@psf.upfronthosting.co.za>


STINNER Victor added the comment:

+    :const:'LC_NUMERIC`settings.

a space is missing before "settings", no?

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

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

From report at bugs.python.org  Thu Oct 23 23:03:58 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 21:03:58 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1414098238.41.0.203326762804.issue13918@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Ah, right, thank you.

----------

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

From report at bugs.python.org  Thu Oct 23 23:04:24 2014
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 23 Oct 2014 21:04:24 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1414098264.63.0.609148620342.issue13918@psf.upfronthosting.co.za>


Georg Brandl added the comment:

And the first quote is wrong.

----------

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

From report at bugs.python.org  Fri Oct 24 00:10:14 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Oct 2014 22:10:14 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414102214.35.0.622633237328.issue22711@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

No, I won't stop closing this issue, because reverting to advertising the legacy installation and distribution docs through a top level docs home page link is *never going to happen* (although I'll note again that direct links into the legacy docs have been explicitly preserved).

If you have concerns that the API reference docs for distutils and setuptools are too hard to locate from packaging.python.org, then the appropriate place to file an issue is at https://github.com/pypa/python-packaging-user-guide/issues

If you have concerns with the setuptools docs, then the place to file issues is https://bitbucket.org/pypa/setuptools/issues. pip injects setuptools into all of its setup.py invocations in order to ensure modern metadata is generated, even on older versions of Python. This is one of the reasons the legacy docs are thoroughly misleading - vanilla distutils will be used only if you run setup.py directly (without pip), and the script itself imports distutils rather than setuptools. If you *do* run setup.py that way, then many now expected features of the Python packaging ecosystem like API entry point declarations, command line wrapper generation and packaging dependency declarations won't be available, as they're setuptools features, rather than distutils ones.

If you'd like more detail on all the things that are sufficiently outdated in the legacy distribution and installation docs to make them actively misleading, then the place to ask for that information is the distutils-sig mailing list, not the CPython issue tracker.

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

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

From report at bugs.python.org  Fri Oct 24 01:14:23 2014
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 23 Oct 2014 23:14:23 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <1414106063.33.0.738631793086.issue22695@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 24 01:32:21 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Oct 2014 23:32:21 +0000
Subject: [docs] [issue22711] "legacy" distutils docs better than packaging
	guide
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414107141.72.0.0999937735643.issue22711@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Surely, if you think you are right, you can still wait for the discussion to happen without aggressively trying to shut it down.

Besides, you are not the docs dictator, nor the distutils maintainer. We are a community, this isn't your private territory.

> If you have concerns that the API reference docs for distutils and
> setuptools are too hard to locate from packaging.python.org

No, I'm having concerns that they are too hard to locate *from docs.python.org* (which is most people's landing point, as well). Which is why I'm opening this issue here.

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

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

From report at bugs.python.org  Fri Oct 24 06:35:08 2014
From: report at bugs.python.org (Van Ly)
Date: Fri, 24 Oct 2014 04:35:08 +0000
Subject: [docs] [issue22714] target of 'import statement' entry in general
	index for	'i' is wrong
Message-ID: <1414125308.24.0.874909264609.issue22714@psf.upfronthosting.co.za>


New submission from Van Ly:

The target points to within '__import__()' but should point to 'import()' method function.

For example,

# 'import statement' entry at index for 'i' on the following page
python-2.7.5-docs-html/genindex-I.html

# points to
python-2.7.5-docs-html/library/functions.html#index-8

# but should point to
python-2.7.5-docs-html/reference/simple_stmts.html#import

----------
assignee: docs at python
components: Documentation
messages: 229914
nosy: docs at python, vy0123
priority: normal
severity: normal
status: open
title: target of 'import statement' entry in general index for 'i' is wrong
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.5

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

From report at bugs.python.org  Fri Oct 24 21:53:20 2014
From: report at bugs.python.org (Buck Golemon)
Date: Fri, 24 Oct 2014 19:53:20 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
Message-ID: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>


New submission from Buck Golemon:

The color needs adjusted such that it has at least 3:1 luminance contrast versus the surrounding non-link text. (See "non-inheritable" https://docs.python.org/3/library/os.html#os.dup)

See also:
 * http://www.w3.org/TR/WCAG20/#visual-audio-contrast-without-color
 * http://www.w3.org/WAI/WCAG20/Techniques/working-examples/G183/link-contrast.html

Given that the surrounding text is #222, the a:visited color should be bumped from #30306f to #6363bb in order to meet the 3:1 luminance-contrast guideline while preserving the hue and saturation.

By the same calculation, the un-visited links are slightly too dark and should be bumped from #00608f to #0072aa

Validation was done here: http://juicystudio.com/services/luminositycontrastratio.php

Luminance adjustments done here: http://colorizer.org/

----------
assignee: docs at python
components: Documentation
messages: 229952
nosy: bukzor, docs at python
priority: normal
severity: normal
status: open
title: visited-link styling is not accessible

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

From report at bugs.python.org  Fri Oct 24 22:14:49 2014
From: report at bugs.python.org (Buck Golemon)
Date: Fri, 24 Oct 2014 20:14:49 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <1414181689.29.0.511302861275.issue22723@psf.upfronthosting.co.za>


Buck Golemon added the comment:

Proposed patch attached.

----------
keywords: +patch
Added file: http://bugs.python.org/file37006/link-color.patch

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

From report at bugs.python.org  Fri Oct 24 22:32:10 2014
From: report at bugs.python.org (Ned Deily)
Date: Fri, 24 Oct 2014 20:32:10 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <1414182730.13.0.100438443452.issue22723@psf.upfronthosting.co.za>


Ned Deily added the comment:

+1  It's a fairly subtle change but definitely an improvement IMO (as viewed with vanilla Safari and Firefox settings on OS X).

----------
nosy: +ned.deily

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

From report at bugs.python.org  Fri Oct 24 22:41:05 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 24 Oct 2014 20:41:05 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <1414183265.88.0.368096620499.issue22723@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag, georg.brandl

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

From report at bugs.python.org  Fri Oct 24 22:48:20 2014
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 24 Oct 2014 20:48:20 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <1414183700.26.0.687453342516.issue22723@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Sounds good to me.

----------

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

From report at bugs.python.org  Sat Oct 25 03:10:47 2014
From: report at bugs.python.org (Martin Panter)
Date: Sat, 25 Oct 2014 01:10:47 +0000
Subject: [docs] [issue10976] json.loads() raises TypeError on bytes object
In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za>
Message-ID: <1414199447.29.0.913043147751.issue10976@psf.upfronthosting.co.za>


Martin Panter added the comment:

Issue 17909 (auto-detecting JSON encoding) looks like it has a patch which would probably satisfy this issue

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

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

From report at bugs.python.org  Sat Oct 25 04:20:04 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 25 Oct 2014 02:20:04 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <20141025021956.104900.24411@psf.io>


Roundup Robot added the comment:

New changeset a3481025a742 by Berker Peksag in branch '3.4':
Issue #22723: Make link styling more accessible.
https://hg.python.org/cpython/rev/a3481025a742

New changeset 56e87f2c6d3c by Berker Peksag in branch 'default':
Issue #22723: Make link styling more accessible.
https://hg.python.org/cpython/rev/56e87f2c6d3c

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

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

From report at bugs.python.org  Sat Oct 25 04:21:08 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 25 Oct 2014 02:21:08 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <1414203668.71.0.909504913005.issue22723@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch, Buck.

----------
assignee: docs at python -> berker.peksag
stage:  -> resolved
type:  -> enhancement
versions: +Python 3.4, Python 3.5

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

From report at bugs.python.org  Sat Oct 25 04:21:27 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 25 Oct 2014 02:21:27 +0000
Subject: [docs] [issue22723] visited-link styling is not accessible
In-Reply-To: <1414180400.68.0.547472264893.issue22723@psf.upfronthosting.co.za>
Message-ID: <1414203687.21.0.782489672947.issue22723@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 25 05:43:56 2014
From: report at bugs.python.org (Van Ly)
Date: Sat, 25 Oct 2014 03:43:56 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
Message-ID: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>


New submission from Van Ly:

The existing documentation is confusing. 

? improve wording as follows

enumerate(sequence, start=0)

Returns pairings of index into sequence[link to glossary.html#term-sequence] with the object at that index in the sequence.

? wording as found in v.2.7.5

enumerate(sequence, start=0)

Return an enumerate object. sequence must be a sequence, an iterator, or some other object which supports iteration. The next() method of the iterator returned by enumerate() returns a tuple containing a count (from start which defaults to 0) and the values obtained from iterating over sequence:

----------
assignee: docs at python
components: Documentation
messages: 229979
nosy: docs at python, vy0123
priority: normal
severity: normal
status: open
title: improve documentation for enumerate() (built-in function)
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.5

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

From report at bugs.python.org  Sat Oct 25 05:56:25 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 25 Oct 2014 03:56:25 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414209385.14.0.531251415945.issue22725@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
versions: +Python 3.4, Python 3.6 -Python 3.3

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

From report at bugs.python.org  Sat Oct 25 07:14:20 2014
From: report at bugs.python.org (R. David Murray)
Date: Sat, 25 Oct 2014 05:14:20 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414214060.32.0.073078568561.issue22725@psf.upfronthosting.co.za>


R. David Murray added the comment:

The existing documentation is technically correct, while your replacement leaves some things out, such as the fact that enumerate accepts an iteratable and returns an iterator that is specifically a special 'enumerate object'. (A sequence is an iteratable, but not all iterables sequences, and enumerate specifically does *not* return a list of pairs, and it is important to know that).

Can you explain what it is you find confusing about the existing documentation?  The examples should go a long way toward clarifying the text for those not familiar enough with the precisely correct terms it uses.

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

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

From report at bugs.python.org  Sat Oct 25 08:11:31 2014
From: report at bugs.python.org (Van Ly)
Date: Sat, 25 Oct 2014 06:11:31 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414217491.36.0.230773462394.issue22725@psf.upfronthosting.co.za>


Van Ly added the comment:

I don't want to argue. Ask a 12-year old and their English teacher, "Does the second sentence qualify as gobbledygook even if it is technically correct and complete and not verbose?"

To be constructive and take on what has been said, an iteration on improving the wording: 

-- improve wording as follows:

enumerate(iteratable, start=0)

Accepts an iteratable[typo for iterable?] and returns an iterator, a special case 'enumerate object'. The method iterator.next() returns a tuple which pairs an index counter with the object at the index in iterable.

>>> led = ['red', 'green', 'blue']
led = ['red', 'green', 'blue']
>>> iter = enumerate(led)
iter = enumerate(led)
>>> iter.next()
iter.next()
(0, 'red')
>>> iter.next()
iter.next()
(1, 'green')
>>> iter.next()
iter.next()
(2, 'blue')

# While enumerate does not return a list of pairs, 
# it is easy to collect the pairs and construct a list as follows
>>> list(enumerate(led))
list(enumerate(led))
[(0, 'red'), (1, 'green'), (2, 'blue')]

----------

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

From report at bugs.python.org  Sat Oct 25 10:20:29 2014
From: report at bugs.python.org (Ethan Furman)
Date: Sat, 25 Oct 2014 08:20:29 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414225229.19.0.00546741491984.issue22725@psf.upfronthosting.co.za>


Ethan Furman added the comment:

rdm was not asking for an argument, he was asking for a more detailed explanation of what was confusing.  Your initial response lacked courtesy and respect, and is not appreciated.

The rest of your reply was much better.  Next time, please skip the non-constructive portion.

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

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

From report at bugs.python.org  Sat Oct 25 10:53:18 2014
From: report at bugs.python.org (Van Ly)
Date: Sat, 25 Oct 2014 08:53:18 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414227198.92.0.207312407986.issue22725@psf.upfronthosting.co.za>


Van Ly added the comment:

Understood. I felt the problem was self evident with "sequence must be a sequence".

----------

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

From report at bugs.python.org  Sat Oct 25 11:54:16 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 25 Oct 2014 09:54:16 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414230856.47.0.650856103328.issue22725@psf.upfronthosting.co.za>


Georg Brandl added the comment:

> I felt the problem was self evident with "sequence must be a sequence".

The two words are not used in the same sense: the first names the argument of the function, the second is one of several possible object types you can pass for that argument.

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

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

From report at bugs.python.org  Sat Oct 25 12:10:23 2014
From: report at bugs.python.org (Van Ly)
Date: Sat, 25 Oct 2014 10:10:23 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414231823.46.0.361716457417.issue22725@psf.upfronthosting.co.za>


Van Ly added the comment:

> "sequence must be a sequence"

The subtle minutiae of aficionados necessary to interpret the meaning of those two words in their distinct relation is opaque to a new comer and doesn?t serve the widest possible audience usefully to get the job done quick. The second placed sense has a range of possibility narrower than iterable as has been said, all sequences are iterables but not all iterables sequences.

----------

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

From report at bugs.python.org  Sat Oct 25 13:20:00 2014
From: report at bugs.python.org (Van Ly)
Date: Sat, 25 Oct 2014 11:20:00 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414236000.52.0.745007575016.issue22725@psf.upfronthosting.co.za>


Van Ly added the comment:

The first mention of iterator should link to 'glossary.html#term-iterator'.

There is a builtin iter() function. This may cause confusion in earlier suggested inline sample code.

-- Use the following inline sample code 
-- in place of 'iter = enumerate(led)'to avoid confusion with iter() builtin:

led = ['red', 'green', 'blue']
iterator = enumerate(led)
try:
    while True:
        print iterator.next()
except StopIteration:
    print 'End of iterator has been reached.'

----------

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

From report at bugs.python.org  Sat Oct 25 15:32:24 2014
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Sat, 25 Oct 2014 13:32:24 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1414243943.88.0.634014610416.issue22237@psf.upfronthosting.co.za>


St?phane Wirtel added the comment:

ping.

----------

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

From report at bugs.python.org  Sat Oct 25 15:37:11 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 25 Oct 2014 13:37:11 +0000
Subject: [docs] [issue22711] Distribution guide should link directly to
	distutils &	setuptools API references
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414244231.5.0.475432258367.issue22711@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Since the community has been so successful at shouting down most previous attempts at fundamental Python packaging ecosystem improvements, I am extraordinarily hostile to anything that even hints at attempting to do so again. I interpreted the proposal originally put forward in this issue as just such an attempt. Specifically, it reads to me as "ah, this link was too hard to find, despite still being the top link when searching 'python distutils', let's revert all the docs changes, so newcomers to Python can go back to being just as lost and confused as they were before PEP 453 was accepted and implemented".

The legacy docs are not better than packaging.python.org or the setuptools docs - they are actively misleading in several respects, and extracting useful information from them requires that you already be an expert in the Python packaging ecosystem so you can successfully figure out which bits you need to ignore and which bits provide relevant information not yet covered anywhere else.

However, on rereading https://docs.python.org/3/distributing/, I agree it should at least point readers directly at the package API references for both distutils and setuptools. At the moment, even the existing inline references aren't hyperlinked.

The "distutils" landing page should also point readers directly at the setuptools docs, rather than requiring an indirection via the packaging user guide.

----------
title: "legacy" distutils docs better than packaging guide -> Distribution guide should link directly to distutils & setuptools API references

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

From report at bugs.python.org  Sat Oct 25 16:03:30 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 25 Oct 2014 14:03:30 +0000
Subject: [docs] [issue22711] Distribution guide should link directly to
	distutils &	setuptools API references
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <20141025140308.58158.26206@psf.io>


Roundup Robot added the comment:

New changeset c46953d76d4c by Nick Coghlan in branch '3.4':
Issue #22711: improve links in new distribution docs
https://hg.python.org/cpython/rev/c46953d76d4c

New changeset cbb9efd48405 by Nick Coghlan in branch 'default':
Merge issue #22711 from 3.4
https://hg.python.org/cpython/rev/cbb9efd48405

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

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

From report at bugs.python.org  Sat Oct 25 16:05:06 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 25 Oct 2014 14:05:06 +0000
Subject: [docs] [issue22711] Distribution guide should link directly to
	distutils &	setuptools API references
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414245906.6.0.525297827128.issue22711@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I added several previously missing hyperlinks, together with a short description of some key setuptools benefits in the distutils landing page.

Let me know if you had more than that in mind.

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

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

From report at bugs.python.org  Sat Oct 25 16:20:17 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 25 Oct 2014 14:20:17 +0000
Subject: [docs] [issue22711] Distribution guide should link directly to
	distutils &	setuptools API references
In-Reply-To: <1414244231.5.0.475432258367.issue22711@psf.upfronthosting.co.za>
Message-ID: <544BB19D.3040203@free.fr>


Antoine Pitrou added the comment:

Le 25/10/2014 15:37, Nick Coghlan a ?crit :
> 
> Since the community has been so successful at shouting down most
previous attempts at fundamental Python packaging ecosystem
improvements, I am extraordinarily hostile to anything that even hints
at attempting to do so again.

You're saying that to the guy who wanted distutils2 to stay in the stdlib.

> I added several previously missing hyperlinks,

This is good. Thank you Nick!

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

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

From report at bugs.python.org  Sat Oct 25 16:20:27 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 25 Oct 2014 14:20:27 +0000
Subject: [docs] [issue22711] Distribution guide should link directly to
	distutils &	setuptools API references
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414246827.46.0.618622270081.issue22711@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Sat Oct 25 16:25:39 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 25 Oct 2014 14:25:39 +0000
Subject: [docs] [issue22711] Distribution guide should link directly to
	distutils &	setuptools API references
In-Reply-To: <1414069046.6.0.438005896108.issue22711@psf.upfronthosting.co.za>
Message-ID: <1414247139.69.0.352075457967.issue22711@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Also, my apologies for overreacting - I interpreted the suggestion in the worst possible light, which you definitely didn't deserve.

Actually going back and rereading the guide with the benefits of a few months distance from originally writing it made the problems you encountered *much* clearer to me - the relevant links were there on the distutils landing page, but that page itself wasn't easily reachable from the top level navigation.

----------

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

From report at bugs.python.org  Sat Oct 25 17:06:58 2014
From: report at bugs.python.org (R. David Murray)
Date: Sat, 25 Oct 2014 15:06:58 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414249618.9.0.459941502887.issue22725@psf.upfronthosting.co.za>


R. David Murray added the comment:

I think you misunderstand the purpose of the documentation you are suggesting modifying.  It is a *reference guide*, and as such it needs to be technically precise and *must* correctly use the "jargon" of the language.  Especially since it also functions as the reference guide for people who implement new versions of Python, and need to know what behavior of things like 'enumerate' they need to reproduce.

That said, we also prefer the reference docs to be clear and understandable to someone who is a relative beginner, as long as we don't lose precision in doing so.  Thus the glossary and the glossary links, so yes it would be a good idea to add those.

I did indeed misspell iterable.

Your sentence is still incorrect...items returned by an iterator do not necessarily have an index (that is, you can't say myiterator[3] in the general case).

So, if I understand correctly, your difficulty was the confusion between the argument name *sequence* and the technical term ``sequence`` (referring to a Python object type).  I agree that that makes things confusing.  It would be better if the argument were named *iterable*, but we can't really change it at this point for backward compatibility reasons.

Maybe if we rearrange things a bit we can make it clearer.  How about this:

Return an enumerate object which when iterated[link to glossary] yields a two-tuple for each element in *sequence*, each tuple consisting of the sequence number of the element (beginning with *start*, which defaults to 0) paired with the element itself.  *sequence* must be a sequence, an iterator, or some other object which supports iteration.

That moves the distracting precise definition of *sequence* to the end, after you've already grasped what the function does.  You will note that I've also dropped the reference to next; that is implicit in the mention of "when iterated", since it is an integral part of the iteration protocol. IMO it is a distraction to mention next in this context.  It confuses the beginner and isn't needed by the expert.

----------

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

From johnnychen94 at hotmail.com  Sat Oct 25 19:14:11 2014
From: johnnychen94 at hotmail.com (johnnychen)
Date: Sun, 26 Oct 2014 01:14:11 +0800
Subject: [docs] a slight doc bug in built-in function
Message-ID: <BLU437-SMTP966EFE99D2FFD0F514BE65D6900@phx.gbl>

there should be a ?class? before basestring().

From report at bugs.python.org  Sat Oct 25 21:41:26 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 25 Oct 2014 19:41:26 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414266086.14.0.0995859601634.issue22725@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 25 22:03:28 2014
From: report at bugs.python.org (Ethan Furman)
Date: Sat, 25 Oct 2014 20:03:28 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414267408.76.0.430953184672.issue22725@psf.upfronthosting.co.za>


Ethan Furman added the comment:

+1 for rdm's change.

----------

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

From report at bugs.python.org  Sat Oct 25 22:44:27 2014
From: report at bugs.python.org (Ben Mather)
Date: Sat, 25 Oct 2014 20:44:27 +0000
Subject: [docs] [issue22630]
	`concurrent.futures.Future.set_running_or_notify_cancel`	does
	not notify cancel
In-Reply-To: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za>
Message-ID: <1414269867.47.0.973072087954.issue22630@psf.upfronthosting.co.za>


Ben Mather added the comment:

Have uploaded patch to re-implement `wait` and `as_completed` using callbacks.  See issue 22729.  Sorry for sitting on it for so long.

----------
Added file: http://bugs.python.org/file37017/non-magic-waiters.patch

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

From report at bugs.python.org  Sun Oct 26 04:57:53 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 26 Oct 2014 03:57:53 +0000
Subject: [docs] [issue22261] Document how to use Concurrent Build when using
	MsBuild
In-Reply-To: <1408840287.23.0.766933762648.issue22261@psf.upfronthosting.co.za>
Message-ID: <20141026035750.58164.68187@psf.io>


Roundup Robot added the comment:

New changeset f35403bf8c91 by Zachary Ware in branch 'default':
Issue #22261: Add a note to PCbuild\readme.txt about MSBuild switches.
https://hg.python.org/cpython/rev/f35403bf8c91

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

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

From report at bugs.python.org  Sun Oct 26 04:59:45 2014
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 26 Oct 2014 03:59:45 +0000
Subject: [docs] [issue22261] Document how to use Concurrent Build when using
	MsBuild
In-Reply-To: <1408840287.23.0.766933762648.issue22261@psf.upfronthosting.co.za>
Message-ID: <1414295985.53.0.0717072490925.issue22261@psf.upfronthosting.co.za>


Zachary Ware added the comment:

I finally made it back to this and committed a tweaked version of your patch.  Thanks for the report and patch!

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

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

From report at bugs.python.org  Sun Oct 26 17:01:03 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sun, 26 Oct 2014 16:01:03 +0000
Subject: [docs] [issue19980] Improve help('non-topic') response
In-Reply-To: <1386984892.27.0.919528696836.issue19980@psf.upfronthosting.co.za>
Message-ID: <1414339263.69.0.833611804346.issue19980@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

ping.

----------

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

From report at bugs.python.org  Sun Oct 26 17:57:09 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 26 Oct 2014 16:57:09 +0000
Subject: [docs] [issue19980] Improve help('non-topic') response
In-Reply-To: <1386984892.27.0.919528696836.issue19980@psf.upfronthosting.co.za>
Message-ID: <1414342629.8.0.94676901674.issue19980@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/issue19980>
_______________________________________

From report at bugs.python.org  Mon Oct 27 01:29:14 2014
From: report at bugs.python.org (Martin Panter)
Date: Mon, 27 Oct 2014 00:29:14 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1414369754.87.0.603531491743.issue22237@psf.upfronthosting.co.za>


Martin Panter added the comment:

The new text seems reasonable to me on its own, however I still think the heapsort() docstring needs updating as well

----------

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

From report at bugs.python.org  Mon Oct 27 02:03:42 2014
From: report at bugs.python.org (Van Ly)
Date: Mon, 27 Oct 2014 01:03:42 +0000
Subject: [docs] [issue22736] tutorial links at top,
	book recommendations at bottom of module documentation
Message-ID: <1414371822.19.0.713420749411.issue22736@psf.upfronthosting.co.za>


New submission from Van Ly:

IMO the box highlight at the top of module documentation, for example, re module (library/re.html#module-re), ought to place book recommendations at the very bottom in a section called 'Further Readings'. Why? Because being at the top of the documentation should mean it is instantly accessible. 

The box highlight of tutorials at the top is a nice touch.

----------
assignee: docs at python
components: Documentation
messages: 230052
nosy: docs at python, vy0123
priority: normal
severity: normal
status: open
title: tutorial links at top, book recommendations at bottom of module documentation
type: enhancement
versions: Python 2.7, Python 3.5

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

From report at bugs.python.org  Mon Oct 27 03:35:15 2014
From: report at bugs.python.org (Van Ly)
Date: Mon, 27 Oct 2014 02:35:15 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414377315.16.0.761564064123.issue22725@psf.upfronthosting.co.za>


Van Ly added the comment:

Reference by the guide to next() should stay for the same reason in re.compile() a regular expression object is returned and the two methods are mentioned, match() and search(). They are useful to know in that context in as much as next() is useful to know here. IMO.

----------

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

From report at bugs.python.org  Mon Oct 27 05:39:46 2014
From: report at bugs.python.org (Van Ly)
Date: Mon, 27 Oct 2014 04:39:46 +0000
Subject: [docs] [issue22738] improve sys.argv, 'python -h' documentation
Message-ID: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>


New submission from Van Ly:

I was looking at sys.argv from the reference guide. 

The font mix and change from v.2.7.5 to v.3.5.0a0 for sentence two of sys.argv (library/sys.html#module-sys) has made the second rendering of -c look capital when in fact it isn't.

--quote: from v.3.5.0a0 at library/sys.html#module-sys
If the command was executed using the -c command line option to the interpreter, argv[0] is set to the string '-c'.
--quote--

--suggest: improve second sentence of sys.argv (v.2.7.5, v.3.5.0a0)
Call the Python interpreter with the option, -c str, and the value of argv[0] is '-c'.
--suggest--

--suggest: improve 'python -h' output
-c str : feed in a string as program (terminates option list)
--suggest--

----------
assignee: docs at python
components: Documentation
messages: 230059
nosy: docs at python, vy0123
priority: normal
severity: normal
status: open
title: improve sys.argv, 'python -h' documentation
type: enhancement
versions: Python 2.7, Python 3.5

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

From report at bugs.python.org  Mon Oct 27 08:52:24 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 27 Oct 2014 07:52:24 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414396344.46.0.0997009041584.issue22725@psf.upfronthosting.co.za>


Georg Brandl added the comment:

next() is quite unlike match() and search(), as you almost never use next() on iterators directly. Rather, the iterator is iterated by constructs like a for loop or a comprehension, or another function that consumes it (list, map, ...)

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

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

From report at bugs.python.org  Mon Oct 27 11:37:29 2014
From: report at bugs.python.org (Van Ly)
Date: Mon, 27 Oct 2014 10:37:29 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414406249.59.0.237906767046.issue22725@psf.upfronthosting.co.za>


Van Ly added the comment:

While next() is rarely used directly on iterators, as you say, it may help to remind the experienced reader of the mechanical characteristic in essence which a new reader on first approach uses to construct a mental model.

----------

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

From report at bugs.python.org  Mon Oct 27 11:49:44 2014
From: report at bugs.python.org (Van Ly)
Date: Mon, 27 Oct 2014 10:49:44 +0000
Subject: [docs] [issue22741] suggestion for improving wording on len(s)
	(built-in	function)
Message-ID: <1414406984.61.0.134350920891.issue22741@psf.upfronthosting.co.za>


New submission from Van Ly:

-- suggest the following because 
-- the parenthetical parts interrupt the reading too often

len(s)

Returns a length count, the number of objects in argument s which may be a sequence, or mapping: a string, list or tuple, or a dictionary.

----------
assignee: docs at python
components: Documentation
messages: 230068
nosy: docs at python, vy0123
priority: normal
severity: normal
status: open
title: suggestion for improving wording on len(s) (built-in function)
type: enhancement
versions: Python 2.7, Python 3.5

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

From report at bugs.python.org  Mon Oct 27 14:29:49 2014
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 27 Oct 2014 13:29:49 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414416589.07.0.626795829035.issue22725@psf.upfronthosting.co.za>


Ethan Furman added the comment:

I do not think 'next' is needed in this context.  Unlike 'match' and 'search', 'next' is a function that can be used with any iterator and mentioning it here is unnecessary.

----------

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

From report at bugs.python.org  Mon Oct 27 14:31:15 2014
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 27 Oct 2014 13:31:15 +0000
Subject: [docs] [issue22738] improve sys.argv, 'python -h' documentation
In-Reply-To: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>
Message-ID: <1414416675.65.0.0977253332573.issue22738@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Oct 27 14:31:42 2014
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 27 Oct 2014 13:31:42 +0000
Subject: [docs] [issue22741] suggestion for improving wording on len(s)
	(built-in	function)
In-Reply-To: <1414406984.61.0.134350920891.issue22741@psf.upfronthosting.co.za>
Message-ID: <1414416702.69.0.0798353854618.issue22741@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Oct 27 14:41:27 2014
From: report at bugs.python.org (Stefan Krah)
Date: Mon, 27 Oct 2014 13:41:27 +0000
Subject: [docs] [issue22741] suggestion for improving wording on len(s)
	(built-in	function)
In-Reply-To: <1414406984.61.0.134350920891.issue22741@psf.upfronthosting.co.za>
Message-ID: <1414417287.16.0.19067569224.issue22741@psf.upfronthosting.co.za>


Stefan Krah added the comment:

The original wording is clearer (this also applies to similar issues
that have been opened recently).

----------
nosy: +skrah

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

From report at bugs.python.org  Mon Oct 27 18:02:22 2014
From: report at bugs.python.org (Friedrich Spee von Langenfeld)
Date: Mon, 27 Oct 2014 17:02:22 +0000
Subject: [docs] [issue22743] Specify supported XML version
Message-ID: <1414429342.52.0.789761709754.issue22743@psf.upfronthosting.co.za>


New submission from Friedrich Spee von Langenfeld:

The W3C has published two versions of the standard specification for the Extensible Markup Language (XML) [version 1.0 and 1.1]. I know that the W3C expects all parsers to understand both versions. I propose to state  here (https://docs.python.org/3/library/xml.html) which versions of XML Python supports, especially, because https://docs.python.org/3/library/xml.etree.elementtree.html uses version 1.0 of the W3C recommendation in its examples. The version compatibility is named in https://docs.python.org/3/library/pyexpat.html#xml.parsers.expat.xmlparser.XmlDeclHandler , but I don?t think a normal user, who only want a quick, but reliable solution, would ever read this entry.

What do you think?

----------
assignee: docs at python
components: Documentation
messages: 230079
nosy: Friedrich.Spee.von.Langenfeld, docs at python
priority: normal
severity: normal
status: open
title: Specify supported XML version
type: enhancement

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

From report at bugs.python.org  Mon Oct 27 18:49:12 2014
From: report at bugs.python.org (=?utf-8?b?0JLQsNGB0LjQu9C40Lkg0JzQsNC60LDRgNC+0LI=?=)
Date: Mon, 27 Oct 2014 17:49:12 +0000
Subject: [docs] [issue22695] open() declared deprecated in python 3 docs
In-Reply-To: <1413964221.11.0.813943721284.issue22695@psf.upfronthosting.co.za>
Message-ID: <1414432152.48.0.429095055771.issue22695@psf.upfronthosting.co.za>


??????? ??????? added the comment:

I can confirm this issue is fixed for now. Closing ticket..

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

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

From report at bugs.python.org  Mon Oct 27 19:50:45 2014
From: report at bugs.python.org (R. David Murray)
Date: Mon, 27 Oct 2014 18:50:45 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414435845.12.0.397085891222.issue22725@psf.upfronthosting.co.za>


R. David Murray added the comment:

That would not be consistent with the rest of the docs.  Consider, for example, that the full documetation of dictionary views (https://docs.python.org/3/library/stdtypes.html#dictionary-view-objects), which are iterables in much the same way that the enumerate object is, does not mention next.  The glossary link to iterable will lead the reader to the discussion of next, which is a fundamental Python concept and does not need to be repeated.  In my opinion, of course, others may disagree.

----------

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

From report at bugs.python.org  Mon Oct 27 20:12:52 2014
From: report at bugs.python.org (R. David Murray)
Date: Mon, 27 Oct 2014 19:12:52 +0000
Subject: [docs] [issue22738] improve sys.argv, 'python -h' documentation
In-Reply-To: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>
Message-ID: <1414437172.91.0.222091163123.issue22738@psf.upfronthosting.co.za>


R. David Murray added the comment:

I don't understand how your suggested change would affect the font size issue (nor do I really understand it as a sentence).

For your second suggestion (which is unrelated), how about instead:

 -c str   : interpret str as a program (terminates option list)

That would make the phrasing more consistent with the text for the other options.

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

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

From report at bugs.python.org  Mon Oct 27 20:21:31 2014
From: report at bugs.python.org (R. David Murray)
Date: Mon, 27 Oct 2014 19:21:31 +0000
Subject: [docs] [issue22741] suggestion for improving wording on len(s)
	(built-in	function)
In-Reply-To: <1414406984.61.0.134350920891.issue22741@psf.upfronthosting.co.za>
Message-ID: <1414437691.53.0.000373328787707.issue22741@psf.upfronthosting.co.za>


R. David Murray added the comment:

Agreed.  The original follows the rules of standard written English (especially as regards to punctuation), while the suggested replacement does not.

----------
nosy: +r.david.murray
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Oct 28 02:54:48 2014
From: report at bugs.python.org (Van Ly)
Date: Tue, 28 Oct 2014 01:54:48 +0000
Subject: [docs] [issue22738] improve sys.argv, 'python -h' documentation
In-Reply-To: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>
Message-ID: <1414461288.23.0.699996903685.issue22738@psf.upfronthosting.co.za>


Van Ly added the comment:

The font choice is a matter of style beyond me. I commented on it as I saw it. The second rendering looks in Capital relative to the first rendering. The problem wasn't there in v.2.7.5. In saying that, perhaps the information would be picked up by someone knowledgeable about the style sheet.

The focus of the suggestion is in the head line about the wording. I chose 'feed' because it would align with the theme of python and pickling. 'interpret' isn't as nice a picture word.

----------

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

From report at bugs.python.org  Tue Oct 28 03:10:14 2014
From: report at bugs.python.org (Van Ly)
Date: Tue, 28 Oct 2014 02:10:14 +0000
Subject: [docs] [issue22741] suggestion for improving wording on len(s)
	(built-in	function)
In-Reply-To: <1414406984.61.0.134350920891.issue22741@psf.upfronthosting.co.za>
Message-ID: <1414462214.37.0.95792782888.issue22741@psf.upfronthosting.co.za>


Van Ly added the comment:

(Well that is a stick in the mud and slap in the face attitude to different ways of describing what is there.) You have the documentation for len(s) perfect, __for_everyone__.

----------

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

From report at bugs.python.org  Tue Oct 28 03:37:46 2014
From: report at bugs.python.org (R. David Murray)
Date: Tue, 28 Oct 2014 02:37:46 +0000
Subject: [docs] [issue22738] improve  'python -h' documentation for '-c'
In-Reply-To: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>
Message-ID: <1414463866.58.0.671672494762.issue22738@psf.upfronthosting.co.za>


R. David Murray added the comment:

Well, again, your suggested change for sys.argv is less optimal English.  The text as is seems fine to me.

'feed' is a term generally used when there is a source separate from the command (for example, we speak about a unix pipe feeding data from one command to the next).  A command line argument is not generally spoken about as being "fed" into the command.  And the relevance of pickle in this context completely escapes me.  Interpret programs is what Python does (Python is, after all, one of the class of programs referred to as an interpreter).

I thank you for your desire to improve the python documentation, but so far your suggestions have not been improvements.  It would probably be most helpful if you stick to pointing out places where you found the documentation confusing, explain your confusion as much as you can, and leave the writing of the improvements to the native English speakers.

----------
title: improve sys.argv, 'python -h' documentation -> improve  'python -h' documentation for '-c'

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

From report at bugs.python.org  Tue Oct 28 03:58:00 2014
From: report at bugs.python.org (Van Ly)
Date: Tue, 28 Oct 2014 02:58:00 +0000
Subject: [docs] [issue22738] improve  'python -h' documentation for '-c'
In-Reply-To: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>
Message-ID: <1414465080.49.0.975585472185.issue22738@psf.upfronthosting.co.za>


Van Ly added the comment:

I don't know what you mean by optimal English. As is, the English is of the native English speaker's comfy couch guides speaking to guides kind rather than guides speaking to audience wanting to be guided by. 

The suggestion I offered is imperfect and can be improved or rejected. As communication, it is shorter than the original and applies the dry principle, don't repeat yourself. Command occurs twice and the native English speaker may feel they are different in their senses. As sequence was in another suggestion for enhancement (and not a bug). 

You have your point of view which is from the internal technical guts of this language. I am approaching the language from the fun of Monty Python and imagery of a python pickled in a jar. I have done a few tutorials and read code with this reference guide as I would use a dictionary to explain words in a passage. I expect in a final stage of approval an editor ensures correctness of English to whatever the standard is.

----------

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

From report at bugs.python.org  Tue Oct 28 04:04:22 2014
From: report at bugs.python.org (Van Ly)
Date: Tue, 28 Oct 2014 03:04:22 +0000
Subject: [docs] [issue22738] improve  'python -h' documentation for '-c'
In-Reply-To: <1414384786.34.0.941168460328.issue22738@psf.upfronthosting.co.za>
Message-ID: <1414465462.26.0.916151802706.issue22738@psf.upfronthosting.co.za>


Van Ly added the comment:

> -c str   : interpret str as a program (terminates option list)

+1 (feed is shorter)

----------

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

From report at bugs.python.org  Tue Oct 28 05:44:29 2014
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 28 Oct 2014 04:44:29 +0000
Subject: [docs] [issue22748] Porting Extension Modules to Python 3
	documentation	mention about PyString_* functions in Python 3
Message-ID: <1414471469.41.0.545994852005.issue22748@psf.upfronthosting.co.za>


New submission from Berker Peksag:

"Porting Extension Modules to Python 3" document mention about "PyString_*" functions in Python 3. I think the correct prefix should be "PyUnicode_*".

>From https://docs.python.org/3/howto/cporting.html#str-unicode-unification:

    "Python 3?s str() (PyString_* functions in C) type is equivalent to Python 2?s unicode() (PyUnicode_*)."

----------
assignee: docs at python
components: Documentation
messages: 230119
nosy: benjamin.peterson, berker.peksag, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Porting Extension Modules to Python 3 documentation mention about PyString_* functions in Python 3
versions: Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue Oct 28 08:36:54 2014
From: report at bugs.python.org (Akira Li)
Date: Tue, 28 Oct 2014 07:36:54 +0000
Subject: [docs] [issue22749] remove obsolete remark in time.clock() docs
Message-ID: <1414481814.68.0.767829383037.issue22749@psf.upfronthosting.co.za>


New submission from Akira Li:

time.clock() documentation [1] says:

  this is the function to use for benchmarking Python or timing algorithms.

and

  Deprecated since version 3.3: The behaviour of this function depends on the platform: use perf_counter() or process_time() instead, depending on your requirements, to have a well defined behaviour.


[1]: https://hg.python.org/cpython/file/a22ef88143b9/Doc/library/time.rst#l127

The first remark is incorrect since 3.3. I've attached a documentation patch that removes it.

----------
assignee: docs at python
components: Documentation
files: docs-time-clock-remove-stale-remark.diff
keywords: patch
messages: 230124
nosy: akira, docs at python
priority: normal
severity: normal
status: open
title: remove obsolete remark in time.clock() docs
type: behavior
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file37048/docs-time-clock-remove-stale-remark.diff

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

From report at bugs.python.org  Tue Oct 28 09:17:39 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 28 Oct 2014 08:17:39 +0000
Subject: [docs] [issue22748] Porting Extension Modules to Python 3
	documentation	mention about PyString_* functions in Python 3
In-Reply-To: <1414471469.41.0.545994852005.issue22748@psf.upfronthosting.co.za>
Message-ID: <1414484259.48.0.00558374944247.issue22748@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Correct, there are no PyString_ functions in 3.x.

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

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

From report at bugs.python.org  Tue Oct 28 09:18:47 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 28 Oct 2014 08:18:47 +0000
Subject: [docs] [issue22749] remove obsolete remark in time.clock() docs
In-Reply-To: <1414481814.68.0.767829383037.issue22749@psf.upfronthosting.co.za>
Message-ID: <1414484327.04.0.247134490686.issue22749@psf.upfronthosting.co.za>


Georg Brandl added the comment:

LGTM.

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

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

From report at bugs.python.org  Tue Oct 28 09:23:39 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 28 Oct 2014 08:23:39 +0000
Subject: [docs] [issue22725] improve documentation for enumerate() (built-in
	function)
In-Reply-To: <1414208636.74.0.462392063973.issue22725@psf.upfronthosting.co.za>
Message-ID: <1414484618.99.0.598997299725.issue22725@psf.upfronthosting.co.za>


Georg Brandl added the comment:

rdm: your suggestion sounds good. Note that the argument name is "iterable" in Py3.

----------

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

From report at bugs.python.org  Tue Oct 28 09:25:29 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 28 Oct 2014 08:25:29 +0000
Subject: [docs] [issue22736] tutorial links at top,
	book recommendations at bottom of module documentation
In-Reply-To: <1414371822.19.0.713420749411.issue22736@psf.upfronthosting.co.za>
Message-ID: <1414484729.88.0.0625847465149.issue22736@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I agree, the "see also" box is better off near the bottom, probably before the examples.

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

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

From report at bugs.python.org  Tue Oct 28 10:14:04 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 28 Oct 2014 09:14:04 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414487644.62.0.565963447777.issue22153@psf.upfronthosting.co.za>


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


----------
nosy: +rbcollins
stage:  -> patch review
versions: +Python 2.7

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

From report at bugs.python.org  Tue Oct 28 11:52:31 2014
From: report at bugs.python.org (Martin Panter)
Date: Tue, 28 Oct 2014 10:52:31 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414493551.41.0.996653180163.issue22153@psf.upfronthosting.co.za>


Martin Panter added the comment:

The patch seems reasonable to me

----------

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

From report at bugs.python.org  Tue Oct 28 12:03:27 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 28 Oct 2014 11:03:27 +0000
Subject: [docs] [issue22232] str.splitlines splitting on non-\r\n characters
In-Reply-To: <1408528911.37.0.452679392827.issue22232@psf.upfronthosting.co.za>
Message-ID: <1414494206.96.0.777242154444.issue22232@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Looks like str.splitlines is using STRINGLIB_ISLINEBREAK which in turn uses Py_UNICODE_ISLINEBREAK, so the behavior should be correct.  If splitting on \n, \r, and \r\n only is common enough with might add a bool arg to splitlines to restrict the splitting on those 3 only, but I can't think about any good name for such arg.

----------

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

From report at bugs.python.org  Tue Oct 28 12:39:58 2014
From: report at bugs.python.org (Karmen Dykstra)
Date: Tue, 28 Oct 2014 11:39:58 +0000
Subject: [docs] [issue22196] namedtuple documentation could/should mention
	the new	Enum type
In-Reply-To: <1408030431.26.0.145305463203.issue22196@psf.upfronthosting.co.za>
Message-ID: <1414496398.17.0.129688071552.issue22196@psf.upfronthosting.co.za>


Karmen Dykstra added the comment:

Updated documentation with Enum example.

----------
keywords: +patch
nosy: +ezio.melotti, kdykstra
Added file: http://bugs.python.org/file37051/mywork.patch

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

From report at bugs.python.org  Tue Oct 28 13:00:33 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 12:00:33 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <20141028115859.69945.30885@psf.io>


Roundup Robot added the comment:

New changeset d44f7d229e00 by Ezio Melotti in branch '2.7':
#22237: document that sorted() is guaranteed to be stable.  Initial patch by Martin Panter.
https://hg.python.org/cpython/rev/d44f7d229e00

New changeset 5dd4906daa62 by Ezio Melotti in branch '3.4':
#22237: document that sorted() is guaranteed to be stable.  Initial patch by Martin Panter.
https://hg.python.org/cpython/rev/5dd4906daa62

New changeset b01568e2597e by Ezio Melotti in branch 'default':
#22237: merge with 3.4.
https://hg.python.org/cpython/rev/b01568e2597e

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

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

From report at bugs.python.org  Tue Oct 28 13:02:49 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 28 Oct 2014 12:02:49 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <1414497769.29.0.982295180369.issue22237@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

----------
assignee: rhettinger -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Oct 28 13:30:37 2014
From: report at bugs.python.org (anupama srinivas murthy)
Date: Tue, 28 Oct 2014 12:30:37 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
	documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1414499437.11.0.826070544898.issue22594@psf.upfronthosting.co.za>


anupama srinivas murthy added the comment:

I have modified the patch and listed the points I know. Could you review it?

----------
versions:  -Python 3.4, Python 3.5
Added file: http://bugs.python.org/file37052/regex-link.patch

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

From report at bugs.python.org  Tue Oct 28 13:35:12 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 28 Oct 2014 12:35:12 +0000
Subject: [docs] [issue22232] str.splitlines splitting on non-\r\n characters
In-Reply-To: <1408528911.37.0.452679392827.issue22232@psf.upfronthosting.co.za>
Message-ID: <1414499712.44.0.579976305143.issue22232@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

With Terry's explanation "linebreak" looks better to me. Yet one alternative is ascii=False (or unicode=True?). And may be worth to add this parameter to strip/rstrip/lstrip/split too. On other hand regular expressions can be used in such special cases.

----------

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

From report at bugs.python.org  Tue Oct 28 13:45:46 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 28 Oct 2014 12:45:46 +0000
Subject: [docs] [issue22232] str.splitlines splitting on non-\r\n characters
In-Reply-To: <1408528911.37.0.452679392827.issue22232@psf.upfronthosting.co.za>
Message-ID: <1414500346.84.0.398296708169.issue22232@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

There are some ascii line breaks other than \n, \r, \r\n.
unicode=True might be better, but might be confused with unicode strings.
Maybe unicode_linebreaks or unicode_newlines?

----------

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

From report at bugs.python.org  Tue Oct 28 14:00:13 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 13:00:13 +0000
Subject: [docs] [issue22237] sorted() docs should state that the sort is
	stable
In-Reply-To: <1408553630.26.0.335574291367.issue22237@psf.upfronthosting.co.za>
Message-ID: <20141028125940.58170.58378@psf.io>


Roundup Robot added the comment:

New changeset af8f678a4a75 by Ezio Melotti in branch '2.7':
#22237: fix patch attribution.
https://hg.python.org/cpython/rev/af8f678a4a75

New changeset 2f697bcc8f86 by Ezio Melotti in branch '3.4':
#22237: fix patch attribution.
https://hg.python.org/cpython/rev/2f697bcc8f86

New changeset 7e870ddd1989 by Ezio Melotti in branch 'default':
#22237: merge patch attribution fix.
https://hg.python.org/cpython/rev/7e870ddd1989

----------

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

From report at bugs.python.org  Tue Oct 28 14:16:18 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 28 Oct 2014 13:16:18 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414502178.6.0.201020563529.issue22153@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

IMO hiding the existence of `runTest` would be best. It doesn't seem to make anything more flexible, and it complicates the documentation.

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

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

From report at bugs.python.org  Tue Oct 28 14:26:44 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 28 Oct 2014 13:26:44 +0000
Subject: [docs] [issue22242] Doc fix in the Import section in language
	reference.
In-Reply-To: <1408632927.48.0.574934380183.issue22242@psf.upfronthosting.co.za>
Message-ID: <1414502804.59.0.501787640709.issue22242@psf.upfronthosting.co.za>


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


----------
nosy: +brett.cannon
stage:  -> patch review

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

From report at bugs.python.org  Tue Oct 28 14:39:45 2014
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 28 Oct 2014 13:39:45 +0000
Subject: [docs] [issue22242] Doc fix in the Import section in language
	reference.
In-Reply-To: <1408632927.48.0.574934380183.issue22242@psf.upfronthosting.co.za>
Message-ID: <1414503585.32.0.566287094919.issue22242@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> brett.cannon

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

From report at bugs.python.org  Tue Oct 28 15:08:08 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 14:08:08 +0000
Subject: [docs] [issue22196] namedtuple documentation could/should mention
	the new	Enum type
In-Reply-To: <1408030431.26.0.145305463203.issue22196@psf.upfronthosting.co.za>
Message-ID: <20141028140727.36696.39733@psf.io>


Roundup Robot added the comment:

New changeset 2e3521e79d93 by Ezio Melotti in branch 'default':
#22196: link to Enum in the nametuple documentation.  Patch by Karmen Dykstra.
https://hg.python.org/cpython/rev/2e3521e79d93

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

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

From report at bugs.python.org  Tue Oct 28 15:18:05 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 14:18:05 +0000
Subject: [docs] [issue22196] namedtuple documentation could/should mention
	the new	Enum type
In-Reply-To: <1408030431.26.0.145305463203.issue22196@psf.upfronthosting.co.za>
Message-ID: <20141028141616.14368.34965@psf.io>


Roundup Robot added the comment:

New changeset 701529f8ca93 by Ezio Melotti in branch '3.4':
#22196: link to Enum in the nametuple documentation.  Patch by Karmen Dykstra.
https://hg.python.org/cpython/rev/701529f8ca93

----------

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

From report at bugs.python.org  Tue Oct 28 15:19:42 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 28 Oct 2014 14:19:42 +0000
Subject: [docs] [issue22232] str.splitlines splitting on non-\r\n characters
In-Reply-To: <1408528911.37.0.452679392827.issue22232@psf.upfronthosting.co.za>
Message-ID: <1414505982.13.0.698857804794.issue22232@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

See also issue18236.

----------

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

From report at bugs.python.org  Tue Oct 28 15:29:38 2014
From: report at bugs.python.org (Jakub Wilk)
Date: Tue, 28 Oct 2014 14:29:38 +0000
Subject: [docs] [issue22232] str.splitlines splitting on non-\r\n characters
In-Reply-To: <1408528911.37.0.452679392827.issue22232@psf.upfronthosting.co.za>
Message-ID: <1414506578.18.0.512705078994.issue22232@psf.upfronthosting.co.za>


Changes by Jakub Wilk <jwilk at jwilk.net>:


----------
nosy: +jwilk

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

From report at bugs.python.org  Tue Oct 28 15:45:43 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 28 Oct 2014 14:45:43 +0000
Subject: [docs] [issue22196] namedtuple documentation could/should mention
	the new	Enum type
In-Reply-To: <1408030431.26.0.145305463203.issue22196@psf.upfronthosting.co.za>
Message-ID: <1414507543.67.0.0844965823496.issue22196@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

----------
assignee: rhettinger -> ezio.melotti
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type:  -> enhancement
versions: +Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue Oct 28 21:35:51 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 20:35:51 +0000
Subject: [docs] [issue22749] remove obsolete remark in time.clock() docs
In-Reply-To: <1414481814.68.0.767829383037.issue22749@psf.upfronthosting.co.za>
Message-ID: <20141028203548.58162.91505@psf.io>


Roundup Robot added the comment:

New changeset 5f086db3b51b by Georg Brandl in branch '3.4':
Closes #22749: remove outdated advice to use clock() for accurate timing.
https://hg.python.org/cpython/rev/5f086db3b51b

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Oct 28 21:39:37 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 20:39:37 +0000
Subject: [docs] [issue22748] Porting Extension Modules to Python 3
	documentation	mention about PyString_* functions in Python 3
In-Reply-To: <1414471469.41.0.545994852005.issue22748@psf.upfronthosting.co.za>
Message-ID: <20141028203859.104872.28954@psf.io>


Roundup Robot added the comment:

New changeset 9141199800fe by Georg Brandl in branch '3.4':
Closes #22748: there are no PyString C functions in 3.x.
https://hg.python.org/cpython/rev/9141199800fe

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Oct 28 21:42:20 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 20:42:20 +0000
Subject: [docs] [issue22736] tutorial links at top,
	book recommendations at bottom of module documentation
In-Reply-To: <1414371822.19.0.713420749411.issue22736@psf.upfronthosting.co.za>
Message-ID: <20141028204204.104876.62127@psf.io>


Roundup Robot added the comment:

New changeset 4ad8b11ca309 by Georg Brandl in branch '3.4':
Closes #22736: move seealso to the bottom of the section about RE syntax.
https://hg.python.org/cpython/rev/4ad8b11ca309

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Oct 28 22:19:33 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 21:19:33 +0000
Subject: [docs] [issue22748] Porting Extension Modules to Python 3
	documentation	mention about PyString_* functions in Python 3
In-Reply-To: <1414471469.41.0.545994852005.issue22748@psf.upfronthosting.co.za>
Message-ID: <20141028211921.58152.50826@psf.io>


Roundup Robot added the comment:

New changeset 18f346abdfbe by Georg Brandl in branch '2.7':
Closes #22748: there are no PyString C functions in 3.x.
https://hg.python.org/cpython/rev/18f346abdfbe

----------

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

From report at bugs.python.org  Tue Oct 28 22:19:33 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 21:19:33 +0000
Subject: [docs] [issue22736] tutorial links at top,
	book recommendations at bottom of module documentation
In-Reply-To: <1414371822.19.0.713420749411.issue22736@psf.upfronthosting.co.za>
Message-ID: <20141028211924.58152.52514@psf.io>


Roundup Robot added the comment:

New changeset 465892bb0c12 by Georg Brandl in branch '2.7':
Closes #22736: move seealso to the bottom of the section about RE syntax.
https://hg.python.org/cpython/rev/465892bb0c12

----------

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

From report at bugs.python.org  Tue Oct 28 22:46:14 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 21:46:14 +0000
Subject: [docs] [issue22249] Possibly incorrect example is given
	for	socket.getaddrinfo()
In-Reply-To: <1408707808.63.0.0809888327352.issue22249@psf.upfronthosting.co.za>
Message-ID: <20141028214608.120914.5265@psf.io>


Roundup Robot added the comment:

New changeset 5611c7c20460 by Georg Brandl in branch '3.4':
Closes #22249: use IPPROTO_TCP constant instead of SOL_TCP constant for getaddrinfo() proto param
https://hg.python.org/cpython/rev/5611c7c20460

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Oct 28 22:47:33 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Oct 2014 21:47:33 +0000
Subject: [docs] [issue22249] Possibly incorrect example is given
	for	socket.getaddrinfo()
In-Reply-To: <1408707808.63.0.0809888327352.issue22249@psf.upfronthosting.co.za>
Message-ID: <20141028214721.120894.47301@psf.io>


Roundup Robot added the comment:

New changeset 999e72ed3fbc by Georg Brandl in branch '2.7':
Closes #22249: use IPPROTO_TCP constant instead of SOL_TCP constant for getaddrinfo() proto param
https://hg.python.org/cpython/rev/999e72ed3fbc

----------

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

From report at bugs.python.org  Tue Oct 28 22:48:57 2014
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 28 Oct 2014 21:48:57 +0000
Subject: [docs] [issue22305] Documentation on deepcopy's problems is
	misleading
In-Reply-To: <1409384500.34.0.359700008646.issue22305@psf.upfronthosting.co.za>
Message-ID: <1414532937.51.0.348601062366.issue22305@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Oct 28 22:57:20 2014
From: report at bugs.python.org (Martin Panter)
Date: Tue, 28 Oct 2014 21:57:20 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414533440.13.0.80113365323.issue22153@psf.upfronthosting.co.za>


Martin Panter added the comment:

Do you mean pretending there is no default ?methodName? value, or pretending that the runTest() method is not invoked by discovery?

I would have to check, but I think I have relied on the runTest() method being discovered in the past, when I did not think a more original test method name was useful. Though I agree that it makes the behaviour more complicated for little extra flexibility.

----------

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

From report at bugs.python.org  Tue Oct 28 23:01:05 2014
From: report at bugs.python.org (Robert Collins)
Date: Tue, 28 Oct 2014 22:01:05 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414533665.94.0.21228179785.issue22153@psf.upfronthosting.co.za>


Robert Collins added the comment:

runTest is part of the current API. I think if we're going to hide it we should do so as part of a deprecation path. (I'm +1 on hiding it).

----------

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

From report at bugs.python.org  Tue Oct 28 23:06:08 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 28 Oct 2014 22:06:08 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1414533665.94.0.21228179785.issue22153@psf.upfronthosting.co.za>
Message-ID: <5450134E.4020306@free.fr>


Antoine Pitrou added the comment:

Le 28/10/2014 23:01, Robert Collins a ?crit :
> 
> runTest is part of the current API. I think if we're going to hide
> it
we should do so as part of a deprecation path. (I'm +1 on hiding it).

We don't need a deprecation path to remove something from the
documentation, IMO. It wouldn't break any existing code, it would just
reduce the cognitive load for newcomers.

(and, while people may have chosen to use runTest, it doesn't mean they
need it in any way)

----------

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

From report at bugs.python.org  Tue Oct 28 23:40:52 2014
From: report at bugs.python.org (Martijn Pieters)
Date: Tue, 28 Oct 2014 22:40:52 +0000
Subject: [docs] [issue22755] contextlib.closing documentation should use a
	new example
Message-ID: <1414536052.52.0.0865505363528.issue22755@psf.upfronthosting.co.za>


New submission from Martijn Pieters:

urllib.request.urlopen() now always produces a context manager (either a HTTPResponse or addinfourl object). The example for contextlib.closing still uses urllib.request.urlopen as an example for the context manager wrapper, see

    https://docs.python.org/3/library/contextlib.html#contextlib.closing

This is confusing users that now expect the object not to be a context manager, see:

    http://stackoverflow.com/questions/26619404/with-and-closing-of-files-in-python

Can a different example be chosen?

----------
assignee: docs at python
components: Documentation
messages: 230184
nosy: docs at python, mjpieters
priority: normal
severity: normal
status: open
title: contextlib.closing documentation should use a new example
versions: Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Wed Oct 29 00:02:16 2014
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 28 Oct 2014 23:02:16 +0000
Subject: [docs] [issue22755] contextlib.closing documentation should use a
	new example
In-Reply-To: <1414536052.52.0.0865505363528.issue22755@psf.upfronthosting.co.za>
Message-ID: <1414537336.35.0.681459274445.issue22755@psf.upfronthosting.co.za>


Andrew Barnert added the comment:

It may be pretty hard to come up with a good example for closing in the stdlib that shouldn't just be turned into a context manager? 

There are some types where using it in a with statement is sensible, but unusual enough that you might want to make it explicit (maybe logging.Handler?), but does that make a good example?

----------
nosy: +abarnert

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

From report at bugs.python.org  Wed Oct 29 00:07:44 2014
From: report at bugs.python.org (Martin Panter)
Date: Tue, 28 Oct 2014 23:07:44 +0000
Subject: [docs] [issue22755] contextlib.closing documentation should use a
	new example
In-Reply-To: <1414536052.52.0.0865505363528.issue22755@psf.upfronthosting.co.za>
Message-ID: <1414537664.92.0.607272303186.issue22755@psf.upfronthosting.co.za>


Martin Panter added the comment:

One exception that comes to mind is generators. According to Issue 13814, it is deliberate that you have to call close(), so perhaps someone could come up with an example based on that.

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

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

From report at bugs.python.org  Wed Oct 29 00:22:50 2014
From: report at bugs.python.org (Martin Panter)
Date: Tue, 28 Oct 2014 23:22:50 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414538570.07.0.119124123657.issue22153@psf.upfronthosting.co.za>


Martin Panter added the comment:

Removing stuff from the documentation would make it hard to understand what existing code means that uses runTest(). Isn?t this a case where you would add a big red ?Deprecated since version . . .? warning instead? Maybe a comprimise would be to ?hide? its documentation away in a separate deprecated section or something.

----------

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

From report at bugs.python.org  Wed Oct 29 01:16:45 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 29 Oct 2014 00:16:45 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1414538570.07.0.119124123657.issue22153@psf.upfronthosting.co.za>
Message-ID: <545031EB.1020507@free.fr>


Antoine Pitrou added the comment:

Le 29/10/2014 00:22, Martin Panter a ?crit :
> 
> Martin Panter added the comment:
> 
> Removing stuff from the documentation would make it hard to
> understand
what existing code means that uses runTest(). Isn?t this a case where
you would add a big red ?Deprecated since version . . .? warning
instead? Maybe a comprimise would be to ?hide? its documentation away in
a separate deprecated section or something.

Well, I wasn't proposing a deprecation (although that can be done as
well, if we want). I was proposing that this detail be hidden. I don't
know if it would make existing software harder to understand. I don't
think I've ever seen an actively-maintained project that used runTest().

The simple way to hide it would be to stop documenting the TestCase
constructor and its signature. You aren't supposed to instantiate
TestCase yourself.

----------

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

From report at bugs.python.org  Wed Oct 29 01:25:21 2014
From: report at bugs.python.org (Robert Collins)
Date: Wed, 29 Oct 2014 00:25:21 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414542321.71.0.231790273281.issue22153@psf.upfronthosting.co.za>


Robert Collins added the comment:

Constructing test case objects directly is part of the protocol, and its needed for framework and extension authors.

I've seen folk use runTest, but rarely enough that I think we could deprecate it. My argument is that while its supported we should be clear about when it should be used, and how.

----------

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

From report at bugs.python.org  Wed Oct 29 19:50:59 2014
From: report at bugs.python.org (Robert Collins)
Date: Wed, 29 Oct 2014 18:50:59 +0000
Subject: [docs] [issue22153] There is no standard TestCase.runTest
	implementation
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414608659.39.0.42487911104.issue22153@psf.upfronthosting.co.za>


Robert Collins added the comment:

Oh, one thought - in testtools we split out 'docs for test writers' and 'docs for framework folk'. That would facilitate getting runTest out of test writers face while still documenting it appropriately.

Related to that is my ongoing push to split the protocol so that these concerns are not intertwined the way they are today, but that needs to wait for the existing backlog to clear up :)

----------

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

From report at bugs.python.org  Wed Oct 29 20:00:06 2014
From: report at bugs.python.org (Robert Collins)
Date: Wed, 29 Oct 2014 19:00:06 +0000
Subject: [docs] [issue22153] Documentation of TestCase.runTest is incorrect
	and	confusing
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414609206.49.0.212388600462.issue22153@psf.upfronthosting.co.za>


Changes by Robert Collins <robertc at robertcollins.net>:


----------
title: There is no standard TestCase.runTest implementation -> Documentation of TestCase.runTest is incorrect and confusing

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

From cwalker343 at yahoo.com  Wed Oct 29 14:21:27 2014
From: cwalker343 at yahoo.com (Charles Walker)
Date: Wed, 29 Oct 2014 06:21:27 -0700
Subject: [docs] Volunteer for documentation
Message-ID: <1414588887.22776.YahooMailNeo@web161804.mail.bf1.yahoo.com>

I'm a technical writer looking for work, and would like to do some documentation to keep my hand in, and to say I'm still active in my resume.

I've been a tech writer for about 20 years. Most of my work has been documenting microprocessors and other hardware, but I've done software documentation (database, compiler, utilities, and some enduser) as well.

I've just started learning Python, mostly using Zed Shaw's Learn Python the Hard Way and I thought volunteering for a documentation project in Python would be good both to strengthen my knowledge and to help you out. I'm not familiar with the online Python resources yet, but I have looked at the reStructuredText page and it looks like yet another markup language, so I should have no problem in working with it.

I look forward to hearing from you about how I may be of assistance. I don't currently have any preferences in what sort of documentation I'd work in. I'm used to doing what needs doing.

Charles Walker
cwalker343 at yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20141029/6146f4c7/attachment.html>

From robertc at robertcollins.net  Wed Oct 29 19:48:17 2014
From: robertc at robertcollins.net (robertc at robertcollins.net)
Date: Wed, 29 Oct 2014 18:48:17 -0000
Subject: [docs] There is no standard TestCase.runTest implementation (issue
	22153)
Message-ID: <20141029184817.29089.39878@psf.upfronthosting.co.za>

Looks fine to me - discussion is still simmering on the issue, will
commit once it settles down (assuming no changes needed by then).

http://bugs.python.org/review/22153/

From zachary.ware+pydocs at gmail.com  Wed Oct 29 21:39:10 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 29 Oct 2014 15:39:10 -0500
Subject: [docs] Volunteer for documentation
In-Reply-To: <1414588887.22776.YahooMailNeo@web161804.mail.bf1.yahoo.com>
References: <1414588887.22776.YahooMailNeo@web161804.mail.bf1.yahoo.com>
Message-ID: <CAKJDb-NFGFN4xHw9BYm88+LAYzADLoXf7k7UJ7rdU=3ZnREobA@mail.gmail.com>

Hi Charles,

On Wed, Oct 29, 2014 at 8:21 AM, Charles Walker
<cwalker343 at yahoo.com.dmarc.invalid> wrote:
> I look forward to hearing from you about how I may be of assistance. I don't
> currently have any preferences in what sort of documentation I'd work in.
> I'm used to doing what needs doing.

There are very few parts of Python that are completely undocumented,
but there are several places that need some amount of tweaking.  The
'Bugs' page of the documentation[1] should have enough information to
get you started; if not, improving the Bugs page is a good place to
get started ;).

If you're looking for a larger project, and especially if you're
familiar with C, all of the C-API documentation ("Extending and
Embedding" and "Python/C API") needs a thorough going-over to make
sure things actually make sense for Python 3 (checking that all
examples work, making sure everything is documented, making sure what
is documented is actually correct anymore, etc).  I'm not sure if
there's any specific open issue for that, but I suspect there are
probably several issues relating to some part of that overall need.

There are also a few tools available to help find things that need
fixing, including the "coverage", "linkcheck", "suspicious", and
"doctest" builders for Sphinx (see Doc/readme.txt).

And, of course, there's always the option of just reading whatever
strikes your fancy and keeping track of any problems you find in it.

Any questions you have, feel free to ask here on docs@ (for
documentation-related questions), or on the core-mentorship list (for
pretty much anything else).

I hope I've been of some help, and welcome to Python!
-- 
Zach

[1] https://docs.python.org/3/bugs.html

From report at bugs.python.org  Fri Oct 31 00:53:52 2014
From: report at bugs.python.org (Robert Collins)
Date: Thu, 30 Oct 2014 23:53:52 +0000
Subject: [docs] [issue22153] Documentation of TestCase.runTest is incorrect
	and	confusing
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414713232.79.0.166629849342.issue22153@psf.upfronthosting.co.za>


Robert Collins added the comment:

I'll apply the patch monday if there are no further comments before then.

----------

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

From report at bugs.python.org  Fri Oct 31 09:27:23 2014
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 31 Oct 2014 08:27:23 +0000
Subject: [docs] [issue22539] Table formatting errors in pydoc
In-Reply-To: <1412249910.15.0.577492255731.issue22539@psf.upfronthosting.co.za>
Message-ID: <1414744043.62.0.207367609437.issue22539@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Couldn't reproduce in 3.4.2.

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

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

From report at bugs.python.org  Fri Oct 31 10:39:47 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 31 Oct 2014 09:39:47 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <20141031093938.109282.24284@psf.io>


Roundup Robot added the comment:

New changeset f72271f05ea4 by Georg Brandl in branch '3.4':
#22613: fix several factual errors in builtin docs (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/f72271f05ea4

New changeset 5faee3db42a7 by Georg Brandl in branch '3.4':
#22613: explain what "buffer" is in the struct documentation (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/5faee3db42a7

New changeset 7d40eff70601 by Georg Brandl in branch '3.4':
#22613: elaborate on arguments of shutil archival functions (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/7d40eff70601

New changeset 307fd58b9694 by Georg Brandl in branch '3.4':
#22613: fix heading levels in tracemalloc docs (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/307fd58b9694

New changeset 0a217d3d581c by Georg Brandl in branch '3.4':
#22613: document Cmd.cmdqueue (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/0a217d3d581c

New changeset 4089047475c5 by Georg Brandl in branch '3.4':
#22613: minor other fixes in library docs (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/4089047475c5

New changeset 53048571de47 by Georg Brandl in branch '3.4':
#22613: remaining corrections in extending/reference docs (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/53048571de47

----------

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

From report at bugs.python.org  Fri Oct 31 10:43:16 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 31 Oct 2014 09:43:16 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <20141031094310.120708.19918@psf.io>


Roundup Robot added the comment:

New changeset 60c6dc1b316f by Georg Brandl in branch '2.7':
#22613: document Cmd.cmdqueue (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/60c6dc1b316f

New changeset d3fd218ef2cf by Georg Brandl in branch '2.7':
#22613: minor other fixes in library docs (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/d3fd218ef2cf

New changeset 9e57654dfdcc by Georg Brandl in branch '2.7':
#22613: fix several factual errors in builtin docs (thanks Jacques Ducasse)
https://hg.python.org/cpython/rev/9e57654dfdcc

----------

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

From report at bugs.python.org  Fri Oct 31 10:43:33 2014
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 31 Oct 2014 09:43:33 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <1414748613.49.0.474504491143.issue22613@psf.upfronthosting.co.za>


Georg Brandl added the comment:

All remaining points have been fixed.

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

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

From georg at python.org  Fri Oct 31 10:46:07 2014
From: georg at python.org (Georg Brandl)
Date: Fri, 31 Oct 2014 10:46:07 +0100
Subject: [docs] your list of docs errors
Message-ID: <54535A5F.7060304@python.org>

Hi Jacques,

many thanks for your very detailed list of issues in the docs.
I've fixed all of the remaining issues, using many of your suggestions,
and they should be in the online version soon.

cheers,
Georg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/docs/attachments/20141031/4f5f0f65/attachment.sig>

From report at bugs.python.org  Fri Oct 31 10:52:56 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 31 Oct 2014 09:52:56 +0000
Subject: [docs] [issue22613] Several minor doc issues
In-Reply-To: <1413065843.62.0.682552430945.issue22613@psf.upfronthosting.co.za>
Message-ID: <1414749176.73.0.805150195266.issue22613@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 31 13:02:27 2014
From: report at bugs.python.org (Lorenz Quack)
Date: Fri, 31 Oct 2014 12:02:27 +0000
Subject: [docs] [issue22772] doc error in __ifloordiv__ and __itruediv__
Message-ID: <1414756946.98.0.846704461281.issue22772@psf.upfronthosting.co.za>


New submission from Lorenz Quack:

the doc string of __itruediv__ and __ifloordiv__ represent the operator as x/y and x//y respectively.
This is obviously false and should be x/=y and x//=y

patch attached

----------
assignee: docs at python
components: Documentation
files: inplace_div_doc.patch
keywords: patch
messages: 230337
nosy: docs at python, donlorenzo
priority: normal
severity: normal
status: open
title: doc error in __ifloordiv__ and __itruediv__
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file37083/inplace_div_doc.patch

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

From report at bugs.python.org  Fri Oct 31 13:13:31 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 31 Oct 2014 12:13:31 +0000
Subject: [docs] [issue22772] doc error in __ifloordiv__ and __itruediv__
In-Reply-To: <1414756946.98.0.846704461281.issue22772@psf.upfronthosting.co.za>
Message-ID: <20141031121316.101670.62528@psf.io>


Roundup Robot added the comment:

New changeset 147518a95b60 by Georg Brandl in branch '3.4':
Closes #22772: fix __ifloordiv__ and __itruediv__ docstring.
https://hg.python.org/cpython/rev/147518a95b60

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Oct 31 13:13:46 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 31 Oct 2014 12:13:46 +0000
Subject: [docs] [issue22772] doc error in __ifloordiv__ and __itruediv__
In-Reply-To: <1414756946.98.0.846704461281.issue22772@psf.upfronthosting.co.za>
Message-ID: <20141031121345.120728.76560@psf.io>


Roundup Robot added the comment:

New changeset 3f13f1620d70 by Georg Brandl in branch '2.7':
Closes #22772: fix __ifloordiv__ and __itruediv__ docstring.
https://hg.python.org/cpython/rev/3f13f1620d70

----------

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

From ezio.melotti at gmail.com  Fri Oct 31 18:00:26 2014
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Fri, 31 Oct 2014 17:00:26 -0000
Subject: [docs] There is no standard TestCase.runTest implementation
	(issue 22153)
Message-ID: <20141031170026.21625.82230@psf.upfronthosting.co.za>


http://bugs.python.org/review/22153/diff/12734/Doc/library/unittest.rst
File Doc/library/unittest.rst (right):

http://bugs.python.org/review/22153/diff/12734/Doc/library/unittest.rst#newcode657
Doc/library/unittest.rst:657: In most uses of :class:`TestCase`, you
will neither change
This line is indented wrong.

http://bugs.python.org/review/22153/diff/12734/Doc/library/unittest.rst#newcode1561
Doc/library/unittest.rst:1561: If no methods with the usual name prefix
are found, but the ``runTest()`` method is implemented, there will be a
single test case using that method.
This line is too long, and also not too clear to me.
What is the usual name prefix? "test_"?
Does "a single test case" refers to *testCaseClass*?  What are test
cases should use runTest? What does "using" mean here?

http://bugs.python.org/review/22153/

From report at bugs.python.org  Fri Oct 31 17:55:48 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 31 Oct 2014 16:55:48 +0000
Subject: [docs] [issue22153] Documentation of TestCase.runTest is incorrect
	and	confusing
In-Reply-To: <1407301202.17.0.719208246986.issue22153@psf.upfronthosting.co.za>
Message-ID: <1414774548.44.0.253390588138.issue22153@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> Oh, one thought - in testtools we split out 'docs for test writers' and
> 'docs for framework folk'. That would facilitate getting runTest out of
> test writers face while still documenting it appropriately.

This has already been discussed in the past, and IIRC there was consensus about giving unittest docs the same treatment.  I don't remember if there was an issue for this.

----------

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

From ezio.melotti at gmail.com  Fri Oct 31 19:11:00 2014
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Fri, 31 Oct 2014 18:11:00 -0000
Subject: [docs] Add a link to the regex module in re documentation (issue
	22594)
Message-ID: <20141031181100.18984.83081@psf.upfronthosting.co.za>


http://bugs.python.org/review/22594/diff/13149/Doc/library/re.rst
File Doc/library/re.rst (right):

http://bugs.python.org/review/22594/diff/13149/Doc/library/re.rst#newcode47
Doc/library/re.rst:47: regex
Maybe this could be 'The "regex" module on PyPI'.

http://bugs.python.org/review/22594/diff/13149/Doc/library/re.rst#newcode48
Doc/library/re.rst:48: This is an alternative regular expressions module
with the following additional features among others in it's Version 1:
s/it's/its/ even though you might omit the last part, since it wasn't
obvious to me what Version 1 was before reading the PyPI page.

Maybe it should be mentioned somewhere that it's supposed to be a
drop-in replacement, with a mostly compatible API.

http://bugs.python.org/review/22594/diff/13149/Doc/library/re.rst#newcode50
Doc/library/re.rst:50: This occurs when the pattern consists only of
lookarounds,anchors or boundaries
Space after the comma, and additional comma after anchors.

http://bugs.python.org/review/22594/diff/13149/Doc/library/re.rst#newcode54
Doc/library/re.rst:54: * Full case folding support is enabled for
Unicode format
Only the first list element ends with a full-stop.  Either all or none
should have it.

These lines are also too long.

http://bugs.python.org/review/22594/

From report at bugs.python.org  Fri Oct 31 19:47:29 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 31 Oct 2014 18:47:29 +0000
Subject: [docs] [issue22581] Other mentions of the buffer protocol
In-Reply-To: <1412785100.97.0.773176507587.issue22581@psf.upfronthosting.co.za>
Message-ID: <1414781249.53.0.976388708404.issue22581@psf.upfronthosting.co.za>


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


----------
type:  -> enhancement
versions: +Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Oct 31 20:08:28 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 31 Oct 2014 19:08:28 +0000
Subject: [docs] [issue16518] add "buffer protocol" to glossary
In-Reply-To: <1353477807.87.0.204584648831.issue16518@psf.upfronthosting.co.za>
Message-ID: <1414782508.75.0.578306209289.issue16518@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

See #22581.

----------

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