From report at bugs.python.org  Thu Sep  1 14:13:57 2016
From: report at bugs.python.org (Jason R. Coombs)
Date: Thu, 01 Sep 2016 18:13:57 +0000
Subject: [docs] [issue901727] extra_path kwarg to setup() undocumented
Message-ID: <1472753637.27.0.325999872851.issue901727@psf.upfronthosting.co.za>


Jason R. Coombs added the comment:

Given the progression in issue27919, I suggest this documentation effort can be dropped, but feel free to revive the conversation if you disagree.

----------
nosy: +jason.coombs
resolution:  -> wont fix
status: open -> closed

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

From report at bugs.python.org  Fri Sep  2 00:09:02 2016
From: report at bugs.python.org (Lisa Roach)
Date: Fri, 02 Sep 2016 04:09:02 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1472789342.47.0.227364470824.issue27779@psf.upfronthosting.co.za>


Lisa Roach added the comment:

I will start working on the patch for this!

Thanks for pointing me this way, Raymond.

----------
nosy: +lisroach

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

From report at bugs.python.org  Fri Sep  2 05:51:25 2016
From: report at bugs.python.org (Stefan Krah)
Date: Fri, 02 Sep 2016 09:51:25 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1472809885.4.0.420565977985.issue27779@psf.upfronthosting.co.za>


Stefan Krah added the comment:

"hand written signatures" refers to the signatures that Argument Clinic would generate if it were used (but I don't want that).

So this is an example of a hand written signature:

    "is_infinite($self, /)\n--\n\n\"


I still wonder if people wouldn't be served better with concise docstrings, but then I'm generally in favor of a Unix manual page documentation style, so perhaps there's a cultural difference.

----------

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

From report at bugs.python.org  Fri Sep  2 16:17:03 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 02 Sep 2016 20:17:03 +0000
Subject: [docs] [issue27905] Add documentation for typing.Type
In-Reply-To: <1472593880.19.0.114422348142.issue27905@psf.upfronthosting.co.za>
Message-ID: <1472847423.55.0.153529100773.issue27905@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

Michael, thank you for helping with this!
Please take a look at my comments on the patch.

----------
nosy: +levkivskyi

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

From report at bugs.python.org  Fri Sep  2 17:09:51 2016
From: report at bugs.python.org (Jaroslav)
Date: Fri, 02 Sep 2016 21:09:51 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1472850591.49.0.357181901014.issue27902@psf.upfronthosting.co.za>


Jaroslav added the comment:

The paragraph is ok.

I'll open. Thanks a lot.

----------

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

From report at bugs.python.org  Sat Sep  3 00:38:19 2016
From: report at bugs.python.org (Zachary Ware)
Date: Sat, 03 Sep 2016 04:38:19 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1472877499.27.0.457230237049.issue19489@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Berker, would you mind giving this another look?  If you give it the OK, I can get it committed if you don't beat me to it.

----------
assignee: docs at python -> berker.peksag

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

From report at bugs.python.org  Sat Sep  3 08:33:47 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 03 Sep 2016 12:33:47 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1472906027.05.0.638523456241.issue19489@psf.upfronthosting.co.za>


Berker Peksag added the comment:

> Do you mean in addition to the "Quick search" text that is already on the page or do you want to remove that?

The latter. All of the popular browsers (Chrome, Firefox, Edge and even Safari) already support the placeholder attribute so I think we can safely ignore IE 8 :)

> What problems are you thinking of?

Honestly, I can't remember now, but I was talking about old Chrome and Firefox versions. Let's ignore my comment for now.

I have two more minor comments:

1. +    <div class="inline-search" style="display: none" role="search">

   I know this is basically a copy of upstream searchbox.html, but we can probably remove ``style="display: none"`` and ``$('.inline-search').show(0);``.

2. +    <li class="right inline-search">

   inline-search doesn't seem to be necessary here. ``display: inline`` is already applied by ``div.related li``.

I also found a regression in search.html. It doesn't show or highlight the search
words provided in the URL. Try the following URL to reproduce the problem: https://docs.python.org/dev/search.html?q=append

Screenshot from docs.python.org: https://dl.dropboxusercontent.com/u/166024/highlight-docs.pyo.png

Screenshor from my local copy with searchbar_in_header.diff3 applied: https://dl.dropboxusercontent.com/u/166024/highlight-after.png

----------

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

From report at bugs.python.org  Sat Sep  3 10:44:33 2016
From: report at bugs.python.org (Xiang Zhang)
Date: Sat, 03 Sep 2016 14:44:33 +0000
Subject: [docs] [issue27949] Fix description in bytes literal doc
Message-ID: <1472913873.18.0.202721343298.issue27949@psf.upfronthosting.co.za>


New submission from Xiang Zhang:

This sentence "bytes with a numeric value of 128 or greater must be expressed with escapes" is wrong and not complete. The value needs to be escaped is >= 127 and < 32.

----------
assignee: docs at python
components: Documentation
files: lexical_bytes_literal.patch
keywords: patch
messages: 274297
nosy: docs at python, xiang.zhang
priority: normal
severity: normal
status: open
title: Fix description in bytes literal doc
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file44354/lexical_bytes_literal.patch

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

From report at bugs.python.org  Sat Sep  3 10:54:45 2016
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 03 Sep 2016 14:54:45 +0000
Subject: [docs] [issue27949] Fix description in bytes literal doc
In-Reply-To: <1472913873.18.0.202721343298.issue27949@psf.upfronthosting.co.za>
Message-ID: <1472914485.77.0.386457290578.issue27949@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

While they probably should be entered with escapes, there's no actual technical requirement for that.

>From the command line, I can enter a control-A with control-V control-A (this might be different depending on your environment, or if you use an editor). This will enter a literal string containing a single character with value 1.

That gives:

>>> '^A'     # ^A is the combination control-V control-A
'\x01'
>>> len('^A')
1
>>> ord('^A')
1
>>> b'^A'
b'\x01'

----------
nosy: +eric.smith

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

From report at bugs.python.org  Sat Sep  3 11:01:23 2016
From: report at bugs.python.org (Xiang Zhang)
Date: Sat, 03 Sep 2016 15:01:23 +0000
Subject: [docs] [issue27949] Fix description in bytes literal doc
In-Reply-To: <1472913873.18.0.202721343298.issue27949@psf.upfronthosting.co.za>
Message-ID: <1472914883.91.0.906896080372.issue27949@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

Ooh, sorry. It seems I misunderstand the meaning of the sentence. I understand the value as the output of repr, I mean b'\x01'. It means how it's created.

Thanks for your reply and sorry for the noise. I close this then.

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

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

From report at bugs.python.org  Sat Sep  3 11:06:20 2016
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 03 Sep 2016 15:06:20 +0000
Subject: [docs] [issue27949] Fix description in bytes literal doc
In-Reply-To: <1472913873.18.0.202721343298.issue27949@psf.upfronthosting.co.za>
Message-ID: <1472915180.01.0.822211321796.issue27949@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

No problem! Thanks for caring enough to open an issue and submit a patch, even if we don't use it.

----------
stage:  -> resolved

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

From report at bugs.python.org  Sat Sep  3 12:14:34 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 03 Sep 2016 16:14:34 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1472919274.19.0.811846014135.issue19489@psf.upfronthosting.co.za>


Berker Peksag added the comment:

> I also found a regression in search.html.

Please ignore this. It doesn't have anything to do with your patch.

----------

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

From levkivskyi at gmail.com  Fri Sep  2 16:16:00 2016
From: levkivskyi at gmail.com (levkivskyi at gmail.com)
Date: Fri, 02 Sep 2016 20:16:00 -0000
Subject: [docs] Add documentation for typing.Type (issue 27905)
Message-ID: <20160902201600.14790.73334@psf.upfronthosting.co.za>


http://bugs.python.org/review/27905/diff/18277/Doc/library/typing.rst
File Doc/library/typing.rst (right):

http://bugs.python.org/review/27905/diff/18277/Doc/library/typing.rst#newcode507
Doc/library/typing.rst:507: A variable of type ``Type[C]`` represents
the class object of some object
I would formulate this a bit longer:

A variable annotated with ``C`` can take values that have type ``C``. In
contrast a variable annotated with ``Type[C]`` can take values that are
classes themselves, namely subclasses of ``C``::

http://bugs.python.org/review/27905/diff/18277/Doc/library/typing.rst#newcode511
Doc/library/typing.rst:511: b = type(a)   # Has type 'Type[int]'
I would replace with simply b = int

http://bugs.python.org/review/27905/diff/18277/Doc/library/typing.rst#newcode533
Doc/library/typing.rst:533: It is also legal to use a union of classes
as the parameter to ``Type``::
Maybe it is worth regrouping this to avoid an exception to exception?
For example:

The only legal parameters for ``Type`` are classes, unions of classes,
and ``Any``::

and then after example continue with your text:

``Type[Any]`` is equivalent to ``Type`` which in turn...

http://bugs.python.org/review/27905/

From post at vladimirboyd.ru  Thu Sep  1 07:00:51 2016
From: post at vladimirboyd.ru (post at vladimirboyd.ru)
Date: Thu, 01 Sep 2016 14:00:51 +0300
Subject: [docs] Broken links on Download page
Message-ID: <bd3cd0a1a6361023e3b1b6b1a149392f@vladimirboyd.ru>

Hello guys and girls,

I was trying to download archives off of your Downloads page 
(https://docs.python.org/3.4/download.html) for Python 3.4 
(https://docs.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-html.tar.bz2) 
and some of the links just don't work.
Please, inform the person responsible for the page.

Thank you,

Vladimir Boyd.

From r1043651621 at hotmail.com  Fri Sep  2 05:12:56 2016
From: r1043651621 at hotmail.com (dan )
Date: Fri, 2 Sep 2016 17:12:56 +0800
Subject: [docs] Download Python 3.5.2 Documentation
Message-ID: <BAY407-EAS150217BB0BCEA46D715FC0ABCE40@phx.gbl>

Hi,

I am from China, and I want to download the python 3.5 document in pdf form,
but when I clicked the link, it turned out "404 error".

so could you help to fix this problem? Or are these documents no longer been
provided for users downloading?

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160902/6be31e37/attachment.html>

From report at bugs.python.org  Mon Sep  5 13:46:42 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 05 Sep 2016 17:46:42 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1473097602.57.0.488252810895.issue27779@psf.upfronthosting.co.za>


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


----------
assignee: skrah -> lisroach

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

From report at bugs.python.org  Mon Sep  5 13:56:41 2016
From: report at bugs.python.org (Stefan Krah)
Date: Mon, 05 Sep 2016 17:56:41 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1473098201.07.0.87687625055.issue27779@psf.upfronthosting.co.za>


Stefan Krah added the comment:

Sorry, Raymond, this is my code area.  I said I'll review a patch.

----------
assignee: lisroach -> skrah

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

From report at bugs.python.org  Mon Sep  5 17:00:31 2016
From: report at bugs.python.org (George London)
Date: Mon, 05 Sep 2016 21:00:31 +0000
Subject: [docs] [issue27957] minor typo in importlib docs
Message-ID: <1473109231.6.0.988528969997.issue27957@psf.upfronthosting.co.za>


New submission from George London:

An extra apostrophe made the grammar of a method description ambiguous. The attached patch removes the apostrophe.

----------
assignee: docs at python
components: Documentation
files: mywork.patch
keywords: patch
messages: 274429
nosy: docs at python, gjlondon
priority: normal
severity: normal
status: open
title: minor typo in importlib docs
type: enhancement
versions: Python 3.5
Added file: http://bugs.python.org/file44377/mywork.patch

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

From report at bugs.python.org  Mon Sep  5 17:03:35 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 05 Sep 2016 21:03:35 +0000
Subject: [docs] [issue27957] minor typo in importlib docs
In-Reply-To: <1473109231.6.0.988528969997.issue27957@psf.upfronthosting.co.za>
Message-ID: <20160905210331.6738.60112.A9A24EF2@psf.io>


Roundup Robot added the comment:

New changeset 33702360acef by Benjamin Peterson in branch '3.5':
remove ungrammarical apostrophe (closes #27957)
https://hg.python.org/cpython/rev/33702360acef

New changeset f8d9569900a9 by Benjamin Peterson in branch 'default':
merge 3.5 (#27957)
https://hg.python.org/cpython/rev/f8d9569900a9

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

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

From report at bugs.python.org  Mon Sep  5 19:14:56 2016
From: report at bugs.python.org (Senthil Kumaran)
Date: Mon, 05 Sep 2016 23:14:56 +0000
Subject: [docs] [issue20842] pkgutil docs should reference glossary terms
 not PEP 302
In-Reply-To: <1393846400.67.0.723549613222.issue20842@psf.upfronthosting.co.za>
Message-ID: <1473117296.04.0.931390546792.issue20842@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

I agree with the comment made by Oren. Not all instances of finder should be referenced as generic finder. Some classes and functions are are still PEP 302 specific finder.

In the commit, 3987667bf98f Nick Coghlan modified the following functions to to use importlib module, thus serving the PEP 302 bind. So these can refer to glossary entry for finder. The documentation has been updated with version changed information.

* get_importer (by the underlying change of using only sys.path_importer_cache and removing the use of ImpImporter)
* iter_importers (by using importlib.import_module)

The glossary entry for both finder and loader has been updated to include both PEP 302 finder, and with PEP 420 and PEP 451.

With these changes already in place, I updated the patch to reflect the current state. 

I am proceed with the commit as this is a non-controversial change. If there are comments, please share and I will address them.

----------
nosy: +orsenthil
Added file: http://bugs.python.org/file44381/issue20842-v3.patch

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

From report at bugs.python.org  Mon Sep  5 20:09:54 2016
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 06 Sep 2016 00:09:54 +0000
Subject: [docs] [issue20842] pkgutil docs should reference glossary terms
 not PEP 302
In-Reply-To: <1393846400.67.0.723549613222.issue20842@psf.upfronthosting.co.za>
Message-ID: <1473120594.15.0.0235557722577.issue20842@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

For 3.5 version of patch, we have bring in some additional changes from issue26896 which properly clarified finder from importer. These changes are not required in the default branch.

----------

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

From report at bugs.python.org  Mon Sep  5 20:18:45 2016
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 06 Sep 2016 00:18:45 +0000
Subject: [docs] [issue20842] pkgutil docs should reference glossary terms
 not PEP 302
In-Reply-To: <1393846400.67.0.723549613222.issue20842@psf.upfronthosting.co.za>
Message-ID: <1473121123.82.0.0245651269736.issue20842@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

This is 3.3 version of patch attached.

----------
Added file: http://bugs.python.org/file44383/issue20842-3.3-v5.patch

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

From report at bugs.python.org  Mon Sep  5 20:20:27 2016
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 06 Sep 2016 00:20:27 +0000
Subject: [docs] [issue20842] pkgutil docs should reference glossary terms
 not PEP 302
In-Reply-To: <1393846400.67.0.723549613222.issue20842@psf.upfronthosting.co.za>
Message-ID: <1473121227.45.0.324976352847.issue20842@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

Change committed.

- 3.5 * 103098:ecbad01262c8
- default * 103099:ee58ece83391

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

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

From report at bugs.python.org  Mon Sep  5 22:27:44 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 06 Sep 2016 02:27:44 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1473128864.46.0.394719085682.issue27779@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Lisa is not a committer.  The assignment means that she is working on the patch.  BTW, the decimal package has long been my area as well (writing a C implementation does not give you exclusive decision making over the docstrings.)

----------

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

From report at bugs.python.org  Tue Sep  6 01:45:11 2016
From: report at bugs.python.org (Mark Hammond)
Date: Tue, 06 Sep 2016 05:45:11 +0000
Subject: [docs] [issue27966] PEP-397 documents incorrect registry path
Message-ID: <1473140711.09.0.302739386387.issue27966@psf.upfronthosting.co.za>


New submission from Mark Hammond:

Received via email:

PEP-397 (PEP 397 -- Python launcher for Windows) says:
"""
The launcher installation is registered in

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion\SharedDLLs with a reference counter.
"""

There is no such entry. It should be HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs

----------
assignee: docs at python
components: Documentation
messages: 274525
nosy: docs at python, mhammond
priority: normal
severity: normal
status: open
title: PEP-397 documents incorrect registry path

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

From report at bugs.python.org  Tue Sep  6 16:03:48 2016
From: report at bugs.python.org (Michael Lee)
Date: Tue, 06 Sep 2016 20:03:48 +0000
Subject: [docs] [issue27905] Add documentation for typing.Type
In-Reply-To: <1472593880.19.0.114422348142.issue27905@psf.upfronthosting.co.za>
Message-ID: <1473192228.95.0.518604017156.issue27905@psf.upfronthosting.co.za>


Michael Lee added the comment:

Ok, here's version 2, taking into account Ivan's feedback!

----------
Added file: http://bugs.python.org/file44401/document-type-v2.patch

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

From report at bugs.python.org  Tue Sep  6 19:36:06 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 06 Sep 2016 23:36:06 +0000
Subject: [docs] [issue23226] Add float linspace recipe to docs
In-Reply-To: <1421102448.57.0.289351503451.issue23226@psf.upfronthosting.co.za>
Message-ID: <20160906233602.1474.74052.7FE098EE@psf.io>


Roundup Robot added the comment:

New changeset bb8fe61d78a4 by Raymond Hettinger in branch 'default':
Issue #23226:  Add linspace() recipe to the docs
https://hg.python.org/cpython/rev/bb8fe61d78a4

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

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

From report at bugs.python.org  Tue Sep  6 19:36:31 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 06 Sep 2016 23:36:31 +0000
Subject: [docs] [issue23226] Add float linspace recipe to docs
In-Reply-To: <1421102448.57.0.289351503451.issue23226@psf.upfronthosting.co.za>
Message-ID: <1473204991.55.0.680532836644.issue23226@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Sep  6 22:34:23 2016
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 07 Sep 2016 02:34:23 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1473215663.61.0.675655457536.issue27292@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

PEP 524 has been implemented for 3.6b1 in #27776, so os.urandom() itself will now do the right thing for cryptographic use cases on Linux. Accordingly, I've removed Python 3.6 from the affected versions for this issue.

I've also flagged this as purely a documentation issue, since no behavioural changes are currently proposed for older versions.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, ncoghlan
title: Warn users that os.urandom() can return insecure values -> Warn users that os.urandom() prior to 3.6 can return insecure values
versions:  -Python 3.6

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

From report at bugs.python.org  Tue Sep  6 23:01:16 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 07 Sep 2016 03:01:16 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1473217276.58.0.430228219992.issue27292@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I dislike urandom-doc.v2.patch. There is no need to worry all users. Just be explicit and explain that the issue is specific to Linux and explain when it occurs: before the entropy pool is filled *and* if the system was not able yet to write enough entropy on disk, this thing:
https://www.python.org/dev/peps/pep-0524/#load-entropy-from-disk-at-boot

----------

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

From report at bugs.python.org  Tue Sep  6 23:04:18 2016
From: report at bugs.python.org (py.user)
Date: Wed, 07 Sep 2016 03:04:18 +0000
Subject: [docs] [issue27991] In the argparse howto there is a misleading
 sentence about store_true
Message-ID: <1473217458.1.0.785896151958.issue27991@psf.upfronthosting.co.za>


New submission from py.user:

https://docs.python.org/3/howto/argparse.html#combining-positional-and-optional-arguments
"And, just like the ?store_true? action, if you don?t specify the -v flag, that flag is considered to have None value."

This sentence is misleading. It supposes that "store_true" action can save None value. But "store_true" action always saves True or False value.

An example:

This code was taken from the argparse howto. I've just added the -f option and printed args to the stdout.

a.py

#!/usr/bin/env python3

import argparse

parser = argparse.ArgumentParser()
parser.add_argument("square", type=int,
                    help="display the square of a given number")
parser.add_argument("-v", "--verbosity", action="count",
                    help="increase output verbosity")
parser.add_argument("-f", "--flag", action="store_true")
args = parser.parse_args()

print('args:', args)


The output in the console:

[guest at localhost bugs]$ ./a.py 1
args: Namespace(flag=False, square=1, verbosity=None)
[guest at localhost bugs]$ 


In the output we see that the -f option have got the False value not None.

Applied a patch to the issue that just removes words about analogy with store_true action.

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: argparse_store_true.diff
keywords: patch
messages: 274725
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In the argparse howto there is a misleading sentence about store_true
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file44419/argparse_store_true.diff

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

From report at bugs.python.org  Tue Sep  6 23:10:53 2016
From: report at bugs.python.org (py.user)
Date: Wed, 07 Sep 2016 03:10:53 +0000
Subject: [docs] [issue27992] In the argparse there is a misleading words
 about %(prog)s value
Message-ID: <1473217852.97.0.553971829799.issue27992@psf.upfronthosting.co.za>


New submission from py.user:

https://docs.python.org/3/library/argparse.html#argumentparser-objects
"prog - The name of the program (default: sys.argv[0])"

It doesn't take all sys.argv[0]. It splits sys.argv[0] and takes only the trailing part.

An example:

a.py

#!/usr/bin/env python3

import argparse
import sys

parser = argparse.ArgumentParser()
parser.add_argument("arg", help="The name is %(prog)s, the sys.argv[0] is " + sys.argv[0])
args = parser.parse_args()


The output in the console:

[guest at localhost bugs]$ ../bugs/a.py -h
usage: a.py [-h] arg

positional arguments:
  arg         The name is a.py and sys.argv[0] is ../bugs/a.py

optional arguments:
  -h, --help  show this help message and exit
[guest at localhost bugs]$


In the output we see that %(prog)s takes only trailing part of sys.argv[0] not all.

Applied a patch to the issue that specifies about part of sys.argv[0].

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: argparse_sys-argv-0-part.diff
keywords: patch
messages: 274729
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In the argparse there is a misleading words about %(prog)s value
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file44420/argparse_sys-argv-0-part.diff

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

From report at bugs.python.org  Tue Sep  6 23:15:03 2016
From: report at bugs.python.org (py.user)
Date: Wed, 07 Sep 2016 03:15:03 +0000
Subject: [docs] [issue27993] In the argparse there are typos with endings in
 plural words
Message-ID: <1473218103.32.0.964912945443.issue27993@psf.upfronthosting.co.za>


New submission from py.user:

https://docs.python.org/3/library/argparse.html#prog
"By default, ArgumentParser objects uses sys.argv[0]"

Should be "objects use" as in all other places in the doc.

https://docs.python.org/3/library/argparse.html#conflict-handler
"By default, ArgumentParser objects raises an exception"

Should be "objects raise" as in all other places in the doc.

Applied a patch to the issue.

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: argparse_objects_endings.diff
keywords: patch
messages: 274735
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In the argparse there are typos with endings in plural words
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file44421/argparse_objects_endings.diff

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

From report at bugs.python.org  Tue Sep  6 23:20:29 2016
From: report at bugs.python.org (py.user)
Date: Wed, 07 Sep 2016 03:20:29 +0000
Subject: [docs] [issue27994] In the argparse help(argparse) prints weird
 comments instead of good docstrings
Message-ID: <1473218429.0.0.161771079956.issue27994@psf.upfronthosting.co.za>


New submission from py.user:

>>> import argparse
>>> help(argparse)

>>>

Output:

|  add_subparsers(self, **kwargs)
|      # ==================================
|      # Optional/Positional adding methods
|      # ==================================
|  
|  convert_arg_line_to_args(self, arg_line)
|  
|  error(self, message)
|      error(message: string)
|      
|      Prints a usage message incorporating the message to stderr and
|      exits.
|      
|      If you override this in a subclass, it should not return -- it
|      should either exit or raise an exception.
|  
|  exit(self, status=0, message=None)
|      # ===============
|      # Exiting methods
|      # ===============
|  
|  format_help(self)
|  
|  format_usage(self)
|      # =======================
|      # Help-formatting methods
|      # =======================
|  
|  parse_args(self, args=None, namespace=None)
|      # =====================================
|      # Command line argument parsing methods
|      # =====================================
|  
|  parse_known_args(self, args=None, namespace=None)
|  
|  print_help(self, file=None)
|  
|  print_usage(self, file=None)
|      # =====================
|      # Help-printing methods
|      # =====================
|  
|  ----------------------------------------------------------------------
|  Methods inherited from _AttributeHolder:
...


There are no docstrings for methods, hence some internal comments picked up instead.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 274738
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In the argparse help(argparse) prints weird comments instead of good docstrings
type: behavior
versions: Python 3.6

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

From report at bugs.python.org  Wed Sep  7 00:13:42 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 Sep 2016 04:13:42 +0000
Subject: [docs] [issue27905] Add documentation for typing.Type
In-Reply-To: <1472593880.19.0.114422348142.issue27905@psf.upfronthosting.co.za>
Message-ID: <20160907041336.12680.88032.B7E9EADB@psf.io>


Roundup Robot added the comment:

New changeset 9fb30d6af6a9 by Guido van Rossum in branch '3.5':
Issue #27905: Docs for typing.Type[C], by Michael Lee.
https://hg.python.org/cpython/rev/9fb30d6af6a9

New changeset 1705cde6266d by Guido van Rossum in branch 'default':
Issue #27905: Docs for typing.Type[C], by Michael Lee. (Merge 3.5->3.6)
https://hg.python.org/cpython/rev/1705cde6266d

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

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

From report at bugs.python.org  Wed Sep  7 00:14:27 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 07 Sep 2016 04:14:27 +0000
Subject: [docs] [issue27905] Add documentation for typing.Type
In-Reply-To: <1472593880.19.0.114422348142.issue27905@psf.upfronthosting.co.za>
Message-ID: <1473221667.48.0.78644320573.issue27905@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Thanks again!  Merged to 3.5 and 3.6 (after cleaning up trailing whitespace -- again ;-).

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

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

From report at bugs.python.org  Wed Sep  7 03:53:45 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 Sep 2016 07:53:45 +0000
Subject: [docs] [issue20842] pkgutil docs should reference glossary terms
 not PEP 302
In-Reply-To: <1393846400.67.0.723549613222.issue20842@psf.upfronthosting.co.za>
Message-ID: <20160907075340.548.16162.26E22B41@psf.io>


Roundup Robot added the comment:

New changeset a4360b1b45a8 by Senthil Kumaran in branch 'default':
issue20842 - null merge with 3.5
https://hg.python.org/cpython/rev/a4360b1b45a8

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

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

From report at bugs.python.org  Wed Sep  7 10:08:38 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 07 Sep 2016 14:08:38 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
Message-ID: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>


New submission from Ivan Levkivskyi:

The documentation at https://docs.python.org/3/reference/simple_stmts.html says that:

"Names listed in a global statement must not be used in the same code block textually preceding that global statement"

But then later:

"CPython implementation detail: The current implementation does not enforce the two restrictions,
but programs should not abuse this freedom, as future implementations may enforce them..."

Code like this

def f():
    x = 1
    global x

gives SyntaxWarning for several releases, maybe it is time to make it a SyntaxError?

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 274813
nosy: docs at python, gvanrossum, levkivskyi
priority: normal
severity: normal
status: open
title: Make "global after use" a SyntaxError
type: behavior
versions: Python 3.6

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

From report at bugs.python.org  Wed Sep  7 11:19:43 2016
From: report at bugs.python.org (Ethan Furman)
Date: Wed, 07 Sep 2016 15:19:43 +0000
Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs
In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za>
Message-ID: <1473261583.01.0.644448592048.issue27877@psf.upfronthosting.co.za>


Ethan Furman added the comment:

New changeset 871bdb06c1cf by Ethan Furman in branch 'default':
add recipes for pseudo-valueless enums
https://hg.python.org/cpython/rev/871bdb06c1cf

----------

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

From report at bugs.python.org  Wed Sep  7 11:23:34 2016
From: report at bugs.python.org (Ethan Furman)
Date: Wed, 07 Sep 2016 15:23:34 +0000
Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs
In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za>
Message-ID: <1473261814.75.0.0768461919395.issue27877@psf.upfronthosting.co.za>


Ethan Furman added the comment:

Thanks for the patch, John and Emanuel!

----------

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

From report at bugs.python.org  Wed Sep  7 12:44:00 2016
From: report at bugs.python.org (Ned Deily)
Date: Wed, 07 Sep 2016 16:44:00 +0000
Subject: [docs] [issue27966] PEP-397 documents incorrect registry path
In-Reply-To: <1473140711.09.0.302739386387.issue27966@psf.upfronthosting.co.za>
Message-ID: <1473266640.95.0.808602628865.issue27966@psf.upfronthosting.co.za>


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


----------
components: +Windows -Documentation
nosy: +paul.moore, steve.dower, tim.golden, zach.ware

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

From report at bugs.python.org  Wed Sep  7 12:58:56 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 07 Sep 2016 16:58:56 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473267536.65.0.718077849111.issue27999@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

I like fixing this. I suppose it'll be fixed for nonlocal too?

----------

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

From report at bugs.python.org  Wed Sep  7 14:02:23 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 Sep 2016 18:02:23 +0000
Subject: [docs] [issue26209] TypeError in smtpd module with string arguments
In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za>
Message-ID: <20160907180220.1062.86254.6F024D61@psf.io>


Roundup Robot added the comment:

New changeset 1ed37f6e91bb by R David Murray in branch '3.5':
#26209: Clarify type of *localaddr*/*remoteadr* in smtpd docs.
https://hg.python.org/cpython/rev/1ed37f6e91bb

New changeset fe2ca2216334 by R David Murray in branch 'default':
Merge: #26209: Clarify type of *localaddr*/*remoteadr* in smtpd docs.
https://hg.python.org/cpython/rev/fe2ca2216334

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

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

From report at bugs.python.org  Wed Sep  7 14:08:17 2016
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 Sep 2016 18:08:17 +0000
Subject: [docs] [issue26209] TypeError in smtpd module with string arguments
In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za>
Message-ID: <1473271697.6.0.641386113148.issue26209@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks for the patch, Ram.  I started from your patch but further clarified exactly what the tuple is by linking to the actual documentation in the socket docs of what a (host, port) tuple looks like.  I'll apply my patch to 2.7 as well as soon as I confirm the docs build correctly.

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

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

From report at bugs.python.org  Wed Sep  7 14:10:38 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 Sep 2016 18:10:38 +0000
Subject: [docs] [issue26209] TypeError in smtpd module with string arguments
In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za>
Message-ID: <20160907181010.31352.59889.2BD2DB8E@psf.io>


Roundup Robot added the comment:

New changeset 7aaf8cff23e5 by R David Murray in branch '2.7':
#26209: Clarify type of *localaddr*/*remoteadr* in smtpd docs.
https://hg.python.org/cpython/rev/7aaf8cff23e5

----------

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

From report at bugs.python.org  Wed Sep  7 14:11:15 2016
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 Sep 2016 18:11:15 +0000
Subject: [docs] [issue26209] TypeError in smtpd module with string arguments
In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za>
Message-ID: <1473271875.67.0.53062366306.issue26209@psf.upfronthosting.co.za>


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


----------
dependencies:  -Deprecate smtpd (based on deprecated asyncore/asynchat): write a new smtp server with asyncio
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed Sep  7 16:51:47 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 07 Sep 2016 20:51:47 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473281507.56.0.444076690527.issue27999@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

Yes, nonlocal will be fixed too. This will be a relatively small patch, but I am a bit afraid there could be merge conflicts (the code affected could overlap with changes for PEP 526).

Easiest way would be to simply make this a single patch with PEP 526 implementation (this will actually even slightly simplify the implementation).

Alternatively we could fix this right after the implementation patch is applied. What do you prefer?

----------

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

From report at bugs.python.org  Wed Sep  7 17:08:05 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 07 Sep 2016 21:08:05 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473281507.56.0.444076690527.issue27999@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJLEBCRd7cKO9GkEpTEp9wYWLCCmmz67oTZbQRk5anHnPA@mail.gmail.com>


Guido van Rossum added the comment:

I strongly prefer to have it as a separate patch (either before or
after) to avoid the appearance of piggy-backing this in with a much
larger change.

----------

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

From report at bugs.python.org  Wed Sep  7 17:11:37 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 07 Sep 2016 21:11:37 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473282697.76.0.87421282966.issue27999@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

OK, then I think after will be safer. Let us came back to this right after PEP 526.

----------

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

From report at bugs.python.org  Wed Sep  7 19:37:10 2016
From: report at bugs.python.org (p0lm)
Date: Wed, 07 Sep 2016 23:37:10 +0000
Subject: [docs] [issue28010] http.client.HTTPConnection.putrequest incorrect
 arguments
Message-ID: <1473291430.61.0.706860588682.issue28010@psf.upfronthosting.co.za>


New submission from p0lm:

Currently the arguments for HTTPConnection.putrequest in the http.client documentation are listed as "request, selector, skip_host=False, skip_accept_encoding=False". This does not reflect the correct arguments:
>>> from http.client import HTTPConnection
>>> help(HTTPConnection.putrequest)

putrequest(self, method, url, skip_host=0, skip_accept_encoding=0)
    Send a request to the server.
    
    `method' specifies an HTTP request method, e.g. 'GET'.
    `url' specifies the object being requested, e.g. '/index.html'.
    `skip_host' if True does not add automatically a 'Host:' header
    `skip_accept_encoding' if True does not add automatically an
       'Accept-Encoding:' header

Fix:
Change `request` and `selector` to `method` and `url` respectively.

----------
assignee: docs at python
components: Documentation
messages: 274913
nosy: docs at python, p0lm
priority: normal
severity: normal
status: open
title: http.client.HTTPConnection.putrequest incorrect arguments
type: enhancement
versions: Python 3.5

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

From report at bugs.python.org  Wed Sep  7 19:42:51 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 Sep 2016 23:42:51 +0000
Subject: [docs] [issue27895] Spelling fixes
In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za>
Message-ID: <20160907234247.3168.23362.54D120E5@psf.io>


Roundup Robot added the comment:

New changeset ff3df2b1ac7f by Martin Panter in branch '3.5':
Issue #27895:  Spelling fixes (Contributed by Ville Skytt?).
https://hg.python.org/cpython/rev/ff3df2b1ac7f

----------

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

From report at bugs.python.org  Wed Sep  7 19:42:51 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 Sep 2016 23:42:51 +0000
Subject: [docs] [issue27993] In the argparse there are typos with endings in
 plural words
In-Reply-To: <1473218103.32.0.964912945443.issue27993@psf.upfronthosting.co.za>
Message-ID: <20160907234247.3168.21034.739831FC@psf.io>


Roundup Robot added the comment:

New changeset 8f02a1a6b647 by Martin Panter in branch '3.5':
Issue #27993: Fix problems with plural objects in docs and comments
https://hg.python.org/cpython/rev/8f02a1a6b647

New changeset bb2a7134d82b by Martin Panter in branch 'default':
Issue #27993: Merge plural fixes from 3.5
https://hg.python.org/cpython/rev/bb2a7134d82b

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

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

From report at bugs.python.org  Wed Sep  7 19:57:21 2016
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 Sep 2016 23:57:21 +0000
Subject: [docs] [issue20476] If new email policies are used,
 default message factory should be EmailMessage
In-Reply-To: <1391292485.67.0.381493162498.issue20476@psf.upfronthosting.co.za>
Message-ID: <1473292639.65.0.957504798548.issue20476@psf.upfronthosting.co.za>


R. David Murray added the comment:

Here's the patch to add the message_factory policy attribute.

----------
Added file: http://bugs.python.org/file44454/message_factory.diff

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

From report at bugs.python.org  Thu Sep  8 01:42:52 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Sep 2016 05:42:52 +0000
Subject: [docs] [issue27993] In the argparse there are typos with endings in
 plural words
In-Reply-To: <1473218103.32.0.964912945443.issue27993@psf.upfronthosting.co.za>
Message-ID: <20160908054248.2885.82261.2CE96947@psf.io>


Roundup Robot added the comment:

New changeset c07aadf9f5cb by Martin Panter in branch '2.7':
Issue #27993: Fix problems with the plural ?objects? in docs and comments
https://hg.python.org/cpython/rev/c07aadf9f5cb

----------

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

From report at bugs.python.org  Thu Sep  8 01:42:52 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Sep 2016 05:42:52 +0000
Subject: [docs] [issue27895] Spelling fixes
In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za>
Message-ID: <20160908054248.2885.31101.9B8DBEA4@psf.io>


Roundup Robot added the comment:

New changeset 9a68ab141c33 by Martin Panter in branch '2.7':
Issue #27895:  Spelling fixes (Contributed by Ville Skytt?).
https://hg.python.org/cpython/rev/9a68ab141c33

----------

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

From report at bugs.python.org  Thu Sep  8 01:44:37 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 08 Sep 2016 05:44:37 +0000
Subject: [docs] [issue27993] In the argparse there are typos with endings in
 plural words
In-Reply-To: <1473218103.32.0.964912945443.issue27993@psf.upfronthosting.co.za>
Message-ID: <1473313477.71.0.356523343057.issue27993@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for the patch. I found a few more related instances to fix too.

----------
nosy: +martin.panter
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.5

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

From report at bugs.python.org  Thu Sep  8 01:50:21 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 08 Sep 2016 05:50:21 +0000
Subject: [docs] [issue27895] Spelling fixes
In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za>
Message-ID: <1473313821.4.0.391723691335.issue27895@psf.upfronthosting.co.za>


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


----------
versions: +Python 2.7, Python 3.5

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

From report at bugs.python.org  Thu Sep  8 02:18:43 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 08 Sep 2016 06:18:43 +0000
Subject: [docs] [issue28010] http.client.HTTPConnection.putrequest incorrect
 arguments
In-Reply-To: <1473291430.61.0.706860588682.issue28010@psf.upfronthosting.co.za>
Message-ID: <1473315523.03.0.777332276183.issue28010@psf.upfronthosting.co.za>


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


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

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

From nlevitt at archive.org  Wed Sep  7 15:16:37 2016
From: nlevitt at archive.org (Noah Levitt)
Date: Wed, 7 Sep 2016 12:16:37 -0700
Subject: [docs] weighted random choice doc bug
Message-ID: <CAA-z70J=wDSP4PyJucK7r=BuzbPoQ8kb37y5QY6CmuLP5tCi4g@mail.gmail.com>

There's a bug in the general approach to weighted random choice at the
bottom of https://docs.python.org/3.6/library/random.html. This is
what happens if all the weights are zero (a real possibility):

>>> import itertools, random, bisect
>>> weighted_choices = [('Red', 0), ('Blue', 0), ('Yellow', 0), ('Green', 0)]
>>> choices, weights = zip(*weighted_choices)
>>> cumdist = list(itertools.accumulate(weights))
>>> cumdist
[0, 0, 0, 0]
>>> x = random.random() * cumdist[-1]
>>> bisect.bisect(cumdist, x)
4
>>> choices[bisect.bisect(cumdist, x)]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
IndexError: tuple index out of range

I think changing the bisect.bisect() call to bisect.bisect_left() is a
correct fix.

Noah

From qa0922656836 at gmail.com  Wed Sep  7 08:51:44 2016
From: qa0922656836 at gmail.com (liff c)
Date: Wed, 7 Sep 2016 20:51:44 +0800
Subject: [docs] bug
Message-ID: <CACDKesq6px9FoXGvnBf+5+iNfwdG6wEJNADOG6AYYt-k-jcmQQ@mail.gmail.com>

can't print chinese word:"?" and "?" in cmd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160907/257e4622/attachment.html>
-------------- next part --------------
import time
print('??')
time.sleep(10)

From report at bugs.python.org  Thu Sep  8 09:15:05 2016
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 08 Sep 2016 13:15:05 +0000
Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs
In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za>
Message-ID: <1473340505.73.0.217939890487.issue27877@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Sep  8 10:51:50 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 14:51:50 +0000
Subject: [docs] [issue18617] TLS and Intermediate Certificates
In-Reply-To: <1375376317.99.0.429350247521.issue18617@psf.upfronthosting.co.za>
Message-ID: <1473346310.44.0.632151529979.issue18617@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Sep  8 10:55:30 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 14:55:30 +0000
Subject: [docs] [issue21649] Mention "Recommendations for Secure Use of TLS
 and DTLS"
In-Reply-To: <1401786597.2.0.166065083457.issue21649@psf.upfronthosting.co.za>
Message-ID: <1473346530.82.0.593394415417.issue21649@psf.upfronthosting.co.za>


Christian Heimes added the comment:

https://wiki.mozilla.org/Security/Server_Side_TLS is a good resource, too.

----------
versions: +Python 3.6, Python 3.7

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

From report at bugs.python.org  Thu Sep  8 11:02:04 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 15:02:04 +0000
Subject: [docs] [issue22301] smtplib.SMTP.starttls' documentation is just
 confusing
In-Reply-To: <1409344383.54.0.340854314506.issue22301@psf.upfronthosting.co.za>
Message-ID: <1473346924.69.0.338761933753.issue22301@psf.upfronthosting.co.za>


Christian Heimes added the comment:

starttls() does accept a ssl_context argument for a while.

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

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

From report at bugs.python.org  Thu Sep  8 11:21:18 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 15:21:18 +0000
Subject: [docs] [issue23843] ssl.wrap_socket doesn't handle virtual TLS hosts
In-Reply-To: <1427913138.81.0.946174755254.issue23843@psf.upfronthosting.co.za>
Message-ID: <1473348078.29.0.495997372403.issue23843@psf.upfronthosting.co.za>


Christian Heimes added the comment:

ssl.wrap_socket() will be deprecated in 3.6. Please use a context. You can still inspect the server cert with a context. In fact ssl.wrap_socket() uses a context internally.

----------
resolution:  -> wont fix
status: open -> closed
versions: +Python 3.6 -Python 3.4

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

From report at bugs.python.org  Thu Sep  8 11:22:12 2016
From: report at bugs.python.org (Giampaolo Rodola')
Date: Thu, 08 Sep 2016 15:22:12 +0000
Subject: [docs] [issue23843] ssl.wrap_socket doesn't handle virtual TLS hosts
In-Reply-To: <1427913138.81.0.946174755254.issue23843@psf.upfronthosting.co.za>
Message-ID: <1473348132.95.0.935944268723.issue23843@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Sep  8 11:24:04 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 15:24:04 +0000
Subject: [docs] [issue24372] Documentation for ssl.wrap_socket's ssl_version
 parameter is odd
In-Reply-To: <1433337046.56.0.760667574061.issue24372@psf.upfronthosting.co.za>
Message-ID: <1473348244.72.0.440970203201.issue24372@psf.upfronthosting.co.za>


Christian Heimes added the comment:

OpenSSL 1.1.0 has deprecated all versions except TLS_METHOD and DTLS_METHOD. TLS_METHOD is the new name for auto-nego SSLv23_METHOD. Python 3.6 defaults to TLS_METHOD already. #27876 will add a better way to configure accepted versions.

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

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

From report at bugs.python.org  Thu Sep  8 11:25:40 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 15:25:40 +0000
Subject: [docs] [issue24516] SSL create_default_socket purpose
 insufficiently documented
In-Reply-To: <1435323940.35.0.0347196481189.issue24516@psf.upfronthosting.co.za>
Message-ID: <1473348340.37.0.543720904308.issue24516@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.6, Python 3.7 -Python 3.4

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

From report at bugs.python.org  Thu Sep  8 14:14:21 2016
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 08 Sep 2016 18:14:21 +0000
Subject: [docs] [issue20683] Add example to tutorial namespace doc,
 section 9.2
In-Reply-To: <1392798452.78.0.903259935516.issue20683@psf.upfronthosting.co.za>
Message-ID: <1473358461.59.0.817999204094.issue20683@psf.upfronthosting.co.za>


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


----------
resolution:  -> not a bug
stage:  -> resolved
status: pending -> closed

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

From report at bugs.python.org  Thu Sep  8 16:31:07 2016
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 08 Sep 2016 20:31:07 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <1473366667.39.0.905659242549.issue20100@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch, priyapappachan. Here is an updated patch. Since EPOLL_CLOEXEC is the only value that can be passed to epoll_create1(), we can also simplify the implementation a bit.

----------
nosy: +berker.peksag
stage: needs patch -> patch review
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.4
Added file: http://bugs.python.org/file44476/issue20100_v2.diff

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

From report at bugs.python.org  Thu Sep  8 16:37:40 2016
From: report at bugs.python.org (Steve Dower)
Date: Thu, 08 Sep 2016 20:37:40 +0000
Subject: [docs] [issue27966] PEP-397 documents incorrect registry path
In-Reply-To: <1473140711.09.0.302739386387.issue27966@psf.upfronthosting.co.za>
Message-ID: <1473367060.7.0.76147270712.issue27966@psf.upfronthosting.co.za>


Steve Dower added the comment:

I'd rather not document this anyway, and I'm not sure it's true right now.

Since 3.5, there is one MSI for the launcher that will be used into the future and handle the reference counting, so this note is irrelevant and solely of historical interest.

----------

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

From report at bugs.python.org  Thu Sep  8 17:25:02 2016
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 08 Sep 2016 21:25:02 +0000
Subject: [docs] [issue28010] http.client.HTTPConnection.putrequest incorrect
 arguments
In-Reply-To: <1473291430.61.0.706860588682.issue28010@psf.upfronthosting.co.za>
Message-ID: <1473369902.05.0.767112238948.issue28010@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

This patch fixes this. It makes the documentation consistent with the code.

----------
keywords: +patch
nosy: +orsenthil
Added file: http://bugs.python.org/file44479/103351.patch

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

From report at bugs.python.org  Thu Sep  8 17:30:13 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Sep 2016 21:30:13 +0000
Subject: [docs] [issue28010] http.client.HTTPConnection.putrequest incorrect
 arguments
In-Reply-To: <1473291430.61.0.706860588682.issue28010@psf.upfronthosting.co.za>
Message-ID: <20160908212951.21237.14152.E94C4E57@psf.io>


Roundup Robot added the comment:

New changeset f6b62cf4a436 by Senthil Kumaran in branch '3.5':
Issue28010 - Make http.client.HTTPConnection.putrequest documentation consistent with the code.
https://hg.python.org/cpython/rev/f6b62cf4a436

New changeset 93c7a893f9b4 by Senthil Kumaran in branch 'default':
[merge from 3.5] - Issue28010 - Make http.client.HTTPConnection.putrequest
https://hg.python.org/cpython/rev/93c7a893f9b4

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

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

From report at bugs.python.org  Thu Sep  8 17:30:43 2016
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 08 Sep 2016 21:30:43 +0000
Subject: [docs] [issue28010] http.client.HTTPConnection.putrequest incorrect
 arguments
In-Reply-To: <1473291430.61.0.706860588682.issue28010@psf.upfronthosting.co.za>
Message-ID: <1473370243.55.0.993364108758.issue28010@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed
versions: +Python 3.6

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

From berker.peksag at gmail.com  Thu Sep  8 17:36:37 2016
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Thu, 08 Sep 2016 21:36:37 -0000
Subject: [docs] http.client.HTTPConnection.putrequest incorrect arguments
 (issue 28010)
Message-ID: <20160908213637.1509.59217@psf.upfronthosting.co.za>


http://bugs.python.org/review/28010/diff/18422/Doc/library/http.client.rst
File Doc/library/http.client.rst (right):

http://bugs.python.org/review/28010/diff/18422/Doc/library/http.client.rst#newcode34
Doc/library/http.client.rst:34: .. class:: HTTPConnection(host,
port=None[, timeout], source_address=None)
This looks like an unnecessary change. It would be nice to keep "hg
blame" usable :)

http://bugs.python.org/review/28010/diff/18422/Lib/http/client.py
File Lib/http/client.py (right):

http://bugs.python.org/review/28010/diff/18422/Lib/http/client.py#newcode1071
Lib/http/client.py:1071: def putrequest(self, method, url,
skip_host=False,
I'd commit this only to default branch.

http://bugs.python.org/review/28010/

From senthil at uthcode.com  Thu Sep  8 17:42:33 2016
From: senthil at uthcode.com (senthil at uthcode.com)
Date: Thu, 08 Sep 2016 21:42:33 -0000
Subject: [docs] http.client.HTTPConnection.putrequest incorrect
 arguments (issue 28010)
Message-ID: <20160908214233.6062.72397@psf.upfronthosting.co.za>

On 2016/09/08 23:36:37, berkerpeksag wrote:

> I'd commit this only to default branch.

The docs were saying the signature with (=False) in both 3.5 and 3.6
version. They had be consistent.

(again) - I voted on the non-controversy of the change. Consistency is
important here, otherwise it will keep lingering due to some process
adherence.


http://bugs.python.org/review/28010/

From senthil at uthcode.com  Thu Sep  8 17:42:45 2016
From: senthil at uthcode.com (senthil at uthcode.com)
Date: Thu, 08 Sep 2016 21:42:45 -0000
Subject: [docs] http.client.HTTPConnection.putrequest incorrect
 arguments (issue 28010)
Message-ID: <20160908214245.6062.24119@psf.upfronthosting.co.za>


http://bugs.python.org/review/28010/diff/18422/Doc/library/http.client.rst
File Doc/library/http.client.rst (right):

http://bugs.python.org/review/28010/diff/18422/Doc/library/http.client.rst#newcode34
Doc/library/http.client.rst:34: .. class:: HTTPConnection(host,
port=None[, timeout], source_address=None)
I agree with this sentiment in general.  Give the 0 cost for improving
this non-controversial change, I made the clean up here.

http://bugs.python.org/review/28010/

From report at bugs.python.org  Thu Sep  8 17:46:18 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Sep 2016 21:46:18 +0000
Subject: [docs] [issue26020] set_display evaluation order doesn't match
 documented behaviour
In-Reply-To: <1452048141.82.0.22346371212.issue26020@psf.upfronthosting.co.za>
Message-ID: <20160908214614.59815.52277.FD84B8DB@psf.io>


Roundup Robot added the comment:

New changeset 0967531fc762 by Raymond Hettinger in branch '3.5':
Issue #26020:  Fix evaluation order for set literals
https://hg.python.org/cpython/rev/0967531fc762

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

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

From report at bugs.python.org  Thu Sep  8 18:25:36 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Sep 2016 22:25:36 +0000
Subject: [docs] [issue26020] set_display evaluation order doesn't match
 documented behaviour
In-Reply-To: <1452048141.82.0.22346371212.issue26020@psf.upfronthosting.co.za>
Message-ID: <20160908222533.69669.24854.5BB66E4A@psf.io>


Roundup Robot added the comment:

New changeset a8d504600c18 by Raymond Hettinger in branch '2.7':
Issue #26020: Fix evaluation order for set literals
https://hg.python.org/cpython/rev/a8d504600c18

----------

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

From report at bugs.python.org  Thu Sep  8 18:27:40 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Sep 2016 22:27:40 +0000
Subject: [docs] [issue26020] set_display evaluation order doesn't match
 documented behaviour
In-Reply-To: <1452048141.82.0.22346371212.issue26020@psf.upfronthosting.co.za>
Message-ID: <20160908222738.20970.45387.B416987D@psf.io>


Roundup Robot added the comment:

New changeset aa2bf603a9bd by Raymond Hettinger in branch '2.7':
Issue #26020: Add news entry
https://hg.python.org/cpython/rev/aa2bf603a9bd

----------

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

From report at bugs.python.org  Thu Sep  8 18:32:51 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 08 Sep 2016 22:32:51 +0000
Subject: [docs] [issue26020] set_display evaluation order doesn't match
 documented behaviour
In-Reply-To: <1452048141.82.0.22346371212.issue26020@psf.upfronthosting.co.za>
Message-ID: <1473373970.98.0.612717233879.issue26020@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Sep  8 18:46:32 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 22:46:32 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <525144B9.3040305@python.org>
Message-ID: <1473374792.53.0.520374395977.issue19180@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.6, Python 3.7

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

From report at bugs.python.org  Thu Sep  8 18:48:44 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 08 Sep 2016 22:48:44 +0000
Subject: [docs] [issue20762] SSLSocket.read() not documented
In-Reply-To: <1393262503.02.0.956219773808.issue20762@psf.upfronthosting.co.za>
Message-ID: <1473374924.87.0.782607230179.issue20762@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Sounds good, let's deprecate them with #28022.

----------
superseder:  -> SSL releated deprecation for 3.6
versions: +Python 3.6, Python 3.7 -Python 3.5

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

From report at bugs.python.org  Thu Sep  8 19:19:19 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Thu, 08 Sep 2016 23:19:19 +0000
Subject: [docs] [issue26982] Clarify forward annotations in PEP 484
In-Reply-To: <1462756311.8.0.304204398387.issue26982@psf.upfronthosting.co.za>
Message-ID: <1473376759.6.0.610415786056.issue26982@psf.upfronthosting.co.za>


Changes by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
nosy: +levkivskyi

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

From report at bugs.python.org  Thu Sep  8 20:53:50 2016
From: report at bugs.python.org (Wesley Emeneker)
Date: Fri, 09 Sep 2016 00:53:50 +0000
Subject: [docs] [issue28033] dictobject.c comment misspelling
Message-ID: <1473382430.74.0.828322185032.issue28033@psf.upfronthosting.co.za>


New submission from Wesley Emeneker:

This is a patch for a simple misspelling fix in a comment in dictobject.c

----------
assignee: docs at python
components: Documentation
files: dictobject_comment_misspell.patch
keywords: patch
messages: 275226
nosy: Wesley Emeneker, docs at python
priority: normal
severity: normal
status: open
title: dictobject.c comment misspelling
type: enhancement
versions: Python 3.7
Added file: http://bugs.python.org/file44481/dictobject_comment_misspell.patch

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

From report at bugs.python.org  Thu Sep  8 20:57:03 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 00:57:03 +0000
Subject: [docs] [issue28033] dictobject.c comment misspelling
In-Reply-To: <1473382430.74.0.828322185032.issue28033@psf.upfronthosting.co.za>
Message-ID: <20160909005659.13637.99262.7D79BCC1@psf.io>


Roundup Robot added the comment:

New changeset 30f20247bd14 by Berker Peksag in branch 'default':
Issue #28033: Fix typo in dictobject.c
https://hg.python.org/cpython/rev/30f20247bd14

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

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

From report at bugs.python.org  Thu Sep  8 20:57:49 2016
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 09 Sep 2016 00:57:49 +0000
Subject: [docs] [issue28033] dictobject.c comment misspelling
In-Reply-To: <1473382430.74.0.828322185032.issue28033@psf.upfronthosting.co.za>
Message-ID: <1473382669.2.0.625848484731.issue28033@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type: enhancement -> behavior
versions: +Python 3.6 -Python 3.7

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

From report at bugs.python.org  Thu Sep  8 21:34:00 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 09 Sep 2016 01:34:00 +0000
Subject: [docs] [issue20762] SSLSocket.read() not documented
In-Reply-To: <1393262503.02.0.956219773808.issue20762@psf.upfronthosting.co.za>
Message-ID: <1473384840.85.0.0724394081399.issue20762@psf.upfronthosting.co.za>


Martin Panter added the comment:

In the meantime, full documentation for the read() and write() methods was added for Python 3 in revision 61e52fda1006. The Python 2 documentation only mentions read() indirectly, in passing and in example code, and does not mention write().

But deprecating them makes sense to me. The essential functionality seems to already be available in the recv(), recv_into(), and send() or sendall() methods. The write() documentation is not clear regarding partial writes, in constrast with send() and sendall().

----------
nosy: +martin.panter

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

From report at bugs.python.org  Fri Sep  9 00:04:38 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 09 Sep 2016 04:04:38 +0000
Subject: [docs] [issue26982] Clarify forward annotations in PEP 484
In-Reply-To: <1462756311.8.0.304204398387.issue26982@psf.upfronthosting.co.za>
Message-ID: <1473393878.04.0.864862418533.issue26982@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

The PEPs repo is not on github. Please resubmit this patch as a PR at https://github.com/python/peps. (Sorry for all the indirections to different trackers.)

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

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

From report at bugs.python.org  Fri Sep  9 00:06:17 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 09 Sep 2016 04:06:17 +0000
Subject: [docs] [issue26982] Clarify forward annotations in PEP 484
In-Reply-To: <1473393878.04.0.864862418533.issue26982@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJL7BiY9OzcPWgvvS6fYRHMT4cAncDWUyrnQUdYV_hmGEA@mail.gmail.com>


Guido van Rossum added the comment:

(And by "not" I meant "now". Sorry.)

----------

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

From report at bugs.python.org  Fri Sep  9 01:13:01 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 09 Sep 2016 05:13:01 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1473397981.54.0.104919799088.issue27292@psf.upfronthosting.co.za>


Martin Panter added the comment:

Do you want to do an alternative patch Victor? Or point out all the specific bits of my patch you don?t like?

I haven?t really been keeping up to date with the getrandom() changes. Though I imagine even Python 3.6?s os.urandom() will still fall back to /dev/urandom (with potential entropy problem) on older Linux versions. Is the consensus that we want to warn about insecure results on Linux >= 3.17, but don?t want to warn about older Linux versions?

----------

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

From report at bugs.python.org  Fri Sep  9 03:01:00 2016
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 09 Sep 2016 07:01:00 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1473404460.48.0.678679158937.issue27292@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Though I imagine even Python 3.6?s os.urandom() will still fall back to /dev/urandom (with potential entropy problem) on older Linux versions.

Right, but you should be more specific in the doc.

os.urandom() is unsecure if and only if:

* getrandom() is not available (ex: Linux < 3.17, or Python built without getrandom() for different reasons) or don't work (ex: blocked by a stupid SECCOMP policy, ex: issue #27955)
* and /dev/urandom is not initialized yet which means that:

  - the currently running Python runs very early during the system initialization,
  - the system has no good source of entropy and slow entropy sources, 
  - no entropy was stored on the disk on a previous boot.

What I don't want: a doc warning that "oh hey, os.urandom() is unsafe, don't use it for anything serious".

os.urandom() is always secure on all platforms except Linux. On Linux, it's secure is almost all cases, except on a very few very tiny corner cases.

I proposed something like:

"On Linux, os.urandom() can return weak entropy when /dev/urandom is used internally and the system urandom entropy pool is not initialized yet."

I'm not even sure about "weak entropy" because in most cases, /dev/urandom is already partially initialized with good entropy, but just not enough to consider that it's fully initialized. Linux uses many entropy sources but don't trust them, so don't consider that these input data counts for the entropy counter.

----------

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

From report at bugs.python.org  Fri Sep  9 08:01:43 2016
From: report at bugs.python.org (Petr Viktorin)
Date: Fri, 09 Sep 2016 12:01:43 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1473422503.71.0.878306546393.issue27910@psf.upfronthosting.co.za>


Petr Viktorin added the comment:

This was a deliberate change in 3.5.

Issue: https://bugs.python.org/issue17911
News entry: https://docs.python.org/3/whatsnew/3.5.html#traceback

Why do you think it is a regression?
Who would be the person that can decide if it is a doc bug or regression?

----------
nosy: +encukou

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

From report at bugs.python.org  Fri Sep  9 08:13:10 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 09 Sep 2016 12:13:10 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473423190.29.0.419504247084.issue27999@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

I am attaching the patch.

Yury, I also added you here, just in case you have time for this.

Btw, while working on this I have found that the second restriction:

"""
Names listed in a global statement must not be ... in a for loop control target, class definition, function definition, or import statement.
"""

is not enforced at all, it does not give even a SyntaxWarning.
Is it something worth fixing?

----------
keywords: +patch
nosy: +yselivanov
Added file: http://bugs.python.org/file44501/patch-v1.diff

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

From report at bugs.python.org  Fri Sep  9 08:22:07 2016
From: report at bugs.python.org (Batiste)
Date: Fri, 09 Sep 2016 12:22:07 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
Message-ID: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>


New submission from Batiste:

Hi,

Here is a small patch for the documentation that make the sidebar follow the headers while scrolling through a long page.

http://imgur.com/UsrFAti

Test on Chrome and Firefox. Seems to work like a charm.

----------
assignee: docs at python
components: Documentation
files: following-sidebar.patch
keywords: patch
messages: 275315
nosy: batiste, docs at python
priority: normal
severity: normal
status: open
title: Make the sidebar in the documentation follow the section automatically
type: enhancement
Added file: http://bugs.python.org/file44502/following-sidebar.patch

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

From report at bugs.python.org  Fri Sep  9 10:18:51 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 09 Sep 2016 14:18:51 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473430731.24.0.35925122504.issue27999@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

Added few tests to the patch

----------
Added file: http://bugs.python.org/file44503/patch-v2.diff

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

From report at bugs.python.org  Fri Sep  9 11:54:05 2016
From: report at bugs.python.org (SilentGhost)
Date: Fri, 09 Sep 2016 15:54:05 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1473436445.57.0.975254509992.issue28044@psf.upfronthosting.co.za>


SilentGhost added the comment:

I get the following warning in Firefox's Developer console: 

This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features!

It would also be good to clear up a patch a little bit: the first chunk in sidebar.js seems spurious, the '.headerlink .headerlink' selector also looks odd. The nested menu items (e.g. in os.html) seem to confuse your code and make navigation non-functional.

----------
nosy: +SilentGhost
stage:  -> needs patch
versions: +Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri Sep  9 12:25:59 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 09 Sep 2016 16:25:59 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473438359.21.0.519351505476.issue27999@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

I'll commit this.

----------
assignee: docs at python -> gvanrossum

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

From report at bugs.python.org  Fri Sep  9 12:53:19 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 16:53:19 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <20160909165315.59448.29597.BC12D453@psf.io>


Roundup Robot added the comment:

New changeset 804b71d43c85 by Guido van Rossum in branch 'default':
Issue #27999: Make "global after use" a SyntaxError, and ditto for nonlocal.
https://hg.python.org/cpython/rev/804b71d43c85

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

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

From report at bugs.python.org  Fri Sep  9 12:53:46 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 16:53:46 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1473440026.02.0.132593265216.issue28044@psf.upfronthosting.co.za>


R. David Murray added the comment:

-1.  I don't like sites that do this, and don't want ours to be one of them.

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

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

From report at bugs.python.org  Fri Sep  9 12:53:54 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 09 Sep 2016 16:53:54 +0000
Subject: [docs] [issue27999] Make "global after use" a SyntaxError
In-Reply-To: <1473257318.94.0.500780981255.issue27999@psf.upfronthosting.co.za>
Message-ID: <1473440034.9.0.306834990602.issue27999@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Thanks again Ivan!

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

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

From report at bugs.python.org  Fri Sep  9 13:00:02 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 17:00:02 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1473440402.9.0.125757911681.issue28044@psf.upfronthosting.co.za>


R. David Murray added the comment:

But thanks for the interest and writing the patch.  Others may disagree with me and it may go in anyway :)

----------

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

From report at bugs.python.org  Fri Sep  9 13:19:26 2016
From: report at bugs.python.org (wim glenn)
Date: Fri, 09 Sep 2016 17:19:26 +0000
Subject: [docs] [issue28045] minor inaccuracy in range_contains_long
Message-ID: <1473441566.35.0.794224681084.issue28045@psf.upfronthosting.co.za>


New submission from wim glenn:

The [commented] code summarising this algorithm is incorrect because % has precedence over -  

Hey, no big deal it's just a comment after all, but may as well fix it up.

----------
assignee: docs at python
components: Documentation, Interpreter Core
files: mywork.patch
keywords: patch
messages: 275353
nosy: docs at python, wim.glenn
priority: normal
severity: normal
status: open
title: minor inaccuracy in range_contains_long
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file44505/mywork.patch

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

From report at bugs.python.org  Fri Sep  9 13:28:39 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 17:28:39 +0000
Subject: [docs] [issue25573] FrameSummary repr() does not support previously
 working uses of repr in traceback module
In-Reply-To: <1446845666.11.0.0803768990935.issue25573@psf.upfronthosting.co.za>
Message-ID: <1473442119.62.0.708039072494.issue25573@psf.upfronthosting.co.za>


R. David Murray added the comment:

Is there a reason the fourth element of the tuple is not included in the FrameSummary repr?  Otherwise I agree that this could be closed.

----------

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

From report at bugs.python.org  Fri Sep  9 13:35:14 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 17:35:14 +0000
Subject: [docs] [issue26502] traceback.extract_tb breaks compatibility by
 returning FrameSummary
In-Reply-To: <1457349348.27.0.253072992901.issue26502@psf.upfronthosting.co.za>
Message-ID: <1473442514.77.0.867868827622.issue26502@psf.upfronthosting.co.za>


R. David Murray added the comment:

I disagree that this is a duplicate.  The question here is, should we add __len__?  Since a FrameSummary object can be "cast into a tuple" and has a known len, I would say the answer is definitely yes.

----------
nosy: +r.david.murray
resolution: duplicate -> 
stage: resolved -> needs patch
status: closed -> open

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

From report at bugs.python.org  Fri Sep  9 14:22:01 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 18:22:01 +0000
Subject: [docs] [issue25573] FrameSummary repr() does not support previously
 working uses of repr in traceback module
In-Reply-To: <1446845666.11.0.0803768990935.issue25573@psf.upfronthosting.co.za>
Message-ID: <1473445321.93.0.843474377178.issue25573@psf.upfronthosting.co.za>


R. David Murray added the comment:

Ah, I see there is.  It is read lazily.  It is an interesting question whether it should be read when the repr is printed...let's say no until/unless someone comes up with a good reason why it would be worthwhile.

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

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

From report at bugs.python.org  Fri Sep  9 14:30:44 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 18:30:44 +0000
Subject: [docs] [issue25573] FrameSummary repr() does not support previously
 working uses of repr in traceback module
In-Reply-To: <1446845666.11.0.0803768990935.issue25573@psf.upfronthosting.co.za>
Message-ID: <1473445844.92.0.183610416904.issue25573@psf.upfronthosting.co.za>


R. David Murray added the comment:

I take it back.  Since tuple(framesummary) produces all four elements, I think the repr should too.  Likewise, in the __len__ issue I think it should always report 4.

Let see if other devs agree.

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

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

From report at bugs.python.org  Fri Sep  9 14:40:51 2016
From: report at bugs.python.org (Michael Lee)
Date: Fri, 09 Sep 2016 18:40:51 +0000
Subject: [docs] [issue28049] Add documentation for typing.Awaitable and
 friends
Message-ID: <1473446451.47.0.453913099768.issue28049@psf.upfronthosting.co.za>


New submission from Michael Lee:

This patch adds documentation for Awaitable, AsyncIterable, and AsyncIterator to the typing module, mostly linking to the corresponding class in collections.abc.

It also briefly clarifies the documentation on generators to explain that you may use either Iterable or Iterator as the return type of a generator.

----------
assignee: docs at python
components: Documentation
files: document-awaitable.patch
keywords: patch
messages: 275379
nosy: docs at python, gvanrossum, michael0x2a
priority: normal
severity: normal
status: open
title: Add documentation for typing.Awaitable and friends
versions: Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file44507/document-awaitable.patch

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

From report at bugs.python.org  Fri Sep  9 14:54:47 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 18:54:47 +0000
Subject: [docs] [issue28049] Add documentation for typing.Awaitable and
 friends
In-Reply-To: <1473446451.47.0.453913099768.issue28049@psf.upfronthosting.co.za>
Message-ID: <20160909185444.8568.96230.DB1B2792@psf.io>


Roundup Robot added the comment:

New changeset eba19d4b2944 by Guido van Rossum in branch 'default':
Issue #28049: Add documentation for typing.Awaitable and friends.
https://hg.python.org/cpython/rev/eba19d4b2944

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

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

From report at bugs.python.org  Fri Sep  9 14:55:46 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 09 Sep 2016 18:55:46 +0000
Subject: [docs] [issue28049] Add documentation for typing.Awaitable and
 friends
In-Reply-To: <1473446451.47.0.453913099768.issue28049@psf.upfronthosting.co.za>
Message-ID: <1473447346.86.0.848921033827.issue28049@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Sep  9 15:44:40 2016
From: report at bugs.python.org (Lorenzo Pascucci)
Date: Fri, 09 Sep 2016 19:44:40 +0000
Subject: [docs] [issue28051] Typo and broken links in page "What's New In
 Python 3.5"
Message-ID: <1473450280.07.0.816222969551.issue28051@psf.upfronthosting.co.za>


New submission from Lorenzo Pascucci:

In the documentation page "What's New In Python 3.5" there is a small typo within the section "Improved Modules" related to `asyncio` [0], along with 3 broken links.

Typo:
The function `loop.set_task_factory()` appears linked twice, but the second link is actually for the function `loop.get_task_factory()`.

Links:
The (duplicate) link for `loop.set_task_factory()` and the link for `loop.create_task()` point to the right documentation page, but to wrong anchors: they refer to `BaseEventLoop` whereas they should refer to `AbstractEventLoop`.


[0] https://docs.python.org/3/whatsnew/3.5.html#asyncio

----------
assignee: docs at python
components: Documentation
messages: 275407
nosy: Lorenzo Pascucci, docs at python
priority: normal
severity: normal
status: open
title: Typo and broken links in page "What's New In Python 3.5"
type: enhancement
versions: Python 3.5

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

From report at bugs.python.org  Fri Sep  9 15:47:17 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 19:47:17 +0000
Subject: [docs] [issue28051] Typo and broken links in page "What's New In
 Python 3.5"
In-Reply-To: <1473450280.07.0.816222969551.issue28051@psf.upfronthosting.co.za>
Message-ID: <20160909194714.1897.64794.C0543D07@psf.io>


Roundup Robot added the comment:

New changeset 8e74e76deda1 by Benjamin Peterson in branch '3.5':
repair errors in (set|get)_task_factory note (#28051)
https://hg.python.org/cpython/rev/8e74e76deda1

New changeset ace662dbfdb6 by Benjamin Peterson in branch 'default':
merge 3.5 (#28051)
https://hg.python.org/cpython/rev/ace662dbfdb6

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

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

From report at bugs.python.org  Fri Sep  9 16:05:20 2016
From: report at bugs.python.org (Ammar Askar)
Date: Fri, 09 Sep 2016 20:05:20 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1473451520.41.0.352321541128.issue19489@psf.upfronthosting.co.za>


Ammar Askar added the comment:

>The latter. All of the popular browsers (Chrome, Firefox, Edge and even Safari) already support the placeholder attribute so I think we can safely ignore IE 8 :)

Roger, I've changed it to placeholder.


>I know this is basically a copy of upstream searchbox.html, but we can probably remove ``style="display: none"`` and ``$('.inline-search').show(0);``.

The reason that exists is because sphinx's search relies on javascript.


>inline-search doesn't seem to be necessary here. ``display: inline`` is already applied by ``div.related li``.

Good catch, I've removed the class from there.

----------
Added file: http://bugs.python.org/file44509/searchbar_in_header.diff4

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

From report at bugs.python.org  Fri Sep  9 16:12:09 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 20:12:09 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <20160909201206.87425.36246.B8AEEC9A@psf.io>


Roundup Robot added the comment:

New changeset 274b25cd501f by Zachary Ware in branch '3.5':
Issue #19489: Move the search box from sidebar to header and footer.
https://hg.python.org/cpython/rev/274b25cd501f

New changeset 0f94a8fa5445 by Zachary Ware in branch 'default':
Closes #19489: Merge with 3.5
https://hg.python.org/cpython/rev/0f94a8fa5445

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

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

From report at bugs.python.org  Fri Sep  9 16:16:01 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 20:16:01 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <20160909201556.12454.96825.6597E469@psf.io>


Roundup Robot added the comment:

New changeset 8927417c5e88 by Zachary Ware in branch '3.5':
Issue #19489: Add NEWS and ACKS
https://hg.python.org/cpython/rev/8927417c5e88

New changeset 086c3e7a7955 by Zachary Ware in branch 'default':
Issue #19489: Merge with 3.5
https://hg.python.org/cpython/rev/086c3e7a7955

----------

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

From report at bugs.python.org  Fri Sep  9 16:16:19 2016
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 09 Sep 2016 20:16:19 +0000
Subject: [docs] [issue19489] move quick search box above TOC
In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>
Message-ID: <1473452179.4.0.261103763431.issue19489@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Ammar, thank you very much for the patch!

----------

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

From report at bugs.python.org  Fri Sep  9 16:26:34 2016
From: report at bugs.python.org (Benjamin Peterson)
Date: Fri, 09 Sep 2016 20:26:34 +0000
Subject: [docs] [issue28051] Typo and broken links in page "What's New In
 Python 3.5"
In-Reply-To: <1473450280.07.0.816222969551.issue28051@psf.upfronthosting.co.za>
Message-ID: <1473452794.28.0.702686209963.issue28051@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Sep  9 16:44:00 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 09 Sep 2016 20:44:00 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1473453840.68.0.163151561345.issue27212@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

The recipe should be modified to consume the initial values.  Something like this:

    start, stop, step = s.start or 0, s.stop or sys.maxsize, s.step or 1
    for i in zip(range(0, start), it):
        pass

The recipe needs to pass these tests:

    it = iter('abcdefghi')
    assert list(islice(it, 4, 4)) == []
    assert list(it) == ['e', 'f', 'g', 'h', 'i']
    assert(list(islice('ABCDEFG', 2)) == ['A', 'B'])
    assert(list(islice('ABCDEFG', 2, 4)) == ['C', 'D'])
    assert(list(islice('ABCDEFG', 2, None)) == ['C', 'D', 'E', 'F', 'G'])
    assert(list(islice('ABCDEFG', 0, None, 2)) == ['A', 'C', 'E', 'G'])

----------

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

From report at bugs.python.org  Fri Sep  9 16:45:52 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 09 Sep 2016 20:45:52 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1473453952.13.0.461537113583.issue27212@psf.upfronthosting.co.za>


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


----------
assignee: rhettinger -> Nofar Schnider
nosy: +Nofar Schnider

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

From report at bugs.python.org  Fri Sep  9 18:36:13 2016
From: report at bugs.python.org (Lisa Roach)
Date: Fri, 09 Sep 2016 22:36:13 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1473460571.82.0.0275697860261.issue27779@psf.upfronthosting.co.za>


Lisa Roach added the comment:

Hi Stefan and Raymond,

Here's my start on the patch, I wanted to get your opinions on the direction before I go too far. 

I've been comparing the two sets of docstrings, and trying to synchronize them in the clearest way that most closely matches the decimal specification docs. 

Let me know what you think!

----------
keywords: +patch
Added file: http://bugs.python.org/file44513/docstrings.patch

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

From report at bugs.python.org  Fri Sep  9 18:40:36 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Sep 2016 22:40:36 +0000
Subject: [docs] [issue20476] If new email policies are used,
 default message factory should be EmailMessage
In-Reply-To: <1391292485.67.0.381493162498.issue20476@psf.upfronthosting.co.za>
Message-ID: <20160909224033.48632.52647.33E7CCF4@psf.io>


Roundup Robot added the comment:

New changeset 9ba8f4be0651 by R David Murray in branch 'default':
#20476: add a message_factory policy attribute to email.
https://hg.python.org/cpython/rev/9ba8f4be0651

----------

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

From report at bugs.python.org  Fri Sep  9 19:05:04 2016
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Sep 2016 23:05:04 +0000
Subject: [docs] [issue20476] If new email policies are used,
 default message factory should be EmailMessage
In-Reply-To: <1391292485.67.0.381493162498.issue20476@psf.upfronthosting.co.za>
Message-ID: <1473462304.17.0.989048595445.issue20476@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed
type: resource usage -> enhancement
versions: +Python 3.6 -Python 3.5

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

From report at bugs.python.org  Fri Sep  9 19:25:59 2016
From: report at bugs.python.org (Lisa Roach)
Date: Fri, 09 Sep 2016 23:25:59 +0000
Subject: [docs] [issue27779] Sync-up docstrings in C version of the the
 decimal module
In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za>
Message-ID: <1473463559.82.0.917120854093.issue27779@psf.upfronthosting.co.za>


Lisa Roach added the comment:

I just noticed some trailing whitespace in the patch, ignore them for now and they'll be removed in the next patch.

----------

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

From report at bugs.python.org  Fri Sep  9 21:25:42 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 10 Sep 2016 01:25:42 +0000
Subject: [docs] [issue27705] Updating old C:/Windows/System32/ucrtbased.dll
In-Reply-To: <1470603749.52.0.375133152623.issue27705@psf.upfronthosting.co.za>
Message-ID: <20160910012539.69505.59822.A9504FD7@psf.io>


Roundup Robot added the comment:

New changeset 7f7a994bbfbc by Steve Dower in branch '3.5':
Issue #27705: Update message in validate_ucrtbase.py
https://hg.python.org/cpython/rev/7f7a994bbfbc

New changeset a791a54c0a1c by Steve Dower in branch 'default':
Issue #27705: Update message in validate_ucrtbase.py
https://hg.python.org/cpython/rev/a791a54c0a1c

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

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

From report at bugs.python.org  Fri Sep  9 21:27:47 2016
From: report at bugs.python.org (Steve Dower)
Date: Sat, 10 Sep 2016 01:27:47 +0000
Subject: [docs] [issue27705] Updating old C:/Windows/System32/ucrtbased.dll
In-Reply-To: <1470603749.52.0.375133152623.issue27705@psf.upfronthosting.co.za>
Message-ID: <1473470866.93.0.619766137323.issue27705@psf.upfronthosting.co.za>


Steve Dower added the comment:

The message now calls out the Windows 10 SDK specifically, and includes the (current) link to the download.

----------

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

From report at bugs.python.org  Sat Sep 10 00:09:46 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Sep 2016 04:09:46 +0000
Subject: [docs] [issue27705] Updating old C:/Windows/System32/ucrtbased.dll
In-Reply-To: <1470603749.52.0.375133152623.issue27705@psf.upfronthosting.co.za>
Message-ID: <1473480586.85.0.426744916447.issue27705@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Thanks, looks good to me.

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

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

From report at bugs.python.org  Sat Sep 10 00:25:34 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 10 Sep 2016 04:25:34 +0000
Subject: [docs] [issue20476] If new email policies are used,
 default message factory should be EmailMessage
In-Reply-To: <1391292485.67.0.381493162498.issue20476@psf.upfronthosting.co.za>
Message-ID: <20160910042531.36243.41514.66E43FC9@psf.io>


Roundup Robot added the comment:

New changeset 8375b8d54bf7 by R David Murray in branch 'default':
#20476: Deal with the message_factory circular import differently.
https://hg.python.org/cpython/rev/8375b8d54bf7

----------

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

From report at bugs.python.org  Sat Sep 10 00:32:45 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Sep 2016 04:32:45 +0000
Subject: [docs] [issue28057] Warnings (45) building Doc/library/email.*.rst
Message-ID: <1473481965.13.0.517391626967.issue28057@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

Sphinx v1.3.6
F:\Python\dev\36\Doc\library\email.compat32-message.rst:54: WARNING: duplicate object description of email.message.Message, other instance in F:\Python\dev\36\Doc\library\email.message.rst, use :noindex: for one of them

+ 44 more

----------
assignee: docs at python
components: Documentation, email
messages: 275564
nosy: barry, docs at python, r.david.murray, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Warnings (45) building Doc/library/email.*.rst
type: behavior
versions: Python 3.6

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

From report at bugs.python.org  Sat Sep 10 00:46:01 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Sep 2016 04:46:01 +0000
Subject: [docs] [issue28057] Warnings (45) building Doc/library/email.*.rst
In-Reply-To: <1473481965.13.0.517391626967.issue28057@psf.upfronthosting.co.za>
Message-ID: <1473482761.81.0.0161677062903.issue28057@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Hmm.  I just touched both email.compat32-message.rst and email.message.rst and retried, and there was no problem.

----------
resolution:  -> not a bug
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Sep 10 04:27:49 2016
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Sep 2016 08:27:49 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1473496069.86.0.434402789307.issue27292@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

On modern Intel chips, one of the entropy sources is the CPU itself, and so this problem is mostly theoretical on such systems unless you're worried about the quality of Intel's entropy generation (in which case you're well and truly into sovereign espionage and advanced persistent threat territory, and really shouldn't be blindly trusting operating systems and programming language runtimes to already be doing the right thing).

So the main ways to get bad entropy from /dev/urandom on Linux are:

- a misconfigured VM that has been cut off from all decent entropy sources, and doesn't have any persistent storage attached
- an embedded non-Intel chip that doesn't have any decent entropy sources or persistent storage attached

If you're not doing either of those things, you're probably fine. If you're worried that you might be, try running Python 3.6 and calling os.getrandom() explicitly to see what happens.

----------

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

From report at bugs.python.org  Sat Sep 10 06:21:47 2016
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Sep 2016 10:21:47 +0000
Subject: [docs] [issue10976] accept bytes in json.loads()
In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za>
Message-ID: <1473502907.13.0.634558228574.issue10976@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

As Martin noted, Serhiy has implemented the autodetection option for json.loads in #17909 so closing this one as out of date - UTF-8, UTF-16 and UTF-32 encoded JSON data will be deserialised automatically in 3.6, while other text encodings aren't officially supported by the JSON RFCs.

----------
resolution:  -> out of date
status: open -> closed
superseder:  -> Autodetecting JSON encoding

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

From report at bugs.python.org  Sat Sep 10 20:07:56 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 11 Sep 2016 00:07:56 +0000
Subject: [docs] [issue26141] typing module documentation incomplete
In-Reply-To: <1453049740.68.0.762293537242.issue26141@psf.upfronthosting.co.za>
Message-ID: <1473552475.53.0.247381218368.issue26141@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

Here is the patch for some omissions in typing module documentation.

Guido, please take a look.

----------
keywords: +patch
nosy: +gvanrossum
Added file: http://bugs.python.org/file44541/typing-doc.diff

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

From report at bugs.python.org  Sat Sep 10 20:17:33 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 11 Sep 2016 00:17:33 +0000
Subject: [docs] [issue26141] typing module documentation incomplete
In-Reply-To: <1453049740.68.0.762293537242.issue26141@psf.upfronthosting.co.za>
Message-ID: <1473553053.13.0.441146005391.issue26141@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Most things mentioned by Ben have been added (thanks Michael Lee!), but it seems the 3.5 docs and the 3.6 docs have deviated more than they ought to. I guess updating the 3.6 docs is more urgent because of the upcoming 3.6b1 release. I'll look later.

----------

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

From report at bugs.python.org  Sat Sep 10 20:27:09 2016
From: report at bugs.python.org (Michael Lee)
Date: Sun, 11 Sep 2016 00:27:09 +0000
Subject: [docs] [issue28073] Update documentation about None vs type(None)
 in typing
Message-ID: <1473553628.91.0.952557141974.issue28073@psf.upfronthosting.co.za>


New submission from Michael Lee:

For some reason, the section of the typing docs about Optional stated that Optional[T] was equivalent to Union[T, type(None)]. While this is true, it's somewhat inconsistent and potentially confusing since everywhere else in the docs, we just use None.

This patch modifies that line to use Union[T, type(None)] instead, and moves the line explaining that None is special-cased to mean type(None) to the first usage of None as a type within the docs.

----------
assignee: docs at python
components: Documentation
files: update-none-vs-type-none.patch
keywords: patch
messages: 275718
nosy: docs at python, gvanrossum, michael0x2a
priority: normal
severity: normal
status: open
title: Update documentation about None vs type(None) in typing
versions: Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file44542/update-none-vs-type-none.patch

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

From report at bugs.python.org  Sat Sep 10 20:32:04 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 11 Sep 2016 00:32:04 +0000
Subject: [docs] [issue26141] typing module documentation incomplete
In-Reply-To: <1453049740.68.0.762293537242.issue26141@psf.upfronthosting.co.za>
Message-ID: <1473553924.17.0.386762370767.issue26141@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

The patch contains docs for both new 3.6 features and missing 3.5:

ClassVar, Collection, plus also Sized, Hashable, DefaultDict, @overload, TYPE_CHECKING

Should I generate a separate patch for 3.5 with only 3.5 omissions?

----------

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

From report at bugs.python.org  Sat Sep 10 21:49:44 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Sep 2016 01:49:44 +0000
Subject: [docs] [issue28073] Update documentation about None vs type(None)
 in typing
In-Reply-To: <1473553628.91.0.952557141974.issue28073@psf.upfronthosting.co.za>
Message-ID: <20160911014940.8881.86921.7EC38F90@psf.io>


Roundup Robot added the comment:

New changeset 75514816741a by Guido van Rossum in branch '3.5':
Issue #28073: Improve wording around None. Michael Lee.
https://hg.python.org/cpython/rev/75514816741a

New changeset 7a4a16a880a4 by Guido van Rossum in branch 'default':
Issue #28073: Improve wording around None. Michael Lee. (3.5->3.6)
https://hg.python.org/cpython/rev/7a4a16a880a4

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

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

From report at bugs.python.org  Sat Sep 10 21:50:17 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 11 Sep 2016 01:50:17 +0000
Subject: [docs] [issue28073] Update documentation about None vs type(None)
 in typing
In-Reply-To: <1473553628.91.0.952557141974.issue28073@psf.upfronthosting.co.za>
Message-ID: <1473558617.76.0.0700887179708.issue28073@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Thanks! Busy Saturday  night, right? :-)

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

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

From report at bugs.python.org  Sat Sep 10 21:51:17 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 11 Sep 2016 01:51:17 +0000
Subject: [docs] [issue26141] typing module documentation incomplete
In-Reply-To: <1453049740.68.0.762293537242.issue26141@psf.upfronthosting.co.za>
Message-ID: <1473558676.95.0.922708734526.issue26141@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

I'll figure it out.

----------

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

From report at bugs.python.org  Sat Sep 10 22:05:56 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Sep 2016 02:05:56 +0000
Subject: [docs] [issue26141] typing module documentation incomplete
In-Reply-To: <1453049740.68.0.762293537242.issue26141@psf.upfronthosting.co.za>
Message-ID: <20160911020552.2793.99749.BECAC3AC@psf.io>


Roundup Robot added the comment:

New changeset 7187d167abe8 by Guido van Rossum in branch 'default':
Issue #26141: Update docs for typing.py. Ivan Levkivskyi.
https://hg.python.org/cpython/rev/7187d167abe8

New changeset 1dc45beca118 by Guido van Rossum in branch '3.5':
Issue #26141: Update docs for typing.py. Ivan Levkivskyi. (Backport from the 3.6 version)
https://hg.python.org/cpython/rev/1dc45beca118

New changeset 960a73507d4d by Guido van Rossum in branch 'default':
Issue #26141: Update docs for typing.py. Ivan Levkivskyi. (null merge 3.5->3.6)
https://hg.python.org/cpython/rev/960a73507d4d

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

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

From report at bugs.python.org  Sat Sep 10 22:06:20 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 11 Sep 2016 02:06:20 +0000
Subject: [docs] [issue26141] typing module documentation incomplete
In-Reply-To: <1453049740.68.0.762293537242.issue26141@psf.upfronthosting.co.za>
Message-ID: <1473559580.16.0.855303518694.issue26141@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Thanks!

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

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

From report at bugs.python.org  Sun Sep 11 00:07:25 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Sep 2016 04:07:25 +0000
Subject: [docs] [issue27680] Reduce Github pull request rate
In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za>
Message-ID: <1473566845.0.0.367630195382.issue27680@psf.upfronthosting.co.za>


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


----------
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

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

From berker.peksag at gmail.com  Sun Sep 11 03:12:18 2016
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Sun, 11 Sep 2016 07:12:18 -0000
Subject: [docs] UUID docs should say how to get "standard form" (issue
 26267)
Message-ID: <20160911071218.20904.8989@psf.upfronthosting.co.za>


https://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst
File Doc/library/uuid.rst (right):

https://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst#newcode56
Doc/library/uuid.rst:56: .. describe:: uuid1 == uuid2
On 2016/08/06 05:20:17, ammar2 wrote:
> On 2016/08/03 10:09:25, berkerpeksag wrote:
> > Same as above. See datetime or decimal documentations for an example
of how to
> > document comparison operations.
> 
> So datetime takes the approach of documenting operators in a table
(presumably
> because it has a lot of ops)
> https://docs.python.org/3/library/datetime.html#datetime.date.day
> 
> decimal seems to do it in  this way
> https://docs.python.org/3/library/decimal.html#decimal.Decimal.compare
> 
> The style I used here is from
> https://docs.python.org/3/library/stdtypes.html#set but now that I
look at it,
> within the stdtypes there's also the datetime style operator
documentation for
> numbers.
>
https://docs.python.org/3/library/stdtypes.html#numeric-types-int-float-complex
> 
> Is there a preferred style for documenting operators? Which one should
I use
> here?
> 
> (apparently I forgot to click the publish button on Rietveld, I wrote
this day
> before yesterday)

Sorry, I wasn't very clear in my earlier message. I was referring to the
following paragraph in datetime documentation:

    Comparisons of timedelta objects are supported with the timedelta
object representing the smaller duration considered to be the smaller
timedelta. In order to stop mixed-type comparisons from falling back to
the default comparison by object address, when a timedelta object is
compared to an object of a different type, TypeError is raised unless
the comparison is == or !=. The latter cases return False or True,
respectively.

https://docs.python.org/3/library/datetime.html#timedelta-objects

In other words, instead of using too much markup, it would be nice to
document that it supports comparison operators in prose.

https://bugs.python.org/review/26267/

From report at bugs.python.org  Sun Sep 11 06:02:25 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Sep 2016 10:02:25 +0000
Subject: [docs] [issue27991] In the argparse howto there is a misleading
 sentence about store_true
In-Reply-To: <1473217458.1.0.785896151958.issue27991@psf.upfronthosting.co.za>
Message-ID: <20160911100222.13175.13397.2F373F9B@psf.io>


Roundup Robot added the comment:

New changeset 0e45cd7859ec by Berker Peksag in branch '3.5':
Issue #27991: Remove incorrect sentence about store_true
https://hg.python.org/cpython/rev/0e45cd7859ec

New changeset 9a75fa28bd0a by Berker Peksag in branch 'default':
Issue #27991: Merge from 3.5
https://hg.python.org/cpython/rev/9a75fa28bd0a

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

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

From report at bugs.python.org  Sun Sep 11 06:02:56 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Sep 2016 10:02:56 +0000
Subject: [docs] [issue27991] In the argparse howto there is a misleading
 sentence about store_true
In-Reply-To: <1473217458.1.0.785896151958.issue27991@psf.upfronthosting.co.za>
Message-ID: <1473588176.44.0.226885084151.issue27991@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Good catch, thanks!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.5

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

From deon.hugo at vodamail.co.za  Thu Sep  8 08:58:26 2016
From: deon.hugo at vodamail.co.za (Deon P Hugo)
Date: Thu, 8 Sep 2016 14:58:26 +0200
Subject: [docs] Python 3.5.2: object() takes no parameters
Message-ID: <004501d209d0$dfc394b0$9f4abe10$@vodamail.co.za>

Good day,

I am using Python 3.5.2.

 

When I try to run the following program:

 

class Robot(object):

    """represents a robot with a name"""

    population = 0

 

    def _init_(self, name):

        self.name = name

        print("(Initializing {})".format(self.name))

 

        Robot.population += 1

 

    def die(self):

        print("{} is being destroyed!".format(self.name))

 

        Robot.population -= 1

 

        if Robot.population == 0:

            print("{} was the last one".format(self.name))

        else:

            print("There are still {:d} robots working. ".format(

                Robot.population))

 

    def say_hi(self):

        print("Greetings, my masters call me {} ".format(self.name))

 

    @classmethod

    def how_many(cls):

        print("we have {:d} robots".format(cls.population))

 

droid1 = Robot("r2r4")

droid1.say_hi()

Robot.how_many()

 

droid2 = Robot("C-3PO")

droid2.say_hi()

Robot.how_many()

 

print("\nRobots can do some work here.\n")

 

print("\nRobots have finished their work, so lets destroy them .\n")

 

droid1.die()

droid2.die()

 

Robot.how_many()

 

I get the following error message:

 

Traceback (most recent call last):

  File "C:\Users\Deon\Bite Of Python\oop_Class)bj_var.py", line 30, in
<module>

    droid1 = Robot("r2r4")

TypeError: object() takes no parameters

 

I have looked everywhere on the internet, however I could find no answer.

 

Any help will be much appreciated.

 

Regards,

 

Deon.

 



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160908/18a4cc23/attachment-0001.html>

From mallika.bachan at gmail.com  Sat Sep 10 15:22:15 2016
From: mallika.bachan at gmail.com (Mallika Bachan)
Date: Sat, 10 Sep 2016 12:22:15 -0700
Subject: [docs] reversing the meaning of shallow and deep copy??
Message-ID: <CAM99CZooxqXSyjCk_ME8ivk8oZf8CRq4q5zZ48mb-QGr9+EBKw@mail.gmail.com>

?All slice operations return a new list containing the requested elements.
This means that the following slice returns a new (shallow) copy of the
list:?

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



Why say (shallow), a **new** list means it is a **deep** copy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160910/61f1a5bf/attachment.html>

From mallika.bachan at gmail.com  Sat Sep 10 15:27:15 2016
From: mallika.bachan at gmail.com (Mallika Bachan)
Date: Sat, 10 Sep 2016 12:27:15 -0700
Subject: [docs] reversing the meaning of shallow and deep copy??
In-Reply-To: <CAM99CZooxqXSyjCk_ME8ivk8oZf8CRq4q5zZ48mb-QGr9+EBKw@mail.gmail.com>
References: <CAM99CZooxqXSyjCk_ME8ivk8oZf8CRq4q5zZ48mb-QGr9+EBKw@mail.gmail.com>
Message-ID: <CAM99CZrWxqR52DX28hReFJ=LeFKbppe=4frM4HSrMD8Co3oRuw@mail.gmail.com>

Just because it's not a *full* deep copy ref:
http://www.python-course.eu/deep_copy.php
doesn't mean it's a shallow copy, rt?

On Sat, Sep 10, 2016 at 12:22 PM, Mallika Bachan <mallika.bachan at gmail.com>
wrote:

> ?All slice operations return a new list containing the requested elements.
> This means that the following slice returns a new (shallow) copy of the
> list:?
>
> Ref: https://docs.python.org/2/tutorial/introduction.html
>
>
>
> Why say (shallow), a **new** list means it is a **deep** copy.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160910/0b6d2ffb/attachment.html>

From report at bugs.python.org  Sun Sep 11 08:45:35 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Sep 2016 12:45:35 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <20160911124532.20970.55859.DFE8CEC1@psf.io>


Roundup Robot added the comment:

New changeset 9023c4f5d467 by Berker Peksag in branch '3.5':
Issue #20100: Clarify that passing flags to epoll() has no effect
https://hg.python.org/cpython/rev/9023c4f5d467

New changeset d2b5806fa770 by Berker Peksag in branch 'default':
Issue #20100: Merge from 3.5
https://hg.python.org/cpython/rev/d2b5806fa770

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

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

From report at bugs.python.org  Sun Sep 11 09:11:35 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Sep 2016 13:11:35 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <1473599495.57.0.896212518935.issue20100@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Here is an updated patch for Modules/selectmodule.c. It would be nice to get a code review.

----------
Added file: http://bugs.python.org/file44553/selectmodule.diff

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

From report at bugs.python.org  Sun Sep 11 10:17:08 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Sep 2016 14:17:08 +0000
Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available
 on Linux
In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za>
Message-ID: <20160911141704.12492.16913.5455B497@psf.io>


Roundup Robot added the comment:

New changeset 5ca4c545dfe4 by Vinay Sajip in branch '2.7':
Issue #23105: Updated documentation on open() flag constants.
https://hg.python.org/cpython/rev/5ca4c545dfe4

New changeset f1427491a8a5 by Vinay Sajip in branch '3.5':
Issue #23105: Updated documentation on open() flag constants.
https://hg.python.org/cpython/rev/f1427491a8a5

New changeset 64610bcd326f by Vinay Sajip in branch 'default':
Closes #23105: Merged update from 3.5.
https://hg.python.org/cpython/rev/64610bcd326f

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

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

From report at bugs.python.org  Sun Sep 11 19:17:23 2016
From: report at bugs.python.org (Thomi Richards)
Date: Sun, 11 Sep 2016 23:17:23 +0000
Subject: [docs] [issue26511] Add link to id() built-in in comparison
 operator documentation for "is"
In-Reply-To: <1457451562.01.0.849547274402.issue26511@psf.upfronthosting.co.za>
Message-ID: <1473635843.59.0.859418686495.issue26511@psf.upfronthosting.co.za>


Thomi Richards added the comment:

Attached patch for master branch.

----------
keywords: +patch
nosy: +thomir
Added file: http://bugs.python.org/file44568/issue_26511.patch

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

From berker.peksag at gmail.com  Sun Sep 11 19:22:17 2016
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Mon, 12 Sep 2016 02:22:17 +0300
Subject: [docs] Python 3.5.2: object() takes no parameters
In-Reply-To: <004501d209d0$dfc394b0$9f4abe10$@vodamail.co.za>
References: <004501d209d0$dfc394b0$9f4abe10$@vodamail.co.za>
Message-ID: <CAF4280+9iDB9=tK4AuJ09rRo03KBDRk98pa4axWG7DuEqat1Nw@mail.gmail.com>

On Thu, Sep 8, 2016 at 3:58 PM, Deon P Hugo <deon.hugo at vodamail.co.za>
wrote:

> Good day,
>
> I am using Python 3.5.2.
>
>
>
> When I try to run the following program:
>
>
>

 Hi Deon,

Questions like this should be asked on StackOverflow or python-list, but I
think you need to rename _init_ to __init__ in the following line:

    def _init_(self, name):

--Berker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160912/52f53847/attachment.html>

From report at bugs.python.org  Sun Sep 11 19:34:59 2016
From: report at bugs.python.org (Thomi Richards)
Date: Sun, 11 Sep 2016 23:34:59 +0000
Subject: [docs] [issue26511] Add link to id() built-in in comparison
 operator documentation for "is"
In-Reply-To: <1457451562.01.0.849547274402.issue26511@psf.upfronthosting.co.za>
Message-ID: <1473636899.4.0.670590736474.issue26511@psf.upfronthosting.co.za>


Thomi Richards added the comment:

The attached patch applies to 3.5, but not 2.7. If you're happy with it, I can work up a version for 2.7 as well.

----------

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

From report at bugs.python.org  Sun Sep 11 20:07:12 2016
From: report at bugs.python.org (Steve Kowalik)
Date: Mon, 12 Sep 2016 00:07:12 +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: <1473638832.89.0.407604124888.issue16700@psf.upfronthosting.co.za>


Steve Kowalik added the comment:

I've looked at the documentation for both Python 3.5 and 3.6, and I think this is all fine -- things like os.environb and os.getcwdb() are clearly stated as not available on Windows, and the path functions look to work fine in my testing.

----------
nosy: +stevenk

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

From report at bugs.python.org  Sun Sep 11 20:07:55 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 12 Sep 2016 00:07:55 +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: <1473638875.77.0.363276638133.issue16700@psf.upfronthosting.co.za>


Barry A. Warsaw added the comment:

Thanks Steve!  Closing.

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

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

From report at bugs.python.org  Sun Sep 11 20:15:27 2016
From: report at bugs.python.org (Robert Collins)
Date: Mon, 12 Sep 2016 00:15:27 +0000
Subject: [docs] [issue25573] FrameSummary repr() does not support previously
 working uses of repr in traceback module
In-Reply-To: <1446845666.11.0.0803768990935.issue25573@psf.upfronthosting.co.za>
Message-ID: <1473639326.1.0.485272951473.issue25573@psf.upfronthosting.co.za>


Robert Collins added the comment:

So I think its fine to have a __len__ reporting 4. tuple(..) works via the iter() call, but thats really just a thunk to keep existing code working, and so __len__ for the same reason makes sense.

On the documentation issue, yes, updating the docs is appropriate.

Having the repr produce all the elements would be ok, the reason it is lazy is to avoid high costs for transient FrameSummary when its created and discarded shortly after.

----------

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

From report at bugs.python.org  Sun Sep 11 20:24:23 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Sep 2016 00:24:23 +0000
Subject: [docs] [issue26511] Add link to id() built-in in comparison
 operator documentation for "is"
In-Reply-To: <1457451562.01.0.849547274402.issue26511@psf.upfronthosting.co.za>
Message-ID: <20160912002410.48474.40199.A7D7F9F9@psf.io>


Roundup Robot added the comment:

New changeset f38b831cb6b9 by Raymond Hettinger in branch '3.5':
Issue #26511:  Reference the id() function in the 'is' and 'is not' docs
https://hg.python.org/cpython/rev/f38b831cb6b9

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

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

From report at bugs.python.org  Sun Sep 11 20:25:23 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 12 Sep 2016 00:25:23 +0000
Subject: [docs] [issue26511] Add link to id() built-in in comparison
 operator documentation for "is"
In-Reply-To: <1457451562.01.0.849547274402.issue26511@psf.upfronthosting.co.za>
Message-ID: <1473639922.52.0.858375077562.issue26511@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Thanks for the patch.  Not need to go back to 2.7.  This is really minor.

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

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

From report at bugs.python.org  Sun Sep 11 21:33:48 2016
From: report at bugs.python.org (Yury Selivanov)
Date: Mon, 12 Sep 2016 01:33:48 +0000
Subject: [docs] [issue28089] Document TCP_NODELAY by default
Message-ID: <1473644028.24.0.015052680352.issue28089@psf.upfronthosting.co.za>


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


----------
assignee: docs at python
components: Documentation, asyncio
keywords: easy
nosy: docs at python, gvanrossum, haypo, ned.deily, yselivanov
priority: release blocker
severity: normal
stage: needs patch
status: open
title: Document TCP_NODELAY by default
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Sun Sep 11 21:34:12 2016
From: report at bugs.python.org (Yury Selivanov)
Date: Mon, 12 Sep 2016 01:34:12 +0000
Subject: [docs] [issue28088] Document Transport.set_protocol and get_protocol
Message-ID: <1473644052.28.0.365675741284.issue28088@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Sep 11 22:20:52 2016
From: report at bugs.python.org (Thomi Richards)
Date: Mon, 12 Sep 2016 02:20:52 +0000
Subject: [docs] [issue26557] dictviews methods not present on shelve objects
In-Reply-To: <1457954340.57.0.630883947605.issue26557@psf.upfronthosting.co.za>
Message-ID: <1473646852.92.0.856830928758.issue26557@psf.upfronthosting.co.za>


Thomi Richards added the comment:

Attached is a patch that adds documentation to `shelve.rst` explicitly stating that it does not support the viewkeys, viewvalues, and viewitems methods. 

I think this is the correct approach since it doesn't seems sensible to add support for these methods to UserDict, *and* also it might give users the impression that they can incrementally iterate over a shelved object without loading it all (which I believe is incorrect).

----------
keywords: +patch
nosy: +thomir
Added file: http://bugs.python.org/file44578/issue26557_shelve.patch

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

From report at bugs.python.org  Sun Sep 11 22:23:22 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 12 Sep 2016 02:23:22 +0000
Subject: [docs] [issue26557] dictviews methods not present on shelve objects
In-Reply-To: <1457954340.57.0.630883947605.issue26557@psf.upfronthosting.co.za>
Message-ID: <1473647002.45.0.751582680863.issue26557@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

This patch looks fine.

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

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

From report at bugs.python.org  Sun Sep 11 22:24:16 2016
From: report at bugs.python.org (Thomi Richards)
Date: Mon, 12 Sep 2016 02:24:16 +0000
Subject: [docs] [issue26557] dictviews methods not present on shelve objects
In-Reply-To: <1457954340.57.0.630883947605.issue26557@psf.upfronthosting.co.za>
Message-ID: <1473647056.77.0.989048523042.issue26557@psf.upfronthosting.co.za>


Thomi Richards added the comment:

Attached is a patch that adds a sentence to the UserDict module docs explicitly stating that the viewkeys, viewitems, and viewvalues functions are not implemented. I don't think it's worth adding support for these newer functions in UserDict. I'm unsure whether landing this patch is as necessary as the patch for the shelve module.

----------
Added file: http://bugs.python.org/file44580/issue26557_userdict.patch

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

From report at bugs.python.org  Sun Sep 11 23:38:35 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Sep 2016 03:38:35 +0000
Subject: [docs] [issue26557] dictviews methods not present on shelve objects
In-Reply-To: <1457954340.57.0.630883947605.issue26557@psf.upfronthosting.co.za>
Message-ID: <20160912033832.21157.50661.BE13B285@psf.io>


Roundup Robot added the comment:

New changeset 2b4bfef0d54a by Raymond Hettinger in branch '2.7':
Issue #26557:  Note that mapping view methods are not present in UserDict or shelves.
https://hg.python.org/cpython/rev/2b4bfef0d54a

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

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

From report at bugs.python.org  Sun Sep 11 23:38:47 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 12 Sep 2016 03:38:47 +0000
Subject: [docs] [issue26557] dictviews methods not present on shelve objects
In-Reply-To: <1457954340.57.0.630883947605.issue26557@psf.upfronthosting.co.za>
Message-ID: <1473651527.06.0.348642945067.issue26557@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Sep 12 00:12:10 2016
From: report at bugs.python.org (Tom Clark)
Date: Mon, 12 Sep 2016 04:12:10 +0000
Subject: [docs] [issue28094] Document behaviour of Process.join() in
 multiprocessing
Message-ID: <1473653530.84.0.163889885928.issue28094@psf.upfronthosting.co.za>


New submission from Tom Clark:

#10673 indicated that the issue should be resolved by clarifying the documentation. The proposed patch is intended to do this.

----------
assignee: docs at python
components: Documentation
files: multiprocessing.patch
keywords: patch
messages: 275943
nosy: docs at python, tclark
priority: normal
severity: normal
status: open
title: Document behaviour of Process.join() in multiprocessing
type: enhancement
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file44584/multiprocessing.patch

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

From report at bugs.python.org  Mon Sep 12 00:20:33 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 Sep 2016 04:20:33 +0000
Subject: [docs] [issue28094] Document behaviour of Process.join() in
 multiprocessing
In-Reply-To: <1473653530.84.0.163889885928.issue28094@psf.upfronthosting.co.za>
Message-ID: <1473654033.14.0.245336712626.issue28094@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Hi Tom, thanks for the patch! Issue 10673 is still open, is there a reason not to attach your patch there?

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

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

From report at bugs.python.org  Mon Sep 12 00:26:28 2016
From: report at bugs.python.org (Tom Clark)
Date: Mon, 12 Sep 2016 04:26:28 +0000
Subject: [docs] [issue28094] Document behaviour of Process.join() in
 multiprocessing
In-Reply-To: <1473653530.84.0.163889885928.issue28094@psf.upfronthosting.co.za>
Message-ID: <1473654388.68.0.330877548525.issue28094@psf.upfronthosting.co.za>


Tom Clark added the comment:

I thought that, since Issue <10673> refers to the library rather than the docs, it was better to create a seperate documentation issue.  In other words, I probably overthought it.

----------

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

From report at bugs.python.org  Mon Sep 12 00:29:56 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 Sep 2016 04:29:56 +0000
Subject: [docs] [issue28094] Document behaviour of Process.join() in
 multiprocessing
In-Reply-To: <1473653530.84.0.163889885928.issue28094@psf.upfronthosting.co.za>
Message-ID: <1473654596.51.0.16205423198.issue28094@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the explanation. We usually handle situations like this in the same issue so I'm closing this as a duplicate of issue 10673. Could you please attach your patch to issue 10673? Thanks!

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> multiprocess.Process join method - timeout indistinguishable from success

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

From report at bugs.python.org  Mon Sep 12 00:46:58 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Sep 2016 04:46:58 +0000
Subject: [docs] [issue28045] minor inaccuracy in range_contains_long
In-Reply-To: <1473441566.35.0.794224681084.issue28045@psf.upfronthosting.co.za>
Message-ID: <20160912044655.18872.2526.AA70EBD3@psf.io>


Roundup Robot added the comment:

New changeset 957084395042 by Berker Peksag in branch '3.5':
Issue #28045: Fix comment in range_contains_long()
https://hg.python.org/cpython/rev/957084395042

New changeset 924a64745168 by Berker Peksag in branch 'default':
Issue #28045: Merge from 3.5
https://hg.python.org/cpython/rev/924a64745168

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

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

From report at bugs.python.org  Mon Sep 12 00:48:02 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 Sep 2016 04:48:02 +0000
Subject: [docs] [issue28045] minor inaccuracy in range_contains_long
In-Reply-To: <1473441566.35.0.794224681084.issue28045@psf.upfronthosting.co.za>
Message-ID: <1473655682.3.0.103408105166.issue28045@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Good catch, thanks!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type: enhancement -> behavior
versions:  -Python 2.7, Python 3.3, Python 3.4, Python 3.7

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

From report at bugs.python.org  Mon Sep 12 02:49:44 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 12 Sep 2016 06:49:44 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <1473662984.6.0.890311339849.issue20100@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

There is small behavior difference. Currently OSError raised for invalid flags has errno=EINVAL, with the patch it wouldn't have errno. If this is okay, the patch LGTM.

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

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

From report at bugs.python.org  Mon Sep 12 04:04:03 2016
From: report at bugs.python.org (Batiste)
Date: Mon, 12 Sep 2016 08:04:03 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1473667443.29.0.194416680366.issue28044@psf.upfronthosting.co.za>


Batiste added the comment:

Here is a second patch which is improved in some ways:

1. removed the '.headerlink .headerlink'
2. when scrolling over the side bar the 'snappin' is disabled therefor it is rather easy to search and find the desired section or the search box
3. removed an error when collapsing the menu
4. Scrolling all the way down with a small viewport doesn't push the sidebar over the footer

----------
Added file: http://bugs.python.org/file44590/following-sidebar-2.patch

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

From report at bugs.python.org  Mon Sep 12 04:19:52 2016
From: report at bugs.python.org (Batiste)
Date: Mon, 12 Sep 2016 08:19:52 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1473668392.25.0.190806920188.issue28044@psf.upfronthosting.co.za>


Batiste added the comment:

Minor typo fix.

----------
Added file: http://bugs.python.org/file44591/following-sidebar-3.patch

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

From report at bugs.python.org  Mon Sep 12 04:36:44 2016
From: report at bugs.python.org (Batiste)
Date: Mon, 12 Sep 2016 08:36:44 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1473669404.73.0.901960415024.issue28044@psf.upfronthosting.co.za>


Batiste added the comment:

So answer to your comments SilentGhost:

I had a look at what Mozilla recommend. Their proposition of using position:sticky is interesting and probably possible for this use case but might require quite a bit of extra work. There is also the other suggestion to use something like https://lodash.com/docs/4.15.0#debounce but that would mean more jumpy animations but less computation. Also there is this http://caniuse.com/#feat=css-snappoints that would solve the issue created just before but it is not well supported yet.

All in all interesting points.

Off course I am willing to spend some time on optimization this if necessary. But before that I might want to have some kind of "approval" that my work as a chance to be used.

And I have a question for you R. David Murray. Look here for example:

https://docs.python.org/3/library/asyncio-protocol.html#udp-echo-server-protocol

What is the value of having an empty left sidebar here? Shoudn't we remove the sidebar completly if you have to scroll all the way up anyway? I don't really see the value for this sidebar in many of the long pages Python documentation offers.

----------

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

From report at bugs.python.org  Mon Sep 12 06:31:50 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 Sep 2016 10:31:50 +0000
Subject: [docs] [issue27604] More details about `-O` flag
In-Reply-To: <1469353581.38.0.811049911305.issue27604@psf.upfronthosting.co.za>
Message-ID: <1473676310.09.0.917715275654.issue27604@psf.upfronthosting.co.za>


Berker Peksag added the comment:

This is a duplicate of issue 17232. Note that "This changes the filename extension for compiled files from ``.pyc`` to ``.pyo``." part is no longer true. See PEP 488 for details.

----------
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Improve -O docs

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

From report at bugs.python.org  Mon Sep 12 11:37:19 2016
From: report at bugs.python.org (Stephen J. Turnbull)
Date: Mon, 12 Sep 2016 15:37:19 +0000
Subject: [docs] [issue28103] Style fix in zipfile.rst
Message-ID: <1473694639.54.0.408781099961.issue28103@psf.upfronthosting.co.za>


New submission from Stephen J. Turnbull:

Makes style of references to open modes 'r', 'a', ... more consistent.

CA pending (I have received PDF, but no star in tracker yet).

----------
assignee: docs at python
components: Documentation
files: zipfile-doc-style
messages: 276058
nosy: docs at python, sjt
priority: normal
severity: normal
status: open
title: Style fix in zipfile.rst
versions: Python 3.7
Added file: http://bugs.python.org/file44595/zipfile-doc-style

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

From report at bugs.python.org  Mon Sep 12 11:51:07 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 12 Sep 2016 15:51:07 +0000
Subject: [docs] [issue28103] Style fix in zipfile.rst
In-Reply-To: <1473694639.54.0.408781099961.issue28103@psf.upfronthosting.co.za>
Message-ID: <1473695467.04.0.172559493433.issue28103@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

LGTM.

----------
nosy: +serhiy.storchaka
stage:  -> commit review
type:  -> enhancement

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

From report at bugs.python.org  Mon Sep 12 13:07:31 2016
From: report at bugs.python.org (Nathan Marrow)
Date: Mon, 12 Sep 2016 17:07:31 +0000
Subject: [docs] [issue28104] Set documentation is incorrect
Message-ID: <1473700051.49.0.516497540366.issue28104@psf.upfronthosting.co.za>


New submission from Nathan Marrow:

The library documentation for set intersection gives this definition:
intersection(other, ...)

For any set, s, however, intersection may be called with no arguments, which returns the same set. The documentation, as written, implies such usage would raise a TypeError. I believe it should be intersection(*others). Same for difference, union, intersection_update, difference_update, and update.

----------
assignee: docs at python
components: Documentation
messages: 276070
nosy: docs at python, nmarrow
priority: normal
severity: normal
status: open
title: Set documentation is incorrect
versions: Python 2.7

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

From report at bugs.python.org  Mon Sep 12 13:15:24 2016
From: report at bugs.python.org (Jakub Stasiak)
Date: Mon, 12 Sep 2016 17:15:24 +0000
Subject: [docs] [issue8840] truncate() semantics changed in 3.1.2
In-Reply-To: <1275005546.82.0.0795236723796.issue8840@psf.upfronthosting.co.za>
Message-ID: <1473700524.16.0.477039153048.issue8840@psf.upfronthosting.co.za>


Changes by Jakub Stasiak <jakub+python.org at stasiak.at>:


----------
nosy: +jstasiak

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

From report at bugs.python.org  Mon Sep 12 13:36:58 2016
From: report at bugs.python.org (R. David Murray)
Date: Mon, 12 Sep 2016 17:36:58 +0000
Subject: [docs] [issue28104] Set documentation is incorrect
In-Reply-To: <1473700051.49.0.516497540366.issue28104@psf.upfronthosting.co.za>
Message-ID: <1473701818.2.0.169464867024.issue28104@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Sep 12 14:06:56 2016
From: report at bugs.python.org (Mark Lawrence)
Date: Mon, 12 Sep 2016 18:06:56 +0000
Subject: [docs] [issue8840] truncate() semantics changed in 3.1.2
In-Reply-To: <1275005546.82.0.0795236723796.issue8840@psf.upfronthosting.co.za>
Message-ID: <1473703616.93.0.523747585336.issue8840@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at yahoo.co.uk>:


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

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

From report at bugs.python.org  Mon Sep 12 14:38:07 2016
From: report at bugs.python.org (Arun Persaud)
Date: Mon, 12 Sep 2016 18:38:07 +0000
Subject: [docs] [issue21018] [patch] added missing documentation about
 escaping characters for configparser
In-Reply-To: <1395464420.76.0.68706986346.issue21018@psf.upfronthosting.co.za>
Message-ID: <1473705487.17.0.572083959503.issue21018@psf.upfronthosting.co.za>


Arun Persaud added the comment:

updated the patch, let me know if it needs additional changes.

----------
Added file: http://bugs.python.org/file44598/escape.patch

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

From report at bugs.python.org  Mon Sep 12 15:07:22 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 12 Sep 2016 19:07:22 +0000
Subject: [docs] [issue28107] Update typing module dicumentation for
 NamedTuple
Message-ID: <1473707242.23.0.095655840586.issue28107@psf.upfronthosting.co.za>


New submission from Ivan Levkivskyi:

The implementation of NamedTuple in typing module has been extended to support PEP 526 variable annotation syntax.

Here is he patch that updates documentation accordingly.

----------
assignee: docs at python
components: Documentation
files: nmtuple-doc.diff
keywords: patch
messages: 276092
nosy: docs at python, gvanrossum, levkivskyi
priority: normal
severity: normal
status: open
title: Update typing module dicumentation for NamedTuple
versions: Python 3.6
Added file: http://bugs.python.org/file44600/nmtuple-doc.diff

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

From report at bugs.python.org  Mon Sep 12 15:23:16 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 12 Sep 2016 19:23:16 +0000
Subject: [docs] [issue28107] Update typing module dicumentation for
 NamedTuple
In-Reply-To: <1473707242.23.0.095655840586.issue28107@psf.upfronthosting.co.za>
Message-ID: <1473708196.26.0.835450073607.issue28107@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Honestly I think it's better if this remains a "hidden" feature until we have support for it in mypy. So let's wait for that.

----------

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

From report at bugs.python.org  Mon Sep 12 15:24:11 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 12 Sep 2016 19:24:11 +0000
Subject: [docs] [issue28107] Update typing module dicumentation for
 NamedTuple
In-Reply-To: <1473707242.23.0.095655840586.issue28107@psf.upfronthosting.co.za>
Message-ID: <1473708251.41.0.822362332065.issue28107@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

OK

----------

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

From report at bugs.python.org  Mon Sep 12 16:00:24 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 12 Sep 2016 20:00:24 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
Message-ID: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>


New submission from Ivan Levkivskyi:

The attached patch contains a simple item summarizing PEP 526 in 3.6 What's New.

----------
assignee: docs at python
components: Documentation
files: whats-new-pep-526.diff
keywords: patch
messages: 276105
nosy: docs at python, gvanrossum, levkivskyi
priority: normal
severity: normal
status: open
title: What's new item for PEP 526 -- Variable annotations
versions: Python 3.6
Added file: http://bugs.python.org/file44602/whats-new-pep-526.diff

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

From report at bugs.python.org  Mon Sep 12 16:13:48 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 12 Sep 2016 20:13:48 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473711228.02.0.917414983066.issue28109@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

This should probably wait until b1 is released; it looks like What's New is mostly empty anyways. The release manager needs to focus on the release.

----------

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

From report at bugs.python.org  Mon Sep 12 16:16:40 2016
From: report at bugs.python.org (Ned Deily)
Date: Mon, 12 Sep 2016 20:16:40 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473711400.59.0.455429498836.issue28109@psf.upfronthosting.co.za>


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


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

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

From guido at python.org  Mon Sep 12 16:20:26 2016
From: guido at python.org (guido at python.org)
Date: Mon, 12 Sep 2016 20:20:26 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations (issue
 28109)
Message-ID: <20160912202026.22903.18759@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18521/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18521/Doc/whatsnew/3.6.rst#newcode295
Doc/whatsnew/3.6.rst:295: Python interpreter does not attach any
particular meaning to these annotations.
The Python interpreter

(also mention __annotations__?)

http://bugs.python.org/review/28109/diff/18521/Doc/whatsnew/3.6.rst#newcode298
Doc/whatsnew/3.6.rst:298: type metadata for third party tools.
and libraries? (again, __annotations__)

http://bugs.python.org/review/28109/

From report at bugs.python.org  Mon Sep 12 16:43:08 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 12 Sep 2016 20:43:08 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473712988.92.0.224963335089.issue28109@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

Updated patch

----------
Added file: http://bugs.python.org/file44603/whats-new-pep-526-v2.diff

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

From report at bugs.python.org  Mon Sep 12 18:23:51 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 12 Sep 2016 22:23:51 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473719031.63.0.747829523132.issue28109@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

Second update, implemented comments by Yury an Guido.

----------
Added file: http://bugs.python.org/file44606/whats-new-pep-526-v3.diff

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

From report at bugs.python.org  Mon Sep 12 18:41:49 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 12 Sep 2016 22:41:49 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473720109.32.0.431154420888.issue28109@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Patch LGTM.

----------

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

From report at bugs.python.org  Mon Sep 12 18:58:18 2016
From: report at bugs.python.org (Robert Collins)
Date: Mon, 12 Sep 2016 22:58:18 +0000
Subject: [docs] [issue26240] Docstring of the subprocess module should be
 cleaned up
In-Reply-To: <1454131083.41.0.870668221205.issue26240@psf.upfronthosting.co.za>
Message-ID: <1473721041.87.0.860787729681.issue26240@psf.upfronthosting.co.za>


Changes by Robert Collins <robertc at robertcollins.net>:


----------
nosy: +rbcollins

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

From report at bugs.python.org  Mon Sep 12 19:03:35 2016
From: report at bugs.python.org (Thomi Richards)
Date: Mon, 12 Sep 2016 23:03:35 +0000
Subject: [docs] [issue17188] Document 'from None' in raise statement doc.
In-Reply-To: <1360631999.8.0.76627095073.issue17188@psf.upfronthosting.co.za>
Message-ID: <1473721415.81.0.975920524821.issue17188@psf.upfronthosting.co.za>


Thomi Richards added the comment:

I have attached a patch for 3.4, based on the patch submitted by Nitika Agarwal. The main difference is that I think it's better to be explicit and show a separate example of `raise X from None`.

I will submit a patch for later versions as well.

----------
nosy: +thomir
Added file: http://bugs.python.org/file44607/issue17188_3.4.patch

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

From report at bugs.python.org  Mon Sep 12 19:07:19 2016
From: report at bugs.python.org (Thomi Richards)
Date: Mon, 12 Sep 2016 23:07:19 +0000
Subject: [docs] [issue17188] Document 'from None' in raise statement doc.
In-Reply-To: <1360631999.8.0.76627095073.issue17188@psf.upfronthosting.co.za>
Message-ID: <1473721639.65.0.473502776447.issue17188@psf.upfronthosting.co.za>


Thomi Richards added the comment:

OK, it seems that patch applies cleanly to 3.5 and 3.6.

----------

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

From report at bugs.python.org  Mon Sep 12 19:28:56 2016
From: report at bugs.python.org (Robert Collins)
Date: Mon, 12 Sep 2016 23:28:56 +0000
Subject: [docs] [issue20140] UnicodeDecodeError in ntpath.py when home dir
 contains non-ascii signs
In-Reply-To: <1389005031.99.0.692658963376.issue20140@psf.upfronthosting.co.za>
Message-ID: <1473722936.47.0.0654204582231.issue20140@psf.upfronthosting.co.za>


Robert Collins added the comment:

Given two (or more) parameters where one is unicode and one is not, upcasting will occur multiples times in path.join on windows: 
 - '\\' is str and will cast up safely in all codecs
 - the other str (or bytes) parameter will be upcast using sys.defaultencoding which is often / usually ASCII on Windows

This will then fail when the str parameter is not valid ASCII.

>From this we can conclude that this is a failure to use path.join correctly: if all the parameters passed in were unicode, no error would occur as only '\\' would be getting coerced to unicode.

The interesting question is why there was a str parameter that wasn't valid ASCII; and that lies with path.expanduser() which is returning a str for the non-ascii home directory.

Changing that to return unicode rather than a no-encoding specified str when HOME or HOMEPATH etc etc contain non-ascii characters is a change that would worry me - specifically that we'd encounter code that assumes it is always str, e.g. by calling path.join(expanduser('~fred'), '\xe1\xbd\x84D') which will then blow up.

Worth noting too is that 

 expanduser(u'~user/\u14ffd')

will also blow up in the same way in the same situation - as it ends up decoding the user home path when it concatenates userhome and path[i:].

So, what to do:
 - It might be worth testing a patch that changes expanduser to decode the environment variables - I'm not sure whether we'd want the filesystemencoding or the defaultencoding for handling these environment variables. Steve Dower probably knows :).
 - Or we say 'sorry, too hard in 2.7' and move on: join *itself* is fine here, given the limits of 2.7.

----------
nosy: +rbcollins, steve.dower

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

From report at bugs.python.org  Mon Sep 12 21:49:32 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Sep 2016 01:49:32 +0000
Subject: [docs] [issue28103] Style fix in zipfile.rst
In-Reply-To: <1473694639.54.0.408781099961.issue28103@psf.upfronthosting.co.za>
Message-ID: <20160913014928.2574.43763.C99C5308@psf.io>


Roundup Robot added the comment:

New changeset 138625694ed6 by Berker Peksag in branch '3.5':
Issue #28103: Use ``'...'`` style in zipfile documentation
https://hg.python.org/cpython/rev/138625694ed6

New changeset 89b0ca61ad03 by Berker Peksag in branch '3.6':
Issue #28103: Merge from 3.5
https://hg.python.org/cpython/rev/89b0ca61ad03

New changeset 5b41ff5b2a8e by Berker Peksag in branch 'default':
Issue #28103: Merge from 3.6
https://hg.python.org/cpython/rev/5b41ff5b2a8e

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

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

From report at bugs.python.org  Mon Sep 12 21:50:31 2016
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 13 Sep 2016 01:50:31 +0000
Subject: [docs] [issue28103] Style fix in zipfile.rst
In-Reply-To: <1473694639.54.0.408781099961.issue28103@psf.upfronthosting.co.za>
Message-ID: <1473731431.57.0.29941271332.issue28103@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed
versions: +Python 3.5, Python 3.6

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

From report at bugs.python.org  Mon Sep 12 22:02:25 2016
From: report at bugs.python.org (Eryk Sun)
Date: Tue, 13 Sep 2016 02:02:25 +0000
Subject: [docs] [issue20140] UnicodeDecodeError in ntpath.py when home dir
 contains non-ascii signs
In-Reply-To: <1389005031.99.0.692658963376.issue20140@psf.upfronthosting.co.za>
Message-ID: <1473732145.35.0.988304518507.issue20140@psf.upfronthosting.co.za>


Eryk Sun added the comment:

> It might be worth testing a patch that changes expanduser to 
> decode the environment variables 

If expanduser() is passed a unicode path, it can use _winreg.ExpandEvironmentStrings(u'%USERPROFILE%') instead of decoding os.environ['USERPROFILE']. In 2.7, os.environ is a lossy ANSI encoding of the native Unicode environment block.

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

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

From report at bugs.python.org  Mon Sep 12 22:20:19 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 13 Sep 2016 02:20:19 +0000
Subject: [docs] [issue28104] Set documentation is incorrect
In-Reply-To: <1473700051.49.0.516497540366.issue28104@psf.upfronthosting.co.za>
Message-ID: <1473733219.05.0.422255726916.issue28104@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Sep 13 00:49:42 2016
From: report at bugs.python.org (Thomi Richards)
Date: Tue, 13 Sep 2016 04:49:42 +0000
Subject: [docs] [issue17188] Document 'from None' in raise statement doc.
In-Reply-To: <1360631999.8.0.76627095073.issue17188@psf.upfronthosting.co.za>
Message-ID: <1473742182.2.0.862784125979.issue17188@psf.upfronthosting.co.za>


Thomi Richards added the comment:

Re-uploaded the patch without the typo.

----------
Added file: http://bugs.python.org/file44618/issue17188_3.4.patch

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

From report at bugs.python.org  Tue Sep 13 02:39:17 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Sep 2016 06:39:17 +0000
Subject: [docs] [issue28104] Set documentation is incorrect
In-Reply-To: <1473700051.49.0.516497540366.issue28104@psf.upfronthosting.co.za>
Message-ID: <20160913063910.21095.47527.454219FD@psf.io>


Roundup Robot added the comment:

New changeset 5d93a9b4f0e8 by Raymond Hettinger in branch '3.5':
Issue #28104: More accurately document set method signatures
https://hg.python.org/cpython/rev/5d93a9b4f0e8

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

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

From report at bugs.python.org  Tue Sep 13 02:43:17 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Sep 2016 06:43:17 +0000
Subject: [docs] [issue28104] Set documentation is incorrect
In-Reply-To: <1473700051.49.0.516497540366.issue28104@psf.upfronthosting.co.za>
Message-ID: <20160913064310.69669.91065.6DD76163@psf.io>


Roundup Robot added the comment:

New changeset f30a76f0d477 by Raymond Hettinger in branch '2.7':
Issue #28104: More accurately document set method signatures
https://hg.python.org/cpython/rev/f30a76f0d477

----------

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

From report at bugs.python.org  Tue Sep 13 02:45:44 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 13 Sep 2016 06:45:44 +0000
Subject: [docs] [issue28104] Set documentation is incorrect
In-Reply-To: <1473700051.49.0.516497540366.issue28104@psf.upfronthosting.co.za>
Message-ID: <1473749144.57.0.700434210696.issue28104@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Sep 13 03:07:35 2016
From: report at bugs.python.org (Pierre Ducroquet)
Date: Tue, 13 Sep 2016 07:07:35 +0000
Subject: [docs] =?utf-8?q?=5Bissue28116=5D_Error_in_what=27s_new_-_PEP?=
 =?utf-8?b?wqA1MTU=?=
Message-ID: <1473750455.95.0.91976047794.issue28116@psf.upfronthosting.co.za>


New submission from Pierre Ducroquet:

The what's new section about PEP 515 says :
?With PEP 515, though, you can use underscores to separate digits as desired to make numeric literals easier to read: 1_000_000_000_000_000. Underscores can be used with other numeric literals beyond integers, e.g. 0x_FF_FF_FF_FF.?

As far as I know, 0xFFFFFFFF is 2 ** 32 - 1, an integer.
I think the author meant ?beyond decimals?

----------
assignee: docs at python
components: Documentation
messages: 276192
nosy: Pierre Ducroquet, docs at python
priority: normal
severity: normal
status: open
title: Error in what's new - PEP?515
versions: Python 3.6

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

From report at bugs.python.org  Tue Sep 13 03:11:39 2016
From: report at bugs.python.org (Petri Lehtinen)
Date: Tue, 13 Sep 2016 07:11:39 +0000
Subject: [docs] [issue17188] Document 'from None' in raise statement doc.
In-Reply-To: <1360631999.8.0.76627095073.issue17188@psf.upfronthosting.co.za>
Message-ID: <1473750699.82.0.54606042558.issue17188@psf.upfronthosting.co.za>


Changes by Petri Lehtinen <petri at digip.org>:


----------
nosy:  -petri.lehtinen

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

From report at bugs.python.org  Tue Sep 13 05:46:46 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Sep 2016 09:46:46 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1342446105.53.0.956340794171.issue15369@psf.upfronthosting.co.za>
Message-ID: <20160913094642.36352.24577.9A63BC89@psf.io>


Roundup Robot added the comment:

New changeset 08a0b75904c6 by Victor Stinner in branch 'default':
Remove pybench microbenchmark
https://hg.python.org/cpython/rev/08a0b75904c6

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

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

From report at bugs.python.org  Tue Sep 13 05:49:24 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Sep 2016 09:49:24 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1342446105.53.0.956340794171.issue15369@psf.upfronthosting.co.za>
Message-ID: <20160913094921.1874.8189.3B1AEAEE@psf.io>


Roundup Robot added the comment:

New changeset e03c1b6830fd by Victor Stinner in branch 'default':
Remove pystone microbenchmark
https://hg.python.org/cpython/rev/e03c1b6830fd

----------

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

From report at bugs.python.org  Tue Sep 13 05:52:02 2016
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 13 Sep 2016 09:52:02 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1342446105.53.0.956340794171.issue15369@psf.upfronthosting.co.za>
Message-ID: <1473760322.58.0.366096964262.issue15369@psf.upfronthosting.co.za>


STINNER Victor added the comment:

We now have a good and stable benchmark suite: https://github.com/python/performance

I removed pystone and pybench from Python 3.7. Please use performance instead of old and not reliable microbenchmarks like pybench or pystone.

----------
nosy: +haypo
resolution:  -> fixed
status: open -> closed
versions: +Python 3.7 -Python 3.3

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

From report at bugs.python.org  Tue Sep 13 06:34:00 2016
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 13 Sep 2016 10:34:00 +0000
Subject: [docs] [issue28124] Rework SSL module documentation
Message-ID: <1473762840.76.0.666078412099.issue28124@psf.upfronthosting.co.za>


New submission from Christian Heimes:

The documentation of the SSL module needs a rework. It's confusing and hard to understand even for experienced developers. The documentation should start with basic use cases and easy-to-reuse best practices.

* The module starts with move ssl.wrap_socket() but it's no longer best practice. The section should be moved down and favor of a quick introduction of SSLContext.

* ssl.create_default_context() is the best way to create a SSLContext. Mention that purpose flags and that Purpose.SERVER_AUTH is the correct setting on the client side. It means: "Create a context to authenticate the certs of a TLS server." (correct also for ftp, imap, ldap, smtp and so on).

* The protocol table is confusing and does not mention the meaning of PROTOCOL_SSLv23 (aka PROTOCOL_TLS). It's auto-negotiation of the highest TLS protocol version and takes OP_NO_* SSLContext.options into account. PROTOCOL_TLS_CLIENT and PROTOCOL_TLS_SERVER are the recommended options nowadays.

* Don't confront users with CERT_OPTIONAL in the first section. It's a super special mode for client cert authentication on the server side. On the client side, CERT_REQUIRED is the right mode with CERT_NONE as workaround. On the server side CERT_NONE (default) is usually the right setting.

* check_hostname is a client-side option that should be enabled all the time.

* Explain that users can load the public key of a  self-signed certificate like a CA cert to have cert validation even for self-signed certs.

----------
assignee: docs at python
components: Documentation
messages: 276238
nosy: christian.heimes, docs at python
priority: high
severity: normal
stage: needs patch
status: open
title: Rework SSL module documentation
type: enhancement
versions: Python 3.6, Python 3.7

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

From report at bugs.python.org  Tue Sep 13 06:36:20 2016
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Tue, 13 Sep 2016 10:36:20 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473762980.49.0.0919708410665.issue28109@psf.upfronthosting.co.za>


Changes by Ivan Levkivskyi <levkivskyi at gmail.com>:


Added file: http://bugs.python.org/file44626/whats-new-pep-526-v3a.diff

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

From guido at python.org  Mon Sep 12 18:19:02 2016
From: guido at python.org (guido at python.org)
Date: Mon, 12 Sep 2016 22:19:02 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160912221902.14715.83528@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode295
Doc/whatsnew/3.6.rst:295: Just as for function annotations, Python
interpreter does not attach any
Still needs "the" in front of "Python interpreter".

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode300
Doc/whatsnew/3.6.rst:300: type metadata for third party tools and
libraries via abstract syntax tree and
*the* abstract syntax tree

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode309
Doc/whatsnew/3.6.rst:309: 
On 2016/09/12 23:54:22, Yury Selivanov wrote:
> I think we can add a link to mypy and/or pytype, and maybe even
mention PyCharm.

Yes.

http://bugs.python.org/review/28109/

From guido at python.org  Tue Sep 13 00:04:19 2016
From: guido at python.org (guido at python.org)
Date: Tue, 13 Sep 2016 04:04:19 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160913040419.21554.83313@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode297
Doc/whatsnew/3.6.rst:297: attribute ``__annotations__`` of a class or
module.
On 2016/09/13 01:14:30, Yury Selivanov wrote:
> Should we add an example like this:
> 
>    x: int = 'spam'
> 
> ^ legal from Python's standpoint, but tools will complain?

No.  We're very carefully not going there. The PEP is neutral on what
code means.  People can use their imagination though. :-)

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode298
Doc/whatsnew/3.6.rst:298: In contrast to variable declarations in
statically typed languages,
On 2016/09/13 01:14:30, Yury Selivanov wrote:
> A new line before "In contrast.." to make this a separate paragraph?

No, it's a clarification of the previous sentence.

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode309
Doc/whatsnew/3.6.rst:309: Tools that could benefit from this syntax
include
On 2016/09/13 01:14:30, Yury Selivanov wrote:
> I'd replace with "Tools that use or will use the new syntax: mypy,
pytype,
> PyCharm" -- Guido, what do you think?

Fine, but I tend not to overthink this -- it's okay either way.

http://bugs.python.org/review/28109/

From i at lufei.so  Tue Sep 13 01:53:55 2016
From: i at lufei.so (=?utf-8?B?SmV0THU=?=)
Date: Tue, 13 Sep 2016 13:53:55 +0800
Subject: [docs] python360b1.chm bugs
Message-ID: <tencent_69B22DA0476430823B240E88@qq.com>

OS: win7
python: python3.6b1 64


error: The value of attribute "$" is null?undefined or not Function.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160913/d8c44c9f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C3B0FB33 at 4D418464.7394D757
Type: application/octet-stream
Size: 19090 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20160913/d8c44c9f/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2016-09-13_134339.jpg
Type: application/octet-stream
Size: 19090 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20160913/d8c44c9f/attachment-0003.obj>

From jetlu93 at gmail.com  Tue Sep 13 01:55:55 2016
From: jetlu93 at gmail.com (Jet Lu)
Date: Tue, 13 Sep 2016 13:55:55 +0800
Subject: [docs] python360b1.chm bugs
Message-ID: <CAOT_kR_DFoTZVH93z+EifEeVJV1qVioux7qHV1atDA3XS_Pkew@mail.gmail.com>

OS: win7
python: python3.6b1 64

error: The value of attribute "$" is null?undefined or not Function.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160913/3205c352/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2016-09-13_134339.jpg
Type: image/jpeg
Size: 19090 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20160913/3205c352/attachment-0001.jpg>

From levkivskyi at gmail.com  Mon Sep 12 16:44:09 2016
From: levkivskyi at gmail.com (levkivskyi at gmail.com)
Date: Mon, 12 Sep 2016 20:44:09 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160912204409.22903.28440@psf.upfronthosting.co.za>

Reviewers: gvanrossum,

Message:
I mentioned ast in addition to __annotations__ at the end.


http://bugs.python.org/review/28109/diff/18521/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18521/Doc/whatsnew/3.6.rst#newcode295
Doc/whatsnew/3.6.rst:295: Python interpreter does not attach any
particular meaning to these annotations.
On 2016/09/12 22:20:26, gvanrossum wrote:
> The Python interpreter
> 
> (also mention __annotations__?)

Done.

http://bugs.python.org/review/28109/diff/18521/Doc/whatsnew/3.6.rst#newcode298
Doc/whatsnew/3.6.rst:298: type metadata for third party tools.
On 2016/09/12 22:20:26, gvanrossum wrote:
> and libraries? (again, __annotations__)

Done.



Please review this at http://bugs.python.org/review/28109/

Affected files:
  Doc/whatsnew/3.6.rst


diff -r da485c6c744e Doc/whatsnew/3.6.rst
--- a/Doc/whatsnew/3.6.rst	Mon Sep 12 19:27:46 2016 +0200
+++ b/Doc/whatsnew/3.6.rst	Mon Sep 12 22:35:45 2016 +0200
@@ -72,7 +72,7 @@
 
 * PEP 515: Underscores in Numeric Literals
 
-* PEP 526: Syntax for Variable Annotations
+* PEP 526: :ref:`Syntax for Variable Annotations <variable-annotations>`
 
 * PEP 525: Asynchronous Generators
 
@@ -275,6 +275,38 @@
 
 See :pep:`498` and the main documentation at :ref:`f-strings`.
 
+
+.. _variable-annotations:
+
+PEP 526: Syntax for variable annotations
+========================================
+
+:pep:`484` introduced standard for type annotations of function parameters,
+a.k.a. type hints. This PEP adds syntax to Python for annotating the
+types of variables (including class variables and instance variables)::
+
+    primes: List[int] = []
+
+    captain: str  # Note: no initial value!
+
+    class Starship:
+        stats: Dict[str, int] = {}
+
+Just as for function annotations, Python interpreter does not attach any
+particular meaning to variable annotations and only stores them in a special
+attribute ``__annotations__`` of a class or module.
+In contrast to variable declarations in statically typed languages,
+the goal of annotation syntax is to provide an easy way to specify structured
+type metadata for third party tools and libraries via abstract syntax tree and
+the ``__annotations__`` attribute. 
+
+.. seealso::
+
+   :pep:`526` -- Syntax for variable annotations.
+      PEP written by Ryan Gonzalez, Philip House, Ivan Levkivskyi, Lisa Roach,
+      and Guido van Rossum
+
+
 .. _pep-529:
 
 PEP 529: Change Windows filesystem encoding to UTF-8



From levkivskyi at gmail.com  Mon Sep 12 18:24:17 2016
From: levkivskyi at gmail.com (levkivskyi at gmail.com)
Date: Mon, 12 Sep 2016 22:24:17 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160912222417.14715.33061@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode286
Doc/whatsnew/3.6.rst:286: types of variables (including class variables
and instance variables)::
On 2016/09/12 23:54:22, Yury Selivanov wrote:
> Drop the parens please

Done.

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode295
Doc/whatsnew/3.6.rst:295: Just as for function annotations, Python
interpreter does not attach any
On 2016/09/13 00:19:02, gvanrossum wrote:
> Still needs "the" in front of "Python interpreter".

Done.

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode300
Doc/whatsnew/3.6.rst:300: type metadata for third party tools and
libraries via abstract syntax tree and
On 2016/09/13 00:19:02, gvanrossum wrote:
> *the* abstract syntax tree

Done.

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode307
Doc/whatsnew/3.6.rst:307: and Guido van Rossum
On 2016/09/12 23:54:22, Yury Selivanov wrote:
> Add "Implemented by <your name>." :)

OK :-)

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode309
Doc/whatsnew/3.6.rst:309: 
On 2016/09/12 23:54:22, Yury Selivanov wrote:
> I think we can add a link to mypy and/or pytype, and maybe even
mention PyCharm.

Done.

http://bugs.python.org/review/28109/

From levkivskyi at gmail.com  Tue Sep 13 06:36:53 2016
From: levkivskyi at gmail.com (levkivskyi at gmail.com)
Date: Tue, 13 Sep 2016 10:36:53 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160913103653.22817.83045@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode309
Doc/whatsnew/3.6.rst:309: Tools that could benefit from this syntax
include
On 2016/09/13 01:14:30, Yury Selivanov wrote:
> I'd replace with "Tools that use or will use the new syntax: mypy,
pytype,
> PyCharm" -- Guido, what do you think?

OK, I don't have a preference here, I attach another patch with this
sentence changed.

http://bugs.python.org/review/28109/

From yselivanov at gmail.com  Mon Sep 12 17:54:22 2016
From: yselivanov at gmail.com (yselivanov at gmail.com)
Date: Mon, 12 Sep 2016 21:54:22 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160912215422.6586.46708@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode286
Doc/whatsnew/3.6.rst:286: types of variables (including class variables
and instance variables)::
Drop the parens please

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode307
Doc/whatsnew/3.6.rst:307: and Guido van Rossum
Add "Implemented by <your name>." :)

http://bugs.python.org/review/28109/diff/18522/Doc/whatsnew/3.6.rst#newcode309
Doc/whatsnew/3.6.rst:309: 
I think we can add a link to mypy and/or pytype, and maybe even mention
PyCharm.

http://bugs.python.org/review/28109/

From yselivanov at gmail.com  Mon Sep 12 19:14:30 2016
From: yselivanov at gmail.com (yselivanov at gmail.com)
Date: Mon, 12 Sep 2016 23:14:30 -0000
Subject: [docs] What's new item for PEP 526 -- Variable annotations
 (issue 28109)
Message-ID: <20160912231430.22903.86904@psf.upfronthosting.co.za>


http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode297
Doc/whatsnew/3.6.rst:297: attribute ``__annotations__`` of a class or
module.
Should we add an example like this:

   x: int = 'spam'

^ legal from Python's standpoint, but tools will complain?

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode298
Doc/whatsnew/3.6.rst:298: In contrast to variable declarations in
statically typed languages,
A new line before "In contrast.." to make this a separate paragraph?

http://bugs.python.org/review/28109/diff/18524/Doc/whatsnew/3.6.rst#newcode309
Doc/whatsnew/3.6.rst:309: Tools that could benefit from this syntax
include
I'd replace with "Tools that use or will use the new syntax: mypy,
pytype, PyCharm" -- Guido, what do you think?

http://bugs.python.org/review/28109/

From report at bugs.python.org  Tue Sep 13 12:01:46 2016
From: report at bugs.python.org (Alexander Belopolsky)
Date: Tue, 13 Sep 2016 16:01:46 +0000
Subject: [docs] [issue28130] Document that time.tzset updates time module
 constants
Message-ID: <1473782506.71.0.242774514927.issue28130@psf.upfronthosting.co.za>


New submission from Alexander Belopolsky:

Reported by MAL in #22798 (msg251840):

"The fact that tzset() does update the module globals is
not documented."

The documentation should explicitly list timezone, daylight, altzone and tzname as the globals that are updated when time.tzset() is called.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 276294
nosy: belopolsky, docs at python
priority: normal
severity: normal
status: open
title: Document that time.tzset updates time module constants
versions: Python 3.6

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

From report at bugs.python.org  Tue Sep 13 12:19:25 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 13 Sep 2016 16:19:25 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473783565.81.0.0502972722517.issue28109@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

I'll take the latter. Give me a sec.

----------

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

From report at bugs.python.org  Tue Sep 13 12:28:02 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 13 Sep 2016 16:28:02 +0000
Subject: [docs] [issue28109] What's new item for PEP 526 -- Variable
 annotations
In-Reply-To: <1473710424.07.0.410665624445.issue28109@psf.upfronthosting.co.za>
Message-ID: <1473784082.54.0.373740553966.issue28109@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

changeset:   103770:2c9e07db0ac4
tag:         tip
parent:      103768:879bde95a456
parent:      103769:f9b22b1bec2d
user:        Guido van Rossum <guido at python.org>
date:        Tue Sep 13 09:27:07 2016 -0700
summary:     Add text about PEP 526 to What's new in 3.6. Ivan L. (merge 3.6->3.7)

changeset:   103769:f9b22b1bec2d
branch:      3.6
parent:      103767:12d88d08f191
user:        Guido van Rossum <guido at python.org>
date:        Tue Sep 13 09:26:38 2016 -0700
summary:     Add text about PEP 526 to What's new in 3.6. Ivan L.

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

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

From report at bugs.python.org  Tue Sep 13 14:16:02 2016
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 13 Sep 2016 18:16:02 +0000
Subject: [docs] =?utf-8?q?=5Bissue28116=5D_Error_in_what=27s_new_-_PEP?=
 =?utf-8?b?wqA1MTU=?=
In-Reply-To: <1473750455.95.0.91976047794.issue28116@psf.upfronthosting.co.za>
Message-ID: <1473790562.76.0.622726074636.issue28116@psf.upfronthosting.co.za>


Brett Cannon added the comment:

the author meant "integer literals" when he said "integers" which is accurate as the hex literal isn't quite the same (e.g. uses different parse rules, etc.). If you would still like to propose different wording then you can submit a pull request at github.com/python/peps for consideration.

----------
nosy: +brett.cannon
resolution:  -> third party
status: open -> closed

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

From report at bugs.python.org  Tue Sep 13 15:27:20 2016
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Tue, 13 Sep 2016 19:27:20 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1342446105.53.0.956340794171.issue15369@psf.upfronthosting.co.za>
Message-ID: <1473794840.69.0.316221750505.issue15369@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

Please add notes to the Tools/README pointing users to the performance suite.

I'd also like to request that you reword this dismissive line in the performance package's readme:

"""
pybench - run the standard Python PyBench benchmark suite. This is considered an unreliable, unrepresentative benchmark; do not base decisions off it. It is included only for completeness.
"""

I suppose this was taken from the Unladden Swallow list of benchmarks and completely misses the point of what pybench is all about: it's a benchmark to run performance tests for individual parts of CPython's VM implementation. It never was intended to be representative. The main purpose is to be able to tell whether an optimization in CPython has an impact on individual areas of the interpreter or not.

Thanks.

----------

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

From report at bugs.python.org  Tue Sep 13 16:30:12 2016
From: report at bugs.python.org (triuan)
Date: Tue, 13 Sep 2016 20:30:12 +0000
Subject: [docs] [issue28136] RegEx documentation error
Message-ID: <1473798612.84.0.969871008678.issue28136@psf.upfronthosting.co.za>


New submission from triuan:

https://docs.python.org/2/library/re.html

error:
...string 'aaaaaa', a{3,5} will match 5 'a' characters...

suggest correction:
...string 'aaaaaa', a{5} will match 5 'a' characters...

----------
assignee: docs at python
components: Documentation
messages: 276336
nosy: docs at python, triuan
priority: normal
severity: normal
status: open
title: RegEx documentation error

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

From report at bugs.python.org  Tue Sep 13 16:34:16 2016
From: report at bugs.python.org (triuan)
Date: Tue, 13 Sep 2016 20:34:16 +0000
Subject: [docs] [issue28136] RegEx documentation error
In-Reply-To: <1473798612.84.0.969871008678.issue28136@psf.upfronthosting.co.za>
Message-ID: <1473798856.1.0.387564519674.issue28136@psf.upfronthosting.co.za>


triuan added the comment:

https://docs.python.org/2/library/re.html

error:
...string 'aaaaaa', a{3,5} will match 5 'a' characters...

suggest correction 2:
...string 'aaaaaa', a{3, 5} will match 3 to 5 'a' characters...

----------

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

From report at bugs.python.org  Tue Sep 13 16:35:23 2016
From: report at bugs.python.org (ppperry)
Date: Tue, 13 Sep 2016 20:35:23 +0000
Subject: [docs] [issue10673] multiprocess.Process join method - timeout
 indistinguishable from success
In-Reply-To: <1291991778.63.0.145134143934.issue10673@psf.upfronthosting.co.za>
Message-ID: <1473798923.78.0.582974000218.issue10673@psf.upfronthosting.co.za>


Changes by ppperry <mapreader at olum.org>:


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

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

From report at bugs.python.org  Tue Sep 13 16:40:41 2016
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 13 Sep 2016 20:40:41 +0000
Subject: [docs] [issue28136] RegEx documentation error
In-Reply-To: <1473798612.84.0.969871008678.issue28136@psf.upfronthosting.co.za>
Message-ID: <1473799241.58.0.486918962081.issue28136@psf.upfronthosting.co.za>


Christian Heimes added the comment:

The documentation is correct. It explains the difference between a default match (greedy) and a non-greedy match.

>>> re.match('(a{3,5})', 'aaaaa').group(1)
'aaaaa'
>>> re.match('(a{3,5}?)', 'aaaaa').group(1)
'aaa'

----------
nosy: +christian.heimes

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

From report at bugs.python.org  Tue Sep 13 16:43:06 2016
From: report at bugs.python.org (SilentGhost)
Date: Tue, 13 Sep 2016 20:43:06 +0000
Subject: [docs] [issue28136] RegEx documentation error
In-Reply-To: <1473798612.84.0.969871008678.issue28136@psf.upfronthosting.co.za>
Message-ID: <1473799386.35.0.368741182159.issue28136@psf.upfronthosting.co.za>


Changes by SilentGhost <ghost.adh at runbox.com>:


----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
type:  -> behavior

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

From report at bugs.python.org  Tue Sep 13 19:57:44 2016
From: report at bugs.python.org (triuan)
Date: Tue, 13 Sep 2016 23:57:44 +0000
Subject: [docs] [issue28136] RegEx documentation error
In-Reply-To: <1473798612.84.0.969871008678.issue28136@psf.upfronthosting.co.za>
Message-ID: <1473811063.5.0.100346775112.issue28136@psf.upfronthosting.co.za>


triuan added the comment:

thanks!

----------

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

From report at bugs.python.org  Wed Sep 14 09:20:48 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 Sep 2016 13:20:48 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1473794840.69.0.316221750505.issue15369@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwZjUPYcNbsh0sHL2_WbO559XTUMn7bFvBfhabauFHzBVg@mail.gmail.com>


STINNER Victor added the comment:

> I'd also like to request that you reword this dismissive line in the performance package's readme: (...)

Please report issues of the performance module on its own bug tracker:
https://github.com/python/performance

Can you please propose a new description? You might even create a pull
request ;-)

Note: I'm not sure that we should keep pybench, this benchmark really
looks unreliable. But I should still try at least to use the same
number of iterations for all worker child processes. Currently the
calibration is done in each child process.

----------

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

From report at bugs.python.org  Wed Sep 14 11:57:28 2016
From: report at bugs.python.org (=?utf-8?b?0JDQvdC00YDQtdC5INCc0L7RgNC+0LfRjNC60L4=?=)
Date: Wed, 14 Sep 2016 15:57:28 +0000
Subject: [docs] [issue28155] Small typo in Json docs
Message-ID: <1473868648.18.0.394667833494.issue28155@psf.upfronthosting.co.za>


New submission from ?????? ????????:

In Json module, example titled "Using json.tool from the shell to validate and pretty-print:"
5th line reads:
echo '{1.2:3.4}' | python -mjson.tool
should
echo '{1.2:3.4}' | python -m json.tool

----------
assignee: docs at python
components: Documentation
messages: 276467
nosy: docs at python, ?????? ????????
priority: normal
severity: normal
status: open
title: Small typo in Json docs
type: enhancement
versions: Python 2.7, Python 3.3

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

From report at bugs.python.org  Wed Sep 14 12:02:20 2016
From: report at bugs.python.org (SilentGhost)
Date: Wed, 14 Sep 2016 16:02:20 +0000
Subject: [docs] [issue28155] Small typo in Json docs
In-Reply-To: <1473868648.18.0.394667833494.issue28155@psf.upfronthosting.co.za>
Message-ID: <1473868940.61.0.893026135783.issue28155@psf.upfronthosting.co.za>


SilentGhost added the comment:

The space between -m switch and module name is not mandatory as you should be able to see if you run those examples.

----------
nosy: +SilentGhost
resolution:  -> not a bug
stage:  -> resolved

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

From report at bugs.python.org  Wed Sep 14 12:02:36 2016
From: report at bugs.python.org (SilentGhost)
Date: Wed, 14 Sep 2016 16:02:36 +0000
Subject: [docs] [issue28155] Small typo in Json docs
In-Reply-To: <1473868648.18.0.394667833494.issue28155@psf.upfronthosting.co.za>
Message-ID: <1473868956.63.0.699942694153.issue28155@psf.upfronthosting.co.za>


Changes by SilentGhost <ghost.adh at runbox.com>:


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

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

From report at bugs.python.org  Wed Sep 14 12:16:45 2016
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 14 Sep 2016 16:16:45 +0000
Subject: [docs] [issue28155] Small typo in Json docs
In-Reply-To: <1473868648.18.0.394667833494.issue28155@psf.upfronthosting.co.za>
Message-ID: <1473869805.08.0.908693818199.issue28155@psf.upfronthosting.co.za>


Zachary Ware added the comment:

See 05e8b25379a3, though; it may be worth a backport.  Not to 3.3, though; it's docs are not being updated anymore.

----------
nosy: +zach.ware
versions:  -Python 3.3

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

From report at bugs.python.org  Wed Sep 14 17:59:29 2016
From: report at bugs.python.org (Alexander Belopolsky)
Date: Wed, 14 Sep 2016 21:59:29 +0000
Subject: [docs] [issue28130] Document that time.tzset updates time module
 globals
In-Reply-To: <1473782506.71.0.242774514927.issue28130@psf.upfronthosting.co.za>
Message-ID: <1473890369.1.0.966422361304.issue28130@psf.upfronthosting.co.za>


Changes by Alexander Belopolsky <alexander.belopolsky at gmail.com>:


----------
title: Document that time.tzset updates time module constants -> Document that time.tzset updates time module globals

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

From report at bugs.python.org  Thu Sep 15 03:48:41 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Sep 2016 07:48:41 +0000
Subject: [docs] [issue28124] Rework SSL module documentation
In-Reply-To: <1473762840.76.0.666078412099.issue28124@psf.upfronthosting.co.za>
Message-ID: <1473925721.65.0.836114624057.issue28124@psf.upfronthosting.co.za>


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


----------
components: +SSL

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

From report at bugs.python.org  Thu Sep 15 03:49:36 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Sep 2016 07:49:36 +0000
Subject: [docs] [issue20762] SSLSocket.read() not documented
In-Reply-To: <1393262503.02.0.956219773808.issue20762@psf.upfronthosting.co.za>
Message-ID: <1473925776.99.0.840804068378.issue20762@psf.upfronthosting.co.za>


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


----------
components: +SSL

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

From report at bugs.python.org  Thu Sep 15 03:54:16 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Sep 2016 07:54:16 +0000
Subject: [docs] [issue24516] SSL create_default_socket purpose
 insufficiently documented
In-Reply-To: <1435323940.35.0.0347196481189.issue24516@psf.upfronthosting.co.za>
Message-ID: <1473926056.16.0.589007675569.issue24516@psf.upfronthosting.co.za>


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


----------
components: +SSL

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

From report at bugs.python.org  Thu Sep 15 03:55:45 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Sep 2016 07:55:45 +0000
Subject: [docs] [issue18617] TLS and Intermediate Certificates
In-Reply-To: <1375376317.99.0.429350247521.issue18617@psf.upfronthosting.co.za>
Message-ID: <1473926145.83.0.204697328919.issue18617@psf.upfronthosting.co.za>


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


----------
components: +SSL
versions:  -Python 3.6

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

From report at bugs.python.org  Thu Sep 15 03:55:52 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Sep 2016 07:55:52 +0000
Subject: [docs] [issue21649] Mention "Recommendations for Secure Use of TLS
 and DTLS"
In-Reply-To: <1401786597.2.0.166065083457.issue21649@psf.upfronthosting.co.za>
Message-ID: <1473926152.64.0.761022191056.issue21649@psf.upfronthosting.co.za>


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


----------
components: +SSL

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

From report at bugs.python.org  Thu Sep 15 04:09:03 2016
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Sep 2016 08:09:03 +0000
Subject: [docs] [issue27340] bytes-like objects with socket.sendall(), SSL,
 and http.client
In-Reply-To: <1466137520.57.0.744540833455.issue27340@psf.upfronthosting.co.za>
Message-ID: <1473926943.13.0.990188980319.issue27340@psf.upfronthosting.co.za>


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


----------
components: +SSL
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.7

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

From report at bugs.python.org  Thu Sep 15 05:00:28 2016
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Thu, 15 Sep 2016 09:00:28 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <CAMpsgwZjUPYcNbsh0sHL2_WbO559XTUMn7bFvBfhabauFHzBVg@mail.gmail.com>
Message-ID: <57DA6324.3090703@egenix.com>


Marc-Andre Lemburg added the comment:

On 14.09.2016 15:20, STINNER Victor wrote:
> 
> STINNER Victor added the comment:
> 
>> I'd also like to request that you reword this dismissive line in the performance package's readme: (...)
> 
> Please report issues of the performance module on its own bug tracker:
> https://github.com/python/performance
> 
> Can you please propose a new description? You might even create a pull
> request ;-)

I'll send a PR.

> Note: I'm not sure that we should keep pybench, this benchmark really
> looks unreliable. But I should still try at least to use the same
> number of iterations for all worker child processes. Currently the
> calibration is done in each child process.

Well, pybench is not just one benchmark, it's a whole collection of
benchmarks for various different aspects of the CPython VM and per
concept it tries to calibrate itself per benchmark, since each
benchmark has different overhead.

The number of iterations per benchmark will not change between
runs, since this number is fixed in each benchmark. These numbers
do need an update, though, since at the time of writing pybench
CPUs were a lot less powerful compare to today.

Here's the comment with the guideline for the number of rounds
to use per benchmark:

    # Number of rounds to execute per test run. This should be
    # adjusted to a figure that results in a test run-time of between
    # 1-2 seconds.
    rounds = 100000

BTW: Why would you want to run benchmarks in child processes
and in parallel ? This will usually dramatically effect the
results of the benchmark runs. Ideally, the pybench process
should be the only CPU intense work load on the entire CPU
to get reasonable results.

----------

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

From report at bugs.python.org  Thu Sep 15 05:11:25 2016
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 15 Sep 2016 09:11:25 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1342446105.53.0.956340794171.issue15369@psf.upfronthosting.co.za>
Message-ID: <1473930685.22.0.675261440375.issue15369@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Hum, since the discussion restarted, I reopen the issue ...

"Well, pybench is not just one benchmark, it's a whole collection of benchmarks for various different aspects of the CPython VM and per concept it tries to calibrate itself per benchmark, since each benchmark has different overhead."

In the performance module, you now get individual timing for each pybench benchmark, instead of an overall total which was less useful.


"The number of iterations per benchmark will not change between runs, since this number is fixed in each benchmark."

Please take a look at the new performance module, it has a different design. Calibration is based on minimum time per sample, no more on hardcoded things. I modified all benchmarks, not only pybench.


"BTW: Why would you want to run benchmarks in child processes and in parallel ?"

Child processes are run sequentially.

Running benchmarks in multiple processes help to get more reliable benchmarks. Read my article if you want to learn more about the design of my perf module:
http://haypo-notes.readthedocs.io/microbenchmark.html#my-articles


"Ideally, the pybench process should be the only CPU intense work load on the entire CPU to get reasonable results."

The perf module automatically uses isolated CPU. It strongly suggests to use this amazing Linux feature to run benchmarks!
https://haypo.github.io/journey-to-stable-benchmark-system.html

I started to write advices to get stable benchmarks:
https://github.com/python/performance#how-to-get-stable-benchmarks

Note: See also the https://mail.python.org/mailman/listinfo/speed mailing list ;-)

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

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

From report at bugs.python.org  Thu Sep 15 05:21:34 2016
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Thu, 15 Sep 2016 09:21:34 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <1473930685.22.0.675261440375.issue15369@psf.upfronthosting.co.za>
Message-ID: <57DA6816.1020102@egenix.com>


Marc-Andre Lemburg added the comment:

On 15.09.2016 11:11, STINNER Victor wrote:
> 
> STINNER Victor added the comment:
> 
> Hum, since the discussion restarted, I reopen the issue ...
> 
> "Well, pybench is not just one benchmark, it's a whole collection of benchmarks for various different aspects of the CPython VM and per concept it tries to calibrate itself per benchmark, since each benchmark has different overhead."
> 
> In the performance module, you now get individual timing for each pybench benchmark, instead of an overall total which was less useful.

pybench had the same intention. It was a design mistake to add an
overall timing to each suite run. The original intention was to
compare each benchmark individually.

Perhaps it would make sense to try to port the individual benchmark
tests in pybench to performance.

> "The number of iterations per benchmark will not change between runs, since this number is fixed in each benchmark."
> 
> Please take a look at the new performance module, it has a different design. Calibration is based on minimum time per sample, no more on hardcoded things. I modified all benchmarks, not only pybench.

I think we are talking about different things here: calibration is
pybench means that you try to determine the overhead of the
outer loop and possible setup code that is needed to run the
the test.

pybench runs a calibration method which has the same
code as the main test, but without the actual operations that you
want to test, in order to determine the timing of the overhead.

It then takes the minimum timing from overhead runs and uses
this as base line for the actual test runs (it subtracts the
overhead timing from the test run results).

This may not be ideal in all cases, but it's the closest
I could get to timing of the test operations at the time.

I'll have a look at what performance does.

> "BTW: Why would you want to run benchmarks in child processes and in parallel ?"
> 
> Child processes are run sequentially.

Ah, ok.

> Running benchmarks in multiple processes help to get more reliable benchmarks. Read my article if you want to learn more about the design of my perf module:
> http://haypo-notes.readthedocs.io/microbenchmark.html#my-articles

Will do, thanks.

> "Ideally, the pybench process should be the only CPU intense work load on the entire CPU to get reasonable results."
> 
> The perf module automatically uses isolated CPU. It strongly suggests to use this amazing Linux feature to run benchmarks!
> https://haypo.github.io/journey-to-stable-benchmark-system.html
> 
> I started to write advices to get stable benchmarks:
> https://github.com/python/performance#how-to-get-stable-benchmarks
> 
> Note: See also the https://mail.python.org/mailman/listinfo/speed mailing list ;-)

I've read some of your blog posts and articles on the subject
and your journey. Interesting stuff, definitely. Benchmarking
these days appears to have gotten harder not simpler compared to
the days of pybench some 19 years ago.

----------

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

From report at bugs.python.org  Thu Sep 15 05:41:56 2016
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 15 Sep 2016 09:41:56 +0000
Subject: [docs] [issue15369] pybench and test.pystone poorly documented
In-Reply-To: <57DA6816.1020102@egenix.com>
Message-ID: <CAMpsgwYaDK4ZVatGiYEhLAKs1WcZX5QELChjKEw8EWssW6a3Sw@mail.gmail.com>


STINNER Victor added the comment:

2016-09-15 11:21 GMT+02:00 Marc-Andre Lemburg <report at bugs.python.org>:
> I think we are talking about different things here: calibration is
> pybench means that you try to determine the overhead of the
> outer loop and possible setup code that is needed to run the
> the test.
> (...)
> It then takes the minimum timing from overhead runs and uses
> this as base line for the actual test runs (it subtracts the
> overhead timing from the test run results).

Calibration in perf means computing automatically the number of
outer-loops to get a sample of at least 100 ms (default min time).

I simply removed the code to estimate the overhead of the outer loop
in pybench. The reason is this line:

        # Get calibration
        min_overhead = min(self.overhead_times)

This is no such "minimum timing", it doesn't exist :-) In benchmarks,
you have to work on statistics: use average, standard deviation, etc.

If you badly estimate the minimum overhead, you might get negative
timings, which is not allowed in perf (even zero is an hard error in
perf).

It's not possible to compute *exactly* the "minimum overhead".

Moreover, removing the code to estimate the overhead simplified the code.

> Benchmarking these days appears to have gotten harder not simpler compared to the days of pybench some 19 years ago.

Benchmarking was always a hard problem. Modern hardware (Out of order
CPU, variable CPU frequency, power saving, etc.) problably didn't help
:-)

----------

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

From karen.little at whoishostingthismail.com  Thu Sep 15 05:16:19 2016
From: karen.little at whoishostingthismail.com (Karen Little)
Date: Thu, 15 Sep 2016 09:16:19 +0000
Subject: [docs] A broken link!
Message-ID: <3513581.or_mail@whoishostingthismail.com>

Hi, 

I appreciate you're busy so I just wanted to follow up on the email I sent you the other day as I noticed the link is still broken. I've included my email below for your reference:

		On Fri, Sep 9, 2016 at 2:55 PM, Karen Little <karen.little at whoishostingthismail.com> wrote:
		
			 Hi, 

Just wanted to let you know about a link that seems to be broken on this page http://rtfd.qiniudn.com/docs-py3_zh/build/html/whatsnew/3.2.html.

It is this link http://mercurial.selenic.com/guide/, but the page doesn?t seem to be active any more. I thought you might want to update.

If you are looking for an alternative please check out http://wiht.link/Mercurial-intro, it may make a suitable replacement.

Kind Regards,
Karen

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

From report at bugs.python.org  Thu Sep 15 15:01:48 2016
From: report at bugs.python.org (Chris Angelico)
Date: Thu, 15 Sep 2016 19:01:48 +0000
Subject: [docs] [issue28172] Upper-case all example enum members
Message-ID: <1473966107.03.0.300297915122.issue28172@psf.upfronthosting.co.za>


New submission from Chris Angelico:

Discussion on python-ideas led to a firm ruling by Guido that enum members are functionally equivalent to constants, and should thus be named in upper-case. This is contrary to the current documentation. Solution? Change the docs.

----------
assignee: docs at python
components: Documentation
files: uppercase-enums.patch
keywords: patch
messages: 276589
nosy: Rosuav, docs at python
priority: normal
severity: normal
status: open
title: Upper-case all example enum members
versions: Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file44676/uppercase-enums.patch

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

From report at bugs.python.org  Thu Sep 15 15:10:15 2016
From: report at bugs.python.org (Chris Rao)
Date: Thu, 15 Sep 2016 19:10:15 +0000
Subject: [docs] [issue28173] Misspelled Assert
Message-ID: <1473966615.29.0.712083850486.issue28173@psf.upfronthosting.co.za>


New submission from Chris Rao:

In the second code block in the section on autospeccing in https://docs.python.org/3/library/unittest.mock.html#auto-speccing, assert is spelled as "assret"

>>> mock = Mock(name='Thing', return_value=None)
>>> mock(1, 2, 3)
>>> mock.assret_called_once_with(4, 5, 6)

----------
assignee: docs at python
components: Documentation
messages: 276596
nosy: Chris Rao, docs at python
priority: normal
severity: normal
status: open
title: Misspelled Assert

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

From report at bugs.python.org  Thu Sep 15 15:10:59 2016
From: report at bugs.python.org (SilentGhost)
Date: Thu, 15 Sep 2016 19:10:59 +0000
Subject: [docs] [issue28172] Upper-case all example enum members
In-Reply-To: <1473966107.03.0.300297915122.issue28172@psf.upfronthosting.co.za>
Message-ID: <1473966659.98.0.213724997537.issue28172@psf.upfronthosting.co.za>


Changes by SilentGhost <ghost.adh at runbox.com>:


----------
stage:  -> patch review

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

From report at bugs.python.org  Thu Sep 15 15:17:50 2016
From: report at bugs.python.org (Ethan Furman)
Date: Thu, 15 Sep 2016 19:17:50 +0000
Subject: [docs] [issue28173] Misspelled Assert
In-Reply-To: <1473966615.29.0.712083850486.issue28173@psf.upfronthosting.co.za>
Message-ID: <1473967070.41.0.188861809478.issue28173@psf.upfronthosting.co.za>


Ethan Furman added the comment:

The misspelling is intentional.  That section is talking about what happens when an "assert_" method is misspelled.

----------
nosy: +ethan.furman, michael.foord
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Sep 15 15:35:38 2016
From: report at bugs.python.org (Ethan Furman)
Date: Thu, 15 Sep 2016 19:35:38 +0000
Subject: [docs] [issue28172] Upper-case all example enum members
In-Reply-To: <1473966107.03.0.300297915122.issue28172@psf.upfronthosting.co.za>
Message-ID: <1473968138.1.0.809019225972.issue28172@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/issue28172>
_______________________________________

From report at bugs.python.org  Thu Sep 15 17:41:15 2016
From: report at bugs.python.org (Yury Selivanov)
Date: Thu, 15 Sep 2016 21:41:15 +0000
Subject: [docs] [issue26050] Add new StreamReader.readuntil() method
In-Reply-To: <1452285476.14.0.419432816204.issue26050@psf.upfronthosting.co.za>
Message-ID: <1473975675.04.0.960175218712.issue26050@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

Looks like we already have docs for readuntil.  Mark, could you please check if we have some docs missing (or just close the issue)?

----------

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

From report at bugs.python.org  Thu Sep 15 18:58:42 2016
From: report at bugs.python.org (Alexander Belopolsky)
Date: Thu, 15 Sep 2016 22:58:42 +0000
Subject: [docs] [issue15941] Time module: effect of time.timezone change
In-Reply-To: <1347559641.51.0.772200483389.issue15941@psf.upfronthosting.co.za>
Message-ID: <1473980322.78.0.467297680407.issue15941@psf.upfronthosting.co.za>


Alexander Belopolsky added the comment:

Closing in favor of #28157.

----------
status: open -> closed
superseder:  -> Document time module constants (timezone, tzname, etc.) as deprecated.

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

From report at bugs.python.org  Fri Sep 16 00:14:37 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 16 Sep 2016 04:14:37 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1473999276.96.0.893978999769.issue26149@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Mention Pycharm community edition, and provide link to the wiki

----------
keywords: +patch
nosy: +Mariatta Wijaya
Added file: http://bugs.python.org/file44686/docupdate.patch

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

From report at bugs.python.org  Fri Sep 16 05:30:50 2016
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Fri, 16 Sep 2016 09:30:50 +0000
Subject: [docs] [issue26050] Add new StreamReader.readuntil() method
In-Reply-To: <1452285476.14.0.419432816204.issue26050@psf.upfronthosting.co.za>
Message-ID: <1474018250.72.0.97133829986.issue26050@psf.upfronthosting.co.za>


???? ????????? added the comment:

It needs to compare python functoin(s) docstrings with  separate documentation. All information from docstrings should also be written in separate docs. Will compare later.

----------

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

From ethan at stoneleaf.us  Thu Sep 15 15:35:24 2016
From: ethan at stoneleaf.us (ethan at stoneleaf.us)
Date: Thu, 15 Sep 2016 19:35:24 -0000
Subject: [docs] Upper-case all example enum members (issue 28172)
Message-ID: <20160915193524.24721.27524@psf.upfronthosting.co.za>

Doc changes look good.  May need to update Lib/test/test_enum.py for the
Fruit test in Doc/library/enum.rst (haven't checked yet).

http://bugs.python.org/review/28172/

From lauraguthrie89 at gmail.com  Fri Sep 16 11:02:10 2016
From: lauraguthrie89 at gmail.com (Laura Guthrie)
Date: Fri, 16 Sep 2016 11:02:10 -0400
Subject: [docs] Python Tutorail Document
Message-ID: <CAH+4Tv93mVatHqQkSOqMhTH+5mto+3aSow2mvKROdYeveV_A1Q@mail.gmail.com>

Hello,

I am on this website: https://docs.python.org/release/2.5.4/tut/tut.html

I was wondering if you have a PDF version of this document available for
download? Is this the most recent? I am currently learning this language
for my job and was recommended this resource, I just want to be able to
save to my desktop so I can open it quickly.

Thank you!




-- 

*Laura Elizabeth Guthrie*

*Orlando, FL*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160916/a46b082d/attachment.html>

From berker.peksag at gmail.com  Fri Sep 16 11:22:54 2016
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Fri, 16 Sep 2016 18:22:54 +0300
Subject: [docs] Python Tutorail Document
In-Reply-To: <CAH+4Tv93mVatHqQkSOqMhTH+5mto+3aSow2mvKROdYeveV_A1Q@mail.gmail.com>
References: <CAH+4Tv93mVatHqQkSOqMhTH+5mto+3aSow2mvKROdYeveV_A1Q@mail.gmail.com>
Message-ID: <CAF4280LM0K_KuJwkNF2ebC5hV=ScWLGycQwb9cooxi28H-Ujpw@mail.gmail.com>

On Fri, Sep 16, 2016 at 6:02 PM, Laura Guthrie <lauraguthrie89 at gmail.com> wrote:
> Hello,
>
> I am on this website: https://docs.python.org/release/2.5.4/tut/tut.html
>
> I was wondering if you have a PDF version of this document available for
> download? Is this the most recent? I am currently learning this language for
> my job and was recommended this resource, I just want to be able to save to
> my desktop so I can open it quickly.

Hi Laura,

First of all, that link is too outdated. You can read the up-to-date
Python tutorial at https://docs.python.org/3.5/tutorial/ PDF version
of the tutorial can be found at
https://docs.python.org/3.5/download.html (see for 'tutorial.pdf' in
the archive)

--Berker

From report at bugs.python.org  Fri Sep 16 14:47:38 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 16 Sep 2016 18:47:38 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474051658.18.0.249956144665.issue26149@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Hm, maybe the list should just removed and only the link to the wiki preserved? Agreed that the list here feels outdated. And updating it is always going to be a political game (e.g. why isn't Wing IDE listed?)

----------
nosy: +gvanrossum

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

From report at bugs.python.org  Fri Sep 16 15:14:15 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Sep 2016 19:14:15 +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: <1474053255.29.0.729409896818.issue16700@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Maybe this issue is outdated in 3.6 (thanks to PEP 529), but this still is a problem under 3.5 and 2.7.

----------
status: closed -> open
versions: +Python 3.5 -Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Sep 16 17:16:35 2016
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 16 Sep 2016 21:16:35 +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: <1474060595.99.0.527348133075.issue16700@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at yahoo.co.uk>:


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

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

From report at bugs.python.org  Fri Sep 16 23:04:39 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 17 Sep 2016 03:04:39 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474081479.65.0.718574304846.issue26149@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks for the feedback :)
As suggested, I removed all other IDEs and just link to the wiki.

----------
Added file: http://bugs.python.org/file44705/docupdate2.patch

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

From report at bugs.python.org  Fri Sep 16 23:07:45 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 17 Sep 2016 03:07:45 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474081665.65.0.623605813452.issue26149@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Hmm.. not sure if I did this correctly. I uploaded another patch file, is this right? Or, how can I edit my original patch?
Thanks.

----------

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

From report at bugs.python.org  Fri Sep 16 23:15:17 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Sat, 17 Sep 2016 03:15:17 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474082117.88.0.394934323134.issue26149@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

You did the right thing. Check out the "review" link.

----------

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

From report at bugs.python.org  Sat Sep 17 07:24:10 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 17 Sep 2016 11:24:10 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474111450.31.0.560713714282.issue26149@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch. I left some comment on Rietveld: http://bugs.python.org/review/26149/#ps18589

----------
stage: needs patch -> patch review
versions: +Python 3.7

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

From report at bugs.python.org  Sat Sep 17 11:00:49 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 17 Sep 2016 15:00:49 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474124449.15.0.797434499812.issue26149@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks for the feedback, Berker :)
I added some introductory statements, and added link to https://wiki.python.org/moin/IntegratedDevelopmentEnvironments

I'll be open to other suggestions as well

Thanks.

----------
Added file: http://bugs.python.org/file44715/docupdate3.patch

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

From report at bugs.python.org  Sat Sep 17 11:03:53 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 17 Sep 2016 15:03:53 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1474124633.19.0.654274638741.issue26149@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Forgot to change the title to Editors and IDEs.
Updated now.

Thanks.

----------
Added file: http://bugs.python.org/file44716/docupdate4.patch

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

From report at bugs.python.org  Sun Sep 18 16:50:32 2016
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Sun, 18 Sep 2016 20:50:32 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
Message-ID: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>


New submission from Vedran ?a?i?:

Look at this:

    >>> from collections.abc import Sequence

    >>> help(Sequence.index)
    index(self, value, start=0, stop=None)
        S.index(value, [start, [stop]]) -> integer -- return first index of value.
        Raises ValueError if the value is not present.

    >>> issubclass(range, Sequence)
    True

    >>> help(range.index)
    index(...)
        rangeobject.index(value, [start, [stop]]) -> integer -- return index of value.
        Raise ValueError if the value is not present.

So far, so good. But:

    >>> range(9).index(2, 1, 5)
    TypeError: index() takes exactly one argument (3 given)

Of course it's not essential, but the docs shouldn't lie. And if range _is_ a Sequence, then it should have the complete interface of a Sequence. Including start and end arguments for .index: they are optional from the point of call, not from the point of implementation. :-)

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 276908
nosy: docs at python, veky
priority: normal
severity: normal
status: open
title: range.index mismatch with documentation
type: behavior
versions: Python 3.5, Python 3.6

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

From report at bugs.python.org  Sun Sep 18 16:55:18 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 18 Sep 2016 20:55:18 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474232118.31.0.216202774394.issue28197@psf.upfronthosting.co.za>


Changes by SilentGhost <ghost.adh at runbox.com>:


----------
versions: +Python 3.7

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

From report at bugs.python.org  Sun Sep 18 17:03:48 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 18 Sep 2016 21:03:48 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474232628.55.0.275328665748.issue28197@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Parameters start and stop were added to the Sequence.index() mixin method in issue23086. These broke some concrete Sequence implementations.

----------
nosy: +Devin Jeanpierre, rhettinger, serhiy.storchaka

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

From report at bugs.python.org  Sun Sep 18 21:13:10 2016
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Mon, 19 Sep 2016 01:13:10 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474247590.82.0.350997771026.issue28197@psf.upfronthosting.co.za>


Vedran ?a?i? added the comment:

Yes, that's the precise reason I caught this. I was implementing some tools to do with Sequences (seqtools, like itertools but having non-ephemeral output given non-ephemeral input), and the Sequence that was easiest to test quickly was range. In `positions` (like .index but gives all the places a value appears), it raised TypeError.

----------

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

From report at bugs.python.org  Sun Sep 18 23:52:52 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 19 Sep 2016 03:52:52 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474257172.28.0.185834348178.issue28197@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> These broke some concrete Sequence implementations.

Poor choice of words.  The concrete implementations didn't change at all. 

Perhaps the concrete implementation need to be brought more in-sync with the ABC.  That would be reasonable; afteralll the goal is substitutability  -- that is the only reason that the old xrange morphed into something with nearly useless count() and index() methods in the first place.

----------

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

From report at bugs.python.org  Mon Sep 19 01:15:54 2016
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Mon, 19 Sep 2016 05:15:54 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474262154.0.0.196922495739.issue28197@psf.upfronthosting.co.za>


Vedran ?a?i? added the comment:

Yes, I agree these are useless _if you know you're dealing with range_. However, if you have a Sequence, it would be very useful not to have range be a special case.

Of course, one solution is to have a default .index implementation in the Sequence ABC itself, but still I'd argue that range can implement the 3-arg .index much better than generic Sequence.

----------

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

From report at bugs.python.org  Mon Sep 19 02:27:53 2016
From: report at bugs.python.org (Chi Hsuan Yen)
Date: Mon, 19 Sep 2016 06:27:53 +0000
Subject: [docs] [issue18617] TLS and Intermediate Certificates
In-Reply-To: <1375376317.99.0.429350247521.issue18617@psf.upfronthosting.co.za>
Message-ID: <1474266473.6.0.580160147989.issue18617@psf.upfronthosting.co.za>


Changes by Chi Hsuan Yen <yan12125 at gmail.com>:


----------
nosy: +Chi Hsuan Yen

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

From berker.peksag at gmail.com  Sat Sep 17 07:23:21 2016
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Sat, 17 Sep 2016 11:23:21 -0000
Subject: [docs] Suggest PyCharm Community as an editor for Unix platforms
 (issue 26149)
Message-ID: <20160917112321.24721.82737@psf.upfronthosting.co.za>


http://bugs.python.org/review/26149/diff/18589/Doc/using/unix.rst
File Doc/using/unix.rst (left):

http://bugs.python.org/review/26149/diff/18589/Doc/using/unix.rst#oldcode135
Doc/using/unix.rst:135: Editors
Perhaps this section can be renamed to "Editors and IDEs".

http://bugs.python.org/review/26149/diff/18589/Doc/using/unix.rst
File Doc/using/unix.rst (right):

http://bugs.python.org/review/26149/diff/18589/Doc/using/unix.rst#newcode138
Doc/using/unix.rst:138: Please go to
https://wiki.python.org/moin/PythonEditors for a comprehensive
It would be nice to start with something like

   There are so many editors and IDEs that support Python very well. You
can find them ...

I'm not a native speaker so you or someone else can suggest a better
alternative :)

http://bugs.python.org/review/26149/diff/18589/Doc/using/unix.rst#newcode139
Doc/using/unix.rst:139: list of Python Editors.
We also need to include IDEs and add a link to
https://wiki.python.org/moin/IntegratedDevelopmentEnvironments

http://bugs.python.org/review/26149/

From savithaa at hotmail.com  Sun Sep 18 12:58:35 2016
From: savithaa at hotmail.com (Savitha Ananth)
Date: Sun, 18 Sep 2016 16:58:35 +0000
Subject: [docs] Math functions
Message-ID: <YQXPR01MB0024805CAC3F08AB254C8D30DEF50@YQXPR01MB0024.CANPRD01.PROD.OUTLOOK.COM>

Hello!

Is there anything to import in order to use the trigonometric sin function?

My code is giving errors on the line x = math.sin(radians)
Please help.

Thanks!

Savitha

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160918/8802b9e2/attachment.html>

From report at bugs.python.org  Mon Sep 19 11:00:04 2016
From: report at bugs.python.org (Samuel Colvin)
Date: Mon, 19 Sep 2016 15:00:04 +0000
Subject: [docs] [issue28206] signal.Signals not documented
Message-ID: <1474297204.47.0.613989661481.issue28206@psf.upfronthosting.co.za>


New submission from Samuel Colvin:

As per discussion on typeshed pull request discussion (https://github.com/python/typeshed/pull/555) the "signal.Signals" enum is not documented but should be.

See https://docs.python.org/3.5/library/signal.html.

----------
assignee: docs at python
components: Documentation
messages: 276979
nosy: Samuel Colvin, docs at python
priority: normal
severity: normal
status: open
title: signal.Signals not documented
versions: Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Sep 20 04:57:27 2016
From: report at bugs.python.org (Xiang Zhang)
Date: Tue, 20 Sep 2016 08:57:27 +0000
Subject: [docs] [issue28211] Wrong return value type in the doc of
 PyMapping_Keys/Values/Items
Message-ID: <1474361846.96.0.641386769432.issue28211@psf.upfronthosting.co.za>


New submission from Xiang Zhang:

PyMapping_Keys/Values/Items can only return a list or tuple. Even in the case of a dict, it returns a list. But the doc tells a dictionary view will be returned in case of dict, which is wrong.

----------
assignee: docs at python
components: Documentation
files: mapping_doc.patch
keywords: patch
messages: 277018
nosy: docs at python, xiang.zhang
priority: normal
severity: normal
stage: patch review
status: open
title: Wrong return value type in the doc of PyMapping_Keys/Values/Items
versions: Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file44752/mapping_doc.patch

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

From johnml1135 at gmail.com  Mon Sep 19 08:19:51 2016
From: johnml1135 at gmail.com (John Lambert)
Date: Mon, 19 Sep 2016 08:19:51 -0400
Subject: [docs] downloads for 3.4.5
Message-ID: <CAG+bLmU141bbGexkZrhx=CuRYj0shmUP_sc-j13mW9PgO+pDQQ@mail.gmail.com>

Hello,

The links on this page (https://docs.python.org/3.4/download.html) are not
working.  After looking at the underlying files on the ftp, it appears that
there are versions up to 3.4.3 but that 3.4.4 and 3.4.5 have not been
posted on the ftp.  The 3.4.3 version works fine for me, but I wanted to
let you know that the links are broken.

John Lambert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160919/c326c449/attachment.html>

From report at bugs.python.org  Tue Sep 20 06:30:37 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 20 Sep 2016 10:30:37 +0000
Subject: [docs] [issue28211] Wrong return value type in the doc of
 PyMapping_Keys/Values/Items
In-Reply-To: <1474361846.96.0.641386769432.issue28211@psf.upfronthosting.co.za>
Message-ID: <1474367437.74.0.728741851117.issue28211@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Hmm, the documentation was changed in issue25909, but seems I was wrong. Since PyDict_Items() returns a list, but not a dict view, PyMapping_Items() can return only a list or a tuple.

----------
nosy: +martin.panter, mine0901, orsenthil, python-dev, r.david.murray, serhiy.storchaka

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

From report at bugs.python.org  Tue Sep 20 10:50:13 2016
From: report at bugs.python.org (R. David Murray)
Date: Tue, 20 Sep 2016 14:50:13 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <1474362608.68.0.912694843367.issue28212@psf.upfronthosting.co.za>
Message-ID: <1474383013.2.0.642234377281.issue28212@psf.upfronthosting.co.za>


R. David Murray added the comment:

You have to call wait_closed to complete the shutdown.

This should probably be mentioned directly in the socket server docs (at least in the examples) (assuming I'm not wrong...but I'm pretty sure I'm right) rather than by implicit reference to Server via the create_server comment.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, r.david.murray

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

From report at bugs.python.org  Tue Sep 20 11:06:57 2016
From: report at bugs.python.org (=?utf-8?b?0JrQvtC90YHRgtCw0L3RgtC40L0g0JLQvtC70LrQvtCy?=)
Date: Tue, 20 Sep 2016 15:06:57 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <1474383013.2.0.642234377281.issue28212@psf.upfronthosting.co.za>
Message-ID: <CAFgzoce-R_oGVRY6r9Mq+phGU5DpA9quqMrftoXTjx6gq_4jDA@mail.gmail.com>


?????????? ?????? added the comment:

Thats not a thing I talking about. But thanks for "wait_closed", I will be
use it in future )

Im talking about reading tasks.When reader removed from selector, there is
reading task for it. Loop do "cancel" for it, but it not really cancelling
task. Its only marking task for be cancelled on next loop step. It must
raise Cancel exception, so task may do corresponding actions inside it (for
exemple try..except Cancel). But it will not happen, because there will be
no next step - task removed from selector and now is missed from loop. It
will freese in "cancelling" state forever if protocol implementation
wouldn`t take care about it itself. Some protocol implementations make
"_step" for such tasks manually to loop them for correct finishing, someone
makes "set_result(None)", but its all looks bad.
Seems it will be better put it in loop after removing from selector, so it
will go "cancelling way" itself as every task do.

2016-09-20 17:50 GMT+03:00 R. David Murray <report at bugs.python.org>:

>
> R. David Murray added the comment:
>
> You have to call wait_closed to complete the shutdown.
>
> This should probably be mentioned directly in the socket server docs (at
> least in the examples) (assuming I'm not wrong...but I'm pretty sure I'm
> right) rather than by implicit reference to Server via the create_server
> comment.
>
> ----------
> assignee:  -> docs at python
> components: +Documentation
> nosy: +docs at python, r.david.murray
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue28212>
> _______________________________________
>

----------

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

From report at bugs.python.org  Tue Sep 20 11:12:26 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 20 Sep 2016 15:12:26 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <CAFgzoce-R_oGVRY6r9Mq+phGU5DpA9quqMrftoXTjx6gq_4jDA@mail.gmail.com>
Message-ID: <CAP7+vJ+Jah5xhvrVghyz=S+KqOfJQ000PhtjeE=xsV7BSeDcUQ@mail.gmail.com>


Guido van Rossum added the comment:

Can you please supply a complete example?

--Guido (mobile)

----------

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

From report at bugs.python.org  Tue Sep 20 11:15:49 2016
From: report at bugs.python.org (=?utf-8?b?0JrQvtC90YHRgtCw0L3RgtC40L0g0JLQvtC70LrQvtCy?=)
Date: Tue, 20 Sep 2016 15:15:49 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <CAP7+vJ+Jah5xhvrVghyz=S+KqOfJQ000PhtjeE=xsV7BSeDcUQ@mail.gmail.com>
Message-ID: <CAFgzoccQ+Q8K39QmXdYgaS2g2=gq5Me5nK2uv7w4AjYbgs7J4g@mail.gmail.com>


?????????? ?????? added the comment:

Yes? may be a in a hour,

2016-09-20 18:12 GMT+03:00 Guido van Rossum <report at bugs.python.org>:

>
> Guido van Rossum added the comment:
>
> Can you please supply a complete example?
>
> --Guido (mobile)
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue28212>
> _______________________________________
>

----------

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

From report at bugs.python.org  Tue Sep 20 12:33:13 2016
From: report at bugs.python.org (=?utf-8?b?0JrQvtC90YHRgtCw0L3RgtC40L0g0JLQvtC70LrQvtCy?=)
Date: Tue, 20 Sep 2016 16:33:13 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <1474362608.68.0.912694843367.issue28212@psf.upfronthosting.co.za>
Message-ID: <1474389193.11.0.536487385549.issue28212@psf.upfronthosting.co.za>


?????????? ?????? added the comment:

Attached file with test example. There in "ping" task "except" and "finally" sections never called as expected (but code inside "try" will work).
Server is closed while client connection is active, and it just removes reading task from loop. You can still find it through Task.all_tasks(), but it is weakref array. So, sometime later GC will simply delete this task and no finalization will be performed.

----------
Added file: http://bugs.python.org/file44756/task_example.py

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

From report at bugs.python.org  Tue Sep 20 15:53:07 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 20 Sep 2016 19:53:07 +0000
Subject: [docs] [issue28219] Is order of argparse --help output officially
 defined?
Message-ID: <1474401187.0.0.781761805381.issue28219@psf.upfronthosting.co.za>


New submission from Barry A. Warsaw:

Sometimes we want to control the order of arguments printed by an argparse defined cli.  In practice, arguments are printed in the order in which they are added via add_argument(), but I don't think this is documented and thus should be considered an implementation detail.  It should be possible to enforce an order by the use of a formatter_class, but you'd probably need some extra metadata on arguments to do this, so it's not completely obvious how to write such a formatter class.

Instead, I propose to document and officially support that the order of add_argument() calls defines the order in which arguments are printed via --help.

----------
assignee: docs at python
components: Documentation
messages: 277060
nosy: barry, docs at python
priority: normal
severity: normal
status: open
title: Is order of argparse --help output officially defined?
versions: Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Tue Sep 20 16:16:24 2016
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 20 Sep 2016 20:16:24 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <1474362608.68.0.912694843367.issue28212@psf.upfronthosting.co.za>
Message-ID: <1474402584.2.0.747399634908.issue28212@psf.upfronthosting.co.za>


Andrew Svetlov added the comment:

It's a known annoying issue.
Honestly I don't know how to fix it properly.
`transport.close()` is affected also because `protocol.connection_lost()` is called on next loop iteration only.

Adding a small `asyncio.sleep()` between finishing all worn and loop closing solves the problem for me but the solution is not obvious for newbies.

----------
nosy: +asvetlov

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

From report at bugs.python.org  Tue Sep 20 16:23:03 2016
From: report at bugs.python.org (=?utf-8?b?0JrQvtC90YHRgtCw0L3RgtC40L0g0JLQvtC70LrQvtCy?=)
Date: Tue, 20 Sep 2016 20:23:03 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <1474402584.2.0.747399634908.issue28212@psf.upfronthosting.co.za>
Message-ID: <CAFgzoccqaxYYPis6sw81rPjnsgbXd+hPTZC1ta_n47L3gzXThA@mail.gmail.com>


?????????? ?????? added the comment:

Seems that its not so hard - in loop.remove_reader add

self._ready.append(reader)

after reader.cancel()

May be its needed to check that its not already there, but I cant imagine
how it can be.

2016-09-20 23:16 GMT+03:00 Andrew Svetlov <report at bugs.python.org>:

>
> Andrew Svetlov added the comment:
>
> It's a known annoying issue.
> Honestly I don't know how to fix it properly.
> `transport.close()` is affected also because `protocol.connection_lost()`
> is called on next loop iteration only.
>
> Adding a small `asyncio.sleep()` between finishing all worn and loop
> closing solves the problem for me but the solution is not obvious for
> newbies.
>
> ----------
> nosy: +asvetlov
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue28212>
> _______________________________________
>

----------

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

From report at bugs.python.org  Tue Sep 20 16:30:28 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 20 Sep 2016 20:30:28 +0000
Subject: [docs] [issue28212] Closing server in asyncio is not efficient
In-Reply-To: <1474362608.68.0.912694843367.issue28212@psf.upfronthosting.co.za>
Message-ID: <1474403428.01.0.216384962142.issue28212@psf.upfronthosting.co.za>


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


----------
nosy:  -gvanrossum

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

From report at bugs.python.org  Tue Sep 20 17:28:44 2016
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 20 Sep 2016 21:28:44 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1474406924.02.0.422957410302.issue27292@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Please ensure that the documentation properly warns users about these edge cases.

I disagree. I don't think that the Python documentation is the right place to document the security level of system urandom.

It's just a mess, there are so many corner cases and it's very hard to provide a clear explanation for end users.

I suggest to keep the positive "suitable for cryptographic use". If you change this sentence, I only expect that users will use something WORSE. For example "os.urandom is not secure! we must use ssl.RAND_bytes!". No. Don't do that, ssl.RAND_bytes() has its own set of issues, like two processes with the same pid producing the same random sequence... (old known issue, very hard to fix)

Python cannot workaround OS limitations, we can only do our best to use the most secure source of entropy. That's why Python 3.5 now uses getrandom() on Linux. That's why Python 3.6 now calls getrandom() in blocking mode.

----------

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

From report at bugs.python.org  Wed Sep 21 05:15:14 2016
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 21 Sep 2016 09:15:14 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1474449314.8.0.505831251145.issue27292@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

With the 3.6 os.urandom() implementation doing the right thing consistently cross-platform, our guidance for folks that care about the quality of the CSPRNG they use should be that they either upgrade to that version, or else ensure that the kernel CSPRNG is properly seeded before they run Python.

That is, I think the tone we're aiming for in the older docs now should be "You're using an older Python version, so if this problem description worries you, you need to either upgrade or else take the necessary steps to satisfy yourself that your host system's CSPRNG is properly configured", rather than the more passive "os.urandom() isn't necessarily secure" (with minimal guidance on what to do about it) that we've previously adopted.

----------

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

From report at bugs.python.org  Wed Sep 21 06:27:48 2016
From: report at bugs.python.org (py.user)
Date: Wed, 21 Sep 2016 10:27:48 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
Message-ID: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>


New submission from py.user:

https://docs.python.org/3/library/xml.etree.elementtree.html#reference

1. Comment
2. iselement()
3. ProcessingInstruction
4. SubElement
5. Element.find()
6. ElementTree._setroot()
7. TreeBuilder

Applied a patch to the issue that adds Element class links.

----------
assignee: docs at python
components: Documentation, Library (Lib), XML
files: element-link.diff
keywords: patch
messages: 277121
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In xml.etree.ElementTree docs there are many absent Element class links
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file44775/element-link.diff

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

From report at bugs.python.org  Wed Sep 21 07:24:17 2016
From: report at bugs.python.org (py.user)
Date: Wed, 21 Sep 2016 11:24:17 +0000
Subject: [docs] [issue28235] In xml.etree.ElementTree docs there is no
 parser argument in fromstring()
Message-ID: <1474457056.95.0.329737294315.issue28235@psf.upfronthosting.co.za>


New submission from py.user:

https://docs.python.org/3/library/xml.etree.elementtree.html#xml.etree.ElementTree.fromstring

The function has argument parser that works like in XML() function, but in the description there is no info about it (copied from XML() description).

Applied a patch to the issue that adds argument to the signature and describes it.

----------
assignee: docs at python
components: Documentation, Library (Lib), XML
files: fromstring-parser.diff
keywords: patch
messages: 277124
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In xml.etree.ElementTree docs there is no parser argument in fromstring()
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file44776/fromstring-parser.diff

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

From karen.little at whoishostingthismail.com  Wed Sep 21 04:39:18 2016
From: karen.little at whoishostingthismail.com (Karen Little)
Date: Wed, 21 Sep 2016 08:39:18 +0000
Subject: [docs] A broken link!
Message-ID: <3598364.or_mail@whoishostingthismail.com>

Hi, 

I've sent you a couple of emails about a broken link I found on your site, but I haven't heard back from you.

Is there someone else I should get in touch with about this?

I've included my previous email below for your reference:

		On Thu, Sep 15, 2016 at 9:16 AM, Karen Little <karen.little at whoishostingthismail.com> wrote:
		
			 Hi, 

I appreciate you're busy so I just wanted to follow up on the email I sent you the other day as I noticed the link is still broken. I've included my email below for your reference:

		On Fri, Sep 9, 2016 at 2:55 PM, Karen Little <karen.little at whoishostingthismail.com> wrote:
		
			 Hi, 

Just wanted to let you know about a link that seems to be broken on this page http://rtfd.qiniudn.com/docs-py3_zh/build/html/whatsnew/3.2.html.

It is this link http://mercurial.selenic.com/guide/, but the page doesn?t seem to be active any more. I thought you might want to update.

If you are looking for an alternative please check out http://wiht.link/Mercurial-intro, it may make a suitable replacement.

Kind Regards,
Karen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160921/5eb38965/attachment.html>

From report at bugs.python.org  Wed Sep 21 11:13:00 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 21 Sep 2016 15:13:00 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474470780.82.0.601953638785.issue28197@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> I'd argue that range can implement the 3-arg .index much better 
> than generic Sequence.

Yes, the range index() method should implement all three arguments.  That shouldn't be difficult.

----------
assignee: docs at python -> 
type: behavior -> enhancement
versions:  -Python 3.5, Python 3.6

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

From report at bugs.python.org  Wed Sep 21 11:26:21 2016
From: report at bugs.python.org (Dennis Jensen)
Date: Wed, 21 Sep 2016 15:26:21 +0000
Subject: [docs] [issue28242] os.environ.get documentation missing
Message-ID: <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>


New submission from Dennis Jensen:

I was encountering what seemed to be odd behavior from os.environ.get() from what I could find out about it and so I tried to locate the actual documentation on how it is supposed to be used now.  However, all I can find is a minor reference to os.environ.  There appears to be no documentation on os.environ.get() and/or any other methods of this sort associated with os.environ.  The alternate functionality os.getenv() is documented but this is not supposed to work the same as os.environ.get()   Still the behavior that I encountered is that it seems that either os.environ.get()) has been changed and/or it is now just simply a proxy for os.getenv() -- as these two seem to function the same way now.  Note: From what I was able to discern about how os.environ.get() worked is that it accepts only 1 parameter and if the item does not exist it throws an error -- while os.getenv() takes 2 parameters and does not throw an error if the item does not exist.

----------
assignee: docs at python
components: Documentation
messages: 277159
nosy: DennisJensen, docs at python
priority: normal
severity: normal
status: open
title: os.environ.get documentation missing
type: resource usage
versions: Python 3.5

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

From report at bugs.python.org  Wed Sep 21 11:28:55 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Sep 2016 15:28:55 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474471734.99.0.597809378781.issue28197@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Sorry for poor words. I was not going to blame anybody. But changing interface always is dangerous. It makes third-party classes that implemented the interface no longer valid substitutions.

I think two things are worth to be done:

1) Explicitly document (including the docstring) that the support of stop and start arguments is optional. Not all sequences implements it. 3.5+.

2) Add the support of stop and start arguments to range() in 3.7.

And would be nice to provide a way for testing if the sequence supports extended index(). If this is possible.

----------

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

From report at bugs.python.org  Wed Sep 21 11:36:36 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 21 Sep 2016 15:36:36 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474472196.49.0.929600581318.issue28197@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

>  2) Add the support of stop and start arguments to range() in 3.7.

Yes, the whole point of adding these bogus methods in the first place was to harmonize the range object with other sequence types.

----------

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

From report at bugs.python.org  Wed Sep 21 11:51:44 2016
From: report at bugs.python.org (Ned Deily)
Date: Wed, 21 Sep 2016 15:51:44 +0000
Subject: [docs] [issue28242] os.environ.get documentation missing
In-Reply-To: <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>
Message-ID: <1474473104.19.0.720229242878.issue28242@psf.upfronthosting.co.za>


Ned Deily added the comment:

os.environ is documented as being a "mapping" object.  The "get" method is a standard method for all mapping objects; it's not unique to os.environ.  Thus, there is no need to specially call out "get" or any of the other "mapping" methods and operations available with os.environ or any other example of a mapping object.  The "Built-in Types" chapter of the Python Standard Library reference describes the standard types and their methods and operations.


https://docs.python.org/3/library/os.html#os.environ
https://docs.python.org/3/library/stdtypes.html#mapping-types-dict
https://docs.python.org/3/library/stdtypes.html

----------
nosy: +ned.deily
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed Sep 21 12:27:41 2016
From: report at bugs.python.org (Dennis Jensen)
Date: Wed, 21 Sep 2016 16:27:41 +0000
Subject: [docs] [issue28242] os.environ.get documentation missing
In-Reply-To: <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>
Message-ID: <1474475261.71.0.579207510608.issue28242@psf.upfronthosting.co.za>


Dennis Jensen added the comment:

Okay well thanks for that information but after investigating this then I have to ask what is the difference between:

os.environ.get()

and

os.getenv()

As these 2 functions now appear to do exactly the same thing?  If this is the case then should there not be something added to either os.environ or to os.getenv() that states something to this effect.

Something along the lines of:  Since version: "whatever version that changed how .get() works" made the os.environ.get() work exactly the same as the os.getenv() -- this way since there are still references floating around that state that these 2 do not function the same and nothing outlined clearly within documentation stating that this is no longer the case.  Creates a bit of confusion on what should and should not be.

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

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

From report at bugs.python.org  Wed Sep 21 12:33:44 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Sep 2016 16:33:44 +0000
Subject: [docs] [issue28235] In xml.etree.ElementTree docs there is no
 parser argument in fromstring()
In-Reply-To: <1474457056.95.0.329737294315.issue28235@psf.upfronthosting.co.za>
Message-ID: <1474475624.72.0.955040573838.issue28235@psf.upfronthosting.co.za>


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


----------
nosy: +eli.bendersky, scoder

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

From report at bugs.python.org  Wed Sep 21 12:34:00 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Sep 2016 16:34:00 +0000
Subject: [docs] [issue28235] In xml.etree.ElementTree docs there is no
 parser argument in fromstring()
In-Reply-To: <1474457056.95.0.329737294315.issue28235@psf.upfronthosting.co.za>
Message-ID: <1474475640.41.0.904804486933.issue28235@psf.upfronthosting.co.za>


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


----------
stage:  -> patch review

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

From report at bugs.python.org  Wed Sep 21 12:35:14 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Sep 2016 16:35:14 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474475713.99.0.689835826415.issue28234@psf.upfronthosting.co.za>


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


----------
nosy: +eli.bendersky, scoder
stage:  -> patch review

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

From report at bugs.python.org  Wed Sep 21 12:41:38 2016
From: report at bugs.python.org (Dennis Jensen)
Date: Wed, 21 Sep 2016 16:41:38 +0000
Subject: [docs] [issue28242] os.environ.get documentation missing
In-Reply-To: <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>
Message-ID: <1474476098.91.0.404647651344.issue28242@psf.upfronthosting.co.za>


Changes by Dennis Jensen <djensen at macsales.com>:


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

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

From report at bugs.python.org  Wed Sep 21 13:04:04 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 21 Sep 2016 17:04:04 +0000
Subject: [docs] [issue28235] In xml.etree.ElementTree docs there is no
 parser argument in fromstring()
In-Reply-To: <1474457056.95.0.329737294315.issue28235@psf.upfronthosting.co.za>
Message-ID: <1474477444.41.0.870768887373.issue28235@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Instead of duplicating XML() documentation, I'd suggest changing fromstring() documentation to say something like "this is an alias for ElementTree.XML()."

----------
nosy: +berker.peksag
versions: +Python 3.5, Python 3.7

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

From report at bugs.python.org  Wed Sep 21 14:18:28 2016
From: report at bugs.python.org (Ned Deily)
Date: Wed, 21 Sep 2016 18:18:28 +0000
Subject: [docs] [issue28242] os.environ.get documentation missing
In-Reply-To: <1474471581.82.0.975810420091.issue28242@psf.upfronthosting.co.za>
Message-ID: <1474481908.38.0.871578171648.issue28242@psf.upfronthosting.co.za>


Ned Deily added the comment:

The difference is that os.environ is a reference to a mapping object, essentially a dict, that has all of the process environment variables. By using the get('x') method on that object, you ask the object to find and return the value corresponding to key 'x' or to return None if the key is not found.  It's the same as using os.environ['x'] except that the latter raises a KeyError exception if the the key is not found.  This is how all mapping objects work.  (Also, os.environ() does not work because os.environ is not callable.)  os.getenv('x') is a call to the function that returns the value corresponding to key 'x' or None.  Yes, the end results of os.getenv('x') and os.environ.get('x') are the same but how they get there is conceptually different.  Why are there two similar ways to do this?  I can only speculate at this point.  It looks like os.environ and os.putenv have been around since the very early days of Python.  os.getenv appeared somewhat later but has been around since at least 2001 (http://bugs.python.org/issue429059).  Since os.putenv already existed, os.getenv could have been added as a convenience to mimic the underlying libc function names.  In any case, it's perfectly fine to use either approach and has been for at least 15 years!

>>> import os
>>> os.environ()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: '_Environ' object is not callable
>>> os.environ
environ({'TERM': 'xterm-256color', 'HISTCONTROL': 'erasedups', 'HOME': '/Users/nad'})
>>> os.environ.get('HOME')
'/Users/nad'
>>> os.environ['HOME']
'/Users/nad'
>>> os.getenv
<function getenv at 0x1007318c8>
>>> os.getenv('HOME')
'/Users/nad'

----------
resolution:  -> not a bug
status: open -> closed
type: resource usage -> 

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

From report at bugs.python.org  Wed Sep 21 15:17:53 2016
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Wed, 21 Sep 2016 19:17:53 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474485473.79.0.957077275082.issue28197@psf.upfronthosting.co.za>


Vedran ?a?i? added the comment:

Why can't this go into 3.6? To me this situation seems like a bug.

----------

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

From vadmium+py at gmail.com  Wed Sep 21 18:34:30 2016
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Wed, 21 Sep 2016 22:34:30 -0000
Subject: [docs] In xml.etree.ElementTree docs there is no parser argument in
 fromstring() (issue 28235)
Message-ID: <20160921223430.20395.88741@psf.upfronthosting.co.za>


https://bugs.python.org/review/28235/diff/18636/Doc/library/xml.etree.elementtree.rst
File Doc/library/xml.etree.elementtree.rst (right):

https://bugs.python.org/review/28235/diff/18636/Doc/library/xml.etree.elementtree.rst#newcode491
Doc/library/xml.etree.elementtree.rst:491: is a string containing XML
data.  *parser* is an optional parser instance.
Would be nice to start sentences with capital letters. I suggest either
*Parser* or something like ?The *parser* argument is . . .?

https://bugs.python.org/review/28235/

From vadmium+py at gmail.com  Wed Sep 21 21:36:09 2016
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Thu, 22 Sep 2016 01:36:09 -0000
Subject: [docs] In xml.etree.ElementTree docs there are many absent Element
 class links (issue 28234)
Message-ID: <20160922013609.20395.6638@psf.upfronthosting.co.za>


https://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst
File Doc/library/xml.etree.elementtree.rst (right):

https://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst#newcode507
Doc/library/xml.etree.elementtree.rst:507: :class:`Element` instance. 
Returns a true value if this is an element object.
This does not make much sense. How could *element* be an Element class
instance, but _not_ an ?element object?? Maybe drop at least one of the
sentences?

The implementation seems to check for a ?tag? attribute. It used to have
an alternative check for an Element class instance, but that was
removed.

https://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst#newcode582
Doc/library/xml.etree.elementtree.rst:582: arguments.  Returns an
:class:`Element` instance.
Wouldn?t it be clearer to say _what_ element it returns (new child,
parent, or something else)?

https://bugs.python.org/review/28234/

From report at bugs.python.org  Wed Sep 21 21:37:36 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 22 Sep 2016 01:37:36 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474508256.19.0.234497096005.issue28234@psf.upfronthosting.co.za>


Martin Panter added the comment:

Mostly looks good to me. I left some comments on the code review.

----------
nosy: +martin.panter
versions: +Python 2.7, Python 3.5, Python 3.7

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

From report at bugs.python.org  Wed Sep 21 23:02:03 2016
From: report at bugs.python.org (Matthew Ekstrand-Abueg)
Date: Thu, 22 Sep 2016 03:02:03 +0000
Subject: [docs] [issue28244] Incorrect Example in itertools.product
 description
Message-ID: <1474513323.36.0.596780277043.issue28244@psf.upfronthosting.co.za>


New submission from Matthew Ekstrand-Abueg:

Documentation states:

    # product('ABCD', 'xy') --> Ax Ay Bx By Cx Cy Dx Dy
    # product(range(2), repeat=3) --> 000 001 010 011 100 101 110 

But:

>>> list(itertools.product('ABCD','xy'))
[('A', 'x'), ('A', 'y'), ('B', 'x'), ('B', 'y'), ('C', 'x'), ('C', 'y'), ('D', 'x'), ('D', 'y')]

https://docs.python.org/2/library/itertools.html#itertools.product

----------
assignee: docs at python
components: Documentation
messages: 277188
nosy: Matthew Ekstrand-Abueg, docs at python
priority: normal
severity: normal
status: open
title: Incorrect Example in itertools.product description
type: behavior
versions: Python 2.7

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

From report at bugs.python.org  Thu Sep 22 02:02:26 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Sep 2016 06:02:26 +0000
Subject: [docs] [issue28244] Incorrect Example in itertools.product
 description
In-Reply-To: <1474513323.36.0.596780277043.issue28244@psf.upfronthosting.co.za>
Message-ID: <1474524146.35.0.761280703017.issue28244@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

The comments in the docs are necessarily terse and communicate the pattern of pairings.  It would not be an improvement to actually list out all the tuples.  

Sorry if this caused you any confusion, but I prefer to leave the comments as they are now.

----------
assignee: docs at python -> rhettinger
nosy: +rhettinger
resolution:  -> wont fix
status: open -> closed

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

From bugzilla-mail-box at yandex.ru  Thu Sep 22 02:02:26 2016
From: bugzilla-mail-box at yandex.ru (bugzilla-mail-box at yandex.ru)
Date: Thu, 22 Sep 2016 06:02:26 -0000
Subject: [docs] In xml.etree.ElementTree docs there are many absent
 Element class links (issue 28234)
Message-ID: <20160922060226.17021.2932@psf.upfronthosting.co.za>

Reviewers: vadmium,


http://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst
File Doc/library/xml.etree.elementtree.rst (right):

http://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst#newcode507
Doc/library/xml.etree.elementtree.rst:507: :class:`Element` instance. 
Returns a true value if this is an element object.
On 2016/09/22 03:36:09, vadmium wrote:
> This does not make much sense. How could *element* be an Element class
instance,
> but _not_ an ?element object?? Maybe drop at least one of the
sentences?
> 
The second sentence can be inserted to the third sentence (to the end)
instead of "element object".
"Returns a true value if this is an :class:`Element` instance."



Please review this at http://bugs.python.org/review/28234/

Affected files:
  Doc/library/xml.etree.elementtree.rst


diff --git a/Doc/library/xml.etree.elementtree.rst b/Doc/library/xml.etree.elementtree.rst
index 99d7e8b..719121f 100644
--- a/Doc/library/xml.etree.elementtree.rst
+++ b/Doc/library/xml.etree.elementtree.rst
@@ -466,7 +466,7 @@ Functions
    Comment element factory.  This factory function creates a special element
    that will be serialized as an XML comment by the standard serializer.  The
    comment string can be either a bytestring or a Unicode string.  *text* is a
-   string containing the comment string.  Returns an element instance
+   string containing the comment string.  Returns an :class:`Element` instance
    representing a comment.
 
    Note that :class:`XMLParser` skips over comments in the input
@@ -504,7 +504,7 @@ Functions
 .. function:: iselement(element)
 
    Checks if an object appears to be a valid element object.  *element* is an
-   element instance.  Returns a true value if this is an element object.
+   :class:`Element` instance.  Returns a true value if this is an element object.
 
 
 .. function:: iterparse(source, events=None, parser=None)
@@ -551,7 +551,7 @@ Functions
    PI element factory.  This factory function creates a special element that
    will be serialized as an XML processing instruction.  *target* is a string
    containing the PI target.  *text* is a string containing the PI contents, if
-   given.  Returns an element instance, representing a processing instruction.
+   given.  Returns an :class:`Element` instance, representing a processing instruction.
 
    Note that :class:`XMLParser` skips over processing instructions
    in the input instead of creating comment objects for them. An
@@ -572,14 +572,14 @@ Functions
 
 .. function:: SubElement(parent, tag, attrib={}, **extra)
 
-   Subelement factory.  This function creates an element instance, and appends
+   Subelement factory.  This function creates an :class:`Element` instance, and appends
    it to an existing element.
 
    The element name, attribute names, and attribute values can be either
    bytestrings or Unicode strings.  *parent* is the parent element.  *tag* is
    the subelement name.  *attrib* is an optional dictionary, containing element
    attributes.  *extra* contains additional attributes, given as keyword
-   arguments.  Returns an element instance.
+   arguments.  Returns an :class:`Element` instance.
 
 
 .. function:: tostring(element, encoding="us-ascii", method="xml", *, \
@@ -742,7 +742,7 @@ Element Objects
    .. method:: find(match, namespaces=None)
 
       Finds the first subelement matching *match*.  *match* may be a tag name
-      or a :ref:`path <elementtree-xpath>`.  Returns an element instance
+      or a :ref:`path <elementtree-xpath>`.  Returns an :class:`Element` instance
       or ``None``.  *namespaces* is an optional mapping from namespace prefix
       to full name.
 
@@ -863,7 +863,7 @@ ElementTree Objects
 
       Replaces the root element for this tree.  This discards the current
       contents of the tree, and replaces it with the given element.  Use with
-      care.  *element* is an element instance.
+      care.  *element* is an :class:`Element` instance.
 
 
    .. method:: find(match, namespaces=None)
@@ -1001,7 +1001,7 @@ TreeBuilder Objects
    can use this class to build an element structure using a custom XML parser,
    or a parser for some other XML-like format.  *element_factory*, when given,
    must be a callable accepting two positional arguments: a tag and
-   a dict of attributes.  It is expected to return a new element instance.
+   a dict of attributes.  It is expected to return a new :class:`Element` instance.
 
    .. method:: close()
 



From report at bugs.python.org  Thu Sep 22 02:11:29 2016
From: report at bugs.python.org (py.user)
Date: Thu, 22 Sep 2016 06:11:29 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474524689.9.0.533015009316.issue28234@psf.upfronthosting.co.za>


py.user added the comment:

> I left some comments on the code review.
Left an answer on a comment. (ISTM, email notification doesn't work there, I didn't get email.)

----------

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

From report at bugs.python.org  Thu Sep 22 02:26:38 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Sep 2016 06:26:38 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474525598.11.0.320320939719.issue28234@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

In lxml Element is a factory function, not a class.

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

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

From report at bugs.python.org  Thu Sep 22 02:38:48 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Sep 2016 06:38:48 +0000
Subject: [docs] [issue28197] range.index mismatch with documentation
In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za>
Message-ID: <1474526328.6.0.569310164467.issue28197@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> Why can't this go into 3.6?

Because it is a new feature and we're already past beta 1; because nothing is actually broken; and because it is a very minor issue (x isn't 100% consistent with y); because this would depend on new code and tests that we haven't written yet; and because the use case for the optional arguments is to do repeated searches and that doesn't make much sense in the context of a range object.  That said, I think it is harmless to add this to 3.7 even though it isn't very useful.

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

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

From report at bugs.python.org  Thu Sep 22 04:38:26 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 22 Sep 2016 08:38:26 +0000
Subject: [docs] [issue28235] In xml.etree.ElementTree docs there is no
 parser argument in fromstring()
In-Reply-To: <1474457056.95.0.329737294315.issue28235@psf.upfronthosting.co.za>
Message-ID: <1474533506.9.0.57710742422.issue28235@psf.upfronthosting.co.za>


Martin Panter added the comment:

Added review comment

----------
nosy: +martin.panter

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

From vadmium+py at gmail.com  Thu Sep 22 04:39:35 2016
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Thu, 22 Sep 2016 08:39:35 -0000
Subject: [docs] In xml.etree.ElementTree docs there are many absent
 Element class links (issue 28234)
Message-ID: <20160922083935.17843.72146@psf.upfronthosting.co.za>


https://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst
File Doc/library/xml.etree.elementtree.rst (right):

https://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst#newcode507
Doc/library/xml.etree.elementtree.rst:507: :class:`Element` instance. 
Returns a true value if this is an element object.
On 2016/09/22 08:02:26, py.user wrote:
> The second sentence can be inserted to the third sentence (to the end)
instead
> of "element object".
> "Returns a true value if this is an :class:`Element` instance."

I think that would be good

https://bugs.python.org/review/28234/

From report at bugs.python.org  Thu Sep 22 04:39:48 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 22 Sep 2016 08:39:48 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474533588.09.0.599873836457.issue28234@psf.upfronthosting.co.za>


Martin Panter added the comment:

Serhiy, what?s the relevance? In the built-in Element Tree package, it is a class: <https://docs.python.org/3.5/library/xml.etree.elementtree.html#element-objects>.

----------

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

From report at bugs.python.org  Thu Sep 22 05:02:11 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Sep 2016 09:02:11 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474534931.26.0.293990489057.issue28234@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

The built-in ElementTree package is derived from lxml.etree. I suppose that the documentation is inherited from lxml.etree.

The built-in ElementTree package supports duck typing. The element object is not always an instance of the Element class. iselement() is not equal to isinstance(e, Element), it just tests the existence of the tag attribute. Many ElementTree functions have fast path for Element, but work with duck typed classes too. I believe that in particular you can mix Python and C implementations of Element and lxml.etree elements in one tree.

----------

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

From report at bugs.python.org  Thu Sep 22 06:26:03 2016
From: report at bugs.python.org (Robert Collins)
Date: Thu, 22 Sep 2016 10:26:03 +0000
Subject: [docs] [issue17188] Document 'from None' in raise statement doc.
In-Reply-To: <1360631999.8.0.76627095073.issue17188@psf.upfronthosting.co.za>
Message-ID: <1474539963.04.0.135170598351.issue17188@psf.upfronthosting.co.za>


Changes by Robert Collins <robertc at robertcollins.net>:


----------
nosy: +rbcollins

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

From report at bugs.python.org  Thu Sep 22 07:31:25 2016
From: report at bugs.python.org (py.user)
Date: Thu, 22 Sep 2016 11:31:25 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474543885.78.0.0217557481535.issue28234@psf.upfronthosting.co.za>


py.user added the comment:

Serhiy Storchaka wrote:
> I believe that in particular you can mix Python and
> C implementations of Element and lxml.etree elements in one tree.


The xml.etree.ElementTree.ElementTree() can accept lxml.etree.Element() as a node, but node in node is impossible.

>>> import xml.etree.ElementTree as etree_xml
>>> import lxml.etree as etree_lxml
>>> 
>>> elem1 = etree_xml.Element('a')
>>> elem2 = etree_lxml.Element('b')
>>> elem1.append(elem2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: must be xml.etree.ElementTree.Element, not lxml.etree._Element
>>>

----------

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

From report at bugs.python.org  Fri Sep 23 01:49:13 2016
From: report at bugs.python.org (Eswar Yaganti)
Date: Fri, 23 Sep 2016 05:49:13 +0000
Subject: [docs] [issue28252] Tuples used before introduction to tuple in
 tutorial
Message-ID: <1474609752.92.0.504291617054.issue28252@psf.upfronthosting.co.za>


New submission from Eswar Yaganti:

In the python tutorial, the tuples were used in an example before the introduction to tuples in section 5.1.4

----------
assignee: docs at python
components: Documentation
messages: 277243
nosy: Eswar Yaganti, docs at python
priority: normal
severity: normal
status: open
title: Tuples used before introduction to tuple in tutorial
type: enhancement
versions: Python 2.7

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

From bugzilla-mail-box at yandex.ru  Fri Sep 23 04:42:58 2016
From: bugzilla-mail-box at yandex.ru (bugzilla-mail-box at yandex.ru)
Date: Fri, 23 Sep 2016 08:42:58 -0000
Subject: [docs] In xml.etree.ElementTree docs there are many absent
 Element class links (issue 28234)
Message-ID: <20160923084258.11942.98707@psf.upfronthosting.co.za>

Add reply and test email notification.


http://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst
File Doc/library/xml.etree.elementtree.rst (right):

http://bugs.python.org/review/28234/diff/18635/Doc/library/xml.etree.elementtree.rst#newcode582
Doc/library/xml.etree.elementtree.rst:582: arguments.  Returns an
:class:`Element` instance.
On 2016/09/22 03:36:09, vadmium wrote:
> Wouldn?t it be clearer to say _what_ element it returns (new child,
parent, or
> something else)?
The last sentence can be more specific
"Returns the new child element which is an :class:`Element` instance."

http://bugs.python.org/review/28234/

From report at bugs.python.org  Fri Sep 23 04:47:46 2016
From: report at bugs.python.org (py.user)
Date: Fri, 23 Sep 2016 08:47:46 +0000
Subject: [docs] [issue28234] In xml.etree.ElementTree docs there are many
 absent Element class links
In-Reply-To: <1474453668.8.0.0192177985612.issue28234@psf.upfronthosting.co.za>
Message-ID: <1474620466.85.0.318728015717.issue28234@psf.upfronthosting.co.za>


py.user added the comment:

Added a reply to the patch about SubElement(). (Realy email notification doesn't work in review. I left a message while publication, and it didn't come.)

----------

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

From report at bugs.python.org  Fri Sep 23 18:03:33 2016
From: report at bugs.python.org (Ned Deily)
Date: Fri, 23 Sep 2016 22:03:33 +0000
Subject: [docs] [issue27292] Warn users that os.urandom() prior to 3.6 can
 return insecure values
In-Reply-To: <1465639674.0.0.865291084778.issue27292@psf.upfronthosting.co.za>
Message-ID: <1474668213.9.0.0140409122023.issue27292@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Sep 24 13:45:49 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Sep 2016 17:45:49 +0000
Subject: [docs] [issue28252] Tuples used before introduction to tuple in
 tutorial
In-Reply-To: <1474609752.92.0.504291617054.issue28252@psf.upfronthosting.co.za>
Message-ID: <1474739149.32.0.353180312272.issue28252@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

The highly interrelated nature of Python makes it necessary for the early parts of any tutorial to have some forward references.  This doesn't appear to have impaired its usability in practice.

----------
nosy: +rhettinger
resolution:  -> not a bug
status: open -> closed

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

From report at bugs.python.org  Sat Sep 24 15:12:21 2016
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 24 Sep 2016 19:12:21 +0000
Subject: [docs] [issue18789] XML Vunerability Table Unclear
In-Reply-To: <1377008574.91.0.12100936862.issue18789@psf.upfronthosting.co.za>
Message-ID: <1474744341.45.0.842591958436.issue18789@psf.upfronthosting.co.za>


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


----------
keywords: +easy
type: security -> enhancement
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Sep 24 15:22:58 2016
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 24 Sep 2016 19:22:58 +0000
Subject: [docs] [issue24778] mailcap.findmatch: document shell command
 Injection danger in filename parameter
In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za>
Message-ID: <1474744978.88.0.50656893819.issue24778@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.7 -Python 3.4

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

From report at bugs.python.org  Sat Sep 24 15:27:00 2016
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 24 Sep 2016 19:27:00 +0000
Subject: [docs] [issue18789] XML Vunerability Table Unclear
In-Reply-To: <1377008574.91.0.12100936862.issue18789@psf.upfronthosting.co.za>
Message-ID: <1474745220.26.0.396199683134.issue18789@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at yahoo.co.uk>:


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

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

From report at bugs.python.org  Sat Sep 24 15:54:37 2016
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 24 Sep 2016 19:54:37 +0000
Subject: [docs] [issue26005] Denial of Service in SimpleHTTPServer and
 BaseHTTPServer
In-Reply-To: <1451897650.58.0.64883073344.issue26005@psf.upfronthosting.co.za>
Message-ID: <1474746877.71.0.928000344724.issue26005@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation -Extension Modules
nosy: +docs at python
type: security -> enhancement
versions: +Python 3.7 -Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Sep 24 17:30:03 2016
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 24 Sep 2016 21:30:03 +0000
Subject: [docs] [issue27778] PEP 524: Add os.getrandom()
In-Reply-To: <1471368341.7.0.188364803995.issue27778@psf.upfronthosting.co.za>
Message-ID: <1474752603.8.0.290424804874.issue27778@psf.upfronthosting.co.za>


Christian Heimes added the comment:

I think the documentation is too specific. We typically don't document all possible error numbers. Something along the lines "fails with OSError when getrandom is not supported" is sufficient.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
priority: normal -> low
type: security -> enhancement

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

From report at bugs.python.org  Sun Sep 25 09:13:42 2016
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 25 Sep 2016 13:13:42 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <1474809222.87.0.452964765191.issue19795@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Sep 25 10:38:52 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 25 Sep 2016 14:38:52 +0000
Subject: [docs] [issue19795] Formatting of True/False/None in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <1474814327.07.0.587671476996.issue19795@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Only the first patch was committed. The patch for None is not reviewed yet.

Here is updated patch.

----------
resolution: fixed -> 
stage: resolved -> patch review
status: closed -> open
title: Formatting of True/False in docs -> Formatting of True/False/None in docs
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3, Python 3.4
Added file: http://bugs.python.org/file44821/doc_none2.patch

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

From regina.ochotzki at online.de  Mon Sep 26 05:51:50 2016
From: regina.ochotzki at online.de (Regina Ochotzki)
Date: Mon, 26 Sep 2016 11:51:50 +0200
Subject: [docs] mknod
Message-ID: <0776eeae-5c39-3b45-aeb4-14b5c78138ef@online.de>

Hi Python Org Team
mknod seams not to be available on windows. This is not mentioned in 
documentation.
Regards Regina

From report at bugs.python.org  Mon Sep 26 13:50:19 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 Sep 2016 17:50:19 +0000
Subject: [docs] [issue25909] Incorrect documentation for PyMapping_Items and
 like
In-Reply-To: <1450525085.87.0.352365699992.issue25909@psf.upfronthosting.co.za>
Message-ID: <1474912218.95.0.104003692601.issue25909@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Seems I was wrong. PyDict_Keys/PyDict_Values/PyDict_Items return a list in Python 3. Thus comments in Include/abstract.h were correct. Xiang Zhang noticed this in issue28211.

----------

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

From report at bugs.python.org  Mon Sep 26 13:54:51 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 Sep 2016 17:54:51 +0000
Subject: [docs] [issue25909] Incorrect documentation for PyMapping_Items and
 like
In-Reply-To: <1450525085.87.0.352365699992.issue25909@psf.upfronthosting.co.za>
Message-ID: <20160926175448.19762.94491.878F1DF9@psf.io>


Roundup Robot added the comment:

New changeset 68fc808bed9f by Serhiy Storchaka in branch '3.5':
Issues #25909, #28211: Restored correct documentation of PyMapping_Items,
https://hg.python.org/cpython/rev/68fc808bed9f

New changeset 21336392a680 by Serhiy Storchaka in branch '3.6':
Issues #25909, #28211: Restored correct documentation of PyMapping_Items,
https://hg.python.org/cpython/rev/21336392a680

New changeset 1229de1ab5c8 by Serhiy Storchaka in branch 'default':
Issues #25909, #28211: Restored correct documentation of PyMapping_Items,
https://hg.python.org/cpython/rev/1229de1ab5c8

----------

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

From report at bugs.python.org  Mon Sep 26 13:54:51 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 Sep 2016 17:54:51 +0000
Subject: [docs] [issue28211] Wrong return value type in the doc of
 PyMapping_Keys/Values/Items
In-Reply-To: <1474361846.96.0.641386769432.issue28211@psf.upfronthosting.co.za>
Message-ID: <20160926175448.19762.85667.2EAD13D4@psf.io>


Roundup Robot added the comment:

New changeset 68fc808bed9f by Serhiy Storchaka in branch '3.5':
Issues #25909, #28211: Restored correct documentation of PyMapping_Items,
https://hg.python.org/cpython/rev/68fc808bed9f

New changeset 21336392a680 by Serhiy Storchaka in branch '3.6':
Issues #25909, #28211: Restored correct documentation of PyMapping_Items,
https://hg.python.org/cpython/rev/21336392a680

New changeset 1229de1ab5c8 by Serhiy Storchaka in branch 'default':
Issues #25909, #28211: Restored correct documentation of PyMapping_Items,
https://hg.python.org/cpython/rev/1229de1ab5c8

----------

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

From report at bugs.python.org  Mon Sep 26 13:56:23 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 Sep 2016 17:56:23 +0000
Subject: [docs] [issue28211] Wrong return value type in the doc of
 PyMapping_Keys/Values/Items
In-Reply-To: <1474361846.96.0.641386769432.issue28211@psf.upfronthosting.co.za>
Message-ID: <1474912583.65.0.596098831682.issue28211@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for your report and patch Xiang Zhang!

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

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

From berker.peksag at gmail.com  Mon Sep 26 15:50:11 2016
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Mon, 26 Sep 2016 22:50:11 +0300
Subject: [docs] mknod
In-Reply-To: <0776eeae-5c39-3b45-aeb4-14b5c78138ef@online.de>
References: <0776eeae-5c39-3b45-aeb4-14b5c78138ef@online.de>
Message-ID: <CAF4280KeOc6X363NPxcJD1dZk8BkO-CXZw8NzmmFtUW=8fUX3Q@mail.gmail.com>

On Mon, Sep 26, 2016 at 12:51 PM, Regina Ochotzki
<regina.ochotzki at online.de> wrote:
> Hi Python Org Team
> mknod seams not to be available on windows. This is not mentioned in
> documentation.

Hi Regina,

Thanks for the report. I've updated the documentation in
https://hg.python.org/cpython/rev/413962973ea6

--Berker

From report at bugs.python.org  Mon Sep 26 16:21:16 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 Sep 2016 20:21:16 +0000
Subject: [docs] [issue10673] multiprocess.Process join method - timeout
 indistinguishable from success
In-Reply-To: <1291991778.63.0.145134143934.issue10673@psf.upfronthosting.co.za>
Message-ID: <20160926202112.100945.25609.11259631@psf.io>


Roundup Robot added the comment:

New changeset 112060f8abe8 by Berker Peksag in branch '3.5':
Issue #10673: Document that Process.exitcode can be used to determine timeout
https://hg.python.org/cpython/rev/112060f8abe8

New changeset 0414ce8a3b5c by Berker Peksag in branch '3.6':
Issue #10673: Merge from 3.5
https://hg.python.org/cpython/rev/0414ce8a3b5c

New changeset f91650739061 by Berker Peksag in branch 'default':
Issue #10673: Merge from 3.6
https://hg.python.org/cpython/rev/f91650739061

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

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

From report at bugs.python.org  Mon Sep 26 16:21:45 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 26 Sep 2016 20:21:45 +0000
Subject: [docs] [issue10673] multiprocess.Process join method - timeout
 indistinguishable from success
In-Reply-To: <1291991778.63.0.145134143934.issue10673@psf.upfronthosting.co.za>
Message-ID: <1474921305.46.0.623875585259.issue10673@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks, Tom.

----------
components:  -Library (Lib)
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7

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

From report at bugs.python.org  Mon Sep 26 16:28:54 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 Sep 2016 20:28:54 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <20160926202851.100670.74465.DF3324A1@psf.io>


Roundup Robot added the comment:

New changeset ac24e5c2fd3e by Berker Peksag in branch 'default':
Issue #20100: Simplify newPyEpoll_Object()
https://hg.python.org/cpython/rev/ac24e5c2fd3e

----------

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

From report at bugs.python.org  Mon Sep 26 16:29:08 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 26 Sep 2016 20:29:08 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <1474921748.88.0.7819731328.issue20100@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Sep 26 18:17:40 2016
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 26 Sep 2016 22:17:40 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <20160926202851.100670.74465.DF3324A1@psf.io>
Message-ID: <CAMpsgwZ1V2GYbpJR4Y7yMEH6JK9oowHaLWvFCT8+2mL6CwAmEQ@mail.gmail.com>


STINNER Victor added the comment:

I dislike this change. Python is not responsible to check parameters of OS
syscalls, this function should be a thin wrapper to the OS function. Linux
may add new flags in the future.

Le lundi 26 septembre 2016, Roundup Robot <report at bugs.python.org> a ?crit :

>
> Roundup Robot added the comment:
>
> New changeset ac24e5c2fd3e by Berker Peksag in branch 'default':
> Issue #20100: Simplify newPyEpoll_Object()
> https://hg.python.org/cpython/rev/ac24e5c2fd3e
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org <javascript:;>>
> <http://bugs.python.org/issue20100>
> _______________________________________
>

----------

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

From report at bugs.python.org  Mon Sep 26 21:27:45 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 27 Sep 2016 01:27:45 +0000
Subject: [docs] [issue28282] find_library("c") defers to find_msvcrt()
Message-ID: <1474939665.29.0.913307125474.issue28282@psf.upfronthosting.co.za>


New submission from Martin Panter:

Issue 1793 added ctypes.util.find_msvcrt(), and special cases that map find_library("c") and "m" to the new function. However this contradicts the documentation <https://docs.python.org/3.5/library/ctypes.html#finding-shared-libraries>:

?On Windows, . . . a call like find_library("c") will fail and return None.?

I think the documentation needs updating or clarifying.

----------
assignee: docs at python
components: Documentation, Windows, ctypes
messages: 277479
nosy: docs at python, martin.panter, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: find_library("c") defers to find_msvcrt()
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Tue Sep 27 04:25:27 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 27 Sep 2016 08:25:27 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1388505494.08.0.643576998185.issue20100@psf.upfronthosting.co.za>
Message-ID: <1474964727.04.0.873960760453.issue20100@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Old code looked strange after issue18571:

        flags |= EPOLL_CLOEXEC;
        if (flags)
            self->epfd = epoll_create1(flags);
        else

The condition is always true unless EPOLL_CLOEXEC is 0.

----------

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

From report at bugs.python.org  Tue Sep 27 04:50:12 2016
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 27 Sep 2016 08:50:12 +0000
Subject: [docs] [issue20100] epoll docs are not clear with regards to
 CLOEXEC.
In-Reply-To: <1474964727.04.0.873960760453.issue20100@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwZCS=fufApAqZuMHOyksyNV4Hb_fgE_Aw1zOe2B+U=iyg@mail.gmail.com>


STINNER Victor added the comment:

> Old code looked strange after issue18571:

epoll_create() is a deprecated. epoll_create(size): "Since Linux
2.6.8, the size argument is ignored, but must be  greater  than  zero"
according to the man page. So it's fine to always call
epoll_create1(flags).

Example of new potential new flag for epoll_create1(): ten years ago,
EPOLL_NONBLOCK was proposed:
https://lkml.org/lkml/2008/8/24/130
(but it seems like it doesn't make sense, since the syscall cannot block)

Recent epoll evolutions don't seem to be on epoll_create1():
https://lwn.net/Articles/633422/

----------

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

From bgailer at gmail.com  Tue Sep 27 10:18:48 2016
From: bgailer at gmail.com (bob gailer)
Date: Tue, 27 Sep 2016 10:18:48 -0400
Subject: [docs] PEP 380: Syntax for Delegating to a Subgenerator (3.5.1 and
 others?)
Message-ID: <9d67a3ca-dc2a-662a-52f5-7bf04e990ff4@gmail.com>

2nd example:

 >>> def accumulate():
...     tally = 0
...     while 1:
...         next = yield
...         if next is None:
...             return tally
...         tally += next

In general we discourage assignment to built-in functions (next in this 
case). I recommend using some other name.

Also it seems to me that we encourage use of True instead of 1 where 
True is intended.


From report at bugs.python.org  Tue Sep 27 19:35:18 2016
From: report at bugs.python.org (paul j3)
Date: Tue, 27 Sep 2016 23:35:18 +0000
Subject: [docs] [issue28219] Is order of argparse --help output officially
 defined?
In-Reply-To: <1474401187.0.0.781761805381.issue28219@psf.upfronthosting.co.za>
Message-ID: <1475019318.59.0.0158033056531.issue28219@psf.upfronthosting.co.za>


paul j3 added the comment:

The display of the Action help lines is determined by the parser.format_help function

https://docs.python.org/3/library/argparse.html#printing-help

This function creates a Formatter, and then loads it with a 'stack' of sections.  Sections are displayed in that order:

        # usage (with self._actions)
        # description
        # groups

        for action_group in self._action_groups:
            formatter.start_section(action_group.title)
            formatter.add_text(action_group.description)
            formatter.add_arguments(action_group._group_actions)
            formatter.end_section()

parser._actions is the list of Actions (arguments) in the order in which they were created.  

Usage displays them, first the optionals, then the positionals.  Some Stackoverflow posters have asked about changing that order.  That requires customizing the usage formatter method.

Help is displayed by group, and with in that by creation order.  There are 2 default groups, positionals and optionals.  User defined groups follow.  https://docs.python.org/3/library/argparse.html#argument-groups

Probably the simplest way to write help lines in a different order is to write a custom parser.format_help method.  

Subclassing HelpFormatter is the 'accepted' way of customizing the help.  The provided subclasses work by modifying just one or two methods.  But given how a formatter works it is much easier to change the order while 'loading' the formatter rather than after it has been created.

I don't see the point to etching this behavior into the documentation. It's the default behavior, and relatively obvious from a few examples.  If we were to add some sort of customization then we'd need to elaborate.  This documentation is more of a how-to document than a formal description of the module.  This is just one of the many details that are determined by the code rather the documentation.  

But feel free to suggest a formal change to the documentation.

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

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

From report at bugs.python.org  Tue Sep 27 20:42:41 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 00:42:41 +0000
Subject: [docs] [issue27470] -3 commandline option documented differently
 via man
In-Reply-To: <1467994985.16.0.513883147731.issue27470@psf.upfronthosting.co.za>
Message-ID: <1475023360.97.0.385730576683.issue27470@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +berker.peksag
stage:  -> needs patch
type:  -> behavior

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

From report at bugs.python.org  Tue Sep 27 20:48:33 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 00:48:33 +0000
Subject: [docs] [issue26869] unittest longMessage docs
In-Reply-To: <1461743267.94.0.620093650485.issue26869@psf.upfronthosting.co.za>
Message-ID: <1475023713.7.0.680689266884.issue26869@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag
versions: +Python 3.7

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

From report at bugs.python.org  Wed Sep 28 05:31:40 2016
From: report at bugs.python.org (Arvind Padmanabhan)
Date: Wed, 28 Sep 2016 09:31:40 +0000
Subject: [docs] [issue28297] sched module example has wrong output
Message-ID: <1475055099.98.0.944260791196.issue28297@psf.upfronthosting.co.za>


New submission from Arvind Padmanabhan:

Example in the sched module shows the following output:

930343690.257
>From print_time 930343695.274 positional
>From print_time 930343695.275 keyword
>From print_time 930343700.273 default
930343700.276

But since "keyword" is scheduled with a higher priority (lower number), it should be printed first.

URL: https://docs.python.org/3/library/sched.html
Section: 17.6

----------
assignee: docs at python
components: Documentation
messages: 277600
nosy: Arvind Padmanabhan, docs at python
priority: normal
severity: normal
status: open
title: sched module example has wrong output
versions: Python 3.5

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

From report at bugs.python.org  Wed Sep 28 05:53:35 2016
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 28 Sep 2016 09:53:35 +0000
Subject: [docs] [issue28297] sched module example has wrong output
In-Reply-To: <1475055099.98.0.944260791196.issue28297@psf.upfronthosting.co.za>
Message-ID: <1475056415.85.0.361781017487.issue28297@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

Though the delay arguments of keyword and positional are both 5, but their register time has tiny difference: 930343695.274 vs 930343695.275, so positional is printed first.

----------
nosy: +xiang.zhang

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

From report at bugs.python.org  Wed Sep 28 06:00:44 2016
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 28 Sep 2016 10:00:44 +0000
Subject: [docs] [issue28297] sched module example has wrong output
In-Reply-To: <1475055099.98.0.944260791196.issue28297@psf.upfronthosting.co.za>
Message-ID: <1475056844.77.0.559861378405.issue28297@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

Sorry, it's not 930343695.274 vs 930343695.275. I mean the register time is time.time() + delay, so there is tiny difference between the two. You can change the timefunc to lambda: int(time.time()), then you'll see keyword is printed first.

----------

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

From report at bugs.python.org  Wed Sep 28 06:51:13 2016
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 28 Sep 2016 10:51:13 +0000
Subject: [docs] [issue28297] sched module example has wrong output
In-Reply-To: <1475055099.98.0.944260791196.issue28297@psf.upfronthosting.co.za>
Message-ID: <1475059873.87.0.391202927592.issue28297@psf.upfronthosting.co.za>


Changes by Xiang Zhang <angwerzx at 126.com>:


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

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

From andrew.jarcho at gmail.com  Tue Sep 27 22:13:09 2016
From: andrew.jarcho at gmail.com (Andrew Jarcho)
Date: Tue, 27 Sep 2016 22:13:09 -0400
Subject: [docs] https://docs.python.org/2/library/copy.html apparent error
Message-ID: <CAHKRt3o+2K+drq+SwhN35aFKSN0L-9MQLrH+4nSytEPiGLd6+w@mail.gmail.com>

Hi,

I believe the following line in the above page of the Python 2.7.12
documentation:

>> Shallow copies of dictionaries can be made using dict.copy()
<https://docs.python.org/2/library/stdtypes.html#dict.copy>, and of lists
by assigning a slice of the entire list, for example, copied_list =
original_list[:].

should read:


>> *Deep* copies of dictionaries...

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160927/6849a341/attachment.html>

From kxw34567 at 163.com  Tue Sep 27 22:09:51 2016
From: kxw34567 at 163.com (=?GBK?B?s6S46LWx0KU=?=)
Date: Wed, 28 Sep 2016 10:09:51 +0800 (CST)
Subject: [docs] A little bug
Message-ID: <f441c83.b0f.1576e8e220a.Coremail.kxw34567@163.com>

There is a wrong blank in fifth paragraph of this page.


https://docs.python.org/3.6/tutorial/appetite.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160928/1110ec04/attachment.html>

From report at bugs.python.org  Wed Sep 28 09:54:55 2016
From: report at bugs.python.org (SilentGhost)
Date: Wed, 28 Sep 2016 13:54:55 +0000
Subject: [docs] [issue28300] [PATCH] Fix misspelled "implemented" word
In-Reply-To: <1475069573.72.0.0295213559618.issue28300@psf.upfronthosting.co.za>
Message-ID: <1475070895.35.0.906875449052.issue28300@psf.upfronthosting.co.za>


SilentGhost added the comment:

LGTM

----------
assignee:  -> docs at python
components: +Documentation
nosy: +SilentGhost, docs at python
stage:  -> commit review
type:  -> behavior
versions: +Python 3.6

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

From report at bugs.python.org  Wed Sep 28 10:06:25 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 Sep 2016 14:06:25 +0000
Subject: [docs] [issue21903] ctypes documentation MessageBoxA example
 produces error
In-Reply-To: <1404292489.9.0.647841786316.issue21903@psf.upfronthosting.co.za>
Message-ID: <20160928140610.20991.42285.2A595588@psf.io>


Roundup Robot added the comment:

New changeset 11c3d6a8f5fd by Berker Peksag in branch '3.5':
Issue #21903: Update ctypes example to use MessageBoxW
https://hg.python.org/cpython/rev/11c3d6a8f5fd

New changeset 3031e4a95131 by Berker Peksag in branch '3.6':
Issue #21903: Merge from 3.5
https://hg.python.org/cpython/rev/3031e4a95131

New changeset cb55aedcc7e8 by Berker Peksag in branch 'default':
Issue #21903: Merge from 3.6
https://hg.python.org/cpython/rev/cb55aedcc7e8

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

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

From report at bugs.python.org  Wed Sep 28 10:13:22 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 14:13:22 +0000
Subject: [docs] [issue21903] ctypes documentation MessageBoxA example
 produces error
In-Reply-To: <1404292489.9.0.647841786316.issue21903@psf.upfronthosting.co.za>
Message-ID: <1475072002.09.0.487596585978.issue21903@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report! I've now updated the example to use MessageBoxw.

Eryk, do you find the second example (GetWindowRect) is useful? Can we make it more usable? Unless I'm missing something, we need to pass the return value of GetActiveWindow() to make it work.

----------
nosy: +berker.peksag, eryksun
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Sep 28 10:21:03 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 Sep 2016 14:21:03 +0000
Subject: [docs] [issue28300] [PATCH] Fix misspelled "implemented" word
In-Reply-To: <1475069573.72.0.0295213559618.issue28300@psf.upfronthosting.co.za>
Message-ID: <20160928142056.20829.97868.C8980087@psf.io>


Roundup Robot added the comment:

New changeset ce19dcce84fe by Berker Peksag in branch '3.5':
Issue #28300: Fix typos, patch by Shlomi Fish
https://hg.python.org/cpython/rev/ce19dcce84fe

New changeset 078f185f0041 by Berker Peksag in branch '3.6':
Issue #28300: Merge from 3.5
https://hg.python.org/cpython/rev/078f185f0041

New changeset b1d2e303570d by Berker Peksag in branch 'default':
Issue #28300: Merge from 3.6
https://hg.python.org/cpython/rev/b1d2e303570d

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

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

From report at bugs.python.org  Wed Sep 28 10:21:50 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 14:21:50 +0000
Subject: [docs] [issue28300] [PATCH] Fix misspelled "implemented" word
In-Reply-To: <1475069573.72.0.0295213559618.issue28300@psf.upfronthosting.co.za>
Message-ID: <1475072510.62.0.124588517667.issue28300@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed
versions: +Python 3.5

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

From report at bugs.python.org  Wed Sep 28 12:23:07 2016
From: report at bugs.python.org (Shlomi Fish)
Date: Wed, 28 Sep 2016 16:23:07 +0000
Subject: [docs] [issue28300] [PATCH] Fix misspelled "implemented" word
In-Reply-To: <1475069573.72.0.0295213559618.issue28300@psf.upfronthosting.co.za>
Message-ID: <1475079787.49.0.426598266205.issue28300@psf.upfronthosting.co.za>


Shlomi Fish added the comment:

You're welcome and thanks for applying it (and so quickl).

----------

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

From report at bugs.python.org  Wed Sep 28 12:29:27 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 16:29:27 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1475080167.06.0.29398439176.issue12743@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.7
Added file: http://bugs.python.org/file44871/issue12743_v2.diff

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

From report at bugs.python.org  Wed Sep 28 12:34:34 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 Sep 2016 16:34:34 +0000
Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags
In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za>
Message-ID: <20160928163428.94922.57380.FD0D0E31@psf.io>


Roundup Robot added the comment:

New changeset ee76e84f115f by Berker Peksag in branch '3.5':
Issue #27740: Fix typo in Py_CompileStringExFlags
https://hg.python.org/cpython/rev/ee76e84f115f

New changeset 2ee939b314a2 by Berker Peksag in branch '3.6':
Issue #27740: Merge from 3.5
https://hg.python.org/cpython/rev/2ee939b314a2

New changeset a0b13ea75849 by Berker Peksag in branch 'default':
Issue #27740: Merge from 3.6
https://hg.python.org/cpython/rev/a0b13ea75849

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

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

From report at bugs.python.org  Wed Sep 28 12:34:55 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 16:34:55 +0000
Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags
In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za>
Message-ID: <1475080495.85.0.754035911881.issue27740@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7

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

From report at bugs.python.org  Wed Sep 28 13:36:38 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 28 Sep 2016 17:36:38 +0000
Subject: [docs] [issue26869] unittest longMessage docs
In-Reply-To: <1461743267.94.0.620093650485.issue26869@psf.upfronthosting.co.za>
Message-ID: <1475084198.81.0.0973220855368.issue26869@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
nosy: +Mariatta

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

From report at bugs.python.org  Wed Sep 28 15:33:50 2016
From: report at bugs.python.org (Viorel Tabara)
Date: Wed, 28 Sep 2016 19:33:50 +0000
Subject: [docs] [issue28306] incorrect output "int division or modulo by
 zero" in Handling Exceptions tutorial
Message-ID: <1475091230.17.0.768129423451.issue28306@psf.upfronthosting.co.za>


New submission from Viorel Tabara:

I'm reading the Python 3.5.2 documentation at:
  
   https://docs.python.org/3/tutorial/errors.html#handling-exceptions

which shows the following example:

   >>> def this_fails():
   ...     x = 1/0
   ...
   >>> try:
   ...     this_fails()
   ... except ZeroDivisionError as err:
   ...     print('Handling run-time error:', err)
   ...
   Handling run-time error: int division or modulo by zero 

Running the code as a script produces:

   $ python3 -V
   Python 3.5.2
   $ python3 p.py
   Handling run-time error: division by zero

   $ python2 -V
   Python 2.7.12
   $ python2 p.py
   ('Handling run-time error:', ZeroDivisionError('integer division or modulo by zero',))
   
The same output is listed for 3.6 and 3.7 tutorials but I don't have those 
versions installed on my system.

----------
assignee: docs at python
components: Documentation
messages: 277657
nosy: docs at python, viorel
priority: normal
severity: normal
status: open
title: incorrect output "int division or modulo by zero" in Handling Exceptions tutorial
type: behavior
versions: Python 3.5

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

From report at bugs.python.org  Wed Sep 28 15:47:51 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 Sep 2016 19:47:51 +0000
Subject: [docs] [issue28306] incorrect output "int division or modulo by
 zero" in Handling Exceptions tutorial
In-Reply-To: <1475091230.17.0.768129423451.issue28306@psf.upfronthosting.co.za>
Message-ID: <20160928194748.13671.15207.3212AEE6@psf.io>


Roundup Robot added the comment:

New changeset f60396d8f95c by Berker Peksag in branch '3.5':
Issue #28306: Update exception message of ZeroDivisionError
https://hg.python.org/cpython/rev/f60396d8f95c

New changeset e6dcb14829cf by Berker Peksag in branch '3.6':
Issue #28306: Merge from 3.5
https://hg.python.org/cpython/rev/e6dcb14829cf

New changeset ddeeb7d666eb by Berker Peksag in branch 'default':
Issue #28306: Merge from 3.6
https://hg.python.org/cpython/rev/ddeeb7d666eb

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

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

From report at bugs.python.org  Wed Sep 28 15:48:38 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 19:48:38 +0000
Subject: [docs] [issue28306] incorrect output "int division or modulo by
 zero" in Handling Exceptions tutorial
In-Reply-To: <1475091230.17.0.768129423451.issue28306@psf.upfronthosting.co.za>
Message-ID: <1475092118.52.0.471990052038.issue28306@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Good catch! Thanks for the report.

----------
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.6, Python 3.7

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

From report at bugs.python.org  Wed Sep 28 17:33:54 2016
From: report at bugs.python.org (Eryk Sun)
Date: Wed, 28 Sep 2016 21:33:54 +0000
Subject: [docs] [issue21903] ctypes documentation MessageBoxA example
 produces error
In-Reply-To: <1404292489.9.0.647841786316.issue21903@psf.upfronthosting.co.za>
Message-ID: <1475098434.25.0.917002233494.issue21903@psf.upfronthosting.co.za>


Eryk Sun added the comment:

The GetWindowRect example seems fine, for the most part. The docs don't have to show it being called. If I were to call it, I'd use GetForegroundWindow to get a window handle. GetActiveWindow returns the active window attached to the current thread's message queue, but a console application probably doesn't own a window. (The console window is owned by conhost.exe.)

A more pressing matter is the GetModuleHandle examples, which need to either be fixed or replaced. GetModuleHandle returns a module's base address, and in a 64-bit process the result could be truncated when returned as the default C int type. GetModuleHandleW.restype has to be set to a pointer type. Setting it to a Python function, such as the ValidHandle example, has the same truncation problem. In general, a ValidHandle checker would have to be implemented as an errcheck function.

----------

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

From report at bugs.python.org  Wed Sep 28 18:27:03 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 22:27:03 +0000
Subject: [docs] [issue22392] Clarify documentation of __getinitargs__
In-Reply-To: <1410461552.96.0.589396040073.issue22392@psf.upfronthosting.co.za>
Message-ID: <1475101623.26.0.736318008038.issue22392@psf.upfronthosting.co.za>


Berker Peksag added the comment:

https://docs.python.org/2/library/pickle.html#object.__getinitargs__ states:

"If it is desirable that the __init__() method be called on unpickling, an old-style class can define a method __getinitargs__(), which should return a tuple containing the arguments to be passed to the class constructor (__init__() for example)."

However, there is no mention that it only accepts positional arguments.

This is a Python 2-only change and the documentation file is located at Doc/library/pickle.rst in 2.7 branch.

----------
keywords: +easy
nosy: +berker.peksag
stage:  -> needs patch

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

From report at bugs.python.org  Wed Sep 28 19:24:38 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 23:24:38 +0000
Subject: [docs] [issue26224] Add "version added" for documentation of
 asyncio.timeout for documentation of python 3.4, 3.5, 3.6
In-Reply-To: <1453935768.98.0.383268297204.issue26224@psf.upfronthosting.co.za>
Message-ID: <1475105078.06.0.265446215949.issue26224@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch. asyncio.timeout() has been removed in 73a28ad66bd9.

----------
nosy: +berker.peksag
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed Sep 28 19:24:46 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 23:24:46 +0000
Subject: [docs] [issue26224] Add "version added" for documentation of
 asyncio.timeout for documentation of python 3.4, 3.5, 3.6
In-Reply-To: <1453935768.98.0.383268297204.issue26224@psf.upfronthosting.co.za>
Message-ID: <1475105086.89.0.0940919989443.issue26224@psf.upfronthosting.co.za>


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


----------
type:  -> behavior

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

From report at bugs.python.org  Wed Sep 28 19:30:55 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 Sep 2016 23:30:55 +0000
Subject: [docs] [issue26550] documentation minor issue : "Step back: WSGI"
 section from "HOWTO Use Python in the web"
In-Reply-To: <1457847869.95.0.52045610793.issue26550@psf.upfronthosting.co.za>
Message-ID: <20160928233051.85654.62336.78BBC64E@psf.io>


Roundup Robot added the comment:

New changeset 522506fcff88 by Berker Peksag in branch '2.7':
Issue #26550: Fix typo in webservers HOWTO
https://hg.python.org/cpython/rev/522506fcff88

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

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

From report at bugs.python.org  Wed Sep 28 19:33:09 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 28 Sep 2016 23:33:09 +0000
Subject: [docs] [issue26550] documentation minor issue : "Step back: WSGI"
 section from "HOWTO Use Python in the web"
In-Reply-To: <1457847869.95.0.52045610793.issue26550@psf.upfronthosting.co.za>
Message-ID: <1475105589.59.0.968791857558.issue26550@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks, Alejandro. Doc/howto/webservers.rst has been removed in Python 3  so I just fixed 2.7.

----------
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type: enhancement -> 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/issue26550>
_______________________________________

From zachary.ware+pydocs at gmail.com  Thu Sep 29 00:28:52 2016
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 28 Sep 2016 23:28:52 -0500
Subject: [docs] A little bug
In-Reply-To: <f441c83.b0f.1576e8e220a.Coremail.kxw34567@163.com>
References: <f441c83.b0f.1576e8e220a.Coremail.kxw34567@163.com>
Message-ID: <CAKJDb-NXi_MPCAEoxtYYxpxmXWte=nR+3LcoYr+zMZ0uio241Q@mail.gmail.com>

On Tue, Sep 27, 2016 at 9:09 PM, ???? <kxw34567 at 163.com> wrote:
> There is a wrong blank in fifth paragraph of this page.
>
> https://docs.python.org/3.6/tutorial/appetite.html

Hello, and thanks for the report!  Unfortunately, I don't see the
issue you're referring to; can you be more specific?

Thanks,
-- 
Zach

From zachary.ware+pydocs at gmail.com  Thu Sep 29 00:36:17 2016
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 28 Sep 2016 23:36:17 -0500
Subject: [docs] https://docs.python.org/2/library/copy.html apparent
 error
In-Reply-To: <CAHKRt3o+2K+drq+SwhN35aFKSN0L-9MQLrH+4nSytEPiGLd6+w@mail.gmail.com>
References: <CAHKRt3o+2K+drq+SwhN35aFKSN0L-9MQLrH+4nSytEPiGLd6+w@mail.gmail.com>
Message-ID: <CAKJDb-Nzke87Hc_eJBBaoOmYi6wCTBb7gOo+6ME4GRQPtkwAGA@mail.gmail.com>

Hi Andrew,

On Tue, Sep 27, 2016 at 9:13 PM, Andrew Jarcho <andrew.jarcho at gmail.com> wrote:
> Hi,
>
> I believe the following line in the above page of the Python 2.7.12
> documentation:
>
>>> Shallow copies of dictionaries can be made using dict.copy(), and of
>>> lists by assigning a slice of the entire list, for example, copied_list =
>>> original_list[:].
>
> should read:
>
>>> Deep copies of dictionaries...

Thanks for the report!  However, the line is accurate as written:
dict.copy() does indeed do a shallow copy:

   >>> l = []
   >>> d = dict(l=l)
   >>> d2 = d.copy()
   >>> l.append('Not a deep copy')
   >>> d2
   {'l': ['Not a deep copy']}

If you want a deep copy of a dict, you'll need to use the deepcopy() function.

Regards,
-- 
Zach

From report at bugs.python.org  Thu Sep 29 20:17:26 2016
From: report at bugs.python.org (Viorel Tabara)
Date: Fri, 30 Sep 2016 00:17:26 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
Message-ID: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>


New submission from Viorel Tabara:

At https://docs.python.org/3.5/tutorial/errors.html#defining-clean-up-actions 
when I'm running the "divide('2', '1')" example I get:

  File "<stdin>", line 1, in <module>

instead of the documentation output of:

   File "<stdin>", line 1, in ? 

The same message is included with the 2.7 tutorial.

To wit:

   $ python3
   Python 3.5.2 (default, Sep 14 2016, 11:28:32)
   [GCC 6.2.1 20160901 (Red Hat 6.2.1-1)] on linux
   Type "help", "copyright", "credits" or "license" for more information.
   >>> def divide(x, y):
   ...     try:
   ...             result = x / y
   ...     except ZeroDivisionError:
   ...             print('division by zero!')
   ...     else:
   ...             print('result is', result)
   ...     finally:
   ...             print('executing finally clause')
   ...
   >>> divide(2, 1)
   result is 2.0
   executing finally clause
   >>> divide(2, 0)
   division by zero!
   executing finally clause
   >>> divide('2', '1')
   executing finally clause
   Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "<stdin>", line 3, in divide
   TypeError: unsupported operand type(s) for /: 'str' and 'str'


   $ python2
   Python 2.7.12 (default, Sep  2 2016, 15:40:50)
   [GCC 6.2.1 20160901 (Red Hat 6.2.1-1)] on linux2
   Type "help", "copyright", "credits" or "license" for more information.
   >>> def divide(x, y):
   ...     result = x / y
   KeyboardInterrupt
   >>> def divide(x, y):
   ...     try:
   ...             result = x / y
   ...     except ZeroDivisionError:
   ...             print('division by zero!')
   ...     else:
   ...             print('result is', result)
   ...     finally:
   ...             print('executing finally clause')
   ...
   >>> divide(2, 1)
   ('result is', 2)
   executing finally clause
   >>> divide(2, 0)
   division by zero!
   executing finally clause
   >>> divide('2', '1')
   executing finally clause
   Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "<stdin>", line 3, in divide
   TypeError: unsupported operand type(s) for /: 'str' and 'str'
  

Nice tutorial by the way ;) Thanks!

----------
assignee: docs at python
components: Documentation
messages: 277731
nosy: docs at python, viorel
priority: normal
severity: normal
status: open
title: incorrect "in ?" output in 'divide' example at "Defining Clean-up Actions" in tutorial
type: behavior
versions: Python 2.7, Python 3.5

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

From report at bugs.python.org  Thu Sep 29 20:24:41 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 30 Sep 2016 00:24:41 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
In-Reply-To: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>
Message-ID: <1475195081.7.0.514346061686.issue28315@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
nosy: +Mariatta

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

From report at bugs.python.org  Thu Sep 29 20:35:42 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 30 Sep 2016 00:35:42 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
In-Reply-To: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>
Message-ID: <1475195742.76.0.912756749563.issue28315@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks for the report. I agree, it should be <module> instead of ?

I'll work on a patch for this :)

----------

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

From report at bugs.python.org  Thu Sep 29 22:55:12 2016
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 30 Sep 2016 02:55:12 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
In-Reply-To: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>
Message-ID: <1475204112.32.0.675173015628.issue28315@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Updated the documentation to use <module> instead of ?

I also went through other examples in the page and fixed those too.

----------
keywords: +patch
Added file: http://bugs.python.org/file44885/issue28315.patch

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

From report at bugs.python.org  Fri Sep 30 14:10:09 2016
From: report at bugs.python.org (Vladimir Rutsky)
Date: Fri, 30 Sep 2016 18:10:09 +0000
Subject: [docs] [issue28319] typo in lzma module documentation
Message-ID: <1475259009.88.0.349229961864.issue28319@psf.upfronthosting.co.za>


New submission from Vladimir Rutsky:

"Specifying custom filter chains" section contains:

> It only supports a single The delta filter supports only one option, dist.

Probably should be just:

> The delta filter supports only one option, dist.

----------
assignee: docs at python
components: Documentation
messages: 277765
nosy: docs at python, vrutsky
priority: normal
severity: normal
status: open
title: typo in lzma module documentation
versions: Python 3.5, Python 3.7

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

From report at bugs.python.org  Fri Sep 30 15:07:08 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Sep 2016 19:07:08 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
In-Reply-To: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>
Message-ID: <1475262428.8.0.957113566526.issue28315@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy
stage:  -> commit review
versions: +Python 3.6, Python 3.7

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

From report at bugs.python.org  Fri Sep 30 15:51:30 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Sep 2016 19:51:30 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
In-Reply-To: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>
Message-ID: <1475265089.96.0.607146621934.issue28315@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Pushed to all 4 versions in ce57a74b5223, 1bead1f0260f, c729a62d4ec5, and 89cc2a6b64aa, but I gave issue # as 28815 instead of 28315.  Thanks for the clean patch for 3.5.  It mostly worked for 2.7, which also had an additional item not in 3.5.

The only other file in /Doc with 'in ?' is Doc/includes/test.py, which is mostly a doctest docstring.  The test obviously have not been run for years and the directory puzzles me, so I left it alone.

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

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

From report at bugs.python.org  Fri Sep 30 18:17:52 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 30 Sep 2016 22:17:52 +0000
Subject: [docs] [issue28319] typo in lzma module documentation
In-Reply-To: <1475259009.88.0.349229961864.issue28319@psf.upfronthosting.co.za>
Message-ID: <20160930221749.17589.61018.B7097805@psf.io>


Roundup Robot added the comment:

New changeset 258436eecb51 by Berker Peksag in branch '3.5':
Issue #28319: Fix typo in lzma.rst
https://hg.python.org/cpython/rev/258436eecb51

New changeset a1e7c9d249ed by Berker Peksag in branch '3.6':
Issue #28319: Merge from 3.5
https://hg.python.org/cpython/rev/a1e7c9d249ed

New changeset 40bcf4a8b57d by Berker Peksag in branch 'default':
Issue #28319: Merge from 3.6
https://hg.python.org/cpython/rev/40bcf4a8b57d

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

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

From report at bugs.python.org  Fri Sep 30 18:18:25 2016
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 30 Sep 2016 22:18:25 +0000
Subject: [docs] [issue28319] typo in lzma module documentation
In-Reply-To: <1475259009.88.0.349229961864.issue28319@psf.upfronthosting.co.za>
Message-ID: <1475273905.27.0.482422962594.issue28319@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.6

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

From report at bugs.python.org  Fri Sep 30 18:18:31 2016
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 30 Sep 2016 22:18:31 +0000
Subject: [docs] [issue28319] typo in lzma module documentation
In-Reply-To: <1475259009.88.0.349229961864.issue28319@psf.upfronthosting.co.za>
Message-ID: <1475273911.04.0.117910214706.issue28319@psf.upfronthosting.co.za>


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


----------
type:  -> behavior

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

From report at bugs.python.org  Fri Sep 30 20:02:51 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 01 Oct 2016 00:02:51 +0000
Subject: [docs] [issue10415] readline.insert_text documentation incomplete
In-Reply-To: <1289718734.94.0.0887962692453.issue10415@psf.upfronthosting.co.za>
Message-ID: <1475280171.44.0.964286482349.issue10415@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I agree with Martin. Closing this as 'out of date' for now, but we can reopen if you could provide more information. Thanks!

----------
resolution:  -> out of date
stage: needs patch -> resolved
status: pending -> closed
type:  -> behavior

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