From report at bugs.python.org  Sun Jul  1 01:16:49 2018
From: report at bugs.python.org (Bumsik Kim)
Date: Sun, 01 Jul 2018 05:16:49 +0000
Subject: [docs] [issue33986] asyncio: Typo in documentation:
 BaseSubprocessTransport -> SubprocessTransport
In-Reply-To: <1530139574.74.0.56676864532.issue33986@psf.upfronthosting.co.za>
Message-ID: <1530422209.01.0.56676864532.issue33986@psf.upfronthosting.co.za>


Bumsik Kim <kbumsik at gmail.com> added the comment:

As a note, BaseSubprocessTransport is used for implementation of SubprocessTransport. BaseSubprocessTransport is not exposed outside of the module.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33986>
_______________________________________

From report at bugs.python.org  Sun Jul  1 03:03:26 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 01 Jul 2018 07:03:26 +0000
Subject: [docs] [issue30660] Lossless Optimization of PNG files
In-Reply-To: <1497395488.74.0.644428672228.issue30660@psf.upfronthosting.co.za>
Message-ID: <1530428606.14.0.902498594338.issue30660@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8 -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30660>
_______________________________________

From report at bugs.python.org  Sun Jul  1 04:03:12 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 01 Jul 2018 08:03:12 +0000
Subject: [docs] [issue34015] doc Add link to Descriptor HowTo Guide in Data
 Model
In-Reply-To: <1530408862.0.0.56676864532.issue34015@psf.upfronthosting.co.za>
Message-ID: <1530432192.94.0.56676864532.issue34015@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

I think "See also" is better than sidebar.
Many other sections in data-model chapter have it.

----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34015>
_______________________________________

From report at bugs.python.org  Sun Jul  1 07:53:34 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 01 Jul 2018 11:53:34 +0000
Subject: [docs] [issue34015] doc Add link to Descriptor HowTo Guide in Data
 Model
In-Reply-To: <1530408862.0.0.56676864532.issue34015@psf.upfronthosting.co.za>
Message-ID: <1530446014.32.0.56676864532.issue34015@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

ok :) I have just updated the PR following your comment.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34015>
_______________________________________

From report at bugs.python.org  Sun Jul  1 18:23:04 2018
From: report at bugs.python.org (Alan Huang)
Date: Sun, 01 Jul 2018 22:23:04 +0000
Subject: [docs] [issue33995] test_min_max_version in test_ssl.py fails when
 Python is built against LibreSSL;
 {min,max}imum_version behavior differs from OpenSSL
In-Reply-To: <1530250345.83.0.56676864532.issue33995@psf.upfronthosting.co.za>
Message-ID: <1530483784.69.0.902498594338.issue33995@psf.upfronthosting.co.za>


Change by Alan Huang <Alan.Huang at utdallas.edu>:


----------
components:  -Documentation
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33995>
_______________________________________

From report at bugs.python.org  Mon Jul  2 04:23:53 2018
From: report at bugs.python.org (Sergey Fedoseev)
Date: Mon, 02 Jul 2018 08:23:53 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
Message-ID: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>


New submission from Sergey Fedoseev <fedoseev.sergey at gmail.com>:

SQLite converters are documented to be sensitive to the case of type names, but they're not.

In [50]: import sqlite3
    ...: 
    ...: sqlite3.converters.clear()
    ...: sqlite3.register_converter('T', lambda x: 'UPPER')
    ...: sqlite3.register_converter('t', lambda x: 'lower')
    ...: 
    ...: con = sqlite3.connect(':memory:', detect_types=sqlite3.PARSE_DECLTYPES)
    ...: cur = con.cursor()
    ...: cur.execute('create table test(upper T, lower t)')
    ...: cur.execute('insert into test values (?, ?)', ('X', 'x'))
    ...: cur.execute('select * from test')
    ...: cur.fetchone()
    ...: 
Out[50]: ('lower', 'lower')

In [51]: sqlite3.converters
Out[51]: {'T': <function __main__.<lambda>>}

Original commit in pysqlite that makes converters case insensitive: https://github.com/ghaering/pysqlite/commit/1e8bd36be93b7d7425910642b72e4152c77b0dfd

----------
assignee: docs at python
components: Documentation
messages: 320855
nosy: docs at python, sir-sigurd
priority: normal
severity: normal
status: open
title: SQLite converters are documented to be sensitive to the case of type names, but they're not

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Mon Jul  2 04:47:08 2018
From: report at bugs.python.org (Sergey Fedoseev)
Date: Mon, 02 Jul 2018 08:47:08 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530521228.99.0.902498594338.issue34018@psf.upfronthosting.co.za>


Change by Sergey Fedoseev <fedoseev.sergey at gmail.com>:


----------
keywords: +patch
pull_requests: +7651
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Mon Jul  2 05:33:06 2018
From: report at bugs.python.org (Bumsik Kim)
Date: Mon, 02 Jul 2018 09:33:06 +0000
Subject: [docs] [issue33986] asyncio: Typo in documentation:
 BaseSubprocessTransport -> SubprocessTransport
In-Reply-To: <1530139574.74.0.56676864532.issue33986@psf.upfronthosting.co.za>
Message-ID: <1530523986.53.0.56676864532.issue33986@psf.upfronthosting.co.za>


Bumsik Kim <kbumsik at gmail.com> added the comment:

I also found that SubprocessTransport.close() does not reflect the changes done in #23347.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33986>
_______________________________________

From report at bugs.python.org  Mon Jul  2 06:22:01 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 02 Jul 2018 10:22:01 +0000
Subject: [docs] [issue33961] Inconsistency in exceptions for
 dataclasses.dataclass documentation
In-Reply-To: <1529963695.74.0.56676864532.issue33961@psf.upfronthosting.co.za>
Message-ID: <1530526921.35.0.56676864532.issue33961@psf.upfronthosting.co.za>


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


New changeset 24d74bd8377d38528566437e70fcd72229695ac7 by Eric V. Smith (Chris Cogdon) in branch '3.7':
bpo-33961: Adjusted dataclasses docs to correct exceptions raised. (GH-7917)
https://github.com/python/cpython/commit/24d74bd8377d38528566437e70fcd72229695ac7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33961>
_______________________________________

From report at bugs.python.org  Mon Jul  2 10:51:00 2018
From: report at bugs.python.org (Alan Huang)
Date: Mon, 02 Jul 2018 14:51:00 +0000
Subject: [docs] [issue33995] test_min_max_version in test_ssl.py fails when
 Python is built against LibreSSL;
 {min,max}imum_version behavior differs from OpenSSL
In-Reply-To: <1530250345.83.0.56676864532.issue33995@psf.upfronthosting.co.za>
Message-ID: <1530543060.29.0.902498594338.issue33995@psf.upfronthosting.co.za>


Change by Alan Huang <Alan.Huang at utdallas.edu>:


----------
keywords: +patch
pull_requests: +7658
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33995>
_______________________________________

From report at bugs.python.org  Mon Jul  2 11:10:31 2018
From: report at bugs.python.org (Alan Huang)
Date: Mon, 02 Jul 2018 15:10:31 +0000
Subject: [docs] [issue33995] test_min_max_version in test_ssl.py fails when
 Python is built against LibreSSL;
 {min,max}imum_version behavior differs from OpenSSL
In-Reply-To: <1530250345.83.0.56676864532.issue33995@psf.upfronthosting.co.za>
Message-ID: <1530544231.08.0.56676864532.issue33995@psf.upfronthosting.co.za>


Alan Huang <Alan.Huang at utdallas.edu> added the comment:

PR 8050 implements option 2a (use PY_PROTO_{MIN,MAX}IMUM_AVAILABLE).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33995>
_______________________________________

From report at bugs.python.org  Mon Jul  2 12:09:56 2018
From: report at bugs.python.org (ndevenish)
Date: Mon, 02 Jul 2018 16:09:56 +0000
Subject: [docs] [issue23850] Missing documentation for
 Py_TPFLAGS_HAVE_NEWBUFFER
In-Reply-To: <1427969373.72.0.801261679654.issue23850@psf.upfronthosting.co.za>
Message-ID: <1530547796.1.0.56676864532.issue23850@psf.upfronthosting.co.za>


ndevenish <ndevenish at gmail.com> added the comment:

I've just spent some time running around because of this. Are documentation contributions still being accepted for python 2.7 at all? Some of the buffer documentation seems to be confusing as to whether you use new or old API.

----------
nosy: +ndevenish

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23850>
_______________________________________

From report at bugs.python.org  Mon Jul  2 13:20:31 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 02 Jul 2018 17:20:31 +0000
Subject: [docs] [issue23850] Missing documentation for
 Py_TPFLAGS_HAVE_NEWBUFFER
In-Reply-To: <1427969373.72.0.801261679654.issue23850@psf.upfronthosting.co.za>
Message-ID: <1530552031.17.0.56676864532.issue23850@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Documentation fixes to 2.7 is still accepted. Please create a PR on GitHub.

----------
nosy: +Mariatta

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23850>
_______________________________________

From report at bugs.python.org  Mon Jul  2 15:56:31 2018
From: report at bugs.python.org (Larry Hastings)
Date: Mon, 02 Jul 2018 19:56:31 +0000
Subject: [docs] [issue31045] Add a language switch to the Python
 documentation
In-Reply-To: <1501078214.01.0.529111921671.issue31045@psf.upfronthosting.co.za>
Message-ID: <1530561391.02.0.902498594338.issue31045@psf.upfronthosting.co.za>


Larry Hastings <larry at hastings.org> added the comment:


New changeset 1b141b9553424971639bde281feb1d4e4e586dbe by larryhastings (Julien Palard) in branch '3.5':
Doc: Backport language switcher (bpo-33700, bpo-31045) (#8048)
https://github.com/python/cpython/commit/1b141b9553424971639bde281feb1d4e4e586dbe


----------
nosy: +larry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31045>
_______________________________________

From report at bugs.python.org  Mon Jul  2 19:26:09 2018
From: report at bugs.python.org (Jim DeLaHunt)
Date: Mon, 02 Jul 2018 23:26:09 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1530573969.58.0.56676864532.issue33649@psf.upfronthosting.co.za>


Jim DeLaHunt <from.python at jdlh.com> added the comment:

I'm a developer using Python in my application. I just spent the last couple of weeks learning about asyncio with the present documentation. I am very happy to see that work is underway for improved documentation. 

I would be glad to take on writing tasks or to review drafts, if there is a way to plug myself into that work.

I like the general structure. 

Some specific topics which would have helped me in my recent learning:

* As an application developer using an event loop as part of the application, how do I develop a Protocol specific to my app, and use with Streams?  An important part of this is being clear what the interface is between Transport and Protocol. This interface resides in both classes; Protocol calls Transport methods, and Transport calls Protocol methods.

* As an application developer using an event loop as part of the application, how do I develop a Transport specific to my app, and use it with Streams?  (In my case, I have two transports in mind: a file, containing data archived from a TCP network port, and an RS232 serial connection, carrying data that might otherwise be sent via a TCP network port. It seems to me that I should be able at run-time to select from any of those three Transports, and apply my app-specific Protocol when creating my connection.)

* As an application developer, how do I give a function which is not a coroutine to the event loop for scheduling and execution?  (I think the answer is loop.call_soon(), but the docs don't say "to run your function call loop.call_soon(myfunc...)", they say "call_soon(): Arrange for a callback to be called as soon as possible". Not the same thing. And, is a "callback" different "an arbitrary function"? Not clear.)

* As an application developer, how do I make an syncio-based streaming server and streaming client respond cleanly to interrupts, e.g. control-C in a command-line app?  (Existing docs hints at catching signals, but don't show how to combine those with exception handlers in the coroutine to shut down connections cleanly.)

* As a Transport developer, what interface must I provide between Transport and Protocol? What services does the EventLoop provide to help implement my Transport? As mentioned before, to me it looks like the Transport-Protocol interface resides in both classes; Protocol calls Transport methods, and Transport calls Protocol methods.  The EventLoop services useful to Transports are not gathered in a discussion of Transports. There is only an enumeration of the EventLoop methods, regardless of purpose.

Editorial checks I suggest making to the revision:

Rewrite to describe the behaviour in the doc, instead of delegating to a PEP. No more "this class is almost like the thing in PEP xyz, except for these differences". Describe the asyncio class, and steal text from PEP xyz as needed to do that.

Every section about a thing must start by saying what that thing is and what it is used for.  There are some big counterexamples in the current text. 

e.g. "19.5.1.2. Calls" <https://docs.python.org/3/library/asyncio-eventloop.html#calls> starts out with: "Most asyncio functions don?t accept keywords. If you want to pass keywords to your callback, use functools.partial()."  That does not describe what "calls" are, nor what they are used for. And, in this case, a better title might be, "Getting the event loop to call regular functions".

e.g. "19.5.1.4. Futures" <https://docs.python.org/3/library/asyncio-eventloop.html#futures> has no starting text. This is the first heading mentioning Futures when reading sequentially in the asyncio doc, so I interpreted it as a place to learn about Futures. It is not. This section would be better titles "Eventloop methods for Futures". The proposed "Low-level APIs" section might solve this problem by explaining the nature and purpose of Futures before mentioning the EventLoop factory for Futures objects.

Consider separating the explanation of the nature and purpose of a thing from the reference to the methods of the thing. The proposed structure talks about "High-Level APIs" and "Low-Level APIs", but not "Architecture" and "API Reference". I would suggest injecting an "Architecture" section which can give the nature and purpose of each of the public classes in Asyncio, without enumerating their methods. Then the sections labelled "High-Level APIs" and "Low-Level APIs" can be the API reference.

I hope these suggestions are helpful. I'll be monitoring this issue to see how I can help.

----------
nosy: +JDLH

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33649>
_______________________________________

From report at bugs.python.org  Tue Jul  3 07:49:45 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 11:49:45 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530618585.32.0.56676864532.issue34018@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

It's worth noting that the referenced commit where this change was made is from 2006...

----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 07:59:34 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 11:59:34 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530619174.74.0.56676864532.issue34018@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 831c29721dcb1b768c6315a4b8a4059c4c97ee8b by Tal Einat (Sergey Fedoseev) in branch 'master':
bpo-34018: Doc'd that type names of SQLite converters are case-insensitive. (GH-8042)
https://github.com/python/cpython/commit/831c29721dcb1b768c6315a4b8a4059c4c97ee8b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:00:44 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 03 Jul 2018 12:00:44 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530619244.28.0.902498594338.issue34018@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7674

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:01:46 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 03 Jul 2018 12:01:46 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530619306.0.0.902498594338.issue34018@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7675

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:02:10 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 12:02:10 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530619330.34.0.56676864532.issue34018@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

I tested and indeed this is case-insensitive even on 2.7.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:02:42 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 03 Jul 2018 12:02:42 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530619362.53.0.902498594338.issue34018@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7676

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:37:19 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 12:37:19 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530621439.22.0.56676864532.issue34018@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 6699386231d326c50439b9e1df752e1aed7ca6b4 by Tal Einat (Miss Islington (bot)) in branch '3.7':
bpo-34018: Doc'd that type names of SQLite converters are case-insensitive. (GH-8042) (GH-8065)
https://github.com/python/cpython/commit/6699386231d326c50439b9e1df752e1aed7ca6b4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:37:29 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 12:37:29 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530621449.24.0.56676864532.issue34018@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset f55a818954212e8e6c97e3d66cf1478120a3220f by Tal Einat (Miss Islington (bot)) in branch '3.6':
bpo-34018: Doc'd that type names of SQLite converters are case-insensitive. (GH-8042) (GH-8067)
https://github.com/python/cpython/commit/f55a818954212e8e6c97e3d66cf1478120a3220f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:37:38 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 12:37:38 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530621458.52.0.56676864532.issue34018@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 292ce153fcc2d991164d19ad3f3deb86157898d5 by Tal Einat (Miss Islington (bot)) in branch '2.7':
bpo-34018: Doc'd that type names of SQLite converters are case-insensitive. (GH-8042) (GH-8066)
https://github.com/python/cpython/commit/292ce153fcc2d991164d19ad3f3deb86157898d5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 08:38:12 2018
From: report at bugs.python.org (Tal Einat)
Date: Tue, 03 Jul 2018 12:38:12 +0000
Subject: [docs] [issue34018] SQLite converters are documented to be
 sensitive to the case of type names, but they're not
In-Reply-To: <1530519833.89.0.56676864532.issue34018@psf.upfronthosting.co.za>
Message-ID: <1530621492.01.0.902498594338.issue34018@psf.upfronthosting.co.za>


Change by Tal Einat <taleinat at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34018>
_______________________________________

From report at bugs.python.org  Tue Jul  3 11:15:22 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 03 Jul 2018 15:15:22 +0000
Subject: [docs] [issue34015] doc Add link to Descriptor HowTo Guide in Data
 Model
In-Reply-To: <1530408862.0.0.56676864532.issue34015@psf.upfronthosting.co.za>
Message-ID: <1530630922.83.0.56676864532.issue34015@psf.upfronthosting.co.za>


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

I don't want to do this.  The docs are the authoritative source and the how-to is a secondary source that is primarily about how particular descriptors are implemented.

----------
nosy: +rhettinger
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34015>
_______________________________________

From report at bugs.python.org  Wed Jul  4 14:42:08 2018
From: report at bugs.python.org (Alexander Belopolsky)
Date: Wed, 04 Jul 2018 18:42:08 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1530729728.63.0.56676864532.issue30516@psf.upfronthosting.co.za>


Alexander Belopolsky <alexander.belopolsky at gmail.com> added the comment:


New changeset 5b6e49a1393b3e2313471696e3568e26296137b4 by Alexander Belopolsky (Farhaan Bukhsh) in branch 'master':
bpo-30516: Fix documentation issue with -timedelta in datetime (GH-7348)
https://github.com/python/cpython/commit/5b6e49a1393b3e2313471696e3568e26296137b4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30516>
_______________________________________

From report at bugs.python.org  Wed Jul  4 14:43:23 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 04 Jul 2018 18:43:23 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1530729803.62.0.902498594338.issue30516@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7693

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30516>
_______________________________________

From report at bugs.python.org  Wed Jul  4 14:44:14 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 04 Jul 2018 18:44:14 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1530729854.22.0.902498594338.issue30516@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7694

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30516>
_______________________________________

From report at bugs.python.org  Wed Jul  4 19:04:06 2018
From: report at bugs.python.org (Alexander Belopolsky)
Date: Wed, 04 Jul 2018 23:04:06 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1530745446.19.0.56676864532.issue30516@psf.upfronthosting.co.za>


Alexander Belopolsky <alexander.belopolsky at gmail.com> added the comment:


New changeset 55f39bdabc91b387c18451c78ee077e6d05d6cfe by Alexander Belopolsky (Miss Islington (bot)) in branch '3.6':
bpo-30516: Fix documentation issue with -timedelta in datetime (GH-7348) (GH-8092)
https://github.com/python/cpython/commit/55f39bdabc91b387c18451c78ee077e6d05d6cfe


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30516>
_______________________________________

From report at bugs.python.org  Wed Jul  4 19:04:27 2018
From: report at bugs.python.org (Alexander Belopolsky)
Date: Wed, 04 Jul 2018 23:04:27 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1530745467.07.0.56676864532.issue30516@psf.upfronthosting.co.za>


Alexander Belopolsky <alexander.belopolsky at gmail.com> added the comment:


New changeset a8bb18bbb9c286cfac5a0b8c8679c440e5c49305 by Alexander Belopolsky (Miss Islington (bot)) in branch '3.7':
bpo-30516: Fix documentation issue with -timedelta in datetime (GH-7348) (GH-8093)
https://github.com/python/cpython/commit/a8bb18bbb9c286cfac5a0b8c8679c440e5c49305


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30516>
_______________________________________

From report at bugs.python.org  Wed Jul  4 19:05:50 2018
From: report at bugs.python.org (Alexander Belopolsky)
Date: Wed, 04 Jul 2018 23:05:50 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1530745550.68.0.902498594338.issue30516@psf.upfronthosting.co.za>


Change by Alexander Belopolsky <alexander.belopolsky at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30516>
_______________________________________

From report at bugs.python.org  Thu Jul  5 04:10:28 2018
From: report at bugs.python.org (Windson Yang)
Date: Thu, 05 Jul 2018 08:10:28 +0000
Subject: [docs] [issue34049] abs() method accept argument that implement
 __abs__()
In-Reply-To: <1530773071.47.0.56676864532.issue34049@psf.upfronthosting.co.za>
Message-ID: <1530778228.41.0.902498594338.issue34049@psf.upfronthosting.co.za>


Change by Windson Yang <wiwindson at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34049>
_______________________________________

From report at bugs.python.org  Thu Jul  5 04:17:41 2018
From: report at bugs.python.org (Roland Weber)
Date: Thu, 05 Jul 2018 08:17:41 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
Message-ID: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>


New submission from Roland Weber <rolweber at de.ibm.com>:

The docs for SSLContext.set_ciphers [1] in Python 3 and ssl.wrap_socket [2] in Python 2 contain a link for "OpenSSL cipher list format", which points to an empty wiki page at https://wiki.openssl.org/index.php/Manual:Ciphers(1)#CIPHER_LIST_FORMAT

The OpenSSL cipher list format is currently documented here instead:
https://www.openssl.org/docs/manmaster/man1/ciphers.html

[1] https://docs.python.org/3/library/ssl.html#ssl.SSLContext.set_ciphers
[2] https://docs.python.org/2/library/ssl.html#ssl.wrap_socket

----------
assignee: docs at python
components: Documentation
messages: 321085
nosy: docs at python, rolweber
priority: normal
severity: normal
status: open
title: Broken links to "OpenSSL cipher list format" in documentation

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Thu Jul  5 04:38:35 2018
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 05 Jul 2018 08:38:35 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1530779915.06.0.56676864532.issue34050@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:

Thanks for your report. Do you want to work on a patch, too?

----------
keywords: +easy
nosy: +christian.heimes
stage:  -> needs patch
versions: +Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Thu Jul  5 04:45:49 2018
From: report at bugs.python.org (Windson Yang)
Date: Thu, 05 Jul 2018 08:45:49 +0000
Subject: [docs] [issue34051] Update multiprocessing example
Message-ID: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>


New submission from Windson Yang <wiwindson at gmail.com>:

The docs at https://docs.python.org/3.8/library/multiprocessing.html#synchronization-between-processes give an example:

from multiprocessing import Process, Lock

def f(l, i):
    l.acquire()
    try:
        print('hello world', i)
    finally:
        l.release()

if __name__ == '__main__':
    lock = Lock()

    for num in range(10):
        Process(target=f, args=(lock, num)).start()

and point out "For instance one can use a lock to ensure that only one process prints to standard output at a time...". I'm not sure this is a good enough example for the reader. The reader can't tell the difference between the function with l.acquire() or not, The output just shows in the terminal at the same time. So I think a better idea just add time.sleep(0.1) before print('hello world', i) like this:

    l.acquire()
    try:
        # do something here
        # time.sleep(0.1)
        print('hello world', i)

I can provide a pr if you guys like this idea.

----------
assignee: docs at python
components: Documentation
messages: 321088
nosy: Windson Yang, docs at python
priority: normal
severity: normal
status: open
title: Update multiprocessing example
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Thu Jul  5 05:18:28 2018
From: report at bugs.python.org (Roland Weber)
Date: Thu, 05 Jul 2018 09:18:28 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1530782308.62.0.56676864532.issue34050@psf.upfronthosting.co.za>


Roland Weber <rolweber at de.ibm.com> added the comment:

I'm afraid I don't have the time to work on a patch.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Thu Jul  5 11:41:41 2018
From: report at bugs.python.org (Paul Ganssle)
Date: Thu, 05 Jul 2018 15:41:41 +0000
Subject: [docs] [issue13305] datetime.strftime("%Y") not consistent for
 years < 1000
In-Reply-To: <1320091957.61.0.759691422668.issue13305@psf.upfronthosting.co.za>
Message-ID: <1530805301.97.0.902498594338.issue13305@psf.upfronthosting.co.za>


Change by Paul Ganssle <p.ganssle at gmail.com>:


----------
nosy: +p-ganssle

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13305>
_______________________________________

From report at bugs.python.org  Thu Jul  5 11:42:37 2018
From: report at bugs.python.org (Paul Ganssle)
Date: Thu, 05 Jul 2018 15:42:37 +0000
Subject: [docs] [issue9305] Don't use east/west of UTC in date/time
 documentation
In-Reply-To: <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za>
Message-ID: <1530805357.31.0.902498594338.issue9305@psf.upfronthosting.co.za>


Change by Paul Ganssle <p.ganssle at gmail.com>:


----------
nosy: +p-ganssle

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue9305>
_______________________________________

From report at bugs.python.org  Thu Jul  5 12:00:32 2018
From: report at bugs.python.org (Paul Ganssle)
Date: Thu, 05 Jul 2018 16:00:32 +0000
Subject: [docs] [issue27741] datetime.datetime.strptime functionality
 description incorrect
In-Reply-To: <1470941311.19.0.0562450492824.issue27741@psf.upfronthosting.co.za>
Message-ID: <1530806432.51.0.902498594338.issue27741@psf.upfronthosting.co.za>


Change by Paul Ganssle <p.ganssle at gmail.com>:


----------
nosy: +p-ganssle

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27741>
_______________________________________

From report at bugs.python.org  Thu Jul  5 19:10:25 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 05 Jul 2018 23:10:25 +0000
Subject: [docs] [issue34049] abs() method accept argument that implement
 __abs__()
In-Reply-To: <1530773071.47.0.56676864532.issue34049@psf.upfronthosting.co.za>
Message-ID: <1530832225.61.0.56676864532.issue34049@psf.upfronthosting.co.za>


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

Thanks

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34049>
_______________________________________

From report at bugs.python.org  Thu Jul  5 19:12:37 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 05 Jul 2018 23:12:37 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1530832357.63.0.902498594338.issue34051@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Thu Jul  5 22:30:50 2018
From: report at bugs.python.org (Windson Yang)
Date: Fri, 06 Jul 2018 02:30:50 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1530844250.6.0.902498594338.issue34051@psf.upfronthosting.co.za>


Change by Windson Yang <wiwindson at gmail.com>:


----------
nosy: +zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Fri Jul  6 12:51:48 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 06 Jul 2018 16:51:48 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
Message-ID: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>


New submission from Berker Peksag <berker.peksag at gmail.com>:

Most of the exceptions in sqlite3 module were documented in issue 6057 (https://github.com/python/cpython/commit/ed789f9cf9586d94e85115bb516a2ab6b9a2f668)

Unfortunately, I noticed that I missed NotSupportedError while reviewing PR 8086. I think it should be documented in the Exceptions section as well:

    https://docs.python.org/3.8/library/sqlite3.html#exceptions

We can adapt the text in PEP 249:

    https://www.python.org/dev/peps/pep-0249/#notsupportederror

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 321184
nosy: berker.peksag, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Document sqlite3.NotSupportedError exception
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Fri Jul  6 14:40:54 2018
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 06 Jul 2018 18:40:54 +0000
Subject: [docs] [issue33922] [Windows] Document the launcher's -64 suffix
In-Reply-To: <1529538222.45.0.56676864532.issue33922@psf.upfronthosting.co.za>
Message-ID: <1530902454.51.0.902498594338.issue33922@psf.upfronthosting.co.za>


Change by Eryk Sun <eryksun at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
dependencies: +Allow windows launcher to specify bit lengths with & without minor version
nosy: +docs at python
resolution: duplicate -> 
stage: resolved -> patch review
status: closed -> open
superseder: Allow windows launcher to specify bit lengths with & without minor version -> 
title: Enforce 64bit Python by Launcher -> [Windows] Document the launcher's -64 suffix
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33922>
_______________________________________

From report at bugs.python.org  Fri Jul  6 17:42:25 2018
From: report at bugs.python.org (Jim Jewett)
Date: Fri, 06 Jul 2018 21:42:25 +0000
Subject: [docs] [issue34063] binhex REASONABLY_LARGE = 32768 so what is
 128000
Message-ID: <1530913345.39.0.56676864532.issue34063@psf.upfronthosting.co.za>


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

binhex defines a module-wide constant of 

REASONABLY_LARGE = 32768  # Minimal amount we pass the rle-coder

Later on, in 5 locations it does either ifp.read(128000) or ifp.read_rsrc(128000)

It isn't clear why a different constant is used, let alone why a literal is used instead of something like REASONABLY_LARGE.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 321193
nosy: Jim.Jewett, docs at python
priority: low
severity: normal
stage: needs patch
status: open
title: binhex REASONABLY_LARGE = 32768 so what is 128000
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34063>
_______________________________________

From report at bugs.python.org  Sat Jul  7 04:34:50 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 07 Jul 2018 08:34:50 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1530952490.64.0.56676864532.issue34051@psf.upfronthosting.co.za>


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

The example feels a bit artificial indeed, but I don't think adding a sleep() call would make it realistic.  Why would you protect sleep() with a lock?

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Sat Jul  7 07:32:03 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 07 Jul 2018 11:32:03 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
Message-ID: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

https://docs.python.org/3.8/library/logging.html#logging.basicConfig

Although I wrote the 'force' as '``force`` ' 
but it is printed as a highlighted font.

The 'force' section should be printed as italic font not highlight font.

Maybe there is something mistake I didn't catch.

----------
assignee: docs at python
components: Documentation
messages: 321214
nosy: corona10, docs at python
priority: normal
severity: normal
status: open
title: 'force' should be printed as italic font not highlight font.
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 07:34:10 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 07 Jul 2018 11:34:10 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530963250.0.0.56676864532.issue34065@psf.upfronthosting.co.za>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Oh it should *force* not ``force``

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 07:41:29 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 07 Jul 2018 11:41:29 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530963689.37.0.902498594338.issue34065@psf.upfronthosting.co.za>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +7719
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 08:36:43 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 12:36:43 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530967003.94.0.56676864532.issue34065@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 2800dcf656229c2ca4c90b4ddbace0717c41bb9e by Serhiy Storchaka (Dong-hee Na) in branch 'master':
bpo-34065: Improve the markup of logging.basicConfig() arguments (GH-8153)
https://github.com/python/cpython/commit/2800dcf656229c2ca4c90b4ddbace0717c41bb9e


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 09:56:55 2018
From: report at bugs.python.org (Julien Palard)
Date: Sat, 07 Jul 2018 13:56:55 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1530971815.05.0.902498594338.issue32523@psf.upfronthosting.co.za>


Change by Julien Palard <julien+python at palard.fr>:


----------
keywords: +patch
pull_requests: +7720
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32523>
_______________________________________

From report at bugs.python.org  Sat Jul  7 10:04:20 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 07 Jul 2018 14:04:20 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530972260.86.0.902498594338.issue34065@psf.upfronthosting.co.za>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
pull_requests: +7721

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 10:07:14 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 07 Jul 2018 14:07:14 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530972434.97.0.902498594338.issue34065@psf.upfronthosting.co.za>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
pull_requests: +7722

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 11:43:37 2018
From: report at bugs.python.org (Windson Yang)
Date: Sat, 07 Jul 2018 15:43:37 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1530978217.6.0.56676864532.issue34051@psf.upfronthosting.co.za>


Windson Yang <wiwindson at gmail.com> added the comment:

Hello, @Antoine Pitrou. Maybe there is another way to let the reader know "only one process prints to standard output at a time" instead of sleep() function?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Sat Jul  7 11:47:44 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 07 Jul 2018 15:47:44 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1530978464.01.0.56676864532.issue34051@psf.upfronthosting.co.za>


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

To be frank, I don't think that matters much.  The user should understand what a lock is already, if they want to make use of multiprocessing fruitfully.  The example showcases how to create a lock and how to pass it to child processes (by giving it as a function parameter).  Printing to standard output is not the important thing here.

However if you want to improve this example, you could replace the acquire/release pair with a "with" statement.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Sat Jul  7 12:11:25 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 16:11:25 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530979885.17.0.56676864532.issue34065@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset cad4a27585e4255295dcc06e80f1140cd11bdfd4 by Serhiy Storchaka (Dong-hee Na) in branch '3.6':
[3.6] bpo-34065: Improve the markup of logging.basicConfig() arguments (GH-8153). (GH-8155)
https://github.com/python/cpython/commit/cad4a27585e4255295dcc06e80f1140cd11bdfd4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 12:12:13 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 16:12:13 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530979933.86.0.56676864532.issue34065@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 75f2eb5eca38d22da62eb5814b9614792cfce13c by Serhiy Storchaka (Dong-hee Na) in branch '3.7':
[3.7] bpo-34065: Improve the markup of logging.basicConfig() arguments (GH-8153). (GH-8156)
https://github.com/python/cpython/commit/75f2eb5eca38d22da62eb5814b9614792cfce13c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 12:44:06 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 07 Jul 2018 16:44:06 +0000
Subject: [docs] [issue34065] 'force' should be printed as italic font not
 highlight font.
In-Reply-To: <1530963123.0.0.56676864532.issue34065@psf.upfronthosting.co.za>
Message-ID: <1530981846.95.0.902498594338.issue34065@psf.upfronthosting.co.za>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34065>
_______________________________________

From report at bugs.python.org  Sat Jul  7 14:10:15 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 07 Jul 2018 18:10:15 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1530987015.46.0.56676864532.issue32523@psf.upfronthosting.co.za>


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

Since 'News entry is one paragraph without subject line' is a change from older policy, I suggest posting a reminder to committers list and rechecking devguide.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32523>
_______________________________________

From report at bugs.python.org  Sat Jul  7 14:32:40 2018
From: report at bugs.python.org (Julien Palard)
Date: Sat, 07 Jul 2018 18:32:40 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1530988360.6.0.56676864532.issue32523@psf.upfronthosting.co.za>


Julien Palard <julien+python at palard.fr> added the comment:

terry: Make sense, I'll also try to add the reminder in blurb if I find an appropriate place and wording.

----------
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32523>
_______________________________________

From report at bugs.python.org  Sat Jul  7 15:08:23 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 19:08:23 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1530990503.78.0.902498594338.issue33888@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
nosy: +gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 15:35:20 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 19:35:20 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530992120.52.0.56676864532.issue33804@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What about other methods and other classes?

----------
nosy: +benjamin.peterson, serhiy.storchaka, stutzbach

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:05:16 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 07 Jul 2018 20:05:16 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530993916.92.0.56676864532.issue33804@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

I do see your point (not bloat BPO with a one line fix per each undocumented feature), but IMHO it's somewhat unrealistic to fix all issues of the same type in a single PR.

I opened this PR because I was reading this particular function and noticed that the "size" parameter is documented as required. If it was documented as optional, the default value is not documented either.

Perhaps we can compromise, and I can look at all the classes/functions in "io", and improve this PR? I cannot propose myself to do this to the whole Python documentation at once :/

Excuse me if I didn't interpret your comment right.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:17:19 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 20:17:19 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530994639.57.0.56676864532.issue33804@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset b6bb77c2b8e83ba6cb845c7b512ac564276e854f by Serhiy Storchaka (Andr?s Delfino) in branch 'master':
bpo-33804: Document that the argument for io.TextIOBase.read() is optional (GH-7510)
https://github.com/python/cpython/commit/b6bb77c2b8e83ba6cb845c7b512ac564276e854f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:18:39 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 20:18:39 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530994719.28.0.902498594338.issue33804@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7724

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:20:28 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 20:20:28 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530994828.11.0.902498594338.issue33804@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7725

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:23:12 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 20:23:12 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530994992.11.0.56676864532.issue33804@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I see. The real problem was that the argument for io.TextIOBase.read() was not documented as optional.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:24:49 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 20:24:49 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1530995089.19.0.56676864532.issue33702@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset caccca78e46bf3c3b24e09b3afb1c1b08c39990c by Serhiy Storchaka (Andr?s Delfino) in branch 'master':
bpo-33702: Add some missing links in production lists and do a little polish (GH-7259)
https://github.com/python/cpython/commit/caccca78e46bf3c3b24e09b3afb1c1b08c39990c


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:25:56 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 20:25:56 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1530995156.2.0.902498594338.issue33702@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7726

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:26:56 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 20:26:56 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1530995216.51.0.902498594338.issue33702@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7727

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:37:29 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 07 Jul 2018 20:37:29 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530995849.26.0.902498594338.issue33804@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
pull_requests: +7728

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:39:06 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 20:39:06 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530995946.25.0.56676864532.issue33804@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e5b47ea5859522f81599a82d49175f6fad263482 by Miss Islington (bot) in branch '3.7':
bpo-33804: Document that the argument for io.TextIOBase.read() is optional (GH-7510)
https://github.com/python/cpython/commit/e5b47ea5859522f81599a82d49175f6fad263482


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:45:10 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 20:45:10 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530996310.16.0.56676864532.issue33804@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 770937b6fd87af91390ac765f6a4c4767432cbc3 by Miss Islington (bot) in branch '3.6':
bpo-33804: Document that the argument for io.TextIOBase.read() is optional (GH-7510)
https://github.com/python/cpython/commit/770937b6fd87af91390ac765f6a4c4767432cbc3


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 16:52:42 2018
From: report at bugs.python.org (Marcin Niemira)
Date: Sat, 07 Jul 2018 20:52:42 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1530996762.57.0.902498594338.issue34061@psf.upfronthosting.co.za>


Change by Marcin Niemira <marcin at niemira.net>:


----------
keywords: +patch
pull_requests: +7729
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:09:11 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 21:09:11 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1530997751.76.0.56676864532.issue33702@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 80c188f3efca3ddb3d588b91938655e52ee65bda by Miss Islington (bot) in branch '3.7':
bpo-33702: Add some missing links in production lists and do a little polish (GH-7259)
https://github.com/python/cpython/commit/80c188f3efca3ddb3d588b91938655e52ee65bda


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:09:22 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 21:09:22 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1530997762.79.0.56676864532.issue33702@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 445f9edaa4efbf76ae0fe8e18707665ac16dd5a4 by Miss Islington (bot) in branch '3.6':
bpo-33702: Add some missing links in production lists and do a little polish (GH-7259)
https://github.com/python/cpython/commit/445f9edaa4efbf76ae0fe8e18707665ac16dd5a4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:10:20 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 21:10:20 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530997820.89.0.56676864532.issue33804@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset ad0fc8ddba0e2f6715dc14c74cb4dbd437b3777d by Serhiy Storchaka (Andr?s Delfino) in branch '2.7':
[2.7] bpo-33804: Document that the argument for io.TextIOBase.read() is optional (GH-7510). (GH-8171)
https://github.com/python/cpython/commit/ad0fc8ddba0e2f6715dc14c74cb4dbd437b3777d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:11:27 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 07 Jul 2018 21:11:27 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1530997887.13.0.902498594338.issue33804@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33804>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:25:21 2018
From: report at bugs.python.org (Marcin Niemira)
Date: Sat, 07 Jul 2018 21:25:21 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1530998721.64.0.902498594338.issue34050@psf.upfronthosting.co.za>


Change by Marcin Niemira <marcin at niemira.net>:


----------
keywords: +patch
pull_requests: +7730
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:36:25 2018
From: report at bugs.python.org (A.M. Kuchling)
Date: Sat, 07 Jul 2018 21:36:25 +0000
Subject: [docs] [issue28626] Tutorial: rearrange discussion of output
 formatting to encourage f-strings
In-Reply-To: <1478452855.22.0.932657206329.issue28626@psf.upfronthosting.co.za>
Message-ID: <1530999385.56.0.56676864532.issue28626@psf.upfronthosting.co.za>


A.M. Kuchling <amk at amk.ca> added the comment:


New changeset ced350b1952857a9b9c68ec7e2786358bcb61050 by Andrew Kuchling in branch 'master':
bpo-28626: rearrange discussion of output formatting to encourage f-strings (#6036)
https://github.com/python/cpython/commit/ced350b1952857a9b9c68ec7e2786358bcb61050


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28626>
_______________________________________

From report at bugs.python.org  Sat Jul  7 17:37:46 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 21:37:46 +0000
Subject: [docs] [issue28626] Tutorial: rearrange discussion of output
 formatting to encourage f-strings
In-Reply-To: <1478452855.22.0.932657206329.issue28626@psf.upfronthosting.co.za>
Message-ID: <1530999466.74.0.902498594338.issue28626@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7731

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28626>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:24:23 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 07 Jul 2018 22:24:23 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531002263.15.0.56676864532.issue34050@psf.upfronthosting.co.za>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset 9c5ba097485c8c643b670acd4026f4382bc92f4b by Benjamin Peterson (Marcin Niemira) in branch 'master':
closes bpo-34050: Fix link in SSL docs (GH-8173)
https://github.com/python/cpython/commit/9c5ba097485c8c643b670acd4026f4382bc92f4b


----------
nosy: +benjamin.peterson
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:25:30 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 22:25:30 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531002330.34.0.902498594338.issue34050@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7732

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:25:54 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 07 Jul 2018 22:25:54 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531002354.13.0.902498594338.issue34050@psf.upfronthosting.co.za>


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


----------
pull_requests: +7733

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:28:12 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 07 Jul 2018 22:28:12 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531002492.08.0.902498594338.issue34050@psf.upfronthosting.co.za>


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


----------
pull_requests: +7734

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:44:08 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 07 Jul 2018 22:44:08 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1531003448.31.0.902498594338.issue33702@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:44:21 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 07 Jul 2018 22:44:21 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1531003460.99.0.902498594338.issue33702@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33702>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:47:38 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 22:47:38 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531003657.97.0.56676864532.issue34050@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a912305512efd08cbaa15dc1488fb626c9fec067 by Miss Islington (bot) in branch '3.7':
closes bpo-34050: Fix link in SSL docs (GH-8173)
https://github.com/python/cpython/commit/a912305512efd08cbaa15dc1488fb626c9fec067


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 18:48:09 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 07 Jul 2018 22:48:09 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531003689.56.0.56676864532.issue34050@psf.upfronthosting.co.za>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset 3707dfaf45baf867f17bbbc78ccf2f0d13711dbd by Benjamin Peterson in branch '2.7':
[2.7] closes bpo-34050: Fix link in SSL docs (GH-8173). (GH-8179)
https://github.com/python/cpython/commit/3707dfaf45baf867f17bbbc78ccf2f0d13711dbd


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:03:39 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 07 Jul 2018 23:03:39 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531004619.51.0.56676864532.issue34050@psf.upfronthosting.co.za>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset becb5277670bdb37e8c8471a5a510466eaf9598a by Benjamin Peterson in branch '3.6':
[3.6] closes bpo-34050: Fix link in SSL docs (GH-8173) (GH-8178)
https://github.com/python/cpython/commit/becb5277670bdb37e8c8471a5a510466eaf9598a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:25:50 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 07 Jul 2018 23:25:50 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531005950.51.0.56676864532.issue33888@psf.upfronthosting.co.za>


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


New changeset 8d41278045ee4e8bf1cadb58a7db58d70ad55237 by Terry Jan Reedy (Andr?s Delfino) in branch 'master':
bpo-33888: Use CPython instead of Python in the FAQ (GH-7767)
https://github.com/python/cpython/commit/8d41278045ee4e8bf1cadb58a7db58d70ad55237


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:27:00 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 23:27:00 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531006020.91.0.902498594338.issue33888@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7735

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:28:01 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 23:28:01 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531006081.85.0.902498594338.issue33888@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7736

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:29:00 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 23:29:00 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531006140.76.0.902498594338.issue33888@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7737

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:33:00 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 23:33:00 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531006380.25.0.56676864532.issue33888@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3a98ddd136275ef944aa4387c964fc0c5adf6fab by Miss Islington (bot) in branch '2.7':
bpo-33888: Use CPython instead of Python in the FAQ (GH-7767)
https://github.com/python/cpython/commit/3a98ddd136275ef944aa4387c964fc0c5adf6fab


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:42:35 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 23:42:35 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531006955.79.0.56676864532.issue33888@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 21fe81c1fea1bca6b500550b5895e9ebcb3ebba6 by Miss Islington (bot) in branch '3.7':
bpo-33888: Use CPython instead of Python in the FAQ (GH-7767)
https://github.com/python/cpython/commit/21fe81c1fea1bca6b500550b5895e9ebcb3ebba6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 19:50:35 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 07 Jul 2018 23:50:35 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531007435.72.0.56676864532.issue33888@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset b7874c809cbead0eb07554b61efe7823238c8bd9 by Miss Islington (bot) in branch '3.6':
bpo-33888: Use CPython instead of Python in the FAQ (GH-7767)
https://github.com/python/cpython/commit/b7874c809cbead0eb07554b61efe7823238c8bd9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sat Jul  7 20:25:17 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 08 Jul 2018 00:25:17 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1531009516.62.0.56676864532.issue33888@psf.upfronthosting.co.za>


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

Merged with Guido's approval on the PR.  Thanks.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33888>
_______________________________________

From report at bugs.python.org  Sun Jul  8 00:14:52 2018
From: report at bugs.python.org (Windson Yang)
Date: Sun, 08 Jul 2018 04:14:52 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1531023292.31.0.56676864532.issue34051@psf.upfronthosting.co.za>


Windson Yang <wiwindson at gmail.com> added the comment:

Thank you, I think to use acquire() and release() may be better than with statement in this example. I will close this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Sun Jul  8 00:15:01 2018
From: report at bugs.python.org (Windson Yang)
Date: Sun, 08 Jul 2018 04:15:01 +0000
Subject: [docs] [issue34051] Update multiprocessing example
In-Reply-To: <1530780349.49.0.56676864532.issue34051@psf.upfronthosting.co.za>
Message-ID: <1531023301.88.0.902498594338.issue34051@psf.upfronthosting.co.za>


Change by Windson Yang <wiwindson at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34051>
_______________________________________

From report at bugs.python.org  Sun Jul  8 08:03:01 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 08 Jul 2018 12:03:01 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531051381.21.0.56676864532.issue34061@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset bc9aa813a34474e517af8999565ff6151559d42f by Berker Peksag (Marcin Niemira) in branch 'master':
bpo-34061: Document sqlite3.NotSupportedError (GH-8172)
https://github.com/python/cpython/commit/bc9aa813a34474e517af8999565ff6151559d42f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sun Jul  8 08:06:32 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 08 Jul 2018 12:06:32 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531051592.8.0.902498594338.issue34061@psf.upfronthosting.co.za>


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


----------
stage: patch review -> backport needed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sun Jul  8 08:42:14 2018
From: report at bugs.python.org (Marcin Niemira)
Date: Sun, 08 Jul 2018 12:42:14 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531053734.79.0.902498594338.issue34061@psf.upfronthosting.co.za>


Change by Marcin Niemira <marcin at niemira.net>:


----------
pull_requests: +7740
stage: backport needed -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sun Jul  8 08:52:40 2018
From: report at bugs.python.org (Marcin Niemira)
Date: Sun, 08 Jul 2018 12:52:40 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531054360.78.0.902498594338.issue34061@psf.upfronthosting.co.za>


Change by Marcin Niemira <marcin at niemira.net>:


----------
pull_requests: +7741

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sun Jul  8 09:58:55 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 08 Jul 2018 13:58:55 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531058335.21.0.56676864532.issue34061@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 404156534893461165bb5b99a42cabe261dddb78 by Berker Peksag (Marcin Niemira) in branch '3.6':
bpo-34061: Document sqlite3.NotSupportedError (GH-8172)
https://github.com/python/cpython/commit/404156534893461165bb5b99a42cabe261dddb78


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sun Jul  8 09:59:51 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 08 Jul 2018 13:59:51 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531058390.69.0.56676864532.issue34061@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 0b63759651b366ddb4c1c1dece12ef776053d5ee by Berker Peksag (Marcin Niemira) in branch '3.7':
bpo-34061: Document sqlite3.NotSupportedError (GH-8172)
https://github.com/python/cpython/commit/0b63759651b366ddb4c1c1dece12ef776053d5ee


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Sun Jul  8 10:01:41 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 08 Jul 2018 14:01:41 +0000
Subject: [docs] [issue34061] Document sqlite3.NotSupportedError exception
In-Reply-To: <1530895908.13.0.56676864532.issue34061@psf.upfronthosting.co.za>
Message-ID: <1531058501.92.0.56676864532.issue34061@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks, Marcin.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34061>
_______________________________________

From report at bugs.python.org  Mon Jul  9 09:52:51 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 09 Jul 2018 13:52:51 +0000
Subject: [docs] [issue28626] Tutorial: rearrange discussion of output
 formatting to encourage f-strings
In-Reply-To: <1478452855.22.0.932657206329.issue28626@psf.upfronthosting.co.za>
Message-ID: <1531144371.3.0.56676864532.issue28626@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 80a5f04592f7d732a541d5c35a1be1e9a6472ecb by Miss Islington (bot) in branch '3.7':
bpo-28626: rearrange discussion of output formatting to encourage f-strings (GH-6036)
https://github.com/python/cpython/commit/80a5f04592f7d732a541d5c35a1be1e9a6472ecb


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28626>
_______________________________________

From report at bugs.python.org  Mon Jul  9 11:57:57 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 09 Jul 2018 15:57:57 +0000
Subject: [docs] [issue34077] doc Be explicit about mock_open created mocks
 not supporting __iter__
Message-ID: <1531151877.58.0.56676864532.issue34077@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

I've been bitten by this one, and while the docs are clear in what the created mock objects support, I think something explicit about __iter__ will help.

----------
assignee: docs at python
components: Documentation
messages: 321327
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Be explicit about mock_open created mocks not supporting __iter__
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34077>
_______________________________________

From report at bugs.python.org  Mon Jul  9 12:05:28 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 09 Jul 2018 16:05:28 +0000
Subject: [docs] [issue34077] doc Be explicit about mock_open created mocks
 not supporting __iter__
In-Reply-To: <1531151877.58.0.56676864532.issue34077@psf.upfronthosting.co.za>
Message-ID: <1531152328.72.0.902498594338.issue34077@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7753
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34077>
_______________________________________

From report at bugs.python.org  Mon Jul  9 12:18:04 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 09 Jul 2018 16:18:04 +0000
Subject: [docs] [issue34077] doc Be explicit about mock_open created mocks
 not supporting __iter__
In-Reply-To: <1531151877.58.0.56676864532.issue34077@psf.upfronthosting.co.za>
Message-ID: <1531153084.73.0.56676864532.issue34077@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

-1. We can't document every non-existent feature in the stdlib documentation.

There is an already open issue for adding __iter__ support to mock_open(): Issue 21258

----------
nosy: +berker.peksag
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34077>
_______________________________________

From report at bugs.python.org  Mon Jul  9 12:33:31 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 09 Jul 2018 16:33:31 +0000
Subject: [docs] [issue34077] doc Be explicit about mock_open created mocks
 not supporting __iter__
In-Reply-To: <1531151877.58.0.56676864532.issue34077@psf.upfronthosting.co.za>
Message-ID: <1531154011.01.0.56676864532.issue34077@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

There is also bpo-32933.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34077>
_______________________________________

From report at bugs.python.org  Mon Jul  9 15:13:36 2018
From: report at bugs.python.org (Joe N)
Date: Mon, 09 Jul 2018 19:13:36 +0000
Subject: [docs] [issue34078] Broken CRL functionality in ssl.py
Message-ID: <1531163616.13.0.56676864532.issue34078@psf.upfronthosting.co.za>


New submission from Joe N <nettijoe at gmail.com>:

CRLs in ssl.py or at the documentation is broken. Specifically I think the documentation here is wrong: https://docs.python.org/3/library/ssl.html#ssl.SSLContext.load_verify_locations

Here is a stackoverflow post: https://stackoverflow.com/questions/51196492/how-to-use-crls-in-pyopenssl?noredirect=1#comment89407186_51196492 

I made a very user friendly test suite of files to show how it is broken. 

Run the code in here (follow readme instructions) to see the bug.
https://github.com/nettijoe96/bugInSSL

----------
assignee: christian.heimes
components: SSL
messages: 321343
nosy: Joe N, christian.heimes, docs at python
priority: normal
severity: normal
status: open
title: Broken CRL functionality in ssl.py
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34078>
_______________________________________

From report at bugs.python.org  Mon Jul  9 15:18:03 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 09 Jul 2018 19:18:03 +0000
Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page
In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za>
Message-ID: <1531163882.95.0.56676864532.issue24459@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 9863de0355caf23c44b708a5d68b603e135f7ae9 by Berker Peksag in branch 'master':
bpo-24459: Document missing env variables in python.man (GH-4142)
https://github.com/python/cpython/commit/9863de0355caf23c44b708a5d68b603e135f7ae9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24459>
_______________________________________

From report at bugs.python.org  Mon Jul  9 15:18:14 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 09 Jul 2018 19:18:14 +0000
Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page
In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za>
Message-ID: <1531163894.75.0.902498594338.issue24459@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7756

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24459>
_______________________________________

From report at bugs.python.org  Mon Jul  9 15:37:27 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 09 Jul 2018 19:37:27 +0000
Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page
In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za>
Message-ID: <1531165047.29.0.56676864532.issue24459@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 22fb674fa4c8343c84c25d93f23a1d6315d0f4f5 by Miss Islington (bot) in branch '3.7':
bpo-24459: Document missing env variables in python.man (GH-4142)
https://github.com/python/cpython/commit/22fb674fa4c8343c84c25d93f23a1d6315d0f4f5


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24459>
_______________________________________

From report at bugs.python.org  Mon Jul  9 15:38:34 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 09 Jul 2018 19:38:34 +0000
Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page
In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za>
Message-ID: <1531165114.7.0.56676864532.issue24459@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks, Joshua!

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24459>
_______________________________________

From report at bugs.python.org  Mon Jul  9 16:37:03 2018
From: report at bugs.python.org (Christian Heimes)
Date: Mon, 09 Jul 2018 20:37:03 +0000
Subject: [docs] [issue34078] Broken CRL functionality in ssl.py
In-Reply-To: <1531163616.13.0.56676864532.issue34078@psf.upfronthosting.co.za>
Message-ID: <1531168623.47.0.56676864532.issue34078@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:

Cert revocation check is working fine for me. I've attached a demo script that uses badssl.com:

$ curl -O http://crl3.digicert.com/ssca-sha2-g5.crl
$ openssl crl -in ssca-sha2-g5.crl -inform DER -out ssca-sha2-g5.pem.crl -outform PEM
$ python3.7 testcrl.py 
Traceback (most recent call last):
  File "testcrl.py", line 19, in <module>
    s.connect(('revoked.badssl.com', 443))
  File "/usr/lib64/python3.7/ssl.py", line 1141, in connect
    self._real_connect(addr, False)
  File "/usr/lib64/python3.7/ssl.py", line 1132, in _real_connect
    self.do_handshake()
  File "/usr/lib64/python3.7/ssl.py", line 1108, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate revoked (_ssl.c:1045)

openssl s_client:

$ cat /etc/pki/tls/cert.pem ssca-sha2-g5.pem.crl > combined.pem
$ openssl s_client -connect revoked.badssl.com:443 -servername revoked.badssl.com -CAfile combined.pem | grep Verify
    Verify return code: 0 (ok)
$ openssl s_client -connect revoked.badssl.com:443 -servername revoked.badssl.com -CAfile combined.pem -crl_check | grep Verify
    Verify return code: 23 (certificate revoked)

----------
Added file: https://bugs.python.org/file47679/testcrl.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34078>
_______________________________________

From report at bugs.python.org  Mon Jul  9 17:35:03 2018
From: report at bugs.python.org (Julien Palard)
Date: Mon, 09 Jul 2018 21:35:03 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1531172103.79.0.56676864532.issue32523@psf.upfronthosting.co.za>


Julien Palard <julien+python at palard.fr> added the comment:

Hi Ned, what do you think about https://github.com/python/cpython/pull/8154?

I feel this is a bit a huge change in NEWS entry writing policy which make them less readable (in text files). Is it really worth it to change the policy to single-paragraph only just for an HTML rendering issue?

Or should we silently join/trim those paragraphs only in blurb merge, maybe with an option like "--trim-paragraphs" while building the HTML documentations?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32523>
_______________________________________

From report at bugs.python.org  Tue Jul 10 04:32:01 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 10 Jul 2018 08:32:01 +0000
Subject: [docs] [issue34081] Sphinx duplicate label warning in docs
Message-ID: <1531211521.37.0.56676864532.issue34081@psf.upfronthosting.co.za>


New submission from Karthikeyan Singaravelan <tir.karthi at gmail.com>:

While running make docs sphinx generates a warning that there are duplicate labels named `_examples`. It seems it's present in `c-api/typeobj.rst` and `distutils/examples.rst` as below : 

?  Doc git:(master) rg '.. _examples:'
c-api/typeobj.rst
2324:.. _examples:

distutils/examples.rst
1:.. _examples:

# Warning

2018-07-10T07:30:36.8709047Z /opt/vsts/work/1/s/Doc/distutils/examples.rst:5: WARNING: duplicate label examples, other instance in /opt/vsts/work/1/s/Doc/c-api/typeobj.rst

Sample log : https://python.visualstudio.com/cpython/cpython%20Team/_build/results?buildId=16141&view=logs

There are no references to the label as far as I have checked and I suppose this is an easy fix to be done if someone wants to take it up. The effect is that in the page https://docs.python.org/3.8/c-api/typeobj.html the following text links to distutils/examples for the text "Examples" which should ideally link to https://docs.python.org/3.8/c-api/typeobj.html#examples

"In addition to the following quick reference, the Examples section provides at-a-glance insight into the meaning and use of PyTypeObject."

It will be also helpful if sphinx warnings are made as an error in CI so that these are caught there.

Thanks

----------
assignee: docs at python
components: Documentation
messages: 321368
nosy: docs at python, xtreak
priority: normal
severity: normal
status: open
title: Sphinx duplicate label warning in docs
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34081>
_______________________________________

From report at bugs.python.org  Tue Jul 10 06:17:05 2018
From: report at bugs.python.org (Stig Johan Berggren)
Date: Tue, 10 Jul 2018 10:17:05 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
Message-ID: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>


New submission from Stig Johan Berggren <stigjb at gmail.com>:

The section about iterators in the Functional Programming HOWTO (https://docs.python.org/3/howto/functional.html#data-types-that-support-iterators) states the following about looping over dictionary keys:

"Note that the order is essentially random, because it?s based on the hash ordering of the objects in the dictionary."

Starting with 3.7, dictionary order is guaranteed to be the same as insertion order.

----------
assignee: docs at python
components: Documentation
messages: 321375
nosy: Stig Johan Berggren, docs at python
priority: normal
severity: normal
status: open
title: Functional Programming HOWTO: Dictionary ordering isn't "essentially random"
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Tue Jul 10 09:21:04 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 10 Jul 2018 13:21:04 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531228864.83.0.56676864532.issue34083@psf.upfronthosting.co.za>


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

Thanks for noticing this.  Do you want to contribute a patch or would you like me to just fix it up?

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From gtg7784 at lab-c.me  Mon Jul  2 10:26:04 2018
From: gtg7784 at lab-c.me (=?utf-8?B?6rOg7YOc6rG0?=)
Date: Mon, 2 Jul 2018 14:26:04 +0000
Subject: [docs] Korean documentation download problem
Message-ID: <B7FA34AC-557E-4E04-A38E-7ECBE83BAB50@lab-c.me>

Hello, I?m Korean middle school student. 
I wanted to download Python 3.7.0 Documentation with ?https://docs.python.org/ko/3/download.html' this URL.
So all of the download link is 404 Not Found. T.T / Nginx
Check and reply plz?

From jxn1558 at rit.edu  Fri Jul  6 10:16:40 2018
From: jxn1558 at rit.edu (Joseph Netti (RIT Student))
Date: Fri, 6 Jul 2018 10:16:40 -0400
Subject: [docs] SSLContext.load_verify_locations
Message-ID: <CAGuEUtX9v3U15spzCcdzFosmrx86YO3ymH74sqYwUWaC9bWpLg@mail.gmail.com>

Hi,

I think I found either a bug in the documentation or a bug in the
load_verify_locations function (or I am just using the function wrong).

https://docs.python.org/3/library/ssl.html#ssl.SSLContext.load_verify_locations

I am trying to use crls with the ssl.py library which according to the
documentation should be done by with the load_verify_locations function.
Here is my stackoverflow post about it:
https://stackoverflow.com/questions/51196492/how-to-use-crls-in-pyopenssl?noredirect=1#comment89404681_51196492

Thanks,

Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180706/1591e67c/attachment-0001.html>

From hesters19 at stxtigers.com  Fri Jul  6 15:35:40 2018
From: hesters19 at stxtigers.com (Steven Hester)
Date: Fri, 6 Jul 2018 14:35:40 -0500
Subject: [docs] Bug - Can you assist -- While installing Python I continue
 to get a quit unexpectedly.
Message-ID: <CAKEAsMiaPr7VnOBz4eW4Bvv7Qibj9nSdK0duG0=Cu6YiFTYaiw@mail.gmail.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180706/3977551c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2018-07-06 at 2.32.30 PM.png
Type: image/png
Size: 355286 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180706/3977551c/attachment-0001.png>

From creditchoi at gmail.com  Sun Jul  8 17:05:08 2018
From: creditchoi at gmail.com (Dongkyu Choi)
Date: Sun, 8 Jul 2018 17:05:08 -0400
Subject: [docs] Error in functools.reduce docs
Message-ID: <CAE_L6LD-BD29i3PBdz2aHG-b1=CDx4jAaE5CpUmrs+Pq8uHQeA@mail.gmail.com>

Hi, I report error at the

https://docs.python.org/3/library/functools.html#functools.reduce

specifically, at ?If the optional initializer is present, it is placed
before the items of the sequence in the calculation, and [serves as a
default when the sequence is empty]. If initializer is not given and
sequence contains only one item, the first item is returned. (bracket is
added by me for emphasis)?

Actually, it should be stated as ?serves as a default to be run before the
lambda reads the given sequence.?

For example, at the code

def string_to_int(s):
return functools.reduce(lambda running_sum, c: running_sum * 10 +
string.digits.index(c), s[s[0] == '-':], 0) * (-1 if s[0] == '-' else 1)

t
he 0 does the job setting running_sum, c
even before it traverses the given string,
? ?
not restricted to the empty string case. Precisely,
 if we have
s =
'
-324
'
,
we need to have ru
nning_sum=0, c=0
? ?
initially, to make it (0*10+index(0)) ? as the running_sum cannot be str,
if so I get the initializer does the job of setting all the argument of
lambda: function as initializer.

Please consider this. Thanks.

?
Best regards,

??
Dongkyu
?

Choi
+1 (929) 302-9410
creditchoi at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180708/7b03d8b2/attachment-0001.html>

From robertvandeneynde at hotmail.com  Mon Jul  9 22:27:13 2018
From: robertvandeneynde at hotmail.com (Robert Vanden Eynde)
Date: Tue, 10 Jul 2018 02:27:13 +0000
Subject: [docs] In an unittest documentation example,
 __version__ is not PEP 396
Message-ID: <VI1PR03MB2909D7D1A16736191C5197C6B65B0@VI1PR03MB2909.eurprd03.prod.outlook.com>

Hello, in an example in

https://docs.python.org/3.8/library/unittest.html#skipping-tests-and-expected-failures

One could read

@unittest.skipIf(mylib.__version__ < (1, 3),
                     "not supported in this library version")


However, PEP 396 indicates "__version__ number SHOULD be a string", therefore the example is against a good python practice, and package manager like me would loose time googling the what the good practice is.

I suggest changing the example to skipIf(mylib.version_info < (1, 3), ...).

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

From j.l.m.vrancken at hr.nl  Tue Jul 10 05:24:51 2018
From: j.l.m.vrancken at hr.nl (Vrancken, J.L.M. (Jos))
Date: Tue, 10 Jul 2018 09:24:51 +0000
Subject: [docs] Another strange expression, 2
Message-ID: <11e96c9c436046aba543b033ebb59baa@hr.nl>

True == False in (True, False)

This expression gives False,
whereas in any interpretation, it should be True:

(True == False)  in (True, False)        returns True

True == (False in (True, False))        returns True

All this in Python 3.7.

Is something wrong or am I'm wrong in thinking something's wrong here?

Jos Vrancken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180710/e0ebdc0a/attachment-0001.html>

From j.l.m.vrancken at hr.nl  Tue Jul 10 05:19:23 2018
From: j.l.m.vrancken at hr.nl (Vrancken, J.L.M. (Jos))
Date: Tue, 10 Jul 2018 09:19:23 +0000
Subject: [docs] Another strange case
Message-ID: <b3f58156cc364b25913f94717e919185@hr.nl>

True == False in undefinedvariable

The expression returns False. Of course the undefinedvariable is indeed undefined.

Anything wrong here?

Jos Vrancken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180710/c568c485/attachment.html>

From j.l.m.vrancken at hr.nl  Tue Jul 10 04:59:11 2018
From: j.l.m.vrancken at hr.nl (Vrancken, J.L.M. (Jos))
Date: Tue, 10 Jul 2018 08:59:11 +0000
Subject: [docs] syntax error    True == not(False)
Message-ID: <805b63fabd9d47e4ba82321604cadd20@hr.nl>

The expression

True == not(False)

gives a syntax error.
Why is that???
Jos Vrancken


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180710/8dffdbe7/attachment.html>

From 2549591051 at qq.com  Mon Jul  9 09:33:59 2018
From: 2549591051 at qq.com (=?ISO-8859-1?B?U3R1ZGVudA==?=)
Date: Mon, 9 Jul 2018 21:33:59 +0800
Subject: [docs] Hello
Message-ID: <tencent_301AE6611BE37B6FE6663113097033483F08@qq.com>

Hello,I am a Chinese programmer.I want to learn Python,but all of your documentation is in English.Do you have a version of Chinese?If you have,please send me one,Thanks a lot!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180709/19436fbe/attachment.html>

From contact at codingbeacon.com  Thu Jul  5 01:37:11 2018
From: contact at codingbeacon.com (=?utf-8?B?Q29kaW5nQmVhY29uIFN1cHBvcnQgVGVhbQ==?=)
Date: Thu, 5 Jul 2018 13:37:11 +0800
Subject: [docs] Questions regarding the permission to translate the
 documentation of Python
Message-ID: <tencent_59BD07696D6513257652BB79@qq.com>

Hi there,
I am the admin of my website https://codingbeacon.com. My website is aimed to provide guidance for new college student to learn Computer Science and develop a career on it. Recently, I plan to translate the official documentation of Python (https://docs.python.org/) into Chinese. However, I am wondering can I have your permission to translate your documentation and put it on my website with the reference to the source page?


Thanks
Tongze Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180705/4b468cec/attachment-0001.html>

From donaldecoho at comcast.net  Tue Jul  3 20:12:00 2018
From: donaldecoho at comcast.net (Donald Coho)
Date: Tue, 3 Jul 2018 20:12:00 -0400
Subject: [docs] Installation for Newbs
Message-ID: <14c5b360-c8a5-fb19-7bd6-a689bf57462d@comcast.net>

If programming and network administration credentials are required to 
install Python then the download should be qualified. Repeat: Newbs 
should be effectually 'locked out' /before /initiating download.

At

https://docs.python.org/3/using/windows.html#installation-steps

The following is the worst example of an instruction from a disdainful 
expert from the Linux or Windows programming world:

..."*or set the registry value 
**|HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem at LongPathsEnabled|**to 
**|1|**.*"

Newbs don't understand the expert's '@' syntax. They shouldn't 
experience the frustration of downloading and running the install 
routine, only to find that nothing functions properly on their machine.

What's required is to navigate to the following folder

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

and to create a new key. THIS KEY DOES NOT PRE-EXIST with a non-unity value.

The new key name is /LongPathsEnabled/. It's type is /DWORD (32-bit) 
value. /After creation, its value must be modified to 1.

There is a critical difference between a /geek /and a /nerd/. The 
*boldfaced *instruction was written by a *NERD*.

Respectfully submitted,

Donald E Coho





---
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/20180703/f02ba9ba/attachment.html>

From asweigart at gmail.com  Tue Jul 10 11:39:35 2018
From: asweigart at gmail.com (Al Sweigart)
Date: Tue, 10 Jul 2018 08:39:35 -0700
Subject: [docs] Another strange expression, 2
In-Reply-To: <11e96c9c436046aba543b033ebb59baa@hr.nl>
References: <11e96c9c436046aba543b033ebb59baa@hr.nl>
Message-ID: <CAPyZGSnctTEQHVkDtmrafVxWR=wK3rTPzNu7oELLv7DBF63tDQ@mail.gmail.com>

This is an unfortunate side effect of chaining the == and in operators.
Look at this equivalent expression:

>>> spam = False
>>>  True == spam in (True, False)
False

The expression `True == spam in (True, False)` is equivalent to `(True ==
spam) and (spam in (True, False))`, which is why it evaluates to False.

This is similar to how `10 < spam < 20` is equivalent to `(10 < spam) and
(spam < 20)`, and not `(10 < spam) < 20` or `10 < (spam < 20)`

The lesson is to not mix different kinds of operators when chaining them.

-Al

On Tue, Jul 10, 2018 at 2:24 AM, Vrancken, J.L.M. (Jos) <
j.l.m.vrancken at hr.nl> wrote:

> True == False in (True, False)
>
>
>
> This expression gives False,
>
> whereas in any interpretation, it should be True:
>
>
>
> (True == False)  in (True, False)        returns True
>
>
>
> True == (False in (True, False))        returns True
>
>
>
> All this in Python 3.7.
>
>
>
> Is something wrong or am I'm wrong in thinking something's wrong here?
>
>
>
> Jos Vrancken
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180710/1a052ff8/attachment-0001.html>

From fred at fdrake.net  Tue Jul 10 11:47:11 2018
From: fred at fdrake.net (Fred Drake)
Date: Tue, 10 Jul 2018 11:47:11 -0400
Subject: [docs] configparser example typo
In-Reply-To: <CABwE9+QjzGNc_D6Du=9FJM8qqKmJo613K0SKDKe9PTcDX6A_bA@mail.gmail.com>
References: <CABwE9+QjzGNc_D6Du=9FJM8qqKmJo613K0SKDKe9PTcDX6A_bA@mail.gmail.com>
Message-ID: <CAFT4OTHJZR8a+HMdwj1yRn5erwseOTJv37BzZZpXkp7Vo=U13w@mail.gmail.com>

On Tue, Jul 10, 2018 at 10:24 AM Weihe Chen <wec3217 at gmail.com> wrote:
> In the page https://docs.python.org/3/library/configparser.html, under 14.2.1 Quick Start, example 2 with code:
...
>  Shouldn't the last line be configfile.write(config) ?

No; the example is correct.

The config object provides a write method that knows how to format the
configuration data and write it to an open file passed as an argument.


  -Fred

-- 
Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein

From report at bugs.python.org  Tue Jul 10 12:04:50 2018
From: report at bugs.python.org (Stig Johan Berggren)
Date: Tue, 10 Jul 2018 16:04:50 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531238690.11.0.56676864532.issue34083@psf.upfronthosting.co.za>


Stig Johan Berggren <stigjb at gmail.com> added the comment:

I'll try to patch it myself.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From bgailer at gmail.com  Tue Jul 10 12:07:36 2018
From: bgailer at gmail.com (Bob Gailer)
Date: Tue, 10 Jul 2018 12:07:36 -0400
Subject: [docs] can python be used by a commercial company on their
 servers?
In-Reply-To: <8F7B6D7D7F2A4D43BFF6ADF60408AD07A0CD5FDC@KMCI0XMB2004.na.corning.com>
References: <8F7B6D7D7F2A4D43BFF6ADF60408AD07A0CD5FDC@KMCI0XMB2004.na.corning.com>
Message-ID: <CAP1rxO7KEX+zf5eqi=HDZ7MTAQWBtLCpsfYpOs6i2v-Cw6cgoQ@mail.gmail.com>

On Jul 10, 2018 10:25 AM, "Edger, Lisa A" <EdgerLA at corning.com> wrote:
>
> Please let me know. I can find a way to contact anyone on this??

Technically this list is for discussion of the Python documentation.

But I can certainly answer your question. Python has no restriction as to
where it can be used.

List. Python. Org is the preferred place for this kind of question.

>
>
>
> Lisa Edger, CSAM
>
> Certified Software Asset Manager
>
> License Management & Software Compliance
>
>
>
> Corning Incorporated
>
> SP-ZV-01-F3L
>
> 21 Lynn Morse Dr.
>
> Painted Post, NY 14870
>
>
>
> t (607)974-9114
>
> m (607)684-8190
>
> edgerla at corning.com
>
>
>
> Reach Software Management on Blue Line
>
>
>
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180710/eeb20382/attachment.html>

From report at bugs.python.org  Tue Jul 10 12:33:43 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 10 Jul 2018 16:33:43 +0000
Subject: [docs] [issue34085] doc Improve wording on classmethod/staticmethod
Message-ID: <1531240423.32.0.56676864532.issue34085@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

1. The classmethod definition reads:

"""
The @classmethod form is a function decorator ? see the description of function definitions in Function definitions for details.

It can be called either on the class (such as C.f()) or on an instance (such as C().f())
"""

The second paragraph seems like talking about the classmethod function instead of a class method. The same goes for staticmethod.

2. The staticmethod definition reads:

"""
It can be called either on the class (such as C.f()) or on an instance (such as C().f()). The instance is ignored except for its class.
"""

"The instance is ignored except for its class." seems to have been copied from classmethod definition.

3. There is redundant text:

"see the description of function definitions in Function definitions"

"consult the documentation on the standard type hierarchy in The standard type hierarchy"

PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 321390
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Improve wording on classmethod/staticmethod
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34085>
_______________________________________

From report at bugs.python.org  Tue Jul 10 12:35:14 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 10 Jul 2018 16:35:14 +0000
Subject: [docs] [issue34085] doc Improve wording on classmethod/staticmethod
In-Reply-To: <1531240423.32.0.56676864532.issue34085@psf.upfronthosting.co.za>
Message-ID: <1531240514.64.0.902498594338.issue34085@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7766
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34085>
_______________________________________

From report at bugs.python.org  Tue Jul 10 15:51:38 2018
From: report at bugs.python.org (Stig Johan Berggren)
Date: Tue, 10 Jul 2018 19:51:38 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531252298.99.0.902498594338.issue34083@psf.upfronthosting.co.za>


Change by Stig Johan Berggren <stigjb at gmail.com>:


----------
keywords: +patch
pull_requests: +7768
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Wed Jul 11 01:29:03 2018
From: report at bugs.python.org (Roland Weber)
Date: Wed, 11 Jul 2018 05:29:03 +0000
Subject: [docs] [issue34050] Broken links to "OpenSSL cipher list format" in
 documentation
In-Reply-To: <1530778661.86.0.56676864532.issue34050@psf.upfronthosting.co.za>
Message-ID: <1531286943.45.0.56676864532.issue34050@psf.upfronthosting.co.za>


Roland Weber <rolweber at de.ibm.com> added the comment:

Thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34050>
_______________________________________

From report at bugs.python.org  Wed Jul 11 02:34:33 2018
From: report at bugs.python.org (Stig Johan Berggren)
Date: Wed, 11 Jul 2018 06:34:33 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531290873.95.0.902498594338.issue34083@psf.upfronthosting.co.za>


Change by Stig Johan Berggren <stigjb at gmail.com>:


----------
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Wed Jul 11 05:53:09 2018
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 11 Jul 2018 09:53:09 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531302789.89.0.56676864532.issue34083@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:


New changeset 5e5bbbec467a1569c914a048a94e7597528f92cf by INADA Naoki (Stig Johan Berggren) in branch 'master':
bpo-34083: Update dict order in Functional HOWTO (GH-8230)
https://github.com/python/cpython/commit/5e5bbbec467a1569c914a048a94e7597528f92cf


----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Wed Jul 11 05:54:19 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 11 Jul 2018 09:54:19 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531302859.43.0.902498594338.issue34083@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7777

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Wed Jul 11 05:59:37 2018
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 11 Jul 2018 09:59:37 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531303177.16.0.56676864532.issue34083@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

Thanks, Stig.
And I'm sorry about I missed Raymond assigned himself.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Wed Jul 11 06:42:09 2018
From: report at bugs.python.org (Bruce Richardson)
Date: Wed, 11 Jul 2018 10:42:09 +0000
Subject: [docs] [issue34094] Porting Python 2 to Python 3 example
 contradicts its own advice
Message-ID: <1531305729.89.0.56676864532.issue34094@psf.upfronthosting.co.za>


New submission from Bruce Richardson <it.is.bruce at gmail.com>:

https://docs.python.org/3/howto/pyporting.html#use-feature-detection-instead-of-version-detection

In this section, the (very good) advice is "It would be better to treat Python 2 as the exceptional case instead of Python 3 and assume that future Python versions will be more compatible with Python 3 than Python 2"

However, it then goes on to present the best solution (for dealing with library imports) is this:

try:
    from importlib import abc
except ImportError:
    from importlib2 import abc

This is literally treating Python 3 as the exception, completely contradicting the advice given a few lines earlier.  Practically, it also has the effect that, as Python 3 adoption spreads, import errors and automatic retries will become *more* common and then universal, adding a small amount of delay and noise to the entire Python estate.  And that's not considering the case where both libraries are installed to cope with old code relying on the old library (in which case you surely want new code to default to using the new library)

If the example is simply changed to

try:
    from importlib2 import abc
except ImportError:
    from importlib import abc

then both the contradiction and the practical problems go away

----------
assignee: docs at python
components: Documentation
messages: 321436
nosy: Bruce Richardson, brett.cannon, docs at python
priority: normal
severity: normal
status: open
title: Porting Python 2 to Python 3 example contradicts its own advice

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34094>
_______________________________________

From report at bugs.python.org  Wed Jul 11 06:43:40 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 11 Jul 2018 10:43:40 +0000
Subject: [docs] [issue34081] Sphinx duplicate label warning in docs
In-Reply-To: <1531211521.37.0.56676864532.issue34081@psf.upfronthosting.co.za>
Message-ID: <1531305820.27.0.902498594338.issue34081@psf.upfronthosting.co.za>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
keywords: +patch
pull_requests: +7780
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34081>
_______________________________________

From report at bugs.python.org  Wed Jul 11 07:21:54 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 11 Jul 2018 11:21:54 +0000
Subject: [docs] [issue34083] Functional Programming HOWTO: Dictionary
 ordering isn't "essentially random"
In-Reply-To: <1531217825.24.0.56676864532.issue34083@psf.upfronthosting.co.za>
Message-ID: <1531308114.62.0.56676864532.issue34083@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 151820e7a0ebe50b3d4fa64e22623c5470f1c56f by Miss Islington (bot) in branch '3.7':
bpo-34083: Update dict order in Functional HOWTO (GH-8230)
https://github.com/python/cpython/commit/151820e7a0ebe50b3d4fa64e22623c5470f1c56f


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34083>
_______________________________________

From report at bugs.python.org  Wed Jul 11 10:19:01 2018
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 11 Jul 2018 14:19:01 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1531318741.28.0.56676864532.issue33729@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

> None of the hashlib functions are taking keyword arguments for data: ...

So it's just a documentation issue, no?

https://docs.python.org/dev/library/hashlib.html#creating-hash-objects

Juuso Lehtivarjo: do you want to write a pull request to fix the documentation?

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Wed Jul 11 11:09:24 2018
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 11 Jul 2018 15:09:24 +0000
Subject: [docs] [issue34094] Porting Python 2 to Python 3 example
 contradicts its own advice
In-Reply-To: <1531305729.89.0.56676864532.issue34094@psf.upfronthosting.co.za>
Message-ID: <1531321764.35.0.56676864532.issue34094@psf.upfronthosting.co.za>


Zachary Ware <zachary.ware at gmail.com> added the comment:

I don't agree with your conclusion here: importlib2 is a PyPI package that backports Python 3's importlib to Python 2, thus the ImportError will only be raised on Python 2 with the example as written.

----------
nosy: +zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34094>
_______________________________________

From report at bugs.python.org  Wed Jul 11 12:46:38 2018
From: report at bugs.python.org (Bruce Richardson)
Date: Wed, 11 Jul 2018 16:46:38 +0000
Subject: [docs] [issue34094] Porting Python 2 to Python 3 example
 contradicts its own advice
In-Reply-To: <1531321764.35.0.56676864532.issue34094@psf.upfronthosting.co.za>
Message-ID: <CAAZN3=Hspr7NmzgkFW2SmqT1sJnrLZ59MuR5kEsCLL7MGLD0PA@mail.gmail.com>


Bruce Richardson <it.is.bruce at gmail.com> added the comment:

Ah, doh. my bad.

On 11 July 2018 at 16:09, Zachary Ware <report at bugs.python.org> wrote:

>
> Zachary Ware <zachary.ware at gmail.com> added the comment:
>
> I don't agree with your conclusion here: importlib2 is a PyPI package that
> backports Python 3's importlib to Python 2, thus the ImportError will only
> be raised on Python 2 with the example as written.
>
> ----------
> nosy: +zach.ware
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue34094>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34094>
_______________________________________

From report at bugs.python.org  Wed Jul 11 14:47:32 2018
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 11 Jul 2018 18:47:32 +0000
Subject: [docs] [issue34094] Porting Python 2 to Python 3 example
 contradicts its own advice
In-Reply-To: <1531305729.89.0.56676864532.issue34094@psf.upfronthosting.co.za>
Message-ID: <1531334852.21.0.902498594338.issue34094@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34094>
_______________________________________

From report at bugs.python.org  Thu Jul 12 03:55:33 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 12 Jul 2018 07:55:33 +0000
Subject: [docs] [issue34101] PyBuffer_GetPointer() not documented
Message-ID: <1531382133.03.0.902498594338.issue34101@psf.upfronthosting.co.za>


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


----------
assignee: docs at python
components: Documentation
nosy: docs at python, pitrou, skrah
priority: normal
severity: normal
status: open
title: PyBuffer_GetPointer() not documented
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34101>
_______________________________________

From kim at abts.io  Thu Jul 12 23:43:41 2018
From: kim at abts.io (Kim Ford)
Date: Fri, 13 Jul 2018 10:43:41 +0700
Subject: [docs] Search Improvement Suggestion - Methods
Message-ID: <E15B465E-408F-4045-AB0D-D25D01E93183@abts.io>

Hi there,

I know there might be a way to get what I?m suggesting, but I haven?t found it, so I?m sharing it here.

In brief, searching for things like ?Dictionary Methods?, ?List Methods?, and ?String Methods? returns long lists or search results.

Searching for any of the above should result in the top search result being a page that contains the methods.  Or at least there should be some easy to find links in the docs that point to such things.

Sadly, I wind up using Google and usually find myself on a different site than the official Python documentation.  While some of these sites are okay, I find the content in the Python documentation to be best.  If only I can find it!

I hope I don?t come across as sounding like a whiner, but? whaaa whaa whaaa :) 

Best,

Kim

To clarify I start my searches from here:  file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/index.html# <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/index.html#>

This like is provided during Python 3.7 install and I?ve bookmarked it for ?easy? reference.

An example is when searching for ?List Methods?, there are 239 results.

In order to actually find List Methods in the docs, I need to do this:

1. Navigate to the General Index page
2. Click L (for List)
3. Search on the page for List (there are 19 matches)
4. Get frustrated as there is not section for Methods to click on

list <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/glossary.html#term-list>
assignment, target <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-6>
comprehensions <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-12>
deletion target <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-21>
display <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-12>
empty <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-12>
expression <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-80>, [1] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-1>, [2] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-2>
object <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/c-api/list.html#index-0>, [1] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-21>, [2] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-23>, [3] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/datamodel.html#index-23>, [4] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-12>, [5] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-33>, [6] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-35>, [7] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-38>, [8] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-10>
target <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/compound_stmts.html#index-6>, [1] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/compound_stmts.html#index-6>, [2] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-5>
type, operations on <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-22>
list (built-in class) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#list>
List (class in typing) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/typing.html#typing.List>
list (pdb command) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/pdb.html#pdbcommand-list>
list comprehension <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/glossary.html#term-list-comprehension>
list() (imaplib.IMAP4 method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/imaplib.html#imaplib.IMAP4.list>
(multiprocessing.managers.SyncManager method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/multiprocessing.html#multiprocessing.managers.SyncManager.list>
(nntplib.NNTP method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/nntplib.html#nntplib.NNTP.list>
(poplib.POP3 method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/poplib.html#poplib.POP3.list>
(tarfile.TarFile method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/tarfile.html#tarfile.TarFile.list>
LIST_APPEND (opcode) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/dis.html#opcode-LIST_APPEND>
list_dialects() (in module csv) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/csv.html#csv.list_dialects>
list_folders() (mailbox.Maildir method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/mailbox.html#mailbox.Maildir.list_folders>
(mailbox.MH method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/mailbox.html#mailbox.MH.list_folders>


At least String has a section called methods:

string
PyObject_Str (C function) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/c-api/object.html#index-2>
__format__() (object method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/datamodel.html#index-74>
__str__() (object method) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/datamodel.html#index-72>
conversion <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/datamodel.html#index-74>, [1] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/simple_stmts.html#index-3>
format() (built-in function) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/functions.html#index-4>
formatted literal <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/lexical_analysis.html#index-20>
formatting, printf <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-33>
immutable sequences <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/datamodel.html#index-18>
interpolated literal <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/lexical_analysis.html#index-20>
interpolation, printf <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-33>
item <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-36>
methods <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-30>
module <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/locale.html#index-6>
object <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-26>, [1] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-35>, [2] <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/reference/expressions.html#index-38>
object representation <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/extending/newtypes.html#index-3>
str (built-in class) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-28>
str() (built-in function) <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/functions.html#index-10>
text sequence type <file:///Library/Frameworks/Python.framework/Versions/3.7/Resources/English.lproj/Documentation/library/stdtypes.html#index-26>



Sent via Migadu.com, world's easiest email hosting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/13fcda72/attachment-0001.html>

From pawel.gieniec at motorolasolutions.com  Fri Jul 13 05:14:41 2018
From: pawel.gieniec at motorolasolutions.com (Pawel Gieniec)
Date: Fri, 13 Jul 2018 11:14:41 +0200
Subject: [docs] Found a bug in your docs
Message-ID: <CAB_W=KktK3z4E11A=qm8Se9Up1zPK08XfUCkPiP3V_QroSkEHw@mail.gmail.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/4ebf0ec9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 31263 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/4ebf0ec9/attachment-0001.png>

From report at bugs.python.org  Fri Jul 13 05:51:19 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 13 Jul 2018 09:51:19 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1531475479.73.0.56676864532.issue33859@psf.upfronthosting.co.za>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Closing this since the related PRs are merged.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33859>
_______________________________________

From fred at fdrake.net  Fri Jul 13 07:50:09 2018
From: fred at fdrake.net (Fred Drake)
Date: Fri, 13 Jul 2018 07:50:09 -0400
Subject: [docs] Found a bug in your docs
In-Reply-To: <CAB_W=KktK3z4E11A=qm8Se9Up1zPK08XfUCkPiP3V_QroSkEHw@mail.gmail.com>
References: <CAB_W=KktK3z4E11A=qm8Se9Up1zPK08XfUCkPiP3V_QroSkEHw@mail.gmail.com>
Message-ID: <CAFT4OTHi5J8NVP5nds36q6habzS3fTtsYybhCbWj3BpL3kZ=ig@mail.gmail.com>

On Fri, Jul 13, 2018 at 5:33 AM Pawel Gieniec <
pawel.gieniec at motorolasolutions.com> wrote:

>
>
That looks right to me.  Could you be more specific regarding what you
think is incorrect?


  -Fred

-- 
Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/32676ea3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 31263 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/32676ea3/attachment-0001.png>

From fred at fdrake.net  Fri Jul 13 11:29:19 2018
From: fred at fdrake.net (Fred Drake)
Date: Fri, 13 Jul 2018 11:29:19 -0400
Subject: [docs] Found a bug in your docs
In-Reply-To: <CAB_W=KkURm+y7tYGZJQB+ovH3zLSpX0-ZEwX2YoXCkrz1xzopg@mail.gmail.com>
References: <CAB_W=KktK3z4E11A=qm8Se9Up1zPK08XfUCkPiP3V_QroSkEHw@mail.gmail.com>
 <CAFT4OTHi5J8NVP5nds36q6habzS3fTtsYybhCbWj3BpL3kZ=ig@mail.gmail.com>
 <CAB_W=KkURm+y7tYGZJQB+ovH3zLSpX0-ZEwX2YoXCkrz1xzopg@mail.gmail.com>
Message-ID: <CAFT4OTHS6e=jvt50JU1r-79bqycVJ199DTdZr1royxhAxQCBGA@mail.gmail.com>

On Fri, Jul 13, 2018 at 7:59 AM Pawel Gieniec <
pawel.gieniec at motorolasolutions.com> wrote:

> For input
>
> >>> "\"Yes,\" they said."
>
> the output will be:
>
> ""Yes," they said."
>
> not:
>
> '"Yes," they said.'
>
>  regarding to quotation
>
> KR,
> Paw
>

In what implementation / version of Python do you see this?  Please verify
with an actual interpreter; the implementation and version would be very
helpful in our understanding.

The reference implementation from python.org behaves as described.


  -Fred

-- 
Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/4bc37547/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 31263 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180713/4bc37547/attachment-0001.png>

From report at bugs.python.org  Fri Jul 13 14:12:41 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 13 Jul 2018 18:12:41 +0000
Subject: [docs] [issue34063] binhex REASONABLY_LARGE = 32768 so what is
 128000
In-Reply-To: <1530913345.39.0.56676864532.issue34063@psf.upfronthosting.co.za>
Message-ID: <1531505561.17.0.56676864532.issue34063@psf.upfronthosting.co.za>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I tried changing it to REASONABLY_LARGE and could see no test failures. It seems the literal was added as part of a220e67a9ed94d66b81e393a3bb9e6acd10068c1 (23/03/1996) and REASONABLY_LARGE was before that as added part of fcdffeaaa144147f43224a641b668df539ffb6fe (07/08/1995)

?  cpython git:(master) time ./python -Werror -m unittest -v test.test_binhex
test_binhex (test.test_binhex.BinHexTestCase) ... ok
test_binhex_error_on_long_filename (test.test_binhex.BinHexTestCase) ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.002s

OK
./python -Werror -m unittest -v test.test_binhex  0.23s user 0.03s system 93% cpu 0.279 total

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34063>
_______________________________________

From report at bugs.python.org  Fri Jul 13 14:49:30 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 13 Jul 2018 18:49:30 +0000
Subject: [docs] [issue27741] datetime.datetime.strptime functionality
 description incorrect
In-Reply-To: <1470941311.19.0.0562450492824.issue27741@psf.upfronthosting.co.za>
Message-ID: <1531507769.95.0.56676864532.issue27741@psf.upfronthosting.co.za>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

The same part repeated at https://docs.python.org/3/library/datetime.html#strftime-and-strptime-behavior can also be corrected. It seems both of them use _strptime which returns microseconds but only datetime.datetime.strptime uses it with time.strptime ignoring it.

Thanks

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27741>
_______________________________________

From report at bugs.python.org  Sat Jul 14 09:09:01 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 14 Jul 2018 13:09:01 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531573741.07.0.56676864532.issue29710@psf.upfronthosting.co.za>


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

I think we have a fairly different notion of what clarity means here - I have no mental concept whatsoever of how to do two's complement arithmetic with an infinite number of sign bits (I learned most of what I know about two's complement by working with fixed point 16-bit and 32-bit microprocessors), so the infinite bits explanation provides me with very little useful insight, whereas I can readily cope with the notion of storing a single extra sign extension bit beyond the minimum required to hold the operands' two's complement representations.

That said, I do like the idea of using infinite precision arithmetic as the formal definition of the intended language semantics, which would lead to wording like the following:

=================
Each bitwise operation has the same result as though carried out in two's complement with an infinite number of sign bits. In practice, performing the calculation with one extra sign extension bit (a bit-width of ``1 + max(x.bit_length(), y.bit_length()``) is sufficient to get the expected result.
=================

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sat Jul 14 20:07:30 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 15 Jul 2018 00:07:30 +0000
Subject: [docs] [issue34116] Move all bytes/bytearray/int/float/complex
 documentation to Built-in Types
Message-ID: <1531613250.34.0.56676864532.issue34116@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

Right now, bytearray, bytes, complex, float and int documentation is splitted into stdtypes.rst and functions.rst. I think stdtypes.rst should be the only source with all documentation, and functions.rst should just point out to stdtypes.rst. This would make it easier to get the complete picture of a given type without having to jump between pages. This is how the documentation of dict, frozenset, list, memoryview, range, set, str and tuple works.

I believe bool() is more useful in functions.rst, as it's really short.

----------
assignee: docs at python
components: Documentation
messages: 321667
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Move all bytes/bytearray/int/float/complex documentation to Built-in Types
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34116>
_______________________________________

From report at bugs.python.org  Sat Jul 14 20:22:45 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 15 Jul 2018 00:22:45 +0000
Subject: [docs] [issue34116] Move all bytes/bytearray/int/float/complex
 documentation to Built-in Types
In-Reply-To: <1531613250.34.0.56676864532.issue34116@psf.upfronthosting.co.za>
Message-ID: <1531614165.59.0.902498594338.issue34116@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7820
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34116>
_______________________________________

From report at bugs.python.org  Sat Jul 14 20:24:24 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 15 Jul 2018 00:24:24 +0000
Subject: [docs] [issue34116] Move all bytes/bytearray/int/float/complex
 documentation to Built-in Types
In-Reply-To: <1531613250.34.0.56676864532.issue34116@psf.upfronthosting.co.za>
Message-ID: <1531614263.93.0.56676864532.issue34116@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

See talk at: https://python.zulipchat.com/#narrow/stream/116633-documentation/subject/Gather.20all.20type.20documentation.20in.20stdtypes

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34116>
_______________________________________

From report at bugs.python.org  Sat Jul 14 20:27:14 2018
From: report at bugs.python.org (Brett Cannon)
Date: Sun, 15 Jul 2018 00:27:14 +0000
Subject: [docs] [issue34117] Rename "generator expressions" to "generator
 comprehensions"
Message-ID: <1531614433.94.0.56676864532.issue34117@psf.upfronthosting.co.za>


New submission from Brett Cannon <brett at python.org>:

The idea came up on python-dev to tweak the names of generator expressions to "generator comprehensions" to align more with list|set|dict comprehensions. This would be strictly a doc change (for now). A reference to generator expressions should be left if nothing else than to point to the new name.

----------
assignee: docs at python
components: Documentation
messages: 321670
nosy: brett.cannon, docs at python
priority: low
severity: normal
status: open
title: Rename "generator expressions" to "generator comprehensions"

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34117>
_______________________________________

From report at bugs.python.org  Sat Jul 14 23:04:38 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 15 Jul 2018 03:04:38 +0000
Subject: [docs] [issue34118] Fix some class entries entries in 'Built-in
 Functions'
Message-ID: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

The Library Reference 'Built-in Functions' chapter includes build-in classes because classes are functions in the sense of being callable with arguments and returning objects.  A proposal to change the name to Built-in Functions and Classes was rejected (by Raymond, as I remember).
I suspect that 'Built-in Callables' has also been proposed.
  
Some of the current entries need one or both of two fixes. 

1. Most, but not all, of the classes are tagged with '*class*' before the class name.  Classes classmethod and staticmethed are instead tagged with '@' since they are mostly used as decorators, although property is tagged *class*.

Classes enumerate, filter, map, memoryview, range, reversed, tuple, and zip are untagged.  I think, to be consistent, that they should all get the *class* tag.

2. Nearly all entries fully describe the arguments and return values.  The exceptions are those for 6 collection classes. The first 3 have an abbreviated description of the result and a reference for further details on the relationship of input to result.

 class dict(iterable, **kwarg)
    Create a new dictionary. The dict object is the dictionary class. See dict and Mapping Types ? dict for documentation about this class.
    For other containers see the built-in list, set, and tuple classes, as well as the collections module.

class frozenset([iterable])
    Return a new frozenset object, optionally with elements taken from iterable. frozenset is a built-in class. See frozenset and Set Types ? set, frozenset for documentation about this class.
    For other containers see the built-in set, list, tuple, and dict classes, as well as the collections module.

class set([iterable])
    Return a new set object, optionally with elements taken from iterable. set is a built-in class. See set and Set Types ? set, frozenset for documentation about this class.
    For other containers see the built-in frozenset, list, tuple, and dict classes, as well as the collections module.

The next 3 replace 'Return a ___' with 'Rather than being a function'.  (This is from Nick's patch 6 years ago.  https://github.com/python/cpython/commit/83c0ae5de642145ec225d29e7b239aa410229539.)  I object to this because it is wrong if one uses the broad definition of function used in the chapter title.  It is also wrong in the implication there is anything special about these classes in regard to being functions verses classess.  

class list([iterable])
    Rather than being a function, list is actually a mutable sequence type, as documented in Lists and Sequence Types ? list, tuple, range.

range(start, stop[, step])
    Rather than being a function, range is actually an immutable sequence type, as documented in Ranges and Sequence Types ? list, tuple, range.

tuple([iterable])
    Rather than being a function, tuple is actually an immutable sequence type, as documented in Tuples and Sequence Types ? list, tuple, range.

I propose that the 2nd 3 follow the model of the 1st 3, except that the final line should be: "For other collections see the built-in range, tuple, list, frozenset, set, and dict classes, as well as the collections module." (with 1 of the 6 omitted as appropriate).  (Range represents a collection, but is not a container in the sense that the others are.)

----------
assignee: docs at python
components: Documentation
messages: 321674
nosy: docs at python, ncoghlan, rhettinger, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Fix some class entries entries in 'Built-in Functions'
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Sat Jul 14 23:28:58 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 15 Jul 2018 03:28:58 +0000
Subject: [docs] [issue34117] Rename "generator expressions" to "generator
 comprehensions"
In-Reply-To: <1531614433.94.0.56676864532.issue34117@psf.upfronthosting.co.za>
Message-ID: <1531625338.4.0.56676864532.issue34117@psf.upfronthosting.co.za>


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

Guido asked me to try this out on students.  I'll report back after next week's class.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34117>
_______________________________________

From report at bugs.python.org  Sun Jul 15 01:05:50 2018
From: report at bugs.python.org (Tim Peters)
Date: Sun, 15 Jul 2018 05:05:50 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531631150.7.0.56676864532.issue29710@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

Nick, that seems a decent compromise.  "Infinite string of sign bits" is how Guido & I both thought of it when the semantics of longs were first defined, and others in this report apparently find it natural enough too.  It also applies to all 6 operations in the table as-is.

It appears that

    a bit-width of ``1 + max(x.bit_length(), y.bit_length()``
    
only applies as-is to 3 (~ has only one operand, while the bit length of the RHS doesn't matter for << and >>).  Provided that's clarified, I'd only suggest inserting "at least" before "one extra sign extension bit" and after "a bit-width of".  That's a bridge between the "infinite" and "fixed-albeit-variable-width" views:  "plus 1" is the smallest approximation to infinity that works, but anything at least that large works too.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sun Jul 15 01:40:11 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 15 Jul 2018 05:40:11 +0000
Subject: [docs] [issue34117] Rename "generator expressions" to "generator
 comprehensions"
In-Reply-To: <1531614433.94.0.56676864532.issue34117@psf.upfronthosting.co.za>
Message-ID: <1531633211.77.0.56676864532.issue34117@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There are also few differences between comprehensions and generator expressions. The author of the patch should not just replace all occurrences of "generator expression" with "generator comprehension", but analyze all occurrences of the sole "comprehension" and replace it with "non-generator comprehension" if needed.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34117>
_______________________________________

From report at bugs.python.org  Sun Jul 15 01:43:22 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 15 Jul 2018 05:43:22 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1531633402.31.0.902498594338.issue34118@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
title: Fix some class entries entries in 'Built-in Functions' -> Fix some class entries in 'Built-in Functions'

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Sun Jul 15 01:55:01 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 15 Jul 2018 05:55:01 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531634101.64.0.56676864532.issue29710@psf.upfronthosting.co.za>


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

The restriction of the footnote to ``x & y``, ``x | y``, and ``x ^ y`` was going to come from the fact that only those rows in the table will reference the new note. However, it likely makes sense to repeat the relevant expressions in the footnote as well, since that makes it clearer what ``x`` and ``y`` refer to in the second sentence.

Latest proposal:

=================
The results of ``x | y``,  ``x ^ y``, and ``x & y`` are calculated as though carried out in two's complement with an infinite number of sign bits. In practice, performing the calculation with at least one extra sign extension bit (a working bit-width of ``1 + max(x.bit_length(), y.bit_length()`` or more) is sufficient to get the expected result.
=================

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sun Jul 15 03:32:52 2018
From: report at bugs.python.org (Tim Peters)
Date: Sun, 15 Jul 2018 07:32:52 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531639972.62.0.56676864532.issue29710@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

Well, all 6 operations "are calculated as though carried out in two's complement with an infinite number of sign bits", so I'd float that part out of the footnote and into the main text.  When, e.g., you're thinking of ints _as_ bitstrings, it's essentially useless to think of `n >> 13` as being equivalent to `n // 2**13`.

Quick:  what's ~0 >> 13?  Well, ~0 is an infinite string of 1 bits, so shifting it right by any finite number of bits doesn't change it.  That, mathematically, floor(~0 / 8192) = -1 is only interesting if you're thinking of ~0 as being an integer instead.

And, if you are, _then_ you need to know that the infinite string of 1 bits ~0 represents is viewed as being a 2's-complement representation of -1.  But so long as you're sticking to the bitstring view, the "2's complement" part is irrelevant to anything these 6 operations do.

Indeed, in the very earliest versions of Python, longs (but not ints!) were viewed as being 1's-complement infinite bitstrings, but "infinite string of sign bits" was just as applicable to what these operations did then.  The meaning of what these operations compute _as bitstrings_ is independent of how bitstrings are mapped to and from integers.  When longs changed from 1's-comp to 2's-comp only the latter changed; code using longs as bitstrings wasn't affected.

So, in all, there's quite a bit of background these telegraphic docs are glossing over.  You (Nick) don't seem to ever think of them as being bitstrings, but what the "bitwise operators" do was driven by the bitstring view.  That some of them can also be defined by arithmetic (+ - * /) is secondary.  It may well take more text to get that all across than is suitable here, though.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sun Jul 15 04:20:26 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 15 Jul 2018 08:20:26 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531642826.22.0.56676864532.issue29710@psf.upfronthosting.co.za>


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

OK, that makes sense to me. Given that, there'd be two changes proposed.

1. Replace the opening paragraph of https://docs.python.org/3/library/stdtypes.html#bitwise-operations-on-integer-types (the one I originally quoted when opening this issue) with the text:

=====================
Bitwise operations only make sense for integers. The result of bitwise operations is calculated as though carried out in two's complement with an infinite number of sign bits.
=====================

2. Add a new footnote ``(4)`` to the table for the ``|``, ``^``, and ``&`` entries that reads:

=====================
4. Performing these calculations with at least one extra sign extension bit in the internal representation (a working bit-width of ``1 + max(x.bit_length(), y.bit_length()`` or more) is sufficient to get the same result as if there were an infinite number of sign bits.
=====================

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sun Jul 15 06:52:41 2018
From: report at bugs.python.org (Farhaan Bukhsh)
Date: Sun, 15 Jul 2018 10:52:41 +0000
Subject: [docs] [issue27741] datetime.datetime.strptime functionality
 description incorrect
In-Reply-To: <1470941311.19.0.0562450492824.issue27741@psf.upfronthosting.co.za>
Message-ID: <1531651960.99.0.56676864532.issue27741@psf.upfronthosting.co.za>


Farhaan Bukhsh <farhaan.bukhsh at gmail.com> added the comment:

Hey I would like to remove this bug I was going through the discussion so does that mean remove the about mentioned lines from 

https://docs.python.org/3/library/datetime.html#datetime.datetime.strptime

will fix this issue? Or should we add some more information there?

----------
nosy: +fhackdroid

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27741>
_______________________________________

From report at bugs.python.org  Mon Jul 16 02:00:27 2018
From: report at bugs.python.org (Dan Snider)
Date: Mon, 16 Jul 2018 06:00:27 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
Message-ID: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>


New submission from Dan Snider <mr.assume.away at gmail.com>:

https://docs.python.org/3/library/stdtypes.html#dict.popitem


`dict.popitem` no longer returns an "arbitrary" (key, value) pair as the documentation suggests. Rather, it always returns the pair whose key was most recently *inserted* (ie., the last entry in `dk_entries`).

Perhaps the docs could reflect that this method is now always LIFO rather arbitrary now that insertion order is guaranteed?

----------
assignee: docs at python
components: Documentation
messages: 321708
nosy: bup, docs at python
priority: normal
severity: normal
status: open
title: ambiguous documentation for dict.popitem
versions: Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 02:07:09 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 16 Jul 2018 06:07:09 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531721229.33.0.56676864532.issue34123@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

I think it is implementation detail yet.
Only iteration order is guaranteed.

----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 02:52:14 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 16 Jul 2018 06:52:14 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531723934.81.0.56676864532.issue34123@psf.upfronthosting.co.za>


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

My opinion is that it is in fact guaranteed. It makes no sense for all other aspects of the dict behavior to be guaranteed and not this one.  This is what PyPy and CPython already do and there is no scenario where an implementation would be able to append a new pair at the end but unable to reverse the operation.

IMO, leaving this in an ambiguous state would created problems unnecessarily and it would preclude reasonable uses of the the ordering feature.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 02:58:25 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 16 Jul 2018 06:58:25 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531724305.69.0.902498594338.issue34123@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 03:12:10 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 16 Jul 2018 07:12:10 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531725130.08.0.902498594338.issue34123@psf.upfronthosting.co.za>


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


----------
keywords: +patch
pull_requests: +7826
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 03:15:43 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 16 Jul 2018 07:15:43 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531725343.72.0.56676864532.issue34123@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

@Armin Rigo
How do you think about this?
Is there no possible optimizations by breaking LIFO dict.popitem()?

----------
nosy: +arigo

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 03:57:49 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 16 Jul 2018 07:57:49 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531727869.8.0.56676864532.issue34123@psf.upfronthosting.co.za>


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

> Is there no possible optimizations by breaking LIFO dict.popitem()?

Even if there were a possible optimization, we wouldn't care.  The API is too desirable to forgo in the name of micro-optimization.  We don't design our APIs that way -- trading the relevant and actionable for ethereal and unknown.

Also, it is common sense that addition of a key/value pair at the end is a readily undoable operation (no more expensive to remove than it was to add). There will be a dummy entry in the hash array just like there is now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 05:24:25 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 16 Jul 2018 09:24:25 +0000
Subject: [docs] [issue33111] Merely importing tkinter breaks parallel code
 (multiprocessing, sharedmem)
In-Reply-To: <1521573656.32.0.467229070634.issue33111@psf.upfronthosting.co.za>
Message-ID: <1531733065.54.0.56676864532.issue33111@psf.upfronthosting.co.za>


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

macOS users, feel free to propose a doc PR for multiprocessing.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 3.7, Python 3.8 -Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33111>
_______________________________________

From report at bugs.python.org  Mon Jul 16 05:53:27 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 16 Jul 2018 09:53:27 +0000
Subject: [docs] [issue34116] Move all bytes/bytearray/int/float/complex
 documentation to Built-in Types
In-Reply-To: <1531613250.34.0.56676864532.issue34116@psf.upfronthosting.co.za>
Message-ID: <1531734806.94.0.56676864532.issue34116@psf.upfronthosting.co.za>


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

I disagree that this would be an improvement.  The current organization has worked well for us.  In particular, some of the these types sometimes used like functions that produce a type (this is where the builtin functions docs do a good job).  In the stdtypes docs, we go into detail about what the types do and have them grouped in a way that can be compared and contrasted.

As a Python instructor, I ask newcomers to read the built-in functions section because it tells them a lot of what they need to know to get up and running with the language (indeed, that is why these are all builitins rather than relegated to modules).  The stdtypes section is more voluminous and rarely read start to finish (mostly just used as a reference).

----------
nosy: +rhettinger
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34116>
_______________________________________

From report at bugs.python.org  Mon Jul 16 06:41:34 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 16 Jul 2018 10:41:34 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1531737694.32.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

> I propose that the 2nd 3 follow the model of the 1st 3,

This makes sense and would read a little better.

> Classes enumerate, filter, map, memoryview, range, reversed, 
> tuple, and zip are untagged.  I think, to be consistent, 
> that they should all get the *class* tag.

To me, that makes the most sense for: memoryview, range and tuple.

The rest are used like functions.  Even though they are technically classes, it is confusing to think of them as such (we don't call map() to get an instance of a mapobject and do a dir() to what interesting methods it may have).  Tools like map() and filter() actually were functions at one time.  The substantive change was that they were made to be lazy.  The implementation detail was that they were implemented as classes -- they could have been generators instead.  Accordingly, I think tagging these as classes is pedantically correct but actually makes the docs a little less usable.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Mon Jul 16 07:39:16 2018
From: report at bugs.python.org (Jon Ribbens)
Date: Mon, 16 Jul 2018 11:39:16 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
Message-ID: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>


New submission from Jon Ribbens <jribbens at gmail.com>:

The documentation for email.message_from_binary_file is missing a line-continuation backslash at the end of the `.. function::` line which means the output formatting is mangled and it has no permalink.

----------
assignee: docs at python
components: Documentation
messages: 321733
nosy: docs at python, jribbens
priority: normal
severity: normal
status: open
title: email.message_from_binary_file documentation is broken
type: compile error
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 07:50:35 2018
From: report at bugs.python.org (Jon Ribbens)
Date: Mon, 16 Jul 2018 11:50:35 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531741835.87.0.902498594338.issue34124@psf.upfronthosting.co.za>


Change by Jon Ribbens <jribbens at gmail.com>:


----------
keywords: +patch
pull_requests: +7831
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 11:03:00 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 16 Jul 2018 15:03:00 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531753380.99.0.902498594338.issue34124@psf.upfronthosting.co.za>


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


----------
type: compile error -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 12:02:02 2018
From: report at bugs.python.org (Armin Rigo)
Date: Mon, 16 Jul 2018 16:02:02 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531756922.0.0.56676864532.issue34123@psf.upfronthosting.co.za>


Armin Rigo <arigo at users.sourceforge.net> added the comment:

Agreed with Raymond.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 13:19:47 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 16 Jul 2018 17:19:47 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531761587.46.0.56676864532.issue34124@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset c9265c1534b7e62bb9b15460d0420c0c3bb57ff9 by Berker Peksag (Jon Ribbens) in branch 'master':
bpo-34124: Fix markup of message_from_binary_file() signature (GH-8297)
https://github.com/python/cpython/commit/c9265c1534b7e62bb9b15460d0420c0c3bb57ff9


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 13:21:24 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 16 Jul 2018 17:21:24 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531761684.05.0.902498594338.issue34124@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7832

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 13:21:57 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 16 Jul 2018 17:21:57 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531761717.96.0.902498594338.issue34124@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7833

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 14:43:46 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 16 Jul 2018 18:43:46 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531766626.12.0.56676864532.issue34124@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 43c2fabb2fe7760be462e008b39169cf16c28b4c by Berker Peksag (Miss Islington (bot)) in branch '3.7':
bpo-34124: Fix markup of message_from_binary_file() signature (GH-8297)
https://github.com/python/cpython/commit/43c2fabb2fe7760be462e008b39169cf16c28b4c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 14:44:39 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 16 Jul 2018 18:44:39 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531766679.64.0.56676864532.issue29710@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

The wording for change 1 looks fine to me.

For change 2, the mention of the internal representation is misleading, since the internal representation of (long) integers in current CPython is effectively sign-magnitude, and so there are some shenanigans to make the operations behave *as though* the internal representation were some form of two's complement [1]. The previously proposed wording (in msg321679) (with the "infinite sign bits" extracted into the main text as Tim suggests) looks fine to me.

[1] https://github.com/python/cpython/blob/c9265c1534b7e62bb9b15460d0420c0c3bb57ff9/Objects/longobject.c#L4415-L4429

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 16 15:03:26 2018
From: report at bugs.python.org (Tim Peters)
Date: Mon, 16 Jul 2018 19:03:26 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1531767806.01.0.56676864532.issue29710@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

Ya, Mark's got a point there.  Perhaps

s/the internal/a finite two's complement/

?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 16 15:25:12 2018
From: report at bugs.python.org (Lee Griffiths)
Date: Mon, 16 Jul 2018 19:25:12 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1531769112.43.0.56676864532.issue32554@psf.upfronthosting.co.za>


Lee Griffiths <poddster at gmail.com> added the comment:

a) This below issue added doc to py2.7 that calls out PYTHONHASHSEED, but py doesn't currently contain those words

https://bugs.python.org/issue27706

It'd be useful to have the something whether the "behaviour" is fixed or not, as providing other objects (like a tuple) will still be non-deterministic.

b) I don't know if this is the correct issue to heap this on, but I think it might as you're looking at changing the seed function? 

The documentation for `object.__hash__` calls out `str`, `bytes` and `datetime` as being affected by `PYTHONHASHSEED`. Doesn't it seem odd that there's a workaround in the seed function for str and bytes, but not for datetime?

https://docs.python.org/3/reference/datamodel.html#object.__hash__

I mainly point this out as seeding random with the current date/time is idiomatic in many languages and environments (usually used when you log the seed to be able to recreate things later, or just blindly copying the historical use `srand(time(NULL))` from C programs!). Anyone shoving a datetime straight into seed() is going to find it non-deterministic and might not understand why, or even notice, especially as the documentation for seed() doesn't call this out. 

Those "in the know" will get a unix timestamp out of the datetime and put that in seed instead, but I feel that falls under the same argument as users-in-the-know SHA512ing a string, mentioned above, which is undesirable and apparently something the function should implement and not users.

Would it be wise for datetime to have a specific implementation as well?

----------
nosy: +poddster

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32554>
_______________________________________

From report at bugs.python.org  Mon Jul 16 15:41:55 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 16 Jul 2018 19:41:55 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531770115.2.0.56676864532.issue34124@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset f1ab9cac909449ad85595245fa49b8660214cd0e by Berker Peksag (Miss Islington (bot)) in branch '3.6':
bpo-34124: Fix markup of message_from_binary_file() signature (GH-8297)
https://github.com/python/cpython/commit/f1ab9cac909449ad85595245fa49b8660214cd0e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 15:42:32 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 16 Jul 2018 19:42:32 +0000
Subject: [docs] [issue34124] email.message_from_binary_file documentation is
 broken
In-Reply-To: <1531741156.21.0.56676864532.issue34124@psf.upfronthosting.co.za>
Message-ID: <1531770152.1.0.56676864532.issue34124@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the report and for the patch, Jon.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34124>
_______________________________________

From report at bugs.python.org  Mon Jul 16 17:31:25 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 16 Jul 2018 21:31:25 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1531776685.31.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

I was forgetting that this is a Python, not CPython doc.  So I agree to not tag the iterator classes as such.  For all I know, PyPy might use (compiled?) generator functions.  And if we were to allow use of Cython, say, for CPython, we might  try that.

How about a note under the index table:

Functions that must be classes are tagged *class*.  The iterator functions enumerate, filter, map, reversed, and zip are classes in CPython, but they are not tagged because they could be implemented as generator functions.

Or we could add an *iterator* tag.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Mon Jul 16 20:20:20 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 00:20:20 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531786819.97.0.56676864532.issue34123@psf.upfronthosting.co.za>


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


New changeset 01b7d5898262dbe0e9edb321b3be9a34da196f6f by Raymond Hettinger in branch 'master':
bpo-34123: Fix missed documentation update for dict.popitem(). (GH-8292)
https://github.com/python/cpython/commit/01b7d5898262dbe0e9edb321b3be9a34da196f6f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 20:20:45 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 17 Jul 2018 00:20:45 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531786845.03.0.902498594338.issue34123@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7842

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 20:51:44 2018
From: report at bugs.python.org (Nathaniel Manista)
Date: Tue, 17 Jul 2018 00:51:44 +0000
Subject: [docs] [issue34133] ValueError should not be documented as being
 restricted to only "a built-in operation or function"
Message-ID: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>


New submission from Nathaniel Manista <nathaniel at google.com>:

The documentation for ValueError currently describes it as being "Raised when a built-in operation or function receives an argument that has the right type but an inappropriate value, and the situation is not described by a more precise exception such as IndexError.", but the Python community has (quite rightly!) adopted it as the exception to raise in any system when that system is passed a value for a parameter that is type-correct but of an invalid value.

(Because what, is every library going to present a "my_library.ValueError" exception instead? That would be ridiculous.)

ValueError's documentation should drop the "a built-in operation or function" wording.

Perhaps go with something like "When raised indicates that a function or method was passed a value of the correct type but an invalid value"?

----------
assignee: docs at python
components: Documentation
messages: 321784
nosy: Nathaniel Manista, docs at python
priority: normal
severity: normal
status: open
title: ValueError should not be documented as being restricted to only "a built-in operation or function"
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Mon Jul 16 21:54:47 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 17 Jul 2018 01:54:47 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1531792487.88.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

SO user abarnert, who I presume is bpo abarnert (Andrew Barnert) claims that "Create a new dictionary. The dict object is the dictionary class." sounds a bit like dict returns the dictionary class.  It is different from "Return a new set object, ... . set is a built-in class."  I like the latter better and will use it as the pattern.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Mon Jul 16 22:08:22 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 02:08:22 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531793302.21.0.56676864532.issue34123@psf.upfronthosting.co.za>


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


New changeset bfa8a358e2cec40484c4655138ca3c6b10f8462a by Raymond Hettinger (Miss Islington (bot)) in branch '3.7':
bpo-34123: Fix missed documentation update for dict.popitem(). (GH-8292) (GH#8307)
https://github.com/python/cpython/commit/bfa8a358e2cec40484c4655138ca3c6b10f8462a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Mon Jul 16 22:08:43 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 02:08:43 +0000
Subject: [docs] [issue34123] ambiguous documentation for dict.popitem
In-Reply-To: <1531720827.11.0.56676864532.issue34123@psf.upfronthosting.co.za>
Message-ID: <1531793323.91.0.902498594338.issue34123@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34123>
_______________________________________

From report at bugs.python.org  Tue Jul 17 02:57:21 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 06:57:21 +0000
Subject: [docs] [issue34133] ValueError should not be documented as being
 restricted to only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531810641.62.0.902498594338.issue34133@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 03:05:10 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 07:05:10 +0000
Subject: [docs] [issue34133] ValueError should not be documented as being
 restricted to only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531811110.25.0.902498594338.issue34133@psf.upfronthosting.co.za>


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


----------
keywords: +patch
pull_requests: +7848
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 03:16:14 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 07:16:14 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1531811774.8.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

> How about a note under the index table:

> Functions that must be classes are tagged *class*.
<  The iterator functions enumerate, filter, map, reversed, and zip 
> are classes in CPython, but they are not tagged because they 
> could be implemented as generator functions.

This doesn't seem like it adds any value at all and I don't see what problem is being solved.  Adding a cryptic note at the top doesn't make the docs any more readable.  I recommend leaving the iterator factories as-is.  AFAICT, the current docs are not a source of confusion and the text descriptions suffice to explain what is being done.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Tue Jul 17 03:47:16 2018
From: report at bugs.python.org (Ronald Oussoren)
Date: Tue, 17 Jul 2018 07:47:16 +0000
Subject: [docs] [issue33111] Merely importing tkinter breaks parallel code
 (multiprocessing, sharedmem)
In-Reply-To: <1531733065.54.0.56676864532.issue33111@psf.upfronthosting.co.za>
Message-ID: <8D00D6AA-C5C4-4B28-8172-133D60101CB3@mac.com>


Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

I can provide a patch, but that will likely be during EuroPython as I?m currently taking a roundabout route towards Edinburgh. 

Btw. I?m not sure yet how impactful changing the default spawning mechanism would be for 3.8.  How likely is that to break user code?   

Op 16 jul. 2018 om 10:24 heeft Antoine Pitrou <report at bugs.python.org> het volgende geschreven:

> 
> Antoine Pitrou <pitrou at free.fr> added the comment:
> 
> macOS users, feel free to propose a doc PR for multiprocessing.
> 
> ----------
> assignee:  -> docs at python
> components: +Documentation
> nosy: +docs at python
> versions: +Python 3.7, Python 3.8 -Python 3.5
> 
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue33111>
> _______________________________________

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33111>
_______________________________________

From report at bugs.python.org  Tue Jul 17 03:48:36 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 17 Jul 2018 07:48:36 +0000
Subject: [docs] [issue33111] Merely importing tkinter breaks parallel code
 (multiprocessing, sharedmem)
In-Reply-To: <1521573656.32.0.467229070634.issue33111@psf.upfronthosting.co.za>
Message-ID: <1531813716.1.0.56676864532.issue33111@psf.upfronthosting.co.za>


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

It will definitely break *some* user code. Also, everyone not using tkinter (which I think is the majority of users) isn't affected by this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33111>
_______________________________________

From report at bugs.python.org  Tue Jul 17 11:55:58 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 17 Jul 2018 15:55:58 +0000
Subject: [docs] [issue34133] ValueError should not be documented as being
 restricted to only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531842958.99.0.902498594338.issue34133@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7850

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 11:56:07 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 17 Jul 2018 15:56:07 +0000
Subject: [docs] [issue34133] ValueError should not be documented as being
 restricted to only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531842967.27.0.902498594338.issue34133@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7851

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 11:56:14 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 17 Jul 2018 15:56:14 +0000
Subject: [docs] [issue34133] ValueError should not be documented as being
 restricted to only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531842974.25.0.902498594338.issue34133@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7852

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 13:41:39 2018
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 17 Jul 2018 17:41:39 +0000
Subject: [docs] [issue34133] ValueError documented as being restricted to
 only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531849299.61.0.56676864532.issue34133@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

Just an FYI, Nathaniel, your title and message are bit "pushy". I've gone ahead and tweaked the title.

----------
nosy: +brett.cannon
title: ValueError should not be documented as being restricted to only "a built-in operation or function" -> ValueError documented as being restricted to only "a built-in operation or function"

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 13:42:21 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 17 Jul 2018 17:42:21 +0000
Subject: [docs] [issue33111] Merely importing tkinter breaks parallel code
 (multiprocessing, sharedmem)
In-Reply-To: <8D00D6AA-C5C4-4B28-8172-133D60101CB3@mac.com>
Message-ID: <9dc048fa-fa6f-0421-a012-228696a9007a@udel.edu>


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

Ronald Oussoren> I can provide a patch, but that will likely be during 
EuroPython as I?m currently taking a roundabout route towards Edinburgh.

Can you add a test of the procedure you document for using _tkinter with 
multiprocessing?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33111>
_______________________________________

From report at bugs.python.org  Tue Jul 17 16:26:26 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 17 Jul 2018 20:26:26 +0000
Subject: [docs] [issue34133] ValueError documented as being restricted to
 only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531859186.4.0.56676864532.issue34133@psf.upfronthosting.co.za>


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

Nathaniel, thanks for the bug report. I've fixed the docs.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Tue Jul 17 18:54:42 2018
From: report at bugs.python.org (Nathaniel Manista)
Date: Tue, 17 Jul 2018 22:54:42 +0000
Subject: [docs] [issue34133] ValueError documented as being restricted to
 only "a built-in operation or function"
In-Reply-To: <1531788704.26.0.56676864532.issue34133@psf.upfronthosting.co.za>
Message-ID: <1531868082.88.0.56676864532.issue34133@psf.upfronthosting.co.za>


Nathaniel Manista <nathaniel at google.com> added the comment:

Thank you both!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34133>
_______________________________________

From report at bugs.python.org  Wed Jul 18 01:02:59 2018
From: report at bugs.python.org (Steve Dower)
Date: Wed, 18 Jul 2018 05:02:59 +0000
Subject: [docs] [issue34142] Windows launcher version lookup flawed
In-Reply-To: <1531879775.21.0.56676864532.issue34142@psf.upfronthosting.co.za>
Message-ID: <1531890179.57.0.56676864532.issue34142@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:

The behavior is correct, so the documentation needs fixing.

Which page has that example on it? Is it assuming that you only have 3.1 installed?

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34142>
_______________________________________

From report at bugs.python.org  Wed Jul 18 01:22:46 2018
From: report at bugs.python.org (LarryZA)
Date: Wed, 18 Jul 2018 05:22:46 +0000
Subject: [docs] [issue34142] Windows launcher version lookup flawed
In-Reply-To: <1531879775.21.0.56676864532.issue34142@psf.upfronthosting.co.za>
Message-ID: <1531891366.04.0.56676864532.issue34142@psf.upfronthosting.co.za>


LarryZA <plattrap at yahoo.com> added the comment:

https://docs.python.org/3/using/windows.html

Section 3.4.4.2

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34142>
_______________________________________

From report at bugs.python.org  Wed Jul 18 03:07:18 2018
From: report at bugs.python.org (Eryk Sun)
Date: Wed, 18 Jul 2018 07:07:18 +0000
Subject: [docs] [issue34142] Windows launcher version lookup flawed
In-Reply-To: <1531879775.21.0.56676864532.issue34142@psf.upfronthosting.co.za>
Message-ID: <1531897638.44.0.56676864532.issue34142@psf.upfronthosting.co.za>


Eryk Sun <eryksun at gmail.com> added the comment:

This line in the docs is incorrect:

    If PY_PYTHON=3 and PY_PYTHON3=3.1, the commands python and python3 
    will both use specifically 3.1

It implies that setting the `python` virtual command to "3" or "2" will use the configured version of the `python3` or `python2` virtual command. As implemented, these three virtual commands are separately configured.

The `python` command is different in one way, since it's also the overall default. If the version set for `python2` or `python3` doesn't match an installed version, that's the end of the search. OTOH, the `python` command will continue to search for any version. For a shebang it prefers "2" over "3", and vice versa for the REPL or a script without a shebang.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34142>
_______________________________________

From report at bugs.python.org  Wed Jul 18 09:51:41 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 18 Jul 2018 13:51:41 +0000
Subject: [docs] [issue34147] doc Describe briefly sampling w/out replacement
 in random
Message-ID: <1531921901.63.0.56676864532.issue34147@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

I think a short footnote explaining these terms could be useful to those without statistics knowledge.

----------
assignee: docs at python
components: Documentation
messages: 321882
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Describe briefly sampling w/out replacement in random
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34147>
_______________________________________

From report at bugs.python.org  Wed Jul 18 09:56:35 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 18 Jul 2018 13:56:35 +0000
Subject: [docs] [issue34147] doc Describe briefly sampling w/out replacement
 in random
In-Reply-To: <1531921901.63.0.56676864532.issue34147@psf.upfronthosting.co.za>
Message-ID: <1531922195.39.0.902498594338.issue34147@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7861
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34147>
_______________________________________

From report at bugs.python.org  Thu Jul 19 01:31:52 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 19 Jul 2018 05:31:52 +0000
Subject: [docs] [issue34147] doc Describe briefly sampling w/out replacement
 in random
In-Reply-To: <1531921901.63.0.56676864532.issue34147@psf.upfronthosting.co.za>
Message-ID: <1531978312.11.0.56676864532.issue34147@psf.upfronthosting.co.za>


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

IMO, this is unnecessary documentation cruft.  I'm concerned that you're continuing to spew lots of minor documentation PRs of dubious value and wasting our time.  Please direct your efforts to known areas where users have actually had a problem with the documentation.

----------
nosy: +rhettinger
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34147>
_______________________________________

From report at bugs.python.org  Thu Jul 19 03:08:46 2018
From: report at bugs.python.org (Larry Hastings)
Date: Thu, 19 Jul 2018 07:08:46 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1531984126.59.0.902498594338.issue33216@psf.upfronthosting.co.za>


Change by Larry Hastings <larry at hastings.org>:


----------
pull_requests: +7872

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33216>
_______________________________________

From report at bugs.python.org  Thu Jul 19 06:16:32 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 19 Jul 2018 10:16:32 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1531995392.9.0.56676864532.issue33729@psf.upfronthosting.co.za>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

This was introduced as part of https://hg.python.org/cpython/rev/4969f6d343b1 . In addition to the signature there is also a line at https://docs.python.org/dev/library/hashlib.html#simple-hashing which could be removed 

> As a shortcut, you can pass the first chunk of data to update directly to the constructor as the first argument (or as data keyword argument)


Thanks

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Thu Jul 19 07:09:33 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 19 Jul 2018 11:09:33 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1531998573.53.0.56676864532.issue33729@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

hashlib.blake2b() and some other constructors accept the first chunk of data as the "string" keyword argument.

>>> hashlib.blake2b(string=b'')
<_blake2.blake2b object at 0x7f2847a9c430>
>>> hashlib.blake2s(string=b'')
<_blake2.blake2s object at 0x7f28468f6290>
>>> hashlib.sha3_224(string=b'')
<_sha3.sha3_224 object at 0x7f28468f6608>
>>> hashlib.sha3_256(string=b'')
<_sha3.sha3_256 object at 0x7f28468f6290>
>>> hashlib.sha3_384(string=b'')
<_sha3.sha3_384 object at 0x7f28468f6608>
>>> hashlib.sha3_512(string=b'')
<_sha3.sha3_512 object at 0x7f28468f6290>
>>> hashlib.shake_128(string=b'')
<_sha3.shake_128 object at 0x7f28468f6608>
>>> hashlib.shake_256(string=b'')
<_sha3.shake_256 object at 0x7f28468f6290>

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Thu Jul 19 07:20:56 2018
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 19 Jul 2018 11:20:56 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1531999256.91.0.56676864532.issue33729@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:

Please treat the first argument as positional-only argument. I don't want to standardize on 'string'.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Thu Jul 19 07:34:31 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 19 Jul 2018 11:34:31 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1532000071.97.0.902498594338.issue33729@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
assignee: docs at python -> serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Thu Jul 19 08:05:02 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 19 Jul 2018 12:05:02 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1532001902.52.0.56676864532.issue33729@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I take this issue because there are many other issues with handling arguments in the hashlib module.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Thu Jul 19 09:31:40 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 19 Jul 2018 13:31:40 +0000
Subject: [docs] [issue33869] doc Add link to list definition in Glossary
 list entry
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1532007100.3.0.902498594338.issue33869@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33869>
_______________________________________

From report at bugs.python.org  Thu Jul 19 15:03:20 2018
From: report at bugs.python.org (Zack Weinberg)
Date: Thu, 19 Jul 2018 19:03:20 +0000
Subject: [docs] [issue34156] Nail down and document the behavior of range
 expressions in RE character classes
Message-ID: <1532027000.32.0.56676864532.issue34156@psf.upfronthosting.co.za>


New submission from Zack Weinberg <zackw at panix.com>:

The documentation of the semantics of range expressions in regular expression character classes is not precise enough.  All it says is

    Ranges of characters can be indicated by giving two characters and separating them by a '-', for example [a-z] will match any lowercase ASCII letter [... more examples, none involving non-ASCII characters]

In testing it seems that the behavior is simply to expand the range to a set of characters by numeric code point, e.g. '[?-?]' will match any single character whose ord() is in between ord('?') and ord('?') (inclusive).  If that is the intended behavior, I would like the documentation to explicitly say so.  If that is _not_ the intended behavior, I would like to know what the intended behavior actually is, and for both the code and the documentation to be changed to reflect the intent.

(I think expansion by numeric code point makes sense and is probably what most existing programs want, but this is a contended issue in the context of POSIX regular expressions, e.g. some C libraries try (not always successfully) to make [0-9] match all of the characters that Python's \d matches, so it's not "obvious".)

----------
assignee: docs at python
components: Documentation, Regular Expressions
messages: 321963
nosy: docs at python, ezio.melotti, mrabarnett, zwol
priority: normal
severity: normal
status: open
title: Nail down and document the behavior of range expressions in RE character classes
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34156>
_______________________________________

From report at bugs.python.org  Thu Jul 19 15:05:07 2018
From: report at bugs.python.org (Zack Weinberg)
Date: Thu, 19 Jul 2018 19:05:07 +0000
Subject: [docs] [issue34156] Nail down and document the behavior of range
 expressions in RE character classes
In-Reply-To: <1532027000.32.0.56676864532.issue34156@psf.upfronthosting.co.za>
Message-ID: <1532027107.77.0.56676864532.issue34156@psf.upfronthosting.co.za>


Zack Weinberg <zackw at panix.com> added the comment:

Also, whether or not the current behavior is the intended behavior, I think programmers would appreciate an explicit statement of whether or not it might change in the future.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34156>
_______________________________________

From report at bugs.python.org  Thu Jul 19 17:34:47 2018
From: report at bugs.python.org (Christophe Nanteuil)
Date: Thu, 19 Jul 2018 21:34:47 +0000
Subject: [docs] [issue34158] Documentation of datetime '%z' format code is
 odd
Message-ID: <1532036087.85.0.56676864532.issue34158@psf.upfronthosting.co.za>


New submission from Christophe Nanteuil <christophe.nanteuil at gmail.com>:

In ? 8.1.8. "strftime() and strptime() Behavior", the documentation states that "%z" format code is a string of the form '?HHMM[SS[.uuuuuu]]' where uuuuuu is a 2-digit string giving the number of UTC offset microseconds.
I think it's a 6-digit string.

----------
assignee: docs at python
components: Documentation
files: datetime.rst.patch
keywords: patch
messages: 321968
nosy: Christophe Nanteuil, docs at python
priority: normal
severity: normal
status: open
title: Documentation of datetime  '%z' format code is odd
versions: Python 3.7
Added file: https://bugs.python.org/file47704/datetime.rst.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34158>
_______________________________________

From report at bugs.python.org  Thu Jul 19 19:35:31 2018
From: report at bugs.python.org (Larry Hastings)
Date: Thu, 19 Jul 2018 23:35:31 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1532043331.5.0.56676864532.issue33216@psf.upfronthosting.co.za>


Larry Hastings <larry at hastings.org> added the comment:


New changeset 76aa2c0a9a8dd3ac90b91e7342c8ce8125bf21f9 by larryhastings in branch '3.5':
bpo-33216: Clarify the documentation for CALL_FUNCTION_* (#8338)
https://github.com/python/cpython/commit/76aa2c0a9a8dd3ac90b91e7342c8ce8125bf21f9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33216>
_______________________________________

From report at bugs.python.org  Fri Jul 20 00:52:03 2018
From: report at bugs.python.org (Orlando)
Date: Fri, 20 Jul 2018 04:52:03 +0000
Subject: [docs] [issue34161] Tutorial 7.1 str.format() code example syntax
 error
Message-ID: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>


New submission from Orlando <oboffill at icloud.com>:

Tutorial 7.1 str.format() example (https://docs.python.org/3.7/tutorial/inputoutput.html#fancier-output-formatting):

[1]yes_votes = 42_572_654 ; no_votes = 43_132_495
[2]percentage = (yes_votes/(yes_votes+no_votes)
[3]'{:-9} YES votes  {:2.2%}'.format(yes_votes, percentage))

Proposed Fix: 
Remove first open parens on line 2 and last close parens on line 3.

----------
assignee: docs at python
components: Documentation
messages: 321977
nosy: docs at python, oboff
priority: normal
severity: normal
status: open
title: Tutorial 7.1 str.format() code example syntax error
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 01:25:09 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 20 Jul 2018 05:25:09 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532064309.84.0.56676864532.issue34161@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Yup. Are you interested in creating the PR?

----------
keywords: +easy
nosy: +Mariatta
stage:  -> needs patch
title: Tutorial 7.1 str.format() code example syntax error -> (good first issue) Tutorial 7.1 str.format() code example syntax error
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 02:13:54 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 20 Jul 2018 06:13:54 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1532067234.62.0.902498594338.issue33729@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +7881
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Fri Jul 20 05:07:27 2018
From: report at bugs.python.org (Windson Yang)
Date: Fri, 20 Jul 2018 09:07:27 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532077647.48.0.56676864532.issue34161@psf.upfronthosting.co.za>


Windson Yang <wiwindson at gmail.com> added the comment:

Hi, Orlando, this link maybe useful: https://devguide.python.org/documenting/

----------
nosy: +Windson Yang

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 06:26:09 2018
From: report at bugs.python.org (Orlando)
Date: Fri, 20 Jul 2018 10:26:09 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532082369.01.0.56676864532.issue34161@psf.upfronthosting.co.za>


Orlando <oboffill at icloud.com> added the comment:

Thanks, Mariatta and Windson. I'll make a PR for the change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 06:35:02 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 20 Jul 2018 10:35:02 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532082902.85.0.56676864532.issue29710@psf.upfronthosting.co.za>


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

Ah, "the internal representation" was meant to refer a hypothetical representation, rather than literally to CPython's actual implementation, but now that you point it out, I agree my wording is ambiguous. I like Tim's suggested replacement:

=====================
4. Performing these calculations with at least one extra sign extension bit in a finite two's complement representation (a working bit-width of ``1 + max(x.bit_length(), y.bit_length()`` or more) is sufficient to get the same result as if there were an infinite number of sign bits.
=====================

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Fri Jul 20 06:49:36 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 20 Jul 2018 10:49:36 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1532083776.12.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

Marking memoryview, range, and tuple explicitly as classes, and making the initial phrasing in the docs consistent across all the builtin collection/container types sounds like a good improvement to me.

I agree with Raymond that we should leave whether or not enumerate, filter, map, reversed, and zip support inheritance, isinstance() and issubclass() ambiguous for now (at least within the scope of this issue). That's the main observable difference between implementations that expose a class definition directly, and those that wrap them in a factory function.

While technically that ambiguity is a portability problem across implementations, in practice folks that want to emulate one of these behaviours are far more likely to write their own generator function or iterator class from scratch than they are to try to inherit from one of these.

If we were going to note anything at all for these, it would be to put a "CPython implementation detail" note in each one about the fact that you can subclass them being a CPython implementation detail, but I'd only suggest adding that if we ever get complaints about this hindering portability in practice, rather than our pointing it ourselves as a potential point of inconsistency.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Fri Jul 20 06:53:24 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 20 Jul 2018 10:53:24 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1532084004.39.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

Note that an alternative option for clarifying the status of the "Are they types or factory functions?" builtins would be for someone to review https://docs.python.org/3/reference/datamodel.html#the-standard-type-hierarchy and compare it to the builtins documentation in the library reference.

The language reference is often a better home for clarifying the Python vs CPython behavioural oundary, since it avoids cluttering up the main docs with info that's going to be irrelevant to the vast majority of users.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Fri Jul 20 08:35:12 2018
From: report at bugs.python.org (Eric Janson)
Date: Fri, 20 Jul 2018 12:35:12 +0000
Subject: [docs] [issue34167] Standard library docs: prev/next skip right
 over 16.11
Message-ID: <1532090112.81.0.56676864532.issue34167@psf.upfronthosting.co.za>


New submission from Eric Janson <janson.eric at gmail.com>:

Hitting next from 16.10 in standard library online docs jumps to 16.12. Previous goes from 16.12 back to 16.10.  Curses.Textpad(16.11) must be random-accessed.

----------
assignee: docs at python
components: Documentation
messages: 322002
nosy: Eric Janson, docs at python
priority: normal
severity: normal
status: open
title: Standard library docs: prev/next skip right over 16.11
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34167>
_______________________________________

From report at bugs.python.org  Fri Jul 20 10:09:15 2018
From: report at bugs.python.org (Aaqa Ishtyaq)
Date: Fri, 20 Jul 2018 14:09:15 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532095755.42.0.902498594338.issue34161@psf.upfronthosting.co.za>


Change by Aaqa Ishtyaq <aaqaishtyaq at gmail.com>:


----------
keywords: +patch
pull_requests: +7884
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 11:06:17 2018
From: report at bugs.python.org (Aaqa Ishtyaq)
Date: Fri, 20 Jul 2018 15:06:17 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532099177.87.0.902498594338.issue34161@psf.upfronthosting.co.za>


Change by Aaqa Ishtyaq <aaqaishtyaq at gmail.com>:


----------
pull_requests: +7885

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 12:08:10 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 20 Jul 2018 16:08:10 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532102890.49.0.56676864532.issue34161@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks!

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 12:17:32 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 20 Jul 2018 16:17:32 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532103452.07.0.902498594338.issue34161@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7889

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 13:06:14 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 20 Jul 2018 17:06:14 +0000
Subject: [docs] [issue34118] Fix some class entries in 'Built-in Functions'
In-Reply-To: <1531623878.78.0.56676864532.issue34118@psf.upfronthosting.co.za>
Message-ID: <1532106374.96.0.56676864532.issue34118@psf.upfronthosting.co.za>


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

I will write a PR only touching the collection class entries.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34118>
_______________________________________

From report at bugs.python.org  Fri Jul 20 16:34:50 2018
From: report at bugs.python.org (Chris Kessler)
Date: Fri, 20 Jul 2018 20:34:50 +0000
Subject: [docs] [issue34174] argparse formatter_class issue for
 RawDescriptionHelpFormatter
Message-ID: <1532118890.75.0.56676864532.issue34174@psf.upfronthosting.co.za>


New submission from Chris Kessler <chriskesslergrfx at gmail.com>:

In document https://docs.python.org/2/library/argparse.html#argparse.RawDescriptionHelpFormatter

this will fail with NameError: global name 'textwrap' is not defiend

>>> parser = argparse.ArgumentParser(
...     prog='PROG',
...     formatter_class=argparse.RawDescriptionHelpFormatter,
...     description=textwrap.dedent('''\
...         Please do not mess up this text!
...         --------------------------------
...             I have indented it
...             exactly the way
...             I want it
...         '''))

----------
assignee: docs at python
components: Documentation
messages: 322034
nosy: ckessler, docs at python
priority: normal
severity: normal
status: open
title: argparse formatter_class issue for RawDescriptionHelpFormatter
type: resource usage
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34174>
_______________________________________

From report at bugs.python.org  Fri Jul 20 16:38:13 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 20 Jul 2018 20:38:13 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1532119093.84.0.56676864532.issue34161@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset 49abd307d222e6fe85b5175eed6b6f87fc656a8d by Mariatta (Miss Islington (bot)) in branch '3.7':
bpo-34161: Remove extra parentheses in output formatting tutorial (GH-8350)
https://github.com/python/cpython/commit/49abd307d222e6fe85b5175eed6b6f87fc656a8d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34161>
_______________________________________

From report at bugs.python.org  Fri Jul 20 16:42:30 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 20 Jul 2018 20:42:30 +0000
Subject: [docs] [issue34174] argparse formatter_class issue for
 RawDescriptionHelpFormatter
In-Reply-To: <1532118890.75.0.56676864532.issue34174@psf.upfronthosting.co.za>
Message-ID: <1532119350.12.0.56676864532.issue34174@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks for the report.

To make it work, you'll have to import textwrap first.

We don't always add all the necessary imports in our code snippets and examples, and we don't need to start adding imports into code examples either. So I'm closing this issue.

Thanks again.

----------
nosy: +Mariatta
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34174>
_______________________________________

From report at bugs.python.org  Fri Jul 20 17:02:39 2018
From: report at bugs.python.org (Chris Kessler)
Date: Fri, 20 Jul 2018 21:02:39 +0000
Subject: [docs] [issue34174] argparse formatter_class issue for
 RawDescriptionHelpFormatter
In-Reply-To: <1532118890.75.0.56676864532.issue34174@psf.upfronthosting.co.za>
Message-ID: <1532120559.69.0.56676864532.issue34174@psf.upfronthosting.co.za>


Chris Kessler <chriskesslergrfx at gmail.com> added the comment:

Thanks for the quick response!
I didnt see it anywhere in the documentation on that page so I assumed it was built in with argparse.
Thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34174>
_______________________________________

From report at bugs.python.org  Fri Jul 20 19:40:36 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 20 Jul 2018 23:40:36 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1531608583.62.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <1532130036.1.0.56676864532.issue34115@psf.upfronthosting.co.za>


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

To investigate your claim about closing sys.stdin, I ran the following on Windows 10, mostly with 3.7.0, in both the console and IDLE, using various exit methods.

import code
import sys

for i in range(2):
    try:
        code.InteractiveConsole().interact()
        print(f'Try {i}: closed is', sys.stdin.closed)
    except SystemExit:
        print(f'Exc {i}: closed is', sys.stdin.closed)

^D in IDLE and ^Z+<enter> in console prints 'Try 0/1...False'.
The IC.interact loop catches EOFError and breaks for a normal exit.

'raise SystemExit' and sys.exit() print 'Exc 0/1...False'.

exit() and quit() print 'Exc 0/1...True' on Console.  On Windows Console, sys.stdin.close() does not prevent a second interact call.  This might be considered a bug.

What OS are you running and what is the result and traceback for the code above?

In IDLE, either function exit causes a 'Kill the running process' popup.  If yes, user code execution ceases and the shell window  closes.  If no, SystemExit is caught and 'SysExit...False' is printed.  The latter is true because sys.stdin.close in the user process is 'sys.shell.close()', and the latter does the popup.  The *purpose* of sys.stdin.close is to get the attention of shells that intercept SystemExit, so that users can say 'Close this now'.  Even so, IDLE asks users first to make sure.

Emulating IDLE in a simplified fashion as follows will negate closure.
import _io
class Stdin(_io.TextIOWrapper):
    def close(self): pass
sys.stdin = Stdin()  # To restore, sys.__stdin__ is the original.


---
History of sys.stdin.close:

https://github.com/python/cpython/commit/24cb053b158a3cd63f7be05ac27f47e45bb2f1b3
Site.py, line 236, Mar 9, 2006, George Brandel added Quitter with __call__ consisting of 'raise SystemExit(code)'.

https://github.com/python/cpython/commit/d112bc7958151fa17c4ccb27413c43e45b8476fb#diff-f34a16518c608b2ca946d3f5ca0a1942
site.py, line Aug 16, 2006, Kurt Kaiser added the following lines
        # Shells like IDLE catch the SystemExit, but listen when their
        # stdin wrapper is closed.
        try:
            sys.stdin.close()
        except:
            pass

https://github.com/python/cpython/commit/862543aa85249b46649b60da96743b4b14c6c83b#diff-f34a16518c608b2ca946d3f5ca0a1942
site.py, line 250, Christian Heimes replace stdin.close with the following to avoid Lib/io.py: RuntimeWarning: Trying to close unclosable fd. (I believe io has since been patched to not do this.)
        fd = -1
        if hasattr(sys.stdin, "fileno"):
            fd = sys.stdin.fileno()
        if fd != 0:
            # Don't close stdin if it wraps fd 0
            sys.stdin.close()

https://hg.python.org/cpython/rev/82451c88b3c0, 11 Apr 2013
After discussion on #17585 with Antoine Pitrou and Serhiy Storchaka, Roger Serwy reverted the above because it was no longer needed 
---

Your code assumes that sys.stdin has a buffer attribute.  Not necessarily true when python is started with pythonw.exe.  With the print removed, it also assumes that sys.stdin has file descriptor 0.  Ditto.
---

Possible doc improvements: the exit/quit doc says that closes.
https://docs.python.org/3/library/constants.html#constants-added-by-the-site-module

interact doc mentions catching exceptions and quit/exit issue.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, terry.reedy
stage:  -> needs patch
type: behavior -> enhancement
versions: +Python 3.8 -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Fri Jul 20 21:09:37 2018
From: report at bugs.python.org (Yonatan Zunger)
Date: Sat, 21 Jul 2018 01:09:37 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1531608583.62.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <1532135377.41.0.56676864532.issue34115@psf.upfronthosting.co.za>


Yonatan Zunger <zunger at humu.com> added the comment:

Testing your code sample on OS X (10.13.6) with Python 3.6.2:

- quit() in the console yields

Exc 0: closed is True
Python 3.6.2 (default, Apr 17 2018, 12:29:33) 
[GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> Traceback (most recent call last):
  File "./test.py", line 6, in <module>
    code.InteractiveConsole().interact()
  File "/Users/zunger/.pyenv/versions/3.6.2/lib/python3.6/code.py", line 228, in interact
    line = self.raw_input(prompt)
  File "/Users/zunger/.pyenv/versions/3.6.2/lib/python3.6/code.py", line 275, in raw_input
    return input(prompt)
ValueError: I/O operation on closed file.

- ^D and raise SystemExit in console both yield:

Python 3.6.2 (default, Apr 17 2018, 12:29:33) 
[GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> ^D
now exiting InteractiveConsole...
Try 0: closed is False
Python 3.6.2 (default, Apr 17 2018, 12:29:33) 
[GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> ^D
now exiting InteractiveConsole...
Try 1: closed is False


So it looks like the issue is specific to quit(), as you say. I'm not sure I understand what the purpose of the sys.stdin.close() call is, though: why would we *want* to alert the parent shell in some way beyond a SystemExit as the default (non-overrideable) behavior? This may be a documentation issue, but it seems extremely surprising to me; no other function does this additional thing, even when raising a SystemExit. I would think that any caller which is running InteractiveConsole.interact() and also wants to do something when it finishes would want to handle that additional logic itself.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Fri Jul 20 21:43:17 2018
From: report at bugs.python.org (Yonatan Zunger)
Date: Sat, 21 Jul 2018 01:43:17 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1531608583.62.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <1532137397.45.0.56676864532.issue34115@psf.upfronthosting.co.za>


Yonatan Zunger <zunger at humu.com> added the comment:

Or perhaps in an alternate phrasing: The sys.stdin.close behavior makes sense if quit is being used inside IDLE, but is very surprising from the perspective of the `code` module. (Really, even the SystemExit is surprising there, and should be documented!)

What if we added a stdin-preserving workaround to code.InteractiveConsole.interact, and added documentation of the SystemExit behavior to that module as well, but left _Quitter itself as-is?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Fri Jul 20 22:33:43 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 21 Jul 2018 02:33:43 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532140423.41.0.56676864532.issue34154@psf.upfronthosting.co.za>


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

By documentation, you mean the doc string for each widget, which is the basis for the help(widget) response.  I checked that there do not seem to be any other issues open for the docstrings.  Go ahead.  Use https://www.tcl.tk/man/tcl8.6/TkCmd/contents.htm as the reference.

C.E.: if you have a list of missing thing, can you post?  This is normal priority.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, serhiy.storchaka, terry.reedy
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Fri Jul 20 22:39:25 2018
From: report at bugs.python.org (Creation Elemental)
Date: Sat, 21 Jul 2018 02:39:25 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532140765.09.0.56676864532.issue34154@psf.upfronthosting.co.za>


Creation Elemental <arceusthe at gmail.com> added the comment:

Ah, yes. That is what I meant to say. The doc string printed by help(widget)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Fri Jul 20 22:41:15 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 21 Jul 2018 02:41:15 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532140874.96.0.56676864532.issue34154@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The official Tk documentation is not always correct. OPTIONS attributes in tests should contain full lists of supported options, and running tests produces warnings for missed options, like: ListboxTest.OPTIONS doesn't contain "justify".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Sat Jul 21 01:16:21 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 21 Jul 2018 05:16:21 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1531608583.62.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <1532150181.27.0.56676864532.issue34115@psf.upfronthosting.co.za>


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

There is an important difference between a program saying 'I am done executing' and a user saying 'I am done with the interactive session'.  This is especially true in an IDE where 'session' can include many editing and shell sessions.

'Stop executing'  happens when execution reaches the end of the file, which causes EOFError upon a read attempt.  It can also be done gracefully before the end of input with sys.exit(), which raises SystemExit.

In Interactive Python, 'leave session' can be done with SystemExit or the EOF control signal, which appears to raise EOFError.  This suggests that quit() and exit(), which were added because newbies did not know the proper way to exit, should raise EOFError rather than SystemExit.  The fact that 'quit' displays 'Use quit() or Ctrl-Z plus Return to exit' (EOF on Windows) suggests the same.  But I need to experiment (another day).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Sat Jul 21 04:21:32 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 21 Jul 2018 08:21:32 +0000
Subject: [docs] [issue34158] Documentation of datetime '%z' format code is
 odd
In-Reply-To: <1532036087.85.0.56676864532.issue34158@psf.upfronthosting.co.za>
Message-ID: <1532161292.58.0.56676864532.issue34158@psf.upfronthosting.co.za>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Added as part of 018d353c1c8c87767d2335cd884017c2ce12e045 and a fix regarding duplicate words for that part was added at bac2d5ba30339298db7d4caa9c8cd31d807cf081. 

Relevant format string at https://github.com/python/cpython/pull/2896/files#diff-25e2d173c84057d069b7890450714eddR214.

Relevant test case with 6-digit string for microsecond : https://github.com/python/cpython/pull/2896/files#diff-acc40bec51c7de832de3361db3edae52R309.

Table at https://docs.python.org/3.7/library/datetime.html#strftime-and-strptime-behavior could also be updated with microseconds being optional in the second column

%z | UTC offset in the form ?HHMM[SS] (empty string if the object is naive). | (empty), +0000, -0400, +1030

You can raise a GitHub PR for the same.

Thanks

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34158>
_______________________________________

From report at bugs.python.org  Sat Jul 21 06:14:37 2018
From: report at bugs.python.org (Anjali Bansal)
Date: Sat, 21 Jul 2018 10:14:37 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1532168077.85.0.56676864532.issue33187@psf.upfronthosting.co.za>


Anjali Bansal <anjali.mca17.du at gmail.com> added the comment:

I would work on it. please guide me how to proceed?

Thanks
Anjali

----------
nosy: +Anjali Bansal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33187>
_______________________________________

From report at bugs.python.org  Sat Jul 21 10:15:21 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 21 Jul 2018 14:15:21 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1532182521.09.0.56676864532.issue33187@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Please read the devguide on how to get started contributing: https://devguide.python.org.

You'll also need to sign the CLA:
https://devguide.python.org/pullrequest/?highlight=Cla#licensing

----------
nosy: +Mariatta

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33187>
_______________________________________

From report at bugs.python.org  Sat Jul 21 10:36:01 2018
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 21 Jul 2018 14:36:01 +0000
Subject: [docs] [issue34158] Documentation of datetime '%z' format code is
 odd
In-Reply-To: <1532036087.85.0.56676864532.issue34158@psf.upfronthosting.co.za>
Message-ID: <1532183761.06.0.902498594338.issue34158@psf.upfronthosting.co.za>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
pull_requests: +7908
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34158>
_______________________________________

From report at bugs.python.org  Sat Jul 21 11:40:54 2018
From: report at bugs.python.org (Noah Haasis)
Date: Sat, 21 Jul 2018 15:40:54 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532187654.36.0.56676864532.issue34154@psf.upfronthosting.co.za>


Noah Haasis <haasis_noah at yahoo.de> added the comment:

This is a list of all valid keywordarguments of Listbox.__init__() listed in the test file: 
'activestyle', 'background', 'borderwidth', 'cursor',
'disabledforeground', 'exportselection',
'font', 'foreground', 'height',
'highlightbackground', 'highlightcolor', 'highlightthickness',
'listvariable', 'relief',
'selectbackground', 'selectborderwidth', 'selectforeground',
'selectmode', 'setgrid', 'state',
'takefocus', 'width', 'xscrollcommand', 'yscrollcommand'

The ones that are missing in the doc string:
'activestyle', 'disabledforeground', 
'listvariable','state'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Sat Jul 21 13:08:32 2018
From: report at bugs.python.org (Noah Haasis)
Date: Sat, 21 Jul 2018 17:08:32 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532192912.79.0.902498594338.issue34154@psf.upfronthosting.co.za>


Change by Noah Haasis <haasis_noah at yahoo.de>:


----------
keywords: +patch
pull_requests: +7909
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Sat Jul 21 17:14:35 2018
From: report at bugs.python.org (Yonatan Zunger)
Date: Sat, 21 Jul 2018 21:14:35 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1532150181.27.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <CAFk=nbScD1NfeWvGRMak3BWu7x0EzzaPuFXpYAXvPsXujKjGNA@mail.gmail.com>


Yonatan Zunger <zunger at humu.com> added the comment:

Definitely agree about the difference.

I'd say that either SystemExit or EOFError would be a reasonable thing for
the interactive session to do, but the combination of closing stdin and
SystemExit is really weird. Honestly, I would have just expected interact()
to return like an ordinary function when it was done; the logic of "it's
time to close the terminal window" feels like it belongs at a *much* higher
level of the stack.

On Fri, Jul 20, 2018 at 10:16 PM Terry J. Reedy <report at bugs.python.org>
wrote:

>
> Terry J. Reedy <tjreedy at udel.edu> added the comment:
>
> There is an important difference between a program saying 'I am done
> executing' and a user saying 'I am done with the interactive session'.
> This is especially true in an IDE where 'session' can include many editing
> and shell sessions.
>
> 'Stop executing'  happens when execution reaches the end of the file,
> which causes EOFError upon a read attempt.  It can also be done gracefully
> before the end of input with sys.exit(), which raises SystemExit.
>
> In Interactive Python, 'leave session' can be done with SystemExit or the
> EOF control signal, which appears to raise EOFError.  This suggests that
> quit() and exit(), which were added because newbies did not know the proper
> way to exit, should raise EOFError rather than SystemExit.  The fact that
> 'quit' displays 'Use quit() or Ctrl-Z plus Return to exit' (EOF on Windows)
> suggests the same.  But I need to experiment (another day).
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue34115>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Sun Jul 22 01:19:37 2018
From: report at bugs.python.org (Noah Haasis)
Date: Sun, 22 Jul 2018 05:19:37 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532236777.3.0.56676864532.issue34154@psf.upfronthosting.co.za>


Noah Haasis <haasis_noah at yahoo.de> added the comment:

This are all the classes where the keywords are missing in the docs and their missing keywords:
TopLevel
['padx', 'pady']

Checkbutton
['compound', 'offrelief', 'overrelief', 'tristateimage', 'tristatevalue']

Entry
['disabledbackground', 'disabledforeground', 'readonlybackground']

Frame
['padx', 'pady']

Label
['compound']

Radiobutton
['compound', 'offrelief', 'overrelief', 'tristateimage', 'tristatevalue']

Text
['blockcursor', 'endline', 'inactiveselectbackground', 'insertunfocussed', 'startline', 'tabstyle']

Spinbox
['validatecommand', 'values']

Menubutton
['activebackground', 'activeforeground', 'anchor', 'background', 'bitmap', 'borderwidth', 'compound', 'cursor', 'direction', 'disabledforeground', 'font', 'foreground', 'height', 'highlightbackground', 'highlightcolor', 'highlightthickness', 'image', 'indicatoron', 'justify', 'menu', 'padx', 'pady', 'relief', 'state', 'takefocus', 'text', 'textvariable', 'underline', 'width', 'wraplength']

Message
['anchor', 'aspect', 'background', 'borderwidth', 'cursor', 'font', 'foreground', 'highlightbackground', 'highlightcolor', 'highlightthickness', 'justify', 'padx', 'pady', 'relief', 'takefocus', 'text', 'textvariable', 'width']

The missing keywords appear in the OPTIONS list in the test but not in the docstring.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Sun Jul 22 05:12:01 2018
From: report at bugs.python.org (Eryk Sun)
Date: Sun, 22 Jul 2018 09:12:01 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1531608583.62.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <1532250721.21.0.56676864532.issue34115@psf.upfronthosting.co.za>


Eryk Sun <eryksun at gmail.com> added the comment:

> On Windows Console, sys.stdin.close() does not prevent a second 
> interact call.  This might be considered a bug.

This is a bug in io._WindowsConsoleIO. 

In Python 3, the sys.std* file objects that get created at startup use closefd=False:

    >>> sys.stdin.buffer.raw.closefd
    False
    >>> sys.stdout.buffer.raw.closefd
    False
    >>> sys.stderr.buffer.raw.closefd
    False

Since the REPL uses C FILE streams (or in 3.6+ the underlying console file handle in Windows), closing sys.stdin does not cause the REPL to exit, and the PyOS_ReadLine call in the interactive loop continues to work in both POSIX and Windows. 

That said, closing sys.stdin should cause input() to raise ValueError due to sys.stdin.fileno() failing (i.e. take the non-tty path) and subsequently sys.stdin.readline() failing. A second call to code.InteractiveConsole.interact() should thus fail. The issue is that the fileno() method of _WindowsConsoleIO isn't raising ValueError like it should when the file is closed and closefd is false. I've created issue 34187 with a suggested fix.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Sun Jul 22 05:15:01 2018
From: report at bugs.python.org (Martin Panter)
Date: Sun, 22 Jul 2018 09:15:01 +0000
Subject: [docs] [issue34158] Documentation of datetime '%z' format code is
 odd
In-Reply-To: <1532036087.85.0.56676864532.issue34158@psf.upfronthosting.co.za>
Message-ID: <1532250899.62.0.56676864532.issue34158@psf.upfronthosting.co.za>


Martin Panter <vadmium+py at gmail.com> added the comment:

FWIW more oddities with this paragraph could be fixed by:

* removing the first ?and? from ?HH is . . ., [and] MM is . . ., SS is . . . and uuuuuu is?,
* changing the condition for omitting ?uuuuuu? from ?a whole number of [minutes]? to ?seconds?, and
* changing ?the [SS parts are] omitted? to singular ?SS part is?.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34158>
_______________________________________

From report at bugs.python.org  Sun Jul 22 10:54:51 2018
From: report at bugs.python.org (A.M. Kuchling)
Date: Sun, 22 Jul 2018 14:54:51 +0000
Subject: [docs] [issue20906] Issues in Unicode HOWTO
In-Reply-To: <1394702187.81.0.00522221343959.issue20906@psf.upfronthosting.co.za>
Message-ID: <1532271291.85.0.902498594338.issue20906@psf.upfronthosting.co.za>


Change by A.M. Kuchling <amk at amk.ca>:


----------
keywords: +patch
pull_requests: +7921
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20906>
_______________________________________

From report at bugs.python.org  Sun Jul 22 11:51:49 2018
From: report at bugs.python.org (Anjali Bansal)
Date: Sun, 22 Jul 2018 15:51:49 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1532274709.29.0.56676864532.issue33187@psf.upfronthosting.co.za>


Anjali Bansal <anjali.mca17.du at gmail.com> added the comment:

Thank you for the information. I had started working on this issue. You can assign it to me if needed. I will create a PR soon.
Github Username: bansalanjali2512

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33187>
_______________________________________

From report at bugs.python.org  Sun Jul 22 12:49:19 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 22 Jul 2018 16:49:19 +0000
Subject: [docs] [issue34154] Tkinter __init__ documentations sometimes
 missing valid keyword values
In-Reply-To: <1531969710.94.0.56676864532.issue34154@psf.upfronthosting.co.za>
Message-ID: <1532278159.4.0.56676864532.issue34154@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Few new options were added: see issue34189.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34154>
_______________________________________

From report at bugs.python.org  Mon Jul 23 06:32:31 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 23 Jul 2018 10:32:31 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1532341951.69.0.56676864532.issue34172@psf.upfronthosting.co.za>


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

Indeed, I think this simply needs a documentation fix.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 3.6, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Mon Jul 23 07:10:27 2018
From: report at bugs.python.org (tzickel)
Date: Mon, 23 Jul 2018 11:10:27 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1532344227.61.0.56676864532.issue34172@psf.upfronthosting.co.za>


tzickel <icebreak at yahoo.com> added the comment:

What other object in the standard lib, leaks resources when deleted in CPython ? Even that documentation says the garbage collector will eventually destroy it, just like here... I think there is an implementation bug.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Mon Jul 23 10:09:10 2018
From: report at bugs.python.org (Paul Ganssle)
Date: Mon, 23 Jul 2018 14:09:10 +0000
Subject: [docs] [issue34158] Documentation of datetime '%z' format code is
 odd
In-Reply-To: <1532036087.85.0.56676864532.issue34158@psf.upfronthosting.co.za>
Message-ID: <1532354950.04.0.902498594338.issue34158@psf.upfronthosting.co.za>


Change by Paul Ganssle <p.ganssle at gmail.com>:


----------
nosy: +p-ganssle

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34158>
_______________________________________

From report at bugs.python.org  Mon Jul 23 12:00:05 2018
From: report at bugs.python.org (paul j3)
Date: Mon, 23 Jul 2018 16:00:05 +0000
Subject: [docs] [issue34174] argparse formatter_class issue for
 RawDescriptionHelpFormatter
In-Reply-To: <1532118890.75.0.56676864532.issue34174@psf.upfronthosting.co.za>
Message-ID: <1532361605.35.0.56676864532.issue34174@psf.upfronthosting.co.za>


paul j3 <ajipanca at gmail.com> added the comment:

argparse does import 'textwrap', but as '_textwrap', so it could be used with:

    argparse._textwrap.dedent(...)

Importing your own is cleaner.

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34174>
_______________________________________

From report at bugs.python.org  Mon Jul 23 12:26:46 2018
From: report at bugs.python.org (tzickel)
Date: Mon, 23 Jul 2018 16:26:46 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1532363206.63.0.56676864532.issue34172@psf.upfronthosting.co.za>


tzickel <icebreak at yahoo.com> added the comment:

I think I've found the code bug causing the leak:

https://github.com/python/cpython/blob/caa331d492acc67d8f4edd16542cebfabbbe1e79/Lib/multiprocessing/pool.py#L180

There is a circular reference between the Pool object, and the self._worker_handler Thread object (and it's also saved in the frame locals for the thread object, which prevents it from being garbage collected).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Mon Jul 23 12:38:06 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 23 Jul 2018 16:38:06 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1532363886.07.0.56676864532.issue34172@psf.upfronthosting.co.za>


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

> What other object in the standard lib, leaks resources when deleted in CPython ?

Threads come to mind, for example:

>>> import time, threading, weakref
>>> t = threading.Thread(target=time.sleep, args=(100000,))
>>> t.start()
>>> wr = weakref.ref(t)
>>> del t
>>> wr()
<Thread(Thread-1, started 139937234327296)>

Note I'm not against fixing this issue, just saying it's not that surprising for Pool to keep lingering around when you lost any user-visible reference to it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Mon Jul 23 13:13:20 2018
From: report at bugs.python.org (Jared Deckard)
Date: Mon, 23 Jul 2018 17:13:20 +0000
Subject: [docs] [issue32752] no information about accessing typing.Generic
 type arguments
In-Reply-To: <1517612346.62.0.467229070634.issue32752@psf.upfronthosting.co.za>
Message-ID: <1532366000.15.0.56676864532.issue32752@psf.upfronthosting.co.za>


Jared Deckard <jared at shademaps.com> added the comment:

typing_inspect is now filled with python version checks for 3.7. The implementation got significantly more complex when differentiating generics at runtime.

3.6 was undocumented, but the OO API was intuitive:

>>> T = typing.Union[int, float]
>>> assert T.__class__ == typing.Union
>>> assert T.__args__ == (int, float)

3.7 is less convenient and less consistent:

>>> T = typing.Union[int, float]
>>> assert T.__class__ == typing._GenericAlias
>>> assert T.__origin__ == typing.Union
>>> L = typing.List[int]
>>> assert L.__class__ == typing._GenericAlias
>>> assert L.__origin__ == list

----------
nosy: +Jared Deckard

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32752>
_______________________________________

From report at bugs.python.org  Mon Jul 23 13:56:09 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 23 Jul 2018 17:56:09 +0000
Subject: [docs] [issue13407] tarfile doesn't support multistream bzipped tar
 files
In-Reply-To: <1321352961.33.0.0944615995053.issue13407@psf.upfronthosting.co.za>
Message-ID: <1532368569.38.0.56676864532.issue13407@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

This is no longer reproducible under 3.7.0.

>>> import tarfile
>>> tf = tarfile.open("kdelibs-4.7.3.tar.bz2", "r")
>>> print(len(tf.getnames()))
9237

Not sure I should be the one closing this.

----------
nosy: +adelfino

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13407>
_______________________________________

From report at bugs.python.org  Mon Jul 23 14:05:22 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 23 Jul 2018 18:05:22 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532369122.26.0.56676864532.issue29710@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> 4. Performing these calculations with at least one extra sign extension bit in a finite two's complement representation (a working bit-width of ``1 + max(x.bit_length(), y.bit_length()`` or more) is sufficient to get the same result as if there were an infinite number of sign bits.

LGTM

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 23 14:31:04 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 23 Jul 2018 18:31:04 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532370664.5.0.56676864532.issue29710@psf.upfronthosting.co.za>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

Seems good to me. I've made the changes in the PR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 23 14:54:19 2018
From: report at bugs.python.org (Tim Peters)
Date: Mon, 23 Jul 2018 18:54:19 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532372058.96.0.56676864532.issue29710@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

@CuriousLearner, does the PR also include Nick's first suggested change?  Here:

"""
1. Replace the opening paragraph of https://docs.python.org/3/library/stdtypes.html#bitwise-operations-on-integer-types (the one I originally quoted when opening this issue) with the text:

=====================
Bitwise operations only make sense for integers. The result of bitwise operations is calculated as though carried out in two's complement with an infinite number of sign bits.
=====================
"""

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 23 14:54:22 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 23 Jul 2018 18:54:22 +0000
Subject: [docs] [issue13407] tarfile doesn't support multistream bzipped tar
 files
In-Reply-To: <1321352961.33.0.0944615995053.issue13407@psf.upfronthosting.co.za>
Message-ID: <1532372062.74.0.56676864532.issue13407@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

This is a 2.7 only documentation issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13407>
_______________________________________

From report at bugs.python.org  Mon Jul 23 15:00:29 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 23 Jul 2018 19:00:29 +0000
Subject: [docs] [issue13407] tarfile doesn't support multistream bzipped tar
 files
In-Reply-To: <1321352961.33.0.0944615995053.issue13407@psf.upfronthosting.co.za>
Message-ID: <1532372429.73.0.56676864532.issue13407@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

Sorry, you are right. I'll try on 2.7 when I get home, and make a PR if needed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13407>
_______________________________________

From report at bugs.python.org  Mon Jul 23 15:01:04 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 23 Jul 2018 19:01:04 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532372464.5.0.56676864532.issue29710@psf.upfronthosting.co.za>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

Hey Tim,

> @CuriousLearner, does the PR also include Nick's first suggested change?  Here:

"""
=====================
Bitwise operations only make sense for integers. The result of bitwise operations is calculated as though carried out in two's complement with an infinite number of sign bits.
=====================
"""

I think it was then discussed to keep this line as:

"""
===========
Bitwise operations only make sense for integers. Negative numbers are treated as their 2's complement value.
===========
"""

Does this needs to be changed?

Here is the link of the PR: https://github.com/python/cpython/pull/1691/files#diff-7498e907ba97646df434a0eb583c6909

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 23 15:03:46 2018
From: report at bugs.python.org (Tim Peters)
Date: Mon, 23 Jul 2018 19:03:46 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532372626.32.0.56676864532.issue29710@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

Nick suggested two changes on 2018-07-15 (look above).  Mark & I agreed about the first change, so it wasn't mentioned again after that.  All the rest has been refining the second change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 23 15:21:03 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 23 Jul 2018 19:21:03 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532373663.18.0.56676864532.issue29710@psf.upfronthosting.co.za>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

On, yes, I think I missed the first point, earlier. Thank You! I did the changes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Mon Jul 23 16:38:52 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 23 Jul 2018 20:38:52 +0000
Subject: [docs] [issue32752] no information about accessing typing.Generic
 type arguments
In-Reply-To: <1517612346.62.0.467229070634.issue32752@psf.upfronthosting.co.za>
Message-ID: <1532378332.44.0.902498594338.issue32752@psf.upfronthosting.co.za>


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


----------
nosy:  -gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32752>
_______________________________________

From report at bugs.python.org  Mon Jul 23 16:43:44 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 23 Jul 2018 20:43:44 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1532378624.68.0.56676864532.issue32500@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset a6fdddb7df00aefad2ec6e362dbf10d4bd8bff32 by Serhiy Storchaka in branch 'master':
bpo-32500: Fix error messages for sequence and mapping C API. (GH-7846)
https://github.com/python/cpython/commit/a6fdddb7df00aefad2ec6e362dbf10d4bd8bff32


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Mon Jul 23 16:45:19 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 23 Jul 2018 20:45:19 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1532378719.35.0.902498594338.issue32500@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Mon Jul 23 18:56:46 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 23 Jul 2018 22:56:46 +0000
Subject: [docs] [issue13407] tarfile doesn't support multistream bzipped tar
 files
In-Reply-To: <1321352961.33.0.0944615995053.issue13407@psf.upfronthosting.co.za>
Message-ID: <1532386606.73.0.902498594338.issue13407@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7954
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13407>
_______________________________________

From report at bugs.python.org  Mon Jul 23 21:55:29 2018
From: report at bugs.python.org (abcdef)
Date: Tue, 24 Jul 2018 01:55:29 +0000
Subject: [docs] [issue34203] documentation: recommend Python 3 over 2 in faq
Message-ID: <1532397328.96.0.56676864532.issue34203@psf.upfronthosting.co.za>


New submission from abcdef <x at mailinator.com>:

FAQ "How stable is Python" https://docs.python.org/3/faq/general.html#how-stable-is-python" states

"There are two recommended production-ready versions at this point in time, because at the moment there are two branches of stable releases: 2.x and 3.x. Python 3.x may be less useful than 2.x, since currently there is more third party software available for Python 2 than for Python 3. Python 2 code will generally not run unchanged in Python 3."

According to git blame, this is from 2009. Could we change this to recommend Python 3 over Python 2 now?

----------
assignee: docs at python
components: Documentation
messages: 322273
nosy: abcdef, docs at python
priority: normal
severity: normal
status: open
title: documentation: recommend Python 3 over 2 in faq
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34203>
_______________________________________

From report at bugs.python.org  Mon Jul 23 22:03:37 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 24 Jul 2018 02:03:37 +0000
Subject: [docs] [issue34203] documentation: recommend Python 3 over 2 in faq
In-Reply-To: <1532397328.96.0.56676864532.issue34203@psf.upfronthosting.co.za>
Message-ID: <1532397817.22.0.56676864532.issue34203@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Yep. Please propose a patch.

I think this should be updated even for Python 2.7 docs, which is nearing EOL.

----------
nosy: +Mariatta
stage:  -> needs patch
versions: +Python 2.7, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34203>
_______________________________________

From report at bugs.python.org  Tue Jul 24 02:21:52 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 24 Jul 2018 06:21:52 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1532413312.99.0.902498594338.issue27671@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
pull_requests: +7957
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From ben at singlethread.eu  Wed Jul 18 02:27:19 2018
From: ben at singlethread.eu (Ben)
Date: Wed, 18 Jul 2018 08:27:19 +0200
Subject: [docs] Broken links : French python docs (all 3.x versions)
Message-ID: <b2404919-7446-06ab-08e4-314a57f45ba0@singlethread.eu>

Hi,

I'm trying to download the python 3.x french versions, and all links are 
broken.

Could you fix this please, thanks.

Best regards.

Benjamin


From cyrilcoelho67 at gmail.com  Sat Jul 21 16:40:04 2018
From: cyrilcoelho67 at gmail.com (Cyril Coelho)
Date: Sat, 21 Jul 2018 22:40:04 +0200
Subject: [docs] Dead link download doc
Message-ID: <9BB75E67-A0E0-4C80-A21B-DC239F298CEF@gmail.com>

Hi the link for download the documentation in french is dead for the version 2.7.15.
Thank you for correct this :)

Envoy? de mon iPhone

From David.Raymond at tomtom.com  Tue Jul 24 09:50:41 2018
From: David.Raymond at tomtom.com (David Raymond)
Date: Tue, 24 Jul 2018 13:50:41 +0000
Subject: [docs] subprocess.run doc doesn't show the new capture_output in
 the parameter list
Message-ID: <VI1PR07MB07846E3E2ADE12A87CD5F7B287550@VI1PR07MB0784.eurprd07.prod.outlook.com>

In the subprocess doc for 3.7, the arguments shown for subprocess.run() don?t include the new capture_output parameter added in 3.7.

capture_output gets mentioned a few times in the .run section, but since it?s not listed in the argument list it makes things confusing while reading through it as to what it?s supposed to be. It has the italics of an argument, but not being in the list caused a lot of ?wait, what are they talking about? It?s not an argument, so what did I miss?? confusion while reading the doc in order.

There is the comment that ?The arguments shown above are merely the most common ones, described below in Frequently Used Arguments? However, immediately after that there is ?most of the arguments to this function are passed through to that interface. (timeout, input, check, and capture_output are not.)? so it?s not mentioned further down in the doc in either Frequently Used Arguments or in Popen, only tiny notes in the ?changed in version 3.7? and the .run example.

Simply adding capture_output with its default to the shown keyword arguments for .run() should be enough to eliminate the confusion.

Thank you,

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

From Eli.Baum at ibm.com  Mon Jul 16 09:35:53 2018
From: Eli.Baum at ibm.com (Eli Baum)
Date: Mon, 16 Jul 2018 13:35:53 +0000
Subject: [docs] minor typo -- site
Message-ID: <OFCDDF738E.3E90019D-ON002582CC.004A8CCE-002582CC.004AB253@notes.na.collabserv.com>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180716/50f88fda/attachment.html>

From hd5man at gmail.com  Tue Jul 24 09:47:28 2018
From: hd5man at gmail.com (Andrew Wellington)
Date: Tue, 24 Jul 2018 09:47:28 -0400
Subject: [docs] Python 3.7.0 Documentation
Message-ID: <CAB0wqO7jQz39_ESFe9AdB2ymjw5gYAuzKcKEDoxMQYg+OHu3DA@mail.gmail.com>

Hello,

I'm trying to access the letter page formatted Python 3.7.0 Documentation,
however the link on the page (https://docs.python.org/3/download.html)
pointing to the resource at
https://docs.python.org/3/archives/python-3.7.0-docs-pdf-letter.zip results
in a 404 error.

Is the file 'python-3.7.0-docs-pdf-letter.zip' available at another URL?

Many thanks,

Andrew Wellington
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180724/f9e0d688/attachment-0001.html>

From jjlemire at gmail.com  Mon Jul 23 16:40:05 2018
From: jjlemire at gmail.com (JJ Lemire)
Date: Mon, 23 Jul 2018 16:40:05 -0400
Subject: [docs] Missing html version of the current documentation, 3.7.0,
 version gz.
Message-ID: <CAO3SRehCs4GMFXiAGmbCbZEDXT=z0+yR24LNoJgv2dVc1qzBCQ@mail.gmail.com>

Hi,

I have a 404 not found when I try to download the html version of the
current documentation, 3.7.0, compression gz.

Thanks
/JL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180723/6f3f8440/attachment-0001.html>

From niedzwiedzwo at gmail.com  Tue Jul 17 17:07:11 2018
From: niedzwiedzwo at gmail.com (=?UTF-8?Q?Wojtek_Bro=C5=BCek?=)
Date: Tue, 17 Jul 2018 23:07:11 +0200
Subject: [docs] asyncio subprocess example fails to run on python 3.7
Message-ID: <CABVbC5gTxsZJtCoY8YXaEHi6Owr_=bs6QK6oaQBm1P1cV-XuiA@mail.gmail.com>

https://docs.python.org/3/library/asyncio-subprocess.html#subprocess-using-streams
this example fails to run on python 3.7. I think the @asyncio.coroutine
decorator should be removed, and instead `async` keyword should be put
before `def` keyword.

Best regards,
Wojtek Bro?ek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180717/7f74318b/attachment.html>

From timliu at outlook.com  Mon Jul 23 01:06:25 2018
From: timliu at outlook.com (Timothy Liu)
Date: Mon, 23 Jul 2018 05:06:25 +0000
Subject: [docs] Where's the Git Repo of Python Documentations?
Message-ID: <MW2PR02MB37690E6F145A8ECB35D96850DC560@MW2PR02MB3769.namprd02.prod.outlook.com>

Dear Python,

Could you add the URL to the Git repo of the Python documentation on the web page? Then the users/readers can catch up the quickly update of the documentations by pulling.

Best Regards!
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180723/3d733fb1/attachment.html>

From zozoula at yahoo.fr  Fri Jul 20 17:55:17 2018
From: zozoula at yahoo.fr (Antony)
Date: Fri, 20 Jul 2018 21:55:17 +0000 (UTC)
Subject: [docs] Python documentation in French
References: <958930375.11862058.1532123717944.ref@mail.yahoo.com>
Message-ID: <958930375.11862058.1532123717944@mail.yahoo.com>

Hello, I'm not able to download any documentation in French language from?https://docs.python.org/fr/3/archives/*?Does it exists ??thanx,Antony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180720/68e4c15a/attachment.html>

From fred at fdrake.net  Tue Jul 24 10:00:32 2018
From: fred at fdrake.net (Fred Drake)
Date: Tue, 24 Jul 2018 10:00:32 -0400
Subject: [docs] Where's the Git Repo of Python Documentations?
In-Reply-To: <MW2PR02MB37690E6F145A8ECB35D96850DC560@MW2PR02MB3769.namprd02.prod.outlook.com>
References: <MW2PR02MB37690E6F145A8ECB35D96850DC560@MW2PR02MB3769.namprd02.prod.outlook.com>
Message-ID: <CAFT4OTFJZALR3c+1jRHkJoEX-CKiaHozAsNrEiNFhL8AOM_wmA@mail.gmail.com>

On Tue, Jul 24, 2018 at 9:53 AM Timothy Liu <timliu at outlook.com> wrote:
> Could you add the URL to the Git repo of the Python documentation on the web page? Then the users/readers can catch up the quickly update of the documentations by pulling.

Tim,

The Python documentation is maintained in the main CPython repository on GitHub:
https://github.com/python/cpython/tree/master/Doc/

I don't know how many users are interested in reading the docs in the
source format, though.


  -Fred

-- 
Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein

From mariatta.wijaya at gmail.com  Tue Jul 24 11:52:42 2018
From: mariatta.wijaya at gmail.com (Mariatta Wijaya)
Date: Tue, 24 Jul 2018 08:52:42 -0700
Subject: [docs] minor typo -- site
In-Reply-To: <OFCDDF738E.3E90019D-ON002582CC.004A8CCE-002582CC.004AB253@notes.na.collabserv.com>
References: <OFCDDF738E.3E90019D-ON002582CC.004A8CCE-002582CC.004AB253@notes.na.collabserv.com>
Message-ID: <CAGbohnbkZoMgd37shCL0Yak4So+Gn_tVY-Q15rkMSvVedkd08w@mail.gmail.com>

Thanks. I've created a PR to fix it, and it will be backported all the way
to 2.7.
https://github.com/python/cpython/pull/8441

Mariatta


On Tue, Jul 24, 2018 at 6:53 AM Eli Baum <Eli.Baum at ibm.com> wrote:

> On this page: https://docs.python.org/3/library/site.html, last
> paragraph, it looks like the first return value (*if the user
> site-packages directory is enabled*) should be zero, not "O".
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180724/53146dbf/attachment-0001.html>

From report at bugs.python.org  Tue Jul 24 12:23:23 2018
From: report at bugs.python.org (Segev Finer)
Date: Tue, 24 Jul 2018 16:23:23 +0000
Subject: [docs] [issue34167] Standard library docs: prev/next skip right
 over 16.11
In-Reply-To: <1532090112.81.0.56676864532.issue34167@psf.upfronthosting.co.za>
Message-ID: <1532449403.87.0.56676864532.issue34167@psf.upfronthosting.co.za>


Segev Finer <segev208 at gmail.com> added the comment:

I think the prev/next links link to the previous/next document while 16.11 is in the same document as 16.10 at the bottom.

----------
nosy: +Segev Finer

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34167>
_______________________________________

From report at bugs.python.org  Tue Jul 24 15:08:16 2018
From: report at bugs.python.org (Christophe Nanteuil)
Date: Tue, 24 Jul 2018 19:08:16 +0000
Subject: [docs] [issue34158] Documentation of datetime '%z' format code is
 odd
In-Reply-To: <1532036087.85.0.56676864532.issue34158@psf.upfronthosting.co.za>
Message-ID: <1532459296.83.0.56676864532.issue34158@psf.upfronthosting.co.za>


Christophe Nanteuil <christophe.nanteuil at gmail.com> added the comment:

PR updated according to Martin Panter comments.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34158>
_______________________________________

From report at bugs.python.org  Tue Jul 24 15:18:34 2018
From: report at bugs.python.org (tzickel)
Date: Tue, 24 Jul 2018 19:18:34 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1532459914.02.0.902498594338.issue34172@psf.upfronthosting.co.za>


Change by tzickel <icebreak at yahoo.com>:


----------
keywords: +patch
pull_requests: +7972
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Tue Jul 24 15:43:22 2018
From: report at bugs.python.org (Yonatan Zunger)
Date: Tue, 24 Jul 2018 19:43:22 +0000
Subject: [docs] [issue34115] code.InteractiveConsole.interact() closes stdin
In-Reply-To: <1532250721.21.0.56676864532.issue34115@psf.upfronthosting.co.za>
Message-ID: <CAFk=nbShZoRUjM1DmTHe2F=J4a4COzuC-ufmqa1qQ7MwB8Y3FA@mail.gmail.com>


Yonatan Zunger <zunger at humu.com> added the comment:

Eryk: Thanks for finding that! So that I'm sure I understand, if 34187 is
resolved, does that mean the stdin.close() is no longer required at all in
_Quitter?

On Sun, Jul 22, 2018 at 2:12 AM Eryk Sun <report at bugs.python.org> wrote:

>
> Eryk Sun <eryksun at gmail.com> added the comment:
>
> > On Windows Console, sys.stdin.close() does not prevent a second
> > interact call.  This might be considered a bug.
>
> This is a bug in io._WindowsConsoleIO.
>
> In Python 3, the sys.std* file objects that get created at startup use
> closefd=False:
>
>     >>> sys.stdin.buffer.raw.closefd
>     False
>     >>> sys.stdout.buffer.raw.closefd
>     False
>     >>> sys.stderr.buffer.raw.closefd
>     False
>
> Since the REPL uses C FILE streams (or in 3.6+ the underlying console file
> handle in Windows), closing sys.stdin does not cause the REPL to exit, and
> the PyOS_ReadLine call in the interactive loop continues to work in both
> POSIX and Windows.
>
> That said, closing sys.stdin should cause input() to raise ValueError due
> to sys.stdin.fileno() failing (i.e. take the non-tty path) and subsequently
> sys.stdin.readline() failing. A second call to
> code.InteractiveConsole.interact() should thus fail. The issue is that the
> fileno() method of _WindowsConsoleIO isn't raising ValueError like it
> should when the file is closed and closefd is false. I've created issue
> 34187 with a suggested fix.
>
> ----------
> nosy: +eryksun
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue34115>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34115>
_______________________________________

From report at bugs.python.org  Wed Jul 25 03:30:05 2018
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 25 Jul 2018 07:30:05 +0000
Subject: [docs] [issue34167] Standard library docs: prev/next skip right
 over 16.11
In-Reply-To: <1532090112.81.0.56676864532.issue34167@psf.upfronthosting.co.za>
Message-ID: <1532503805.92.0.902498594338.issue34167@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34167>
_______________________________________

From report at bugs.python.org  Wed Jul 25 04:43:04 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 25 Jul 2018 08:43:04 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532508184.32.0.902498594338.issue12743@psf.upfronthosting.co.za>


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


----------
pull_requests: +7981

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From anderson.wang368 at gmail.com  Tue Jul 24 13:27:56 2018
From: anderson.wang368 at gmail.com (Cpurr Luvs2Purr)
Date: Tue, 24 Jul 2018 13:27:56 -0400
Subject: [docs] tkinter
Message-ID: <CABZxeMaC1_kwJAttNagTMn_Dscbhwgsg4+=HphVSsrSGsRTuGg@mail.gmail.com>

tkinter is not working, is it import tkinter for python 2.7.15?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180724/b1318782/attachment.html>

From timliu at outlook.com  Tue Jul 24 11:26:54 2018
From: timliu at outlook.com (Timothy Liu)
Date: Tue, 24 Jul 2018 15:26:54 +0000
Subject: [docs] Where's the Git Repo of Python Documentations?
In-Reply-To: <CAFT4OTFJZALR3c+1jRHkJoEX-CKiaHozAsNrEiNFhL8AOM_wmA@mail.gmail.com>
References: <MW2PR02MB37690E6F145A8ECB35D96850DC560@MW2PR02MB3769.namprd02.prod.outlook.com>
 <CAFT4OTFJZALR3c+1jRHkJoEX-CKiaHozAsNrEiNFhL8AOM_wmA@mail.gmail.com>
Message-ID: <MW2PR02MB37692F7C033632C415C9C899DC550@MW2PR02MB3769.namprd02.prod.outlook.com>

Hi Fred,

Thanks a lot for the reply. Since Python is so hot, I believe many developers and learners will have interesting to read (and contribute to) the Python documentations.

Best Regards,
Tim


-----Original Message-----
From: Fred Drake <fred at fdrake.net> 
Sent: Tuesday, July 24, 2018 7:01 AM
To: timliu at outlook.com
Cc: docs <docs at python.org>
Subject: Re: [docs] Where's the Git Repo of Python Documentations?

On Tue, Jul 24, 2018 at 9:53 AM Timothy Liu <timliu at outlook.com> wrote:
> Could you add the URL to the Git repo of the Python documentation on the web page? Then the users/readers can catch up the quickly update of the documentations by pulling.

Tim,

The Python documentation is maintained in the main CPython repository on GitHub:
https://github.com/python/cpython/tree/master/Doc/

I don't know how many users are interested in reading the docs in the source format, though.


  -Fred

-- 
Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein

From tobias.fielitz at redmarker.com.au  Wed Jul 25 00:21:57 2018
From: tobias.fielitz at redmarker.com.au (Tobias Fielitz)
Date: Wed, 25 Jul 2018 14:21:57 +1000
Subject: [docs] (no subject)
Message-ID: <CACWJDdbGm9yiufdyhfcHSJ=e1PbNHNPRMB6OSoj=4R9CmoPo9A@mail.gmail.com>

1. Context.get() requires "key" parameter

https://docs.python.org/3/library/contextvars.html#contextvars.Context

I the asyncio example: "client's address by calling
'client_addr_var.get()'" indicates .get() does not require any parameters,
but it does:

Context.get.__doc__

> 'D.get(k[,d]) -> D[k] if k in D, else d.  d defaults to None.'

contextvars==2.2


2. Context.set() is not documented
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180725/6b0511fb/attachment.html>

From tobias.fielitz at redmarker.com.au  Wed Jul 25 00:24:51 2018
From: tobias.fielitz at redmarker.com.au (Tobias Fielitz)
Date: Wed, 25 Jul 2018 14:24:51 +1000
Subject: [docs] (no subject)
In-Reply-To: <CACWJDdbGm9yiufdyhfcHSJ=e1PbNHNPRMB6OSoj=4R9CmoPo9A@mail.gmail.com>
References: <CACWJDdbGm9yiufdyhfcHSJ=e1PbNHNPRMB6OSoj=4R9CmoPo9A@mail.gmail.com>
Message-ID: <CACWJDdZ01VF8qm9grMq0i1vzeGu3EJSJswmZHPOnav=B6HrOVA@mail.gmail.com>

My bad. I mixed up Context and ContextVar. Please disregard the previous
email.

On Wed, Jul 25, 2018 at 2:21 PM, Tobias Fielitz <
tobias.fielitz at redmarker.com.au> wrote:

> 1. Context.get() requires "key" parameter
>
> https://docs.python.org/3/library/contextvars.html#contextvars.Context
>
> I the asyncio example: "client's address by calling
> 'client_addr_var.get()'" indicates .get() does not require any parameters,
> but it does:
>
> Context.get.__doc__
>
> > 'D.get(k[,d]) -> D[k] if k in D, else d.  d defaults to None.'
>
> contextvars==2.2
>
>
> 2. Context.set() is not documented
>
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180725/41bf1bd9/attachment.html>

From report at bugs.python.org  Wed Jul 25 13:40:36 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 25 Jul 2018 17:40:36 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532540436.89.0.56676864532.issue28677@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset cfadd1c2421e13d76d588982147d4fbdc71d5527 by Miss Islington (bot) in branch '3.6':
bpo-28677: Improve phrasing of when instance attribute is referenced (GH-6208)
https://github.com/python/cpython/commit/cfadd1c2421e13d76d588982147d4fbdc71d5527


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 13:40:13 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 25 Jul 2018 17:40:13 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532540413.33.0.56676864532.issue28677@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 1c8f6553ad5a7f97495972da8f35f4dabcb372d4 by Miss Islington (bot) in branch '2.7':
bpo-28677: Improve phrasing of when instance attribute is referenced (GH-6208)
https://github.com/python/cpython/commit/1c8f6553ad5a7f97495972da8f35f4dabcb372d4


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 11:19:20 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 25 Jul 2018 15:19:20 +0000
Subject: [docs] [issue34226] cgi.parse_multipart() requires undocumented
 CONTENT-LENGTH in Python 3.7
In-Reply-To: <1532530540.72.0.56676864532.issue34226@psf.upfronthosting.co.za>
Message-ID: <1532531960.91.0.902498594338.issue34226@psf.upfronthosting.co.za>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34226>
_______________________________________

From report at bugs.python.org  Wed Jul 25 10:21:36 2018
From: report at bugs.python.org (Tal Einat)
Date: Wed, 25 Jul 2018 14:21:36 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532528496.1.0.56676864532.issue28677@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset c0f0a7669c73c0d444851dd4c5299de2479214cc by Tal Einat (Aaron Ang) in branch 'master':
bpo-28677: Improve phrasing of when instance attribute is referenced (GH-6208)
https://github.com/python/cpython/commit/c0f0a7669c73c0d444851dd4c5299de2479214cc


----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 10:21:54 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 25 Jul 2018 14:21:54 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532528514.55.0.902498594338.issue28677@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7985

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 13:53:04 2018
From: report at bugs.python.org (Tal Einat)
Date: Wed, 25 Jul 2018 17:53:04 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532541184.89.0.56676864532.issue28677@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

Thanks for the PR, Aaron!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 10:22:47 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 25 Jul 2018 14:22:47 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532528567.5.0.902498594338.issue28677@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7986

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 13:52:21 2018
From: report at bugs.python.org (Tal Einat)
Date: Wed, 25 Jul 2018 17:52:21 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532541141.64.0.56676864532.issue28677@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset ec02c58f5a6fdb06b769f53255fcb5d393812160 by Tal Einat (Miss Islington (bot)) in branch '3.7':
bpo-28677: Improve phrasing of when instance attribute is referenced (GH-6208)
https://github.com/python/cpython/commit/ec02c58f5a6fdb06b769f53255fcb5d393812160


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 14:11:20 2018
From: report at bugs.python.org (Tal Einat)
Date: Wed, 25 Jul 2018 18:11:20 +0000
Subject: [docs] [issue33121] recv returning 0 on closed connection not
 documented
In-Reply-To: <1521728108.91.0.467229070634.issue33121@psf.upfronthosting.co.za>
Message-ID: <1532542280.19.0.56676864532.issue33121@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

My guess would be the docs for socket.recv()[1], which indeed don't mention what the return value is after a socket has been closed, nor can I find that info elsewhere on that page.

Those docs for socket generally avoid going into detail, including specifically regarding returned values.  Apparently the approach is that this general note about the class explains where to look for more info:

"Socket objects have the following methods. Except for makefile(), these correspond to Unix system calls applicable to sockets."

Given this, I don't think adding this one small detail would be in line with the existing approach to documenting the socket class.


..[1]: https://docs.python.org/3/library/socket.html#socket.socket.recv

----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33121>
_______________________________________

From report at bugs.python.org  Wed Jul 25 10:55:40 2018
From: report at bugs.python.org (Chih-Hsuan Yen)
Date: Wed, 25 Jul 2018 14:55:40 +0000
Subject: [docs] [issue34226] cgi.parse_multipart() requires undocumented
 CONTENT-LENGTH in Python 3.7
Message-ID: <1532530540.72.0.56676864532.issue34226@psf.upfronthosting.co.za>


New submission from Chih-Hsuan Yen <yan12125 at gmail.com>:

In Python 3.7, cgi.parse_multipart() requires "CONTENT-LENGTH" in the second parameter `pdict`. This is not necesary in Python 3.6.

For example, the following code runs with 3.6:

$ python3.6
Python 3.6.6 (default, Jun 27 2018, 13:11:40) 
[GCC 8.1.1 20180531] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cgi, io
>>> data = b'--heyDavid\r\nContent-Disposition: form-data; name="cfield"\r\n\r\njust a string\r\n\r\n--heyDavid--\r\n'
>>> cgi.parse_multipart(io.BytesIO(data), {"boundary": b"heyDavid"})
{'cfield': [b'just a string\r\n']}

While not on 3.7:

$ python3.7
Python 3.7.0 (default, Jul 15 2018, 10:44:58) 
[GCC 8.1.1 20180531] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cgi, io
>>> data = b'--heyDavid\r\nContent-Disposition: form-data; name="cfield"\r\n\r\njust a string\r\n\r\n--heyDavid--\r\n'
>>> cgi.parse_multipart(io.BytesIO(data), {"boundary": b"heyDavid"})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.7/cgi.py", line 220, in parse_multipart
    headers['Content-Length'] = pdict['CONTENT-LENGTH']
KeyError: 'CONTENT-LENGTH'

I looked into the source code of CPython, and found CONTENT-LENGTH in nowhere but cgi.py and test_cgi.py. I guess it has the same meaning as the Content-Length header in HTTP or CONTENT_LENGTH environment variable in CGI? It would be great to document such a backward-incompatible behavior.

Environment: Arch Linux with Python 3.6.6 from [extra] repo and 3.7.0 from [staging] repo.

CC the author and the reviewer of issue29979, where relevant codes are introduced.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 322362
nosy: docs at python, orsenthil, quentel, yan12125
priority: normal
severity: normal
status: open
title: cgi.parse_multipart() requires undocumented CONTENT-LENGTH in Python 3.7
type: behavior
versions: Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34226>
_______________________________________

From report at bugs.python.org  Wed Jul 25 13:32:48 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 25 Jul 2018 17:32:48 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1532539968.94.0.902498594338.issue28677@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7993

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28677>
_______________________________________

From report at bugs.python.org  Wed Jul 25 07:41:19 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 25 Jul 2018 11:41:19 +0000
Subject: [docs] [issue33028] tempfile.TemporaryDirectory incorrectly
 documented
In-Reply-To: <1520503262.87.0.467229070634.issue33028@psf.upfronthosting.co.za>
Message-ID: <1532518879.41.0.56676864532.issue33028@psf.upfronthosting.co.za>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

On a similar note SpooledTemporaryFile is also documented as a function though it's a class. Ref : https://docs.python.org/3.8/library/tempfile.html#tempfile.SpooledTemporaryFile

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33028>
_______________________________________

From report at bugs.python.org  Wed Jul 25 10:03:57 2018
From: report at bugs.python.org (Tal Einat)
Date: Wed, 25 Jul 2018 14:03:57 +0000
Subject: [docs] [issue31823] Opaque default value for close_fds argument in
 Popen.__init__
In-Reply-To: <1508445256.4.0.213398074469.issue31823@psf.upfronthosting.co.za>
Message-ID: <1532527437.39.0.56676864532.issue31823@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

ISTM that the docs need to be fixed for both 3.7+ and for 3.6.

The signature is indeed awkward for 3.6, but it's too minor a detail to address considering it's no longer relevant for 3.7 and later.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy
nosy: +docs at python, taleinat
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31823>
_______________________________________

From report at bugs.python.org  Thu Jul 26 01:37:12 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 26 Jul 2018 05:37:12 +0000
Subject: [docs] [issue22374] Replace contextmanager example and improve
 explanation
In-Reply-To: <1410296292.35.0.34327651623.issue22374@psf.upfronthosting.co.za>
Message-ID: <1532583432.16.0.56676864532.issue22374@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

The old tag() example has been replaced with a different example in https://github.com/python/cpython/commit/bde782bb594edffeabe978abeee2b7082ab9bc2a (bpo-33468)

----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> Add try-finally contextlib.contextmanager example

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22374>
_______________________________________

From report at bugs.python.org  Thu Jul 26 10:19:36 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Thu, 26 Jul 2018 14:19:36 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
Message-ID: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>


New submission from Jonathan Fine <jfine2358 at gmail.com>:

The title says it all.
faq/design: PEP 572 adds assignment expressions

https://docs.python.org/3.8/faq/design.html#why-can-t-i-use-an-assignment-in-an-expression
[Can't use] this C idiom:
while (line = readline(f)) {
    // do something with line
}

https://www.python.org/dev/peps/pep-0572/
while chunk := file.read(8192):
   process(chunk)

----------
assignee: docs at python
components: Documentation
messages: 322430
nosy: docs at python, jfine2358
priority: normal
severity: normal
status: open
title: faq/design: PEP 572 adds assignment expressions
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Thu Jul 26 15:51:30 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Thu, 26 Jul 2018 19:51:30 +0000
Subject: [docs] [issue25461] Unclear language (the word ineffective) in the
 documentation for os.walk
In-Reply-To: <1445533538.52.0.421272081658.issue25461@psf.upfronthosting.co.za>
Message-ID: <1532634690.71.0.902498594338.issue25461@psf.upfronthosting.co.za>


Change by Jonathan Fine <jfine2358 at gmail.com>:


----------
nosy: +jfine2358

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25461>
_______________________________________

From report at bugs.python.org  Fri Jul 27 00:35:19 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 27 Jul 2018 04:35:19 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532666119.84.0.56676864532.issue12743@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset defcffdf86780e3a184ebb25dc9a7b807753d57a by Berker Peksag in branch 'master':
bpo-12743: Delete comment from marshal.rst (GH-8457)
https://github.com/python/cpython/commit/defcffdf86780e3a184ebb25dc9a7b807753d57a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From report at bugs.python.org  Fri Jul 27 00:35:24 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 27 Jul 2018 04:35:24 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532666124.11.0.902498594338.issue12743@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8010

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From report at bugs.python.org  Fri Jul 27 00:36:21 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 27 Jul 2018 04:36:21 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532666181.19.0.902498594338.issue12743@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8011

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From report at bugs.python.org  Fri Jul 27 00:40:40 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 27 Jul 2018 04:40:40 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532666440.67.0.56676864532.issue12743@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 21ed29ac290b10d31dcac947f9246ae4d8b94a86 by Miss Islington (bot) in branch '3.7':
bpo-12743: Delete comment from marshal.rst (GH-8457)
https://github.com/python/cpython/commit/21ed29ac290b10d31dcac947f9246ae4d8b94a86


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From report at bugs.python.org  Fri Jul 27 00:42:47 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 27 Jul 2018 04:42:47 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532666567.88.0.56676864532.issue12743@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 146ba436cc0457b8ef7fea8b054b9ccb15e24748 by Miss Islington (bot) in branch '3.6':
bpo-12743: Delete comment from marshal.rst (GH-8457)
https://github.com/python/cpython/commit/146ba436cc0457b8ef7fea8b054b9ccb15e24748


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From report at bugs.python.org  Fri Jul 27 00:47:23 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 27 Jul 2018 04:47:23 +0000
Subject: [docs] [issue12743] C API marshalling doc contains XXX
In-Reply-To: <1313160183.82.0.137409262179.issue12743@psf.upfronthosting.co.za>
Message-ID: <1532666843.1.0.902498594338.issue12743@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8 -Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12743>
_______________________________________

From report at bugs.python.org  Fri Jul 27 03:53:00 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 27 Jul 2018 07:53:00 +0000
Subject: [docs] [issue27717] sqlite documentation bug
In-Reply-To: <1470745775.08.0.0704550754852.issue27717@psf.upfronthosting.co.za>
Message-ID: <1532677980.44.0.56676864532.issue27717@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Looking at this again, I think the current version of the documentation should stay as-is. Perhaps my patch can make the insecure example separated from the secure one, but I don't think it's worth to apply it.

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27717>
_______________________________________

From report at bugs.python.org  Fri Jul 27 05:52:05 2018
From: report at bugs.python.org (Vadim Pushtaev)
Date: Fri, 27 Jul 2018 09:52:05 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532685124.98.0.56676864532.issue34237@psf.upfronthosting.co.za>


Vadim Pushtaev <pushtaev.vm at gmail.com> added the comment:

This indeed doesn't make much sense now. I'll try to send a PR today.

----------
nosy: +Vadim Pushtaev

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Fri Jul 27 05:55:45 2018
From: report at bugs.python.org (Ammar Askar)
Date: Fri, 27 Jul 2018 09:55:45 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532685345.78.0.56676864532.issue34237@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

This should be done as part of the doc changes for the full PEP 572 implementation, no point in independently doing it now when it hasn't even been implemented yet.

----------
nosy: +ammar2
resolution:  -> postponed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Fri Jul 27 05:56:57 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 27 Jul 2018 09:56:57 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1532685417.38.0.902498594338.issue33666@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
keywords: +patch
pull_requests: +8015
stage: resolved -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33666>
_______________________________________

From report at bugs.python.org  Fri Jul 27 06:21:01 2018
From: report at bugs.python.org (Vadim Pushtaev)
Date: Fri, 27 Jul 2018 10:21:01 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532686861.14.0.56676864532.issue34237@psf.upfronthosting.co.za>


Vadim Pushtaev <pushtaev.vm at gmail.com> added the comment:

Okay then.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Fri Jul 27 06:26:56 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 27 Jul 2018 10:26:56 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532687216.09.0.902498594338.issue8145@psf.upfronthosting.co.za>


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


----------
pull_requests: +8017

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Fri Jul 27 06:46:07 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Fri, 27 Jul 2018 10:46:07 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532688367.61.0.56676864532.issue34237@psf.upfronthosting.co.za>


Jonathan Fine <jfine2358 at gmail.com> added the comment:

My mistake. But not mine only.

According to https://www.python.org/dev/peps/pep-0572/ the PEP is Python-Version: 3.8

I took this to mean that it had been implemented in Python 3.8. Reading the PEP more closely, it also says Status: Accepted.

According to https://www.python.org/dev/peps/pep-0001/#pep-header-preamble each PEP can have an optional Python-Version, which is "described below". I thus find
===
Standards Track PEPs will typically have a Python-Version header which indicates the version of Python that the feature will be released with.
===

I seems to me that there is a bug in the PEP, perhaps caused either by a failure to increment its Python-Version as part of the release of Python 3.8, or the PEP itself providing too early the optional Python-Version.

I'll email Chris Angelico about this. I'm very happy for the issue to remain closed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Fri Jul 27 08:41:08 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 27 Jul 2018 12:41:08 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1532695268.91.0.902498594338.issue22021@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22021>
_______________________________________

From report at bugs.python.org  Fri Jul 27 09:25:03 2018
From: report at bugs.python.org (Chris Angelico)
Date: Fri, 27 Jul 2018 13:25:03 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532697903.6.0.56676864532.issue34237@psf.upfronthosting.co.za>


Chris Angelico <rosuav at gmail.com> added the comment:

Yes, the PEP says version 3.8. Why is this a problem? Sit tight, let the implementation land. I don't understand why this needed me to get emailed saying that the PEP has the wrong version number in it.

----------
nosy: +Rosuav

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From przemyslaw.szrama at gmail.com  Wed Jul 25 09:34:17 2018
From: przemyslaw.szrama at gmail.com (Przemyslaw Szrama)
Date: Wed, 25 Jul 2018 15:34:17 +0200
Subject: [docs] Python 2.7 docs error
Message-ID: <209C67E0-0C9D-46D2-8491-460C969F7A25@gmail.com>

Hi,
When I try to download docs for python 2.7 I get Nginix 404 error - on all documents.
I don?t check on other docs.

Kind regards 
Przemyslaw 

Wys?ane z iPhone'a

From coreygumbs at me.com  Wed Jul 25 13:20:11 2018
From: coreygumbs at me.com (Corey Gumbs)
Date: Wed, 25 Jul 2018 13:20:11 -0400
Subject: [docs] Python Documentation Downloads.
Message-ID: <2D6134F6-10E1-48E4-BCC7-8366E0A3DCFF@me.com>

To whom it may concern, 


All of the links on the documentation download page are returning 404 errors and aren?t downloading the links.


Thank you.

Sincerely,

Corey Gumbs

From report at bugs.python.org  Fri Jul 27 10:24:47 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Fri, 27 Jul 2018 14:24:47 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532701487.04.0.56676864532.issue34237@psf.upfronthosting.co.za>


Jonathan Fine <jfine2358 at gmail.com> added the comment:

First, I'm delighted that the current docs are in fact correct regarding assignment expressions. (I should have said this earlier.)

I'm happy to wait for the implementation to land. (And if you like, I'm willing to help with the documentation. I seem to have an eye for detail.)

Whether or not mine was the only my mistake, I was misled by the PEP 572 header. (And perhaps Vadim was also - msg322479.)

This issue is, rightly, closed. Perhaps the discussion should continue in a new issue? And without Chris, if he doesn't want to be involved. Perhaps it's a matter for the release manager?

Or perhaps having Python-Version:3.8 in the PEP remain until the change lands (and then both Status and Python-Version will be changed). 

I'm new here. I'm happy for someone else to decide. No action is one option.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Fri Jul 27 10:59:59 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Fri, 27 Jul 2018 14:59:59 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1532703599.82.0.56676864532.issue34237@psf.upfronthosting.co.za>


Jonathan Fine <jfine2358 at gmail.com> added the comment:

I'm sorry. I apologise. I'm being a bit stupid. Everything is fine. Nothing to do.

In case you care, here's the situation. Python 3.8 is in development, and not yet released. Somehow, I'd got it into my mind that it had already been released.

So the PEP 572 header is correct. The PEP status is accepted, the feature is in development (including documentation), and all being well the feature and the documentation will appear in Python3.8.

By the way, according to https://www.python.org/dev/peps/pep-0569/#id5, the first alpha is due 2019-01-27.

So please, all of you, accept my apologies.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Fri Jul 27 11:07:15 2018
From: report at bugs.python.org (v kats)
Date: Fri, 27 Jul 2018 15:07:15 +0000
Subject: [docs] [issue34249] Full set of format codes applies to strftime
 only
Message-ID: <1532704035.87.0.56676864532.issue34249@psf.upfronthosting.co.za>


New submission from v kats <vkatsikaros at gmail.com>:

Section "strftime() and strptime() Behavior" says:

"The full set of format codes supported varies across platforms, because Python calls the platform C library?s strftime() function, and platform variations are common. To see the full set of format codes supported on your platform, consult the strftime(3) documentation."

It implies that this applies for strftime only, and indeed it refers to C library?s strftime().

However, it's easy to miss (at least I got confused and lost some time), so I propose to clarify the paragraph.

strptime and %s

# python
Python 2.7.6 (default, Nov 23 2017, 15:49:48) 
[GCC 4.8.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from datetime import datetime
>>> datetime.strptime('1532689414','%s')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>


strftime and %s

python
Python 2.7.6 (default, Nov 23 2017, 15:49:48) 
[GCC 4.8.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from datetime import datetime
>>> datetime.now().strftime('%s')
'1532702817'

  File "/usr/lib/python2.7/_strptime.py", line 317, in _strptime
    (bad_directive, format))
ValueError: 's' is a bad directive in format '%s'

----------
assignee: docs at python
components: Documentation
messages: 322498
nosy: docs at python, v kats
priority: normal
severity: normal
status: open
title: Full set of format codes applies to strftime only
type: enhancement
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34249>
_______________________________________

From report at bugs.python.org  Fri Jul 27 11:08:05 2018
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 27 Jul 2018 15:08:05 +0000
Subject: [docs] [issue34249] Full set of format codes applies to strftime
 only
In-Reply-To: <1532704035.87.0.56676864532.issue34249@psf.upfronthosting.co.za>
Message-ID: <1532704085.23.0.902498594338.issue34249@psf.upfronthosting.co.za>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +8020
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34249>
_______________________________________

From report at bugs.python.org  Fri Jul 27 11:19:22 2018
From: report at bugs.python.org (v kats)
Date: Fri, 27 Jul 2018 15:19:22 +0000
Subject: [docs] [issue34249] Full set of format codes applies to strftime
 only
In-Reply-To: <1532704035.87.0.56676864532.issue34249@psf.upfronthosting.co.za>
Message-ID: <1532704762.64.0.56676864532.issue34249@psf.upfronthosting.co.za>


v kats <vkatsikaros at gmail.com> added the comment:

Note, the last 3 lines of the previous comment seem to be a rogue copy-paste

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34249>
_______________________________________

From report at bugs.python.org  Sat Jul 28 01:15:54 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 28 Jul 2018 05:15:54 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532754954.13.0.56676864532.issue29710@psf.upfronthosting.co.za>


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


New changeset b4bc5cab82e6855e4ebc33ba0b669ddffad30fb3 by Nick Coghlan (Sanyam Khurana) in branch 'master':
bpo-29710: Clarify documentation for Bitwise binary operation (GH-1691)
https://github.com/python/cpython/commit/b4bc5cab82e6855e4ebc33ba0b669ddffad30fb3


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sat Jul 28 01:16:05 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 05:16:05 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532754965.34.0.902498594338.issue29710@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
keywords: +patch
pull_requests: +8025
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sat Jul 28 01:17:00 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 05:17:00 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532755020.54.0.902498594338.issue29710@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8026

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sat Jul 28 01:18:35 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 28 Jul 2018 05:18:35 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532755115.25.0.56676864532.issue29710@psf.upfronthosting.co.za>


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

Mark & Tim: thanks for the discussion and clarifications above, I learned some new things myself!

Sanyam: thanks for the patch, and for your patience while we figured out what we wanted the new wording to actually say :)

(Technically the backport PRs are still in progress, but I'll track that through the GitHub notifications)

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:01:27 2018
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 28 Jul 2018 10:01:27 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1532772087.13.0.56676864532.issue5978@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:


New changeset 937fb55d35373fd2701078251840b6be0465a6e1 by Christian Heimes (Andr?s Delfino) in branch 'master':
bpo-5978: Document that profiling needs cmd/function to return (GH-7938)
https://github.com/python/cpython/commit/937fb55d35373fd2701078251840b6be0465a6e1


----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:01:45 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 10:01:45 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1532772105.56.0.902498594338.issue5978@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8029

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:03:26 2018
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 28 Jul 2018 10:03:26 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1532772206.24.0.56676864532.issue33921@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:


New changeset 95dfb9c3aefdc981d23af700b753a6c97159ccad by Christian Heimes (johnthagen) in branch 'master':
bpo-33921: Clarify how to bind to all interfaces using socket (GH-7877)
https://github.com/python/cpython/commit/95dfb9c3aefdc981d23af700b753a6c97159ccad


----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:03:33 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 10:03:33 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1532772213.79.0.902498594338.issue33921@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8030

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:04:32 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 10:04:32 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1532772272.59.0.902498594338.issue33921@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8031

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:28:04 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 28 Jul 2018 10:28:04 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1532773684.38.0.902498594338.issue5978@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
pull_requests: +8032

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Sat Jul 28 06:55:08 2018
From: report at bugs.python.org (roger)
Date: Sat, 28 Jul 2018 10:55:08 +0000
Subject: [docs] [issue34226] cgi.parse_multipart() requires undocumented
 CONTENT-LENGTH in Python 3.7
In-Reply-To: <1532530540.72.0.56676864532.issue34226@psf.upfronthosting.co.za>
Message-ID: <1532775308.17.0.56676864532.issue34226@psf.upfronthosting.co.za>


roger <rogerduran at gmail.com> added the comment:

working on this on europython

----------
nosy: +rogerduran

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34226>
_______________________________________

From report at bugs.python.org  Sat Jul 28 07:14:21 2018
From: report at bugs.python.org (Eivind Teig)
Date: Sat, 28 Jul 2018 11:14:21 +0000
Subject: [docs] [issue22062] Fix pathlib.Path.(r)glob doc glitches.
In-Reply-To: <1406239862.0.0.293742999811.issue22062@psf.upfronthosting.co.za>
Message-ID: <1532776461.78.0.902498594338.issue22062@psf.upfronthosting.co.za>


Change by Eivind Teig <eivind.teig at gmail.com>:


----------
pull_requests: +8034
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22062>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:20:27 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:20:27 +0000
Subject: [docs] [issue22062] Fix pathlib.Path.(r)glob doc glitches.
In-Reply-To: <1406239862.0.0.293742999811.issue22062@psf.upfronthosting.co.za>
Message-ID: <1532780427.77.0.902498594338.issue22062@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22062>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:22:58 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:22:58 +0000
Subject: [docs] [issue22062] Fix pathlib.Path.(r)glob doc glitches.
In-Reply-To: <1406239862.0.0.293742999811.issue22062@psf.upfronthosting.co.za>
Message-ID: <1532780578.11.0.902498594338.issue22062@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords:  -easy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22062>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:23:45 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 12:23:45 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1532780625.08.0.56676864532.issue5978@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset c6801b48a1964d87a77f1303e0c6ddf31f54259b by Miss Islington (bot) in branch '3.7':
bpo-5978: Document that profiling needs cmd/function to return (GH-7938)
https://github.com/python/cpython/commit/c6801b48a1964d87a77f1303e0c6ddf31f54259b


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:24:37 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:24:37 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1532780677.87.0.56676864532.issue5978@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 0041d721a6f6b312ef762838d390fc4d64cf5e3a by Steve Dower (Andr?s Delfino) in branch '3.6':
[3.6] bpo-5978: Document that profiling needs cmd/function to return (GH-8515)
https://github.com/python/cpython/commit/0041d721a6f6b312ef762838d390fc4d64cf5e3a


----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:26:51 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:26:51 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1532780811.15.0.902498594338.issue5978@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:27:18 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 12:27:18 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1532780838.32.0.56676864532.issue33921@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 23355445625b8b41030dbda9decaf2f4aa7035a6 by Miss Islington (bot) in branch '3.7':
bpo-33921: Clarify how to bind to all interfaces using socket (GH-7877)
https://github.com/python/cpython/commit/23355445625b8b41030dbda9decaf2f4aa7035a6


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:27:30 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 12:27:30 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1532780850.12.0.56676864532.issue33921@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 30f295b85ece2dc2b2b65018bd15090efa1de7dc by Miss Islington (bot) in branch '3.6':
bpo-33921: Clarify how to bind to all interfaces using socket (GH-7877)
https://github.com/python/cpython/commit/30f295b85ece2dc2b2b65018bd15090efa1de7dc


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:30:05 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:30:05 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1532781005.82.0.902498594338.issue33921@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:31:52 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:31:52 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532781112.56.0.902498594338.issue8145@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords:  -easy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:47:34 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Sat, 28 Jul 2018 12:47:34 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1532782054.08.0.56676864532.issue33666@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:


New changeset 1d2dafa249c7fb34f3d24e7a77d1bea02907d92b by Petr Viktorin (INADA Naoki) in branch 'master':
bpo-33666: Add what's new entry for os.errno removal (GH-#8497)
https://github.com/python/cpython/commit/1d2dafa249c7fb34f3d24e7a77d1bea02907d92b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33666>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:56:35 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:56:35 +0000
Subject: [docs] [issue30974] Update os.samefile docstring to match
 documentation
In-Reply-To: <1500538030.77.0.17785692497.issue30974@psf.upfronthosting.co.za>
Message-ID: <1532782595.63.0.56676864532.issue30974@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:

I think the docs are too specific about the mechanism used here - if we document *how* it works then we may not be able to make it work correctly (with a different mechanic) on a different platform.

----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30974>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:56:47 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:56:47 +0000
Subject: [docs] [issue30974] Update os.samefile docstring to match
 documentation
In-Reply-To: <1500538030.77.0.17785692497.issue30974@psf.upfronthosting.co.za>
Message-ID: <1532782607.44.0.56676864532.issue30974@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:

Sorry, I meant the docs after the patch. Before, it's fine.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30974>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:56:59 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:56:59 +0000
Subject: [docs] [issue30974] Update os.samefile docstring to match
 documentation
In-Reply-To: <1500538030.77.0.17785692497.issue30974@psf.upfronthosting.co.za>
Message-ID: <1532782619.76.0.902498594338.issue30974@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords:  -easy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30974>
_______________________________________

From report at bugs.python.org  Sat Jul 28 08:58:07 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 12:58:07 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1532782687.62.0.56676864532.issue24356@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 50326927465c3f5c6c0168fc43310c8e97db0a47 by Steve Dower (Elena Oat) in branch 'master':
bpo-24356: Specify which Python binary will be used with venv (GH-6589)
https://github.com/python/cpython/commit/50326927465c3f5c6c0168fc43310c8e97db0a47


----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24356>
_______________________________________

From report at bugs.python.org  Sat Jul 28 09:02:09 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 13:02:09 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1532782929.57.0.902498594338.issue24356@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
pull_requests: +8043

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24356>
_______________________________________

From report at bugs.python.org  Sat Jul 28 09:04:20 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 13:04:20 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1532783060.57.0.902498594338.issue32769@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32769>
_______________________________________

From report at bugs.python.org  Sat Jul 28 09:04:42 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 13:04:42 +0000
Subject: [docs] [issue33601] [EASY DOC] Py_UTF8Mode is not documented
In-Reply-To: <1526996981.47.0.682650639539.issue33601@psf.upfronthosting.co.za>
Message-ID: <1532783082.99.0.902498594338.issue33601@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords:  -easy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33601>
_______________________________________

From report at bugs.python.org  Sat Jul 28 09:06:29 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 13:06:29 +0000
Subject: [docs] [issue13474] Mention of "-m" Flag Missing From Doc on
 Execution Model
In-Reply-To: <1322165458.97.0.989343856998.issue13474@psf.upfronthosting.co.za>
Message-ID: <1532783189.24.0.902498594338.issue13474@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords:  -easy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13474>
_______________________________________

From report at bugs.python.org  Sat Jul 28 09:24:45 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 13:24:45 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1532784285.08.0.902498594338.issue33666@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8044

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33666>
_______________________________________

From report at bugs.python.org  Sat Jul 28 09:27:43 2018
From: report at bugs.python.org (Ronald Oussoren)
Date: Sat, 28 Jul 2018 13:27:43 +0000
Subject: [docs] [issue33111] Merely importing tkinter breaks parallel code
 (multiprocessing, sharedmem)
In-Reply-To: <1521573656.32.0.467229070634.issue33111@psf.upfronthosting.co.za>
Message-ID: <1532784463.65.0.56676864532.issue33111@psf.upfronthosting.co.za>


Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

That's annoying, I cannot reproduce the issue on macOS 10.13. I don't have access to my test VM running 10.11 at the moment, I'll work on documenting this when I get back home (and do have access to 10.11 again).

BTW. I don't know if providing a reliable test is possible other than testing that the documented procedure works in general.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33111>
_______________________________________

From report at bugs.python.org  Sat Jul 28 11:07:11 2018
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 28 Jul 2018 15:07:11 +0000
Subject: [docs] [issue34226] cgi.parse_multipart() requires undocumented
 CONTENT-LENGTH in Python 3.7
In-Reply-To: <1532530540.72.0.56676864532.issue34226@psf.upfronthosting.co.za>
Message-ID: <1532790431.86.0.902498594338.issue34226@psf.upfronthosting.co.za>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +8047
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34226>
_______________________________________

From report at bugs.python.org  Sat Jul 28 12:48:32 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 16:48:32 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1532796512.74.0.56676864532.issue24356@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 83b449d754f4da3be107b508392ef5180f105c8b by Steve Dower in branch '3.7':
bpo-24356: Specify which Python binary will be used with venv (GH-6589)
https://github.com/python/cpython/commit/83b449d754f4da3be107b508392ef5180f105c8b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24356>
_______________________________________

From report at bugs.python.org  Sat Jul 28 12:50:23 2018
From: report at bugs.python.org (Steve Dower)
Date: Sat, 28 Jul 2018 16:50:23 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1532796623.18.0.902498594338.issue24356@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24356>
_______________________________________

From report at bugs.python.org  Sat Jul 28 12:52:17 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 16:52:17 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532796737.54.0.56676864532.issue29710@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 8764a6ffda896af4586f07b55d7df916f86dd9b0 by Miss Islington (bot) in branch '3.7':
bpo-29710: Clarify documentation for Bitwise binary operation (GH-1691)
https://github.com/python/cpython/commit/8764a6ffda896af4586f07b55d7df916f86dd9b0


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sat Jul 28 12:52:33 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 28 Jul 2018 16:52:33 +0000
Subject: [docs] [issue29710] Incorrect representation caveat on bitwise
 operation docs
In-Reply-To: <1488551919.31.0.20533072889.issue29710@psf.upfronthosting.co.za>
Message-ID: <1532796753.89.0.56676864532.issue29710@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3100b7e710dccdcfbc6991ea7e8985a1881d42e6 by Miss Islington (bot) in branch '3.6':
bpo-29710: Clarify documentation for Bitwise binary operation (GH-1691)
https://github.com/python/cpython/commit/3100b7e710dccdcfbc6991ea7e8985a1881d42e6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29710>
_______________________________________

From report at bugs.python.org  Sun Jul 29 05:01:45 2018
From: report at bugs.python.org (Steve Dower)
Date: Sun, 29 Jul 2018 09:01:45 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532854905.56.0.56676864532.issue8145@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:


New changeset a71fed0b7596f1c11a2fa6c1b7311157148f5f9f by Steve Dower (Berker Peksag) in branch 'master':
bpo-8145: Improve isolation_level documentation (GH-8499)
https://github.com/python/cpython/commit/a71fed0b7596f1c11a2fa6c1b7311157148f5f9f


----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sun Jul 29 05:01:55 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 29 Jul 2018 09:01:55 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532854915.17.0.902498594338.issue8145@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8056

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sun Jul 29 05:07:42 2018
From: report at bugs.python.org (Steve Dower)
Date: Sun, 29 Jul 2018 09:07:42 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532855262.58.0.56676864532.issue8145@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 94972d50bda19000bce498bd2c5ace6be9bec711 by Steve Dower (Miss Islington (bot)) in branch '3.6':
bpo-8145: Improve isolation_level documentation (GH-8499)
https://github.com/python/cpython/commit/94972d50bda19000bce498bd2c5ace6be9bec711


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sun Jul 29 05:09:44 2018
From: report at bugs.python.org (Steve Dower)
Date: Sun, 29 Jul 2018 09:09:44 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532855384.81.0.902498594338.issue8145@psf.upfronthosting.co.za>


Change by Steve Dower <steve.dower at python.org>:


----------
pull_requests: +8060

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sun Jul 29 05:39:52 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Sun, 29 Jul 2018 09:39:52 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1532857192.07.0.56676864532.issue33666@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:


New changeset 78c54de575fd121d91749c2316fef1949d76fb07 by Petr Viktorin (Miss Islington (bot)) in branch '3.7':
bpo-33666: Add what's new entry for os.errno removal (GH-8497) (GH-8526)
https://github.com/python/cpython/commit/78c54de575fd121d91749c2316fef1949d76fb07


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33666>
_______________________________________

From report at bugs.python.org  Sun Jul 29 07:06:38 2018
From: report at bugs.python.org (Steve Dower)
Date: Sun, 29 Jul 2018 11:06:38 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532862398.0.0.56676864532.issue8145@psf.upfronthosting.co.za>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 3dc8cdf56d056fb7722061ac3b3863e8a385b8de by Steve Dower in branch '3.7':
bpo-8145: Improve isolation_level documentation (GH-8499)
https://github.com/python/cpython/commit/3dc8cdf56d056fb7722061ac3b3863e8a385b8de


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sun Jul 29 07:08:23 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 29 Jul 2018 11:08:23 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1532862503.27.0.902498594338.issue33666@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33666>
_______________________________________

From report at bugs.python.org  Sun Jul 29 07:12:07 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 29 Jul 2018 11:12:07 +0000
Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level
In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za>
Message-ID: <1532862727.12.0.902498594338.issue8145@psf.upfronthosting.co.za>


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


----------
keywords:  -needs review
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8 -Python 2.7, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8145>
_______________________________________

From report at bugs.python.org  Sun Jul 29 17:25:52 2018
From: report at bugs.python.org (Michael Fischer)
Date: Sun, 29 Jul 2018 21:25:52 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
Message-ID: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>


New submission from Michael Fischer <michael-fischer89 at web.de>:

In section "7.1.3.1. Format Specification Mini-Language" of the documentation (https://docs.python.org/2/library/string.html) both %f and %F are labelled "Fixed point". This is confusing for someone who a) transitions over from C or variants or b) knows the difference between fixed and floating point numbers. 

I suggest either changing the "Fixed" to "Floating" or explaining what is meant by "Fixed Point" (because I'm sure there's a reason why someone has named it like that in the first place).

----------
assignee: docs at python
components: Documentation
messages: 322644
nosy: MikeFoxtrot, docs at python
priority: normal
severity: normal
status: open
title: %f is confusingly associated with fixed point format
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34273>
_______________________________________

From report at bugs.python.org  Mon Jul 30 05:02:57 2018
From: report at bugs.python.org (crzbear)
Date: Mon, 30 Jul 2018 09:02:57 +0000
Subject: [docs] [issue34278] Documentation: os.waitid and os.WNOHANG
Message-ID: <1532941377.17.0.56676864532.issue34278@psf.upfronthosting.co.za>


New submission from crzbear <python at 01.crabdance.com>:

os.waitid states that  None  is returned
if WNOHANG was specified and no children are in a waitable state

os.WNOHANG states that the return value in this case would be  (0, 0)  


Python 3.6.5 returns None, so the latter probably needs to be changed

----------
assignee: docs at python
components: Documentation
messages: 322660
nosy: crzbear, docs at python
priority: normal
severity: normal
status: open
title: Documentation: os.waitid and os.WNOHANG
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34278>
_______________________________________

From report at bugs.python.org  Mon Jul 30 06:13:05 2018
From: report at bugs.python.org (Evgeny)
Date: Mon, 30 Jul 2018 10:13:05 +0000
Subject: [docs] [issue16399] argparse: append action with default list adds
 to list instead of overriding
In-Reply-To: <1351992623.71.0.851432414607.issue16399@psf.upfronthosting.co.za>
Message-ID: <1532945585.73.0.56676864532.issue16399@psf.upfronthosting.co.za>


Evgeny <p3gus at yandex.ru> added the comment:

You don't need action='append'. 
For desired behavior you can pass action='store' with nargs='*'.
I think it's a simplest workaround.

----------
nosy: +gun146

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16399>
_______________________________________

From report at bugs.python.org  Mon Jul 30 10:52:32 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 30 Jul 2018 14:52:32 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1532962352.28.0.56676864532.issue34273@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

FTR, here "fixed point" refers to the output representation (a decimal string) rather than the input (a floating-point binary value). The output of %f gives a *fixed* number of places after the decimal point (6 by default).

Contrast with %e, which gives a floating-point output representation.

But yes, there are probably less confusing ways to word this. Did you have a particular alternative wording in mind?

Here's the behaviour of %f for different scale values: note that the output always has the same number of digits after the point, but the number of significant digits varies.

>>> "%f" % math.pi
'3.141593'
>>> "%f" % (100.0 * math.pi)
'314.159265'
>>> "%f" % (0.01 * math.pi)
'0.031416'

And here's %e. Now it's the other way around: the number of significant digits stays the same, but the exponent changes to reflect the magnitude.

>>> "%e" % math.pi
'3.141593e+00'
>>> "%e" % (100 * math.pi)
'3.141593e+02'
>>> "%e" % (0.01 * math.pi)
'3.141593e-02'

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34273>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:49:26 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 31 Jul 2018 05:49:26 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016166.26.0.56676864532.issue27671@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:


New changeset c48e26dcadbff8620bb5881d3bd148fc8894d0ef by INADA Naoki in branch 'master':
bpo-27671: Update FAQ about why len is function (GH-8432)
https://github.com/python/cpython/commit/c48e26dcadbff8620bb5881d3bd148fc8894d0ef


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:49:41 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 31 Jul 2018 05:49:41 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016181.08.0.902498594338.issue27671@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8085

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:50:33 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 31 Jul 2018 05:50:33 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016233.18.0.902498594338.issue27671@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8086

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:51:33 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 31 Jul 2018 05:51:33 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016293.07.0.902498594338.issue27671@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +8087

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:54:27 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 31 Jul 2018 05:54:27 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016467.92.0.56676864532.issue27671@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a621f406402e05febb302cf31962e9d2d747d8f6 by Miss Islington (bot) in branch '3.7':
bpo-27671: Update FAQ about why len is function (GH-8432)
https://github.com/python/cpython/commit/a621f406402e05febb302cf31962e9d2d747d8f6


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:56:29 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 31 Jul 2018 05:56:29 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016589.59.0.56676864532.issue27671@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 0b376eb0d63e0c51ed55c620b40edae6ded4ea48 by Miss Islington (bot) in branch '3.6':
bpo-27671: Update FAQ about why len is function (GH-8432)
https://github.com/python/cpython/commit/0b376eb0d63e0c51ed55c620b40edae6ded4ea48


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 01:58:14 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 31 Jul 2018 05:58:14 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533016694.75.0.56676864532.issue27671@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset dc9039da239ee572eaaf56e4a026be1fc4d74e24 by Miss Islington (bot) in branch '2.7':
bpo-27671: Update FAQ about why len is function (GH-8432)
https://github.com/python/cpython/commit/dc9039da239ee572eaaf56e4a026be1fc4d74e24


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 02:50:19 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 31 Jul 2018 06:50:19 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533019819.15.0.56676864532.issue33729@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset f1d36d8efaecd5c84cb35e35119b283f37d83c40 by Serhiy Storchaka in branch 'master':
bpo-33729: Fix issues with arguments parsing in hashlib. (GH-8346)
https://github.com/python/cpython/commit/f1d36d8efaecd5c84cb35e35119b283f37d83c40


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 02:57:47 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 31 Jul 2018 06:57:47 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533020267.06.0.902498594338.issue33729@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +8090

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 03:22:46 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 31 Jul 2018 07:22:46 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533021766.52.0.56676864532.issue33729@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 47957dab94a4efa2fee61c9a8193f78300950769 by Serhiy Storchaka in branch '3.7':
[3.7] bpo-33729: Fix issues with arguments parsing in hashlib. (GH-8346) (GH-8581)
https://github.com/python/cpython/commit/47957dab94a4efa2fee61c9a8193f78300950769


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 03:26:48 2018
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 31 Jul 2018 07:26:48 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533022008.96.0.56676864532.issue33729@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:

Your PR changed way to many aspects of the code in one commit. I also don't like the fact, that you pushed such a big change without waiting for my feedback. For the past two weeks I have been travelling to conferences and had no time to review your PR. There was no need to rush it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 03:28:55 2018
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 31 Jul 2018 07:28:55 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533022135.05.0.56676864532.issue33729@psf.upfronthosting.co.za>


Christian Heimes <lists at cheimes.de> added the comment:

The backport to 3.6 and 3.7 are breaking backwards compatibility and compatibility with PEP 247.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 03:37:40 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 31 Jul 2018 07:37:40 +0000
Subject: [docs] [issue27671] FAQ: len() is still function for good reason.
In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za>
Message-ID: <1533022660.73.0.902498594338.issue27671@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27671>
_______________________________________

From report at bugs.python.org  Tue Jul 31 04:06:49 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 31 Jul 2018 08:06:49 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533024409.91.0.56676864532.issue33729@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Sorry. Do you prefer to revert the whole changes or just some parts?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 09:10:13 2018
From: report at bugs.python.org (jfbu)
Date: Tue, 31 Jul 2018 13:10:13 +0000
Subject: [docs] [issue34293] DOC: Makefile inherits a Sphinx 1.5 bug
 regarding PAPER envvar
Message-ID: <1533042613.34.0.56676864532.issue34293@psf.upfronthosting.co.za>


New submission from jfbu <jfbu at free.fr>:

There has been a bug at Sphinx since release 1.5 https://github.com/sphinx-doc/sphinx/issues/5234 about wrong handling of PAPER environment variable. The Makefile in Doc/ reproduces the error. As a result the "A4 latex" and "letter latex" sub targets of "dist" mis-behave.

A bugfix will be released at Sphinx 1.7.7 or 1.8 but the CPython Doc/Makefile needs an update, because the bugfix can only solve problems for new projects created with sphinx-quickstart (whether or not using the "make-mode" small Makefile, or the "no-make-mode" bigger Makefile which was default up to Sphinx 1.5).

I will send PR next.

----------
assignee: docs at python
components: Documentation
messages: 322770
nosy: docs at python, jfbu
priority: normal
severity: normal
status: open
title: DOC: Makefile inherits a Sphinx 1.5 bug regarding PAPER envvar
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34293>
_______________________________________

From report at bugs.python.org  Tue Jul 31 09:32:34 2018
From: report at bugs.python.org (jfbu)
Date: Tue, 31 Jul 2018 13:32:34 +0000
Subject: [docs] [issue34293] DOC: Makefile inherits a Sphinx 1.5 bug
 regarding PAPER envvar
In-Reply-To: <1533042613.34.0.56676864532.issue34293@psf.upfronthosting.co.za>
Message-ID: <1533043954.26.0.902498594338.issue34293@psf.upfronthosting.co.za>


Change by jfbu <jfbu at free.fr>:


----------
keywords: +patch
pull_requests: +8094
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34293>
_______________________________________

From report at bugs.python.org  Tue Jul 31 09:40:15 2018
From: report at bugs.python.org (jfbu)
Date: Tue, 31 Jul 2018 13:40:15 +0000
Subject: [docs] [issue34293] DOC: Makefile inherits a Sphinx 1.5 bug
 regarding PAPER envvar
In-Reply-To: <1533042613.34.0.56676864532.issue34293@psf.upfronthosting.co.za>
Message-ID: <1533044415.8.0.56676864532.issue34293@psf.upfronthosting.co.za>


jfbu <jfbu at free.fr> added the comment:

https://github.com/python/cpython/pull/8585

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34293>
_______________________________________

From report at bugs.python.org  Tue Jul 31 10:25:08 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 31 Jul 2018 14:25:08 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533047107.99.0.56676864532.issue33729@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

I have no opinion on the change in the master branch, but I agree with Christian that the 3.7 change should be reverted since it breaks the backward compatibility.

Serhiy modified int() in Python 3.7 to convert its first parameter to positional only parameter. IMHO it's ok to do such change. Moreover, the change has been documented in What's New in Python 3.7:
https://docs.python.org/dev/whatsnew/3.7.html#api-and-feature-removals

If you decide to keep the change in the master branch, it should be documented in What's New in Python 3.8, no?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 11:54:12 2018
From: report at bugs.python.org (Emily Morehouse)
Date: Tue, 31 Jul 2018 15:54:12 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1533052452.42.0.56676864532.issue34237@psf.upfronthosting.co.za>


Emily Morehouse <emilyemorehouse at gmail.com> added the comment:

This issue was brought to my attention -- I'm helping build the PEP 572 implementation. I'll make sure the docs get updated (and Jonathan, I didn't actually know that assignment expressions were mentioned in the FAQ, so this was still helpful!)

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

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Tue Jul 31 11:57:24 2018
From: report at bugs.python.org (Chris Angelico)
Date: Tue, 31 Jul 2018 15:57:24 +0000
Subject: [docs] [issue34237] faq/design: PEP 572 adds assignment expressions
In-Reply-To: <1532614776.63.0.56676864532.issue34237@psf.upfronthosting.co.za>
Message-ID: <1533052644.8.0.56676864532.issue34237@psf.upfronthosting.co.za>


Chris Angelico <rosuav at gmail.com> added the comment:

BTW, sorry for sounding a bit snippy in my comment. Jonathan, in future, rather than dropping someone an email, it'd be more normal to just ping the person on the issue itself.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34237>
_______________________________________

From report at bugs.python.org  Tue Jul 31 12:22:18 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 31 Jul 2018 16:22:18 +0000
Subject: [docs] [issue33729] Hashlib/blake2* missing 'data' keyword argument
In-Reply-To: <1527842171.52.0.682650639539.issue33729@psf.upfronthosting.co.za>
Message-ID: <1533054138.55.0.56676864532.issue33729@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

In case of int() the name of it's first argument was documented, in both the module documentation, and in interactive help. But the documented name of the first blake2b() argument was "data", and it never worked. Since help() was not worked for blake2b, the user had weak chance to know that the actual name is "string". Thus there is much less chance of breaking the user code by making this parameter a positional-only than in case of int().

But I think Christian has other concerns.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33729>
_______________________________________

From report at bugs.python.org  Tue Jul 31 14:07:05 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 31 Jul 2018 18:07:05 +0000
Subject: [docs] [issue34203] documentation: recommend Python 3 over 2 in faq
In-Reply-To: <1532397328.96.0.56676864532.issue34203@psf.upfronthosting.co.za>
Message-ID: <1533060425.9.0.902498594338.issue34203@psf.upfronthosting.co.za>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34203>
_______________________________________

From gottfried.mueller at gmx.de  Mon Jul 30 05:51:17 2018
From: gottfried.mueller at gmx.de (=?UTF-8?Q?Gottfried_M=c3=bcller?=)
Date: Mon, 30 Jul 2018 11:51:17 +0200
Subject: [docs] Documentation python3/library/signal: example does not work:
 SIGALARM unknow in signal
Message-ID: <db29a57a-5525-80ec-70f8-5d2f17c266e3@gmx.de>

Hello,

I've got this message:

signal.signal(signal.SIGALARM, myHandler)
AttributeError: module 'signal' has no attribute 'SIGALARM'

I am using Manjaro/Python version 3.6.6.

Gottfried