From report at bugs.python.org  Wed Feb  1 12:38:56 2017
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 01 Feb 2017 17:38:56 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485970736.59.0.781535386185.issue29407@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

LGTM, and should be committed to 3.5 and merged upwards from there.

And yes, it's time for the asyncio docs to converge on async/await everywhere, making `yield from` a footnoot to history.

----------

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

From report at bugs.python.org  Wed Feb  1 14:10:16 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Wed, 01 Feb 2017 19:10:16 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
Message-ID: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>


New submission from Jim Fasarakis-Hilliard:

The current line is confusing hinting that the for statement is actually an object, it also makes a reference to iterators which the tutorial doesn't disambiguate until the chapter on Classes.

I've added a small patch that, in my opinion, makes it clearer by using the terminology of the previous sentence.

----------
assignee: docs at python
components: Documentation
messages: 286678
nosy: Jim Fasarakis-Hilliard, docs at python
priority: normal
severity: normal
status: open
title: Change 'the for statement is such an iterator' in Tutorial
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Wed Feb  1 14:11:11 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Wed, 01 Feb 2017 19:11:11 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1485976271.44.0.272078377169.issue29414@psf.upfronthosting.co.za>


Changes by Jim Fasarakis-Hilliard <d.f.hilliard at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file46482/issue29414.patch

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

From report at bugs.python.org  Wed Feb  1 14:33:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 19:33:26 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <20170201193322.111010.77928.F94BB257@psf.io>


Roundup Robot added the comment:

New changeset e4f6874abda6 by Berker Peksag in branch '3.5':
Issue #29407: Remove redundant ensure_future() calls in factorial example
https://hg.python.org/cpython/rev/e4f6874abda6

New changeset 7196ab02b7ce by Berker Peksag in branch '3.6':
Issue #29407: Merge from 3.5
https://hg.python.org/cpython/rev/7196ab02b7ce

New changeset 0990a071751f by Berker Peksag in branch 'default':
Issue #29407: Merge from 3.6
https://hg.python.org/cpython/rev/0990a071751f

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

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

From report at bugs.python.org  Wed Feb  1 14:35:06 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 01 Feb 2017 19:35:06 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485977706.47.0.592078649495.issue29407@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the review, Guido.

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

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

From report at bugs.python.org  Wed Feb  1 14:49:24 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 01 Feb 2017 19:49:24 +0000
Subject: [docs] [issue29344] sock_recv not detected a coroutine
In-Reply-To: <1485094185.41.0.725056014669.issue29344@psf.upfronthosting.co.za>
Message-ID: <1485978564.57.0.131253081603.issue29344@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Here's a patch. sock_connect() wrapped by @coroutine in Lib/asyncio/selector_events.py so I left it as-is. Let me know if it still needs to be updated:

    @coroutine
    def sock_connect(self, sock, address):
        """Connect to a remote socket at address.

        This method is a coroutine.
        """
        ...

        return (yield from fut)

----------
assignee:  -> docs at python
components: +Documentation
keywords: +patch
nosy: +docs at python
stage:  -> patch review
Added file: http://bugs.python.org/file46483/issue29344.diff

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

From report at bugs.python.org  Wed Feb  1 15:00:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:26 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979226.49.0.601618712593.issue29407@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset 94aa4efdf0196de9f99b6f1bd68322939d8d6974 by Berker Peksag in branch '3.6':
Issue #29407: Remove redundant ensure_future() calls in factorial example
https://github.com/python/cpython/commit/94aa4efdf0196de9f99b6f1bd68322939d8d6974

New changeset 96104636fa5bd3054367d4667d86d43690c24293 by Berker Peksag in branch '3.6':
Issue #29407: Merge from 3.5
https://github.com/python/cpython/commit/96104636fa5bd3054367d4667d86d43690c24293


----------

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

From report at bugs.python.org  Wed Feb  1 15:00:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:26 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979226.6.0.714866812229.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:26 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979226.71.0.871067258531.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:26 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979226.65.0.404570458147.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:28 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979228.52.0.498720746591.issue29407@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset 94aa4efdf0196de9f99b6f1bd68322939d8d6974 by Berker Peksag in branch '3.5':
Issue #29407: Remove redundant ensure_future() calls in factorial example
https://github.com/python/cpython/commit/94aa4efdf0196de9f99b6f1bd68322939d8d6974


----------

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

From report at bugs.python.org  Wed Feb  1 15:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:28 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979228.64.0.946577703984.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:28 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979228.7.0.322241624083.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:28 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979228.75.0.633146283546.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:30 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:30 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979230.7.0.254527598692.issue29407@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset 94aa4efdf0196de9f99b6f1bd68322939d8d6974 by Berker Peksag in branch 'master':
Issue #29407: Remove redundant ensure_future() calls in factorial example
https://github.com/python/cpython/commit/94aa4efdf0196de9f99b6f1bd68322939d8d6974

New changeset 96104636fa5bd3054367d4667d86d43690c24293 by Berker Peksag in branch 'master':
Issue #29407: Merge from 3.5
https://github.com/python/cpython/commit/96104636fa5bd3054367d4667d86d43690c24293

New changeset 6b569a0de28e3c341837030d6aa739422d315a6f by Berker Peksag in branch 'master':
Issue #29407: Merge from 3.6
https://github.com/python/cpython/commit/6b569a0de28e3c341837030d6aa739422d315a6f


----------

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

From report at bugs.python.org  Wed Feb  1 15:00:30 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:30 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979230.8.0.357540339666.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:30 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:30 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979230.9.0.245098170535.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:00:30 2017
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 01 Feb 2017 20:00:30 +0000
Subject: [docs] [issue29407] Remove redundant ensure_future() calls in
 factorial example
In-Reply-To: <1485911347.12.0.0497985806483.issue29407@psf.upfronthosting.co.za>
Message-ID: <1485979230.86.0.586944809653.issue29407@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Wed Feb  1 15:06:00 2017
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 01 Feb 2017 20:06:00 +0000
Subject: [docs] [issue29344] sock_recv not detected a coroutine
In-Reply-To: <1485094185.41.0.725056014669.issue29344@psf.upfronthosting.co.za>
Message-ID: <1485979560.83.0.375108885525.issue29344@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

I think the original idea was to document that all methods of the loop are coroutines, so that:

1. if a user needs a Future object they call ensure_future: 

   fut = asyncio.ensure_future(loop.method())

2. it gives us ability to refactor things. For instance, sock_connect was a method that returned Futures, but at one point of 3.5 we changed it to be coroutine.  Because the method was documented as a coroutine, it wasn't strictly a backwards incompatible way.

In general, I think it would be safer for us to simple make all loop methods coroutines. Or, less radical, just keeping the status quo: document everything as a coroutine.

----------

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

From ncoghlan at gmail.com  Wed Feb  1 15:40:11 2017
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Wed, 1 Feb 2017 21:40:11 +0100
Subject: [docs] [Python-ideas]  https://docs.python.org/fr/ ?
In-Reply-To: <CAP1=2W5AxCj7V-Gnq-Dj4hmXJouL3m5=gneDk784x9==LLutPg@mail.gmail.com>
References: <56ED7EBD.5050804@palard.fr>
 <CAEfz+Txw+oh_rP1j4nCEpOzbvEmEU+Z8f8wgEqO7V3yd8HuwzA@mail.gmail.com>
 <CAF4280J-0cS7wU31qwCG_axGF-CmQ-iA3j1NGkRExY0ZgfN3sA@mail.gmail.com>
 <CAP1=2W5AxCj7V-Gnq-Dj4hmXJouL3m5=gneDk784x9==LLutPg@mail.gmail.com>
Message-ID: <CADiSq7fFYXfsRzMrD7TBn_j_aNJS-spBD4zyDrkBa2Ww0rVsOw@mail.gmail.com>

On 30 January 2017 at 19:03, Brett Cannon <brett at python.org> wrote:
> On Mon, 30 Jan 2017 at 07:16 Berker Peksa? <berker.peksag at gmail.com> wrote:
>> +1 for b) or any idea that would indicate that the Python developers
>> don't maintain translations of the official documentation. I don't
>> have a strong opinion on naming the GitHub organization (maybe
>> python-docs-translations?) but that can be discussed later. Another
>> advantage of this approach is that you can have separate issue
>> trackers for each language (e.g. python-docs-fr) so people can easily
>> report documentation issues in their native languages.
>
> Does hosting on Read the Docs makes any of this easier/harder?

RTD models translations as separate projects, so it should make it
easier: http://docs.readthedocs.io/en/latest/localization.html#project-with-multiple-translations

Most importantly, because they're separate projects, each translation
will get to set its own project home page and source control repo
reference.

It will still be up to translation authors to make some of the manual
changes that Terry mentions to point people to the right issue
trackers, but it shouldn't be any worse than what we see with
occasionally redirecting people to the Python Packaging Authority
issue trackers for various purposes.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From report at bugs.python.org  Wed Feb  1 16:32:34 2017
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 01 Feb 2017 21:32:34 +0000
Subject: [docs] [issue29344] sock_recv not detected a coroutine
In-Reply-To: <1485094185.41.0.725056014669.issue29344@psf.upfronthosting.co.za>
Message-ID: <1485984754.39.0.00325334146915.issue29344@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

The word coroutine has a more specific meaning though (and we have iscoroutine*() inspection functions to check for it).

Maybe we should switch all these to "awaitable"?

Also note that in proactor_events.py, sock_connect() is *not* a coroutine. In fact I'm not sure what it is -- it calls self._proactor.connect() which appears to return None from the code in windows_events.py. That's presumably a separate bug.

----------

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

From report at bugs.python.org  Wed Feb  1 16:46:57 2017
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 01 Feb 2017 21:46:57 +0000
Subject: [docs] [issue29344] sock_recv not detected a coroutine
In-Reply-To: <1485094185.41.0.725056014669.issue29344@psf.upfronthosting.co.za>
Message-ID: <1485985617.34.0.102213112583.issue29344@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

> Maybe we should switch all these to "awaitable"?

I like this!  Would it be OK to add a new sphinx declaration?  So that:

   .. coroutinemethod:: AbstractEventLoop.shutdown_asyncgens()

would become:

   .. awaitable:: AbstractEventLoop.shutdown_asyncgens()
   
?

> Also note that in proactor_events.py, sock_connect() is *not* a coroutine. 

Yeah, those small incompatibilities are inevitable for asyncio programs/frameworks -- something that returns a Future may occasionally become a coroutine.  Your idea to document API methods as "awaitables" seems to be the right way to go.

> In fact I'm not sure what it is -- it calls self._proactor.connect() which appears to return None from the code in windows_events.py. That's presumably a separate bug.

It looks like it returns the result of "IocpProactor.connect()" call, which returns an _OverlappedFuture instance (I don't really know Windows part of asyncio code, so I might be missing something).

----------

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

From report at bugs.python.org  Wed Feb  1 16:58:49 2017
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 01 Feb 2017 21:58:49 +0000
Subject: [docs] [issue29344] sock_recv not detected a coroutine
In-Reply-To: <1485985617.34.0.102213112583.issue29344@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJJLnPQZUgqmxDdRy=me==iFK+KY7ZAOajh5GgWu++m+zg@mail.gmail.com>


Guido van Rossum added the comment:

A new Sphinx declaration sounds great to me, but you might want to check
with some Sphinx or Python-docs expert.

I somehow misread the code of IocpProactor.connect(), so ignore that part
-- the point is that it's not always a coroutine.

----------

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

From report at bugs.python.org  Wed Feb  1 23:21:39 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 04:21:39 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <20170202042135.25874.71162.E2DFD25B@psf.io>


Roundup Robot added the comment:

New changeset 3d712292f2fa by Mariatta Wijaya in branch '3.6':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://hg.python.org/cpython/rev/3d712292f2fa

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

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

From report at bugs.python.org  Thu Feb  2 00:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 05:00:23 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486011622.96.0.40727776318.issue29381@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset abfa17511f7ce8f1a6394f28f82ffb9a916fcf03 by Mariatta Wijaya in branch '3.6':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://github.com/python/cpython/commit/abfa17511f7ce8f1a6394f28f82ffb9a916fcf03


----------

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

From report at bugs.python.org  Thu Feb  2 00:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 05:00:23 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486011623.18.0.66376762644.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

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

From report at bugs.python.org  Thu Feb  2 00:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 05:00:23 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486011623.38.0.868773825339.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
resolution:  -> fixed

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

From report at bugs.python.org  Thu Feb  2 00:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 05:00:23 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486011623.47.0.762911527976.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

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

From report at bugs.python.org  Thu Feb  2 00:04:01 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 05:04:01 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <20170202050358.8335.36941.9EF9A91B@psf.io>


Roundup Robot added the comment:

New changeset 483d9133fd7e by Mariatta Wijaya in branch '3.6':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://hg.python.org/cpython/rev/483d9133fd7e

New changeset 762a93935afd by Mariatta Wijaya in branch 'default':
Issue #29381: merge with 3.6
https://hg.python.org/cpython/rev/762a93935afd

----------

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

From report at bugs.python.org  Thu Feb  2 00:21:16 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 05:21:16 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <20170202052113.7701.10871.571B1073@psf.io>


Roundup Robot added the comment:

New changeset df356d3c916e by Mariatta Wijaya in branch '2.7':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://hg.python.org/cpython/rev/df356d3c916e

----------

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

From report at bugs.python.org  Thu Feb  2 00:42:59 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 02 Feb 2017 05:42:59 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486014178.94.0.215543133238.issue29381@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Jim, Marco, and Raymond :)

----------

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

From report at bugs.python.org  Thu Feb  2 01:00:22 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:22 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015222.78.0.0881624672436.issue29381@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset 848eeb1debc94a82660bf5af4e3d554b02b81c2e by Mariatta Wijaya in branch '3.6':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://github.com/python/cpython/commit/848eeb1debc94a82660bf5af4e3d554b02b81c2e


----------

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

From report at bugs.python.org  Thu Feb  2 01:00:22 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:22 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015222.89.0.427116885172.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:23 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015223.15.0.665876836772.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:23 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015223.29.0.469230937733.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:24 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:24 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015224.6.0.048592625285.issue29381@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset 3f5b24dd4b38bf885a80f4bb5f605cd6b0c49ead by Mariatta Wijaya in branch '2.7':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://github.com/python/cpython/commit/3f5b24dd4b38bf885a80f4bb5f605cd6b0c49ead


----------

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

From report at bugs.python.org  Thu Feb  2 01:00:24 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:24 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015224.71.0.715154668298.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:24 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:24 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015224.77.0.718165113001.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:24 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:24 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015224.83.0.602765154229.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:28 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015228.55.0.0470688286526.issue29381@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset abfa17511f7ce8f1a6394f28f82ffb9a916fcf03 by Mariatta Wijaya in branch 'master':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://github.com/python/cpython/commit/abfa17511f7ce8f1a6394f28f82ffb9a916fcf03

New changeset 848eeb1debc94a82660bf5af4e3d554b02b81c2e by Mariatta Wijaya in branch 'master':
Issue #29381: Clarify ordering of UNIX shebang line as source encoding line
https://github.com/python/cpython/commit/848eeb1debc94a82660bf5af4e3d554b02b81c2e

New changeset 35519d021ece942efc4a710ea3e94bcc5c06b130 by Mariatta Wijaya in branch 'master':
Issue #29381: merge with 3.6
https://github.com/python/cpython/commit/35519d021ece942efc4a710ea3e94bcc5c06b130


----------

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

From report at bugs.python.org  Thu Feb  2 01:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:28 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015228.67.0.645425626448.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:28 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015228.73.0.953738297283.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:00:28 +0000
Subject: [docs] [issue29381] Tutorial documentation contains undefined
 reference to #!
In-Reply-To: <1485537602.74.0.811037724367.issue29381@psf.upfronthosting.co.za>
Message-ID: <1486015228.79.0.101228020481.issue29381@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 01:22:28 2017
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 02 Feb 2017 06:22:28 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486016548.47.0.00296056144412.issue29329@psf.upfronthosting.co.za>


Zachary Ware added the comment:

LGTM.

----------
assignee: docs at python -> Mariatta
nosy: +Mariatta, zach.ware
stage: needs patch -> commit review

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

From report at bugs.python.org  Thu Feb  2 01:27:17 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 06:27:17 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <20170202062713.96198.75158.3B5D3721@psf.io>


Roundup Robot added the comment:

New changeset d7804789368a by Mariatta Wijaya in branch '2.7':
Issue #29329: Improve documentation for hex(). Patch by Ammar Askar
https://hg.python.org/cpython/rev/d7804789368a

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

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

From report at bugs.python.org  Thu Feb  2 01:33:57 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 02 Feb 2017 06:33:57 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486017237.77.0.390590159532.issue29329@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Pekka, Eryk, Ammar, and Zachary :)

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

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

From report at bugs.python.org  Thu Feb  2 01:49:43 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 02 Feb 2017 06:49:43 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486018183.08.0.383902112447.issue29329@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Thu Feb  2 02:00:19 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 07:00:19 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486018819.45.0.66162438403.issue29329@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset d03fd5d041b6f514daf0aabc0c159d8727c33980 by Mariatta Wijaya in branch '2.7':
Issue #29329: Improve documentation for hex(). Patch by Ammar Askar
https://github.com/python/cpython/commit/d03fd5d041b6f514daf0aabc0c159d8727c33980


----------

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

From report at bugs.python.org  Thu Feb  2 02:00:19 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 07:00:19 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486018819.58.0.468036422294.issue29329@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 02:00:19 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 07:00:19 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486018819.65.0.582510790483.issue29329@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From report at bugs.python.org  Thu Feb  2 02:00:19 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2017 07:00:19 +0000
Subject: [docs] [issue29329] Incorrect documentation for custom `hex()`
 support on Python 2
In-Reply-To: <1484852138.82.0.311515909069.issue29329@psf.upfronthosting.co.za>
Message-ID: <1486018819.72.0.505707349548.issue29329@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


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

From songofacandy at gmail.com  Thu Feb  2 05:12:24 2017
From: songofacandy at gmail.com (INADA Naoki)
Date: Thu, 2 Feb 2017 19:12:24 +0900
Subject: [docs] [Python-ideas]  https://docs.python.org/fr/ ?
In-Reply-To: <CADiSq7fFYXfsRzMrD7TBn_j_aNJS-spBD4zyDrkBa2Ww0rVsOw@mail.gmail.com>
References: <56ED7EBD.5050804@palard.fr>
 <CAEfz+Txw+oh_rP1j4nCEpOzbvEmEU+Z8f8wgEqO7V3yd8HuwzA@mail.gmail.com>
 <CAF4280J-0cS7wU31qwCG_axGF-CmQ-iA3j1NGkRExY0ZgfN3sA@mail.gmail.com>
 <CAP1=2W5AxCj7V-Gnq-Dj4hmXJouL3m5=gneDk784x9==LLutPg@mail.gmail.com>
 <CADiSq7fFYXfsRzMrD7TBn_j_aNJS-spBD4zyDrkBa2Ww0rVsOw@mail.gmail.com>
Message-ID: <CAEfz+TwOk0D-WnPEwdtjd2g12oFxibXqCJwa+iWX1mmYkNX9Eg@mail.gmail.com>

>> Does hosting on Read the Docs makes any of this easier/harder?
>
> RTD models translations as separate projects, so it should make it
> easier: http://docs.readthedocs.io/en/latest/localization.html#project-with-multiple-translations
>
> Most importantly, because they're separate projects, each translation
> will get to set its own project home page and source control repo
> reference.

I haven't know RTD supports i18n!

But we split repository of Python and *.po files.  So we need Travis
or other CI server.

Current our build script is here.
https://github.com/python-doc-ja/py35-locale/blob/master/.travis.yml

From report at bugs.python.org  Thu Feb  2 06:10:41 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 02 Feb 2017 11:10:41 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1486033841.41.0.379284141192.issue29414@psf.upfronthosting.co.za>


Marco Buttu added the comment:

I agree with you that the current sentence:

"We have seen that the for statement is such an iterator"

is wrong. But also the new sentence IMHO is confusing, because it stills compare statementes with objects:

"the for statement expects an object that is iterable. The function list is another; it creates lists from iterables". 

Also list is a class, not a function.
IMHO the goal of the sentence you want to patch is to complete the previous one [1], adding an example of "construct" that operates with iterables, and of function that takes an iterable. If you want to follow that purpose, I suggest somethink like this:

"We have seen that the for statement is such a construct, while examples of functions that take an iterable are ``sum()`` and ``max()``::"

Written in better English than mine...


[1] "We say such an object is iterable, that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted."

----------
nosy: +marco.buttu

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

From report at bugs.python.org  Thu Feb  2 09:58:05 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 02 Feb 2017 14:58:05 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1486047485.13.0.357031506183.issue29414@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Feb  2 14:10:41 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 02 Feb 2017 19:10:41 +0000
Subject: [docs] [issue28749] Fixed the documentation of the mapping codec
 APIs
In-Reply-To: <1479637798.25.0.994184606714.issue28749@psf.upfronthosting.co.za>
Message-ID: <1486062641.01.0.495979150719.issue28749@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> serhiy.storchaka

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

From report at bugs.python.org  Thu Feb  2 21:37:49 2017
From: report at bugs.python.org (Eric Lafontaine)
Date: Fri, 03 Feb 2017 02:37:49 +0000
Subject: [docs] [issue28972] Document all "python -m" utilities
In-Reply-To: <1481720403.32.0.43245427479.issue28972@psf.upfronthosting.co.za>
Message-ID: <1486089469.37.0.893811903782.issue28972@psf.upfronthosting.co.za>


Eric Lafontaine added the comment:

Hi,

I've just watched the old David Beazley video about the packaging system in python and got me thinking about this issue.

I'm throwing the idea, please critize it!

If we were to make a "hook" for the .rst files of the modules to go and scan the __main__.py file for the comments, generating the 'index' of all those options from the comments inside the file (__main__.py).  That would be in my opinion a solution to make sure they are kept to date and would also insure someone knows minimally what he's doing as he's playing inside the main of a package.  The idea is similar to the autodoc module of sphinx that scan a module for the doc, but would apply to the __main__.py only.  However, I've just started with .rst files and I'm not sure how we could 'implement' that and even less if it's possible at all.

(BTW, I would only enable the .rst "hook" option generation on the __main__.py file as to keep sort of a standardisation but not obligation)

P.S. I know I initially seems skeptical, but I have started to see the use thanks to you :)  The example was good (msg283470).  
Regards,
Eric Lafontaine

----------

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

From report at bugs.python.org  Fri Feb  3 01:25:13 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 03 Feb 2017 06:25:13 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
Message-ID: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>


New submission from Jim DeLaHunt:

I just had a problem with doctests. It manifested as an error that occurred when I did
>>> import StringIO
in my doctest. 

After some investigation, I realised that my actual problem was that the doctest library documentation https://docs.python.org/3/library/doctest.html left me unclear about three aspects of multi-line doctest fixtures.

1. There is no example of a multiple-line doctest fixture: specifically, a fixture which involves at least one line to set up state, and another line to be the example that tested.  I suggest adding such an example as a new section, "26.3.2. Usage: multi-line tests".  Note that the example in 26.3.3.2 doesn't count: that is a Compound Statement, and I'm talking about a test consisting of multiple interactive statements.

2. Section "26.3.3.2. How are Docstring Examples Recognized?" does not talk about when to use a PS1 prefix (>>>) and when to use a PS2 prefix (...). It should say to use the PS1 at the start of each Python "interactive statement", that is, a statement list ending with a newline, or a Compound Statement. And, to use the PS2 to prefix each continuing line within a Compound Statement. 

3. Section "26.3.3.3. What?s the Execution Context?" is not clear about the crucial difference between state that accumulates within a single docstring from Example to Example, and that is reset from one docstring to another. The phrase "so that one test in M can?t leave behind crumbs that accidentally allow another test to work" can be interpreted as applying within a single docstring. The phrase "names defined earlier in the docstring being run" is easy to miss.

A StackOverflow Question and Answer describing my problem and my insight about what the library documentation didn't tell me is at http://stackoverflow.com/questions/41070547/why-is-importing-a-module-breaking-my-doctest-python-2-7 . A blog post of mine, a source for documentation improvements, is at http://blog.jdlh.com/en/2017/01/31/multi-line-doctests/ .

I actually encountered this problem in a Python 2.7 context, with https://docs.python.org/2/library/doctest.html . But it also applies to Python 3.6 https://docs.python.org/3/library/doctest.html and to the current dev https://docs.python.org/dev/library/doctest.html . In the spirit of fixing the new stuff first, I am filing this issue against Python 3.7. 

Unless someone tells me otherwise, I'll get around to filing similar issues against Python 3.6 and Python 2.7.
Then it's my intention to write improvements to the documentation for Python 3.7, 3.6, and 2.7, and submit each of those. It looks like they will be pretty similar, because the library documentation is pretty similar in each version.

I'm new to Python issue filing and doc fixing, so I would appreciate correction if (when?) I start to blunder.

----------
assignee: docs at python
components: Documentation
messages: 286843
nosy: JDLH, docs at python
priority: normal
severity: normal
status: open
title: Doctest documentation unclear about multi-line fixtures
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Fri Feb  3 04:29:15 2017
From: report at bugs.python.org (Marco Buttu)
Date: Fri, 03 Feb 2017 09:29:15 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486114155.31.0.761428422055.issue29428@psf.upfronthosting.co.za>


Marco Buttu added the comment:

> I just had a problem with doctests. It manifested as an
> error that occurred when I did
> >>> import StringIO in my doctest.

Maybe you are running the doctest with Python 3. The StringIO module is no more available in Python 3, so your doctest will fail on Python 3 and will pass on Python 2.

> 1. There is no example of a multiple-line doctest fixture:
> specifically, a fixture which involves at least one line to
> set up state, and another line to be the example that tested.
> I suggest adding such an example as a new section, "26.3.2.
> Usage: multi-line tests".
> Note that the example in 26.3.3.2 doesn't count: that is a
> Compound Statement, and I'm talking about a test consisting
> of multiple interactive statements.

The example in section 26.3.3.2 [1], before the compound statement (the if/else), contains two simple statements. I also think the example is complete and straightforward for its purpose, and it does not have to be complicated adding avanced features. If you want a more complex control over your tests, for instance adding fixtures, you can find how to do it later, in [2].

> 2. Section "26.3.3.2. How are Docstring Examples Recognized?" does
> not talk about when to use a PS1 prefix (>>>) and when to use a
> PS2 prefix (...). It should say to use the PS1 at the start of each
> Python "interactive statement", that is, a statement list ending with
> a newline, or a Compound Statement. And, to use the PS2 to prefix each
> continuing line within a Compound Statement. 

I am -1 on this. IMHO there is no need to add extra description to a such self-explaining, clear and concise example. But this I think is also clear from the beginning. Infact, the first line of the doc says: "The doctest module searches for pieces of text that look like interactive Python sessions"

> 3. Section "26.3.3.3. What?s the Execution Context?" is not
> clear about the crucial difference between state that accumulates
> within a single docstring from Example to Example, and that is reset
> from one docstring to another. The phrase "so that one test in M can?t
> leave behind crumbs that accidentally allow another test to work"
> can be interpreted as applying within a single docstring. The phrase
> "names defined earlier in the docstring being run" is easy to miss.

Also this section IMO is well written and clear. I do not know what to say... If someone else thinks it is not enough understandable, maybe the better think to do is to add a very small example, with two functions, that shows their docstrings have independent globals.

> Unless someone tells me otherwise, I'll get around to filing similar
> issues against Python 3.6 and Python 2.7.
> Then it's my intention to write improvements to the documentation
> for Python 3.7, 3.6, and 2.7, and submit each of those.

Keep in mind that writing a patch is not enough. The patch has to be reviewed, and that means other people have to find the time to work on it. I suggest you to watch this talk of Raymond Hettinger, before going on:

https://www.youtube.com/watch?v=voXVTjwnn-U


[1] https://docs.python.org/3/library/doctest.html#how-are-docstring-examples-recognized
[2] https://docs.python.org/3/library/doctest.html#unittest-api

----------
nosy: +marco.buttu

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

From report at bugs.python.org  Fri Feb  3 05:11:51 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Fri, 03 Feb 2017 10:11:51 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486116711.2.0.433491410887.issue29387@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

LGTM. -t is not removed but only ignored in Py3 for backwards compatibility. And I am fine with the wording.

----------
nosy: +xiang.zhang

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

From 13781136833 at 163.com  Fri Feb  3 06:16:09 2017
From: 13781136833 at 163.com (=?GBK?B?5/c=?=)
Date: Fri, 3 Feb 2017 19:16:09 +0800 (CST)
Subject: [docs] python calculate error
Message-ID: <5a17557f.78bc.15a03b04c84.Coremail.13781136833@163.com>

I just test the version 2.7.10 and 3.5.2, on windows 7 SP1 x86, windows 7 SP1 x64 and linux debian amd64.
I hope can get the answer from you quickly, thanks.


18.35 - 9.35
9.000000000000002


18.35 - (12 - 2.65)
9.000000000000002















 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/2e4a8104/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 527a6bbf.png
Type: image/png
Size: 28910 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/2e4a8104/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7b8a8eb9.png
Type: image/png
Size: 358867 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/2e4a8104/attachment-0003.png>

From httese at gmail.com  Fri Feb  3 06:21:08 2017
From: httese at gmail.com (=?UTF-8?B?55Cq?=)
Date: Fri, 3 Feb 2017 19:21:08 +0800
Subject: [docs] Fwd: python calculate error
In-Reply-To: <60e17e0b.78f0.15a03b3313d.Coremail.13781136833@163.com>
References: <60e17e0b.78f0.15a03b3313d.Coremail.13781136833@163.com>
Message-ID: <CAEGvqSZooux=_QFNv5svaP5viY33cSO3ehL4XbGDEn4hKW=yxw@mail.gmail.com>

---------- Forwarded message ----------
From: ? <13781136833 at 163.com>
Date: 2017-02-03 19:19 GMT+08:00
Subject: python calculate error
To: httese at gmail.com


I just test the version 2.7.10 and 3.5.2, on windows 7 SP1 x86, windows 7
SP1 x64 and linux debian amd64.
I hope can get the answer from you quickly, thanks.

18.35 - 9.35
9.000000000000002

18.35 - (12 - 2.65)
9.000000000000002
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/c64309ab/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7b8a8eb9.png
Type: image/png
Size: 358867 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/c64309ab/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 527a6bbf.png
Type: image/png
Size: 28910 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/c64309ab/attachment-0003.png>

From report at bugs.python.org  Fri Feb  3 08:09:51 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Fri, 03 Feb 2017 13:09:51 +0000
Subject: [docs] [issue29378] Invalid example in documentation for PyErr_Fetch
In-Reply-To: <1485447904.37.0.693014852804.issue29378@psf.upfronthosting.co.za>
Message-ID: <1486127391.6.0.787060158724.issue29378@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

I can't see any problem with the example either. So I just close this issue for now. But if you still think it gets problems please reopen it and tell your thoughts.

----------
nosy: +xiang.zhang
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From 13781136833 at 163.com  Fri Feb  3 06:02:50 2017
From: 13781136833 at 163.com (=?GBK?B?5/c=?=)
Date: Fri, 3 Feb 2017 19:02:50 +0800 (CST)
Subject: [docs] python calculate error
Message-ID: <65b21097.77dd.15a03a4190b.Coremail.13781136833@163.com>

I just test the version 2.7.10 and 3.5.2, on windows 7 SP1 x86, windows 7 SP1 x64 and linux debian amd64.
I hope can get the answer from you quickly, thanks.


18.35 - 9.35
9.000000000000002


18.35 - (12 - 2.65)
9.000000000000002









-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/23fcb62c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 527a6bbf.png
Type: image/png
Size: 28910 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/23fcb62c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7b8a8eb9.png
Type: image/png
Size: 358867 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/23fcb62c/attachment-0003.png>

From report at bugs.python.org  Fri Feb  3 09:42:56 2017
From: report at bugs.python.org (R. David Murray)
Date: Fri, 03 Feb 2017 14:42:56 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486132976.88.0.95919708864.issue29428@psf.upfronthosting.co.za>


R. David Murray added the comment:

It does appear that "test" is being used ambiguously in the docs.  In most places it means a single statement, but in execution context it appears to be being used as a synonym for "docstring".  In that section it should be replaced by "docstring".  It would probably be worth checking the rest of the doc to make sure it is used consistently elsewhere as well.

As for the prompts, I agree with Marco: I don't think there is any need to add words, since it clearly says it is supposed to look like an interactive session and the reader gets reminded of the rules for that by the example provided.  IMO it is not appropriate to re-document those rules here.  However, if you come up with a really concise addition that clarifies it, we'll consider it.

I don't think an additional example of using previous state is required, and certainly not an additional section.  The execution context section makes it clear that you can use names defined earlier, as does the fact that doctests emulate interactive sessions.  Both of these make it clear you can do multi line examples that use shared state.  However, if you come up with an example that adds value to the documentation, we'll certainly consider it.

So in summary, I think we *need* a one word change in the execution context section, and we'll consider any other enhancements you want to propose.

----------
nosy: +r.david.murray
versions: +Python 2.7, Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri Feb  3 09:44:17 2017
From: report at bugs.python.org (R. David Murray)
Date: Fri, 03 Feb 2017 14:44:17 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486133057.87.0.782169346745.issue29428@psf.upfronthosting.co.za>


R. David Murray added the comment:

And thanks for wanting to improve the docs!

----------

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

From report at bugs.python.org  Fri Feb  3 09:58:01 2017
From: report at bugs.python.org (Anthony Scopatz)
Date: Fri, 03 Feb 2017 14:58:01 +0000
Subject: [docs] [issue15451] PATH is not honored in subprocess.Popen in win32
In-Reply-To: <1343264230.45.0.645552285699.issue15451@psf.upfronthosting.co.za>
Message-ID: <1486133881.41.0.0391304169707.issue15451@psf.upfronthosting.co.za>


Changes by Anthony Scopatz <scopatz at gmail.com>:


----------
nosy: +Anthony Scopatz
versions: +Python 3.6

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

From report at bugs.python.org  Fri Feb  3 14:57:32 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 03 Feb 2017 19:57:32 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486151852.15.0.436397381295.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Marco, thank you for your prompt comment. 

However, 
> Maybe you are running the doctest with Python 3. The StringIO module is no more available in Python 3, so your doctest will fail on Python 3 ....

Please let me be clear. This issue is not about the StringIO module or about any of my doctests. It is about the documentation of the doctests module, and the ways in which that documentation is less helpful than it could be.

----------

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

From report at bugs.python.org  Fri Feb  3 15:14:01 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 03 Feb 2017 20:14:01 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486152841.89.0.854304207707.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Marco, thank you for the suggestion to watch Raymond Hettinger's talk. 

> I suggest you to watch this talk of Raymond Hettinger, before going on:
>
> https://www.youtube.com/watch?v=voXVTjwnn-U

That video is 63 minutes long, and a lot of those minutes are taken up by stories. I will watch the rest when I get time. I wish his insights were summarised in writing; I'll bet that would take much less than 63 minutes to read. I find that written text is a much faster way to deliver information, though maybe it takes the teacher more time to write well than to give a talk.

I understand your point about the need for a review, and reviews being the bottleneck. The "Lifecycle of a Patch" document[1] is clear about that.

[1] https://docs.python.org/devguide/patch.html#reviewing

----------

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

From report at bugs.python.org  Fri Feb  3 15:58:25 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 03 Feb 2017 20:58:25 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486155505.02.0.239316045168.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Marco and David, thank you again for your prompt replies. 

Let me respond to both of your comments on the doctest module documentation itself.


[Marco] > The example in section 26.3.3.2 [1], before the compound statement (the if/else), contains two simple statements. I also think the example is complete and straightforward for its purpose, and it does not have to be complicated adding avanced features.

You are correct, it contain two simple statements. I missed this when I first read the example.  Part of the problem is that the example is contrived. It is an actual test. I think it would be better to replace these two lines by a two-line test, one which sets up state and another which exercises the module under test.

You believe "the example is complete and straightforward for its purpose, and it does not have to be complicated adding avanced features." I am giving you feedback that it was not complete and straightforward for me, as an ordinary software developer trying to use the documentation. 


[Marco] > If you want a more complex control over your tests, for instance adding fixtures, you can find how to do it later...

No, control over tests is not what I am bringing up in this issue. I an concerned with documentation of doctest "Examples".


[Marco] > I am -1 on this [changing 26.3.3.2]. IMHO there is no need to add extra description to a such self-explaining, clear and concise example. But this I think is also clear from the beginning. Infact, the first line of the doc says: "The doctest module searches for pieces of text that look like interactive Python sessions"

[David] > As for the prompts, I agree with Marco: I don't think there is any need to add words, since it clearly says it is supposed to look like an interactive session and the reader gets reminded of the rules for that by the example provided.  IMO it is not appropriate to re-document those rules here.


My feedback to you is that for me, as an ordinary software developer trying to use the doctest module, this section is not "self-explaining, clear and concise", and that "How Docstring examples are recognised" is not "clear from the beginning". 

Perhaps we have a difference of opinion on how clear and effective this documentation is.  The best way to resolve that would be to gather data: having several ordinary software developers reading the document, then measuring their comprehension. That would be hard to arrange. At least this bug report will serve as a data point.

I believe that a library module documentation should at some point clearly specify how the module works. I believe section Section "26.3.3.2. How are Docstring Examples Recognized?" does poorly at that. To say, "In most cases a copy-and-paste of an interactive console session works fine, but doctest isn?t trying to do an exact emulation of any specific Python shell." is not a specification. It's a blurry generalisation. The list of "fine print" is at a better level of detail, but still doesn't mention how the parser treats statements, nor how prefixes relate to statement boundaries.

I am giving you feedback that for me, as a developer trying to use the doctest module, this documentation failed to give me the comprehension I needed to be effective.


[Marco] >Also this section [26.3.3.3, execution context] IMO is well written and clear. I do not know what to say... If someone else thinks it is not enough understandable, maybe the better think to do is to add a very small example, with two functions, that shows their docstrings have independent globals.

[David] > It does appear that "test" is being used ambiguously in the docs.  In most places it means a single statement, but in execution context it appears to be being used as a synonym for "docstring".  In that section it should be replaced by "docstring".  It would probably be worth checking the rest of the doc to make sure it is used consistently elsewhere as well.

[David] > The execution context section makes it clear that you can use names defined earlier, as does the fact that doctests emulate interactive sessions.  Both of these make it clear you can do multi line examples that use shared state. 

Again, I am giving you feedback that this document was not "clear" for me. I am taking the time to write this issue because I think the documentation has weaknesses, and would like to help improve it.

I agree with David, that one problem in this section is that the word "test" is used with three different meanings. Some instances of the word "test" should be changed to "docstring" or similar. That would help. 


[David] > So in summary, I think we *need* a one word change in the execution context section, and we'll consider any other enhancements you want to propose.

All right, I'll work on a patch that makes that one-word change, and offers some other concise improvements. I expect it will be more that you think necessary, given that we disagree on how "clear" the current documentation is.

Given that reviews are a bottleneck, I fear my patch may grind to a halt waiting for review. But this is my first contribution to Python. We'll see. I clearly have a lot to learn.


[David] > And thanks for wanting to improve the docs!

You are welcome!

Thank you again for your prompt responses. And thank you for all your work to build this marvelous Python language, which helps so many.


[1] https://docs.python.org/3/library/doctest.html#how-are-docstring-examples-recognized

----------

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

From report at bugs.python.org  Fri Feb  3 17:30:25 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 03 Feb 2017 22:30:25 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486161025.23.0.40718362786.issue29387@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I agree with Marco in that I do not understand the 'should'.  Py 3 has a definite rule for when it raises.  (I don't remember the exact details as I don't use tabs.)  "Python raises xxxError if one mixes tabs and spaces in the same file." (Or whatever the rule is.)

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

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

From report at bugs.python.org  Fri Feb  3 18:01:09 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 03 Feb 2017 23:01:09 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1486162869.9.0.855476595192.issue29414@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

The preceding sentences are also off.  "In many ways the object returned by range() behaves as if it is a list, but in fact it isn?t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn?t really make the list, thus saving space."

A range object is more like a tuple than a list.  Ranges and tuples are immutable sequences and the only non-dunder methods of both are count and index.  Lists, on the other hand, are mutable and several other exposed methods.  The difference between range and tuple is that ranges generate items as requested while tuples can be added and multiplied.

"Ranges are similar to tuples in being sequences with count and index methods.  Both can be indexed, sliced, and iterated.  However, ranges cannot be added or multiplied.  They generate their items on request, thus saving space"

I am still thinking about the next two sentences, discussed above.  I do not like 'construct' to mean 'statement' (or callable).

----------
nosy: +terry.reedy
versions:  -Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Feb  3 19:16:42 2017
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 04 Feb 2017 00:16:42 +0000
Subject: [docs] [issue15451] PATH is not honored in subprocess.Popen in win32
In-Reply-To: <1343264230.45.0.645552285699.issue15451@psf.upfronthosting.co.za>
Message-ID: <1486167402.35.0.220182704154.issue15451@psf.upfronthosting.co.za>


Eryk Sun added the comment:

> difference from the behaviour of Posix's execvpe() was deliberate

POSIX doesn't define execvpe [1]. GNU glibc implemented it in 2009 [2]. On Windows, MSC has had execvpe and spawnvpe since at least 5.0 [3], and I think it arrived in 4.0 in 1986. Guido added os._execvpe in 1.2b4 [4] in 1995. I think it's the only implementation of execvpe that searches the passed environment. 

[1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/execvp.html
[2]: https://sourceware.org/ml/libc-alpha/2009-10/msg00063.html
[3]: https://openlibrary.org/works/OL2028669W
[4]: https://hg.python.org/cpython/file/534a97c400cc/Lib/os.py

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

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

From report at bugs.python.org  Fri Feb  3 23:30:56 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Feb 2017 04:30:56 +0000
Subject: [docs] [issue29430] zipfile: invalid link
In-Reply-To: <1486113194.67.0.258347417914.issue29430@psf.upfronthosting.co.za>
Message-ID: <1486182656.65.0.0460459009657.issue29430@psf.upfronthosting.co.za>


Berker Peksag added the comment:

> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

I think that HTML output suggests that their server configuration is broken. If you look at further down the page there is this error message:

    <p>Something has triggered missing webpage on your
    website. This is the default 404 error page for
    <strong>nginx</strong> that is distributed with
    EPEL.  It is located
    <tt>/usr/share/nginx/html/404.html</tt></p>

And:

    $ curl -I https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT
    HTTP/1.1 404 Not Found
    ...

https://support.pkware.com/display/PKZIP/Application+Note+Archives might be a suitable alternative to the broken link. I'm adding Serhiy to nosy list since he knows a lot about the ZIP file format.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +berker.peksag, docs at python, serhiy.storchaka
resolution: not a bug -> 
stage: resolved -> needs patch
status: closed -> open
type:  -> behavior
versions: +Python 3.5, Python 3.7

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

From report at bugs.python.org  Sat Feb  4 00:36:08 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 04 Feb 2017 05:36:08 +0000
Subject: [docs] [issue29430] zipfile: invalid link
In-Reply-To: <1486113194.67.0.258347417914.issue29430@psf.upfronthosting.co.za>
Message-ID: <1486186568.77.0.754455926746.issue29430@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

https://support.pkware.com/display/PKZIP/Application+Note+Archives contains links to old versions of APPNOTE (the last is 6.3.3). But the actual version was at least 6.3.4 (I have a local copy).

All external links refer to http://www.pkware.com/documents/casestudies/APPNOTE.TXT. I think we should report a bug to PKWare.

----------

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

From report at bugs.python.org  Sat Feb  4 00:49:52 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Feb 2017 05:49:52 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
Message-ID: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>


New submission from Berker Peksag:

Attached patch converts all examples that use @coroutine decorator in Doc/library/asyncio-task.rst. I also removed the generator example at https://docs.python.org/3/library/asyncio-task.html#example-coroutine-displaying-the-current-date

See issue 29407 for context.

----------
assignee: docs at python
components: Documentation, asyncio
files: update-examples-task.diff
keywords: patch
messages: 286911
nosy: berker.peksag, docs at python, gvanrossum, yselivanov
priority: normal
severity: normal
stage: patch review
status: open
title: Update examples to use async and await keywords in asyncio-task.rst
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file46508/update-examples-task.diff

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

From report at bugs.python.org  Sat Feb  4 02:20:15 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 04 Feb 2017 07:20:15 +0000
Subject: [docs] [issue18069] Subprocess searches special directories before
 PATH on Windows
In-Reply-To: <1369595742.19.0.584828873115.issue18069@psf.upfronthosting.co.za>
Message-ID: <1486192815.44.0.125864351519.issue18069@psf.upfronthosting.co.za>


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


----------
title: Subprocess picks the wrong executable on Windows -> Subprocess searches special directories before PATH on Windows

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

From report at bugs.python.org  Sat Feb  4 02:48:01 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 04 Feb 2017 07:48:01 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
 necessary to find executable in Windows PATH
In-Reply-To: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>
Message-ID: <1486194481.68.0.233917406065.issue13196@psf.upfronthosting.co.za>


Martin Panter added the comment:

It is hard to make sense of this without decoding your URLs, downloading the repository and finding the relevant commit. Anyway, what you have posted sounds like a duplicate of Issue 8557.

----------
nosy: +martin.panter
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> subprocess PATH semantics and portability

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

From report at bugs.python.org  Sat Feb  4 03:09:30 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 04 Feb 2017 08:09:30 +0000
Subject: [docs] [issue20927] Different behaviour on Posix and Windows when
 using subprocess.Popen(..., cwd=path)
In-Reply-To: <1394816385.18.0.912805951896.issue20927@psf.upfronthosting.co.za>
Message-ID: <1486195770.73.0.757211319541.issue20927@psf.upfronthosting.co.za>


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


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> subprocess.Popen(cwd) documentation

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

From report at bugs.python.org  Sat Feb  4 03:33:17 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 04 Feb 2017 08:33:17 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486197197.55.0.824286912155.issue29387@psf.upfronthosting.co.za>


Martin Panter added the comment:

Marco: I agree ?Python reports an error? would have been simpler. That is what I meant to say. Anyway, perhaps we should put

Python raises :exc:`IndentationError` if mixed tabs and spaces are causing problems in leading whitespace.

In general, the exception seems to be IndentationError. TabError is a subclass, but is not raised in all circumstances. It seems the compiler assumes a particular tab model, so the exact exception depends on the amount of tabs and spaces:

>>> exec("if True:\n" + " "*8 + "1\n" "\t2\n")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<string>", line 3
    2
    ^
TabError: inconsistent use of tabs and spaces in indentation
>>> exec("if True:\n" + " "*9 + "1\n" "\t2\n")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<string>", line 3
    2
    ^
IndentationError: unindent does not match any outer indentation level

----------

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

From report at bugs.python.org  Sat Feb  4 03:43:01 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 04 Feb 2017 08:43:01 +0000
Subject: [docs] [issue15451] PATH is not honored in subprocess.Popen in win32
In-Reply-To: <1343264230.45.0.645552285699.issue15451@psf.upfronthosting.co.za>
Message-ID: <1486197781.59.0.362310245856.issue15451@psf.upfronthosting.co.za>


Martin Panter added the comment:

Perhaps this is a duplicate of Issue 8557

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

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

From report at bugs.python.org  Sat Feb  4 03:45:05 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 04 Feb 2017 08:45:05 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1486197905.16.0.728570523954.issue15533@psf.upfronthosting.co.za>


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


----------
components: +Windows
stage: test needed -> needs patch
title: subprocess.Popen(cwd) documentation -> subprocess.Popen(cwd) documentation: Posix vs Windows

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

From report at bugs.python.org  Sat Feb  4 05:45:05 2017
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 04 Feb 2017 10:45:05 +0000
Subject: [docs] [issue15451] PATH is not honored in subprocess.Popen in win32
In-Reply-To: <1343264230.45.0.645552285699.issue15451@psf.upfronthosting.co.za>
Message-ID: <1486205105.03.0.282444861241.issue15451@psf.upfronthosting.co.za>


Eryk Sun added the comment:

Sure, let's close this in favor of the older documentation issue 8557.

----------
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> subprocess PATH semantics and portability

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

From report at bugs.python.org  Sat Feb  4 05:48:48 2017
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 04 Feb 2017 10:48:48 +0000
Subject: [docs] [issue8557] subprocess PATH semantics and portability
In-Reply-To: <1272451494.53.0.273790888777.issue8557@psf.upfronthosting.co.za>
Message-ID: <1486205328.76.0.525944064242.issue8557@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 2.6, Python 3.1, Python 3.2

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

From report at bugs.python.org  Sat Feb  4 06:55:49 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Sat, 04 Feb 2017 11:55:49 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1486209349.2.0.660482767605.issue29414@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Agreed. The issue I see with the additional suggestions by you and Marco (p.s the English was perfect!) is the introduction of other functions and/or objects that haven't been introduced yet. 

If you want to draw parallels with tuples, you'll need to introduce them first, right? (or would a link to the definition of tuples suffice?)

----------

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

From report at bugs.python.org  Sat Feb  4 09:55:52 2017
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 04 Feb 2017 14:55:52 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1486220152.61.0.134793874137.issue15533@psf.upfronthosting.co.za>


Eryk Sun added the comment:

The Unix implementation of subprocess.Popen follows the behavior of os.execvpe, which is an outlier. Other execvpe implementations, such as the one added to glibc in 2009, search PATH in the current environment instead of the passed environment. As such, and given the natural expectations of a Windows programmer, I do not see the current behavior of the Windows implementation as incorrect. It's a documentation bug.

On a related note, the Popen documentation for Windows should also mention that defining the environment variable NoDefaultCurrentDirectoryInExePath removes the current directory from the executable search path, in both CreateProcess and cmd.exe (i.e. w/ shell=True). This feature was introduced in Windows Vista, so it applies to Python 3.5+. 

> Python actually executes the program, but argv[0] is inconsistent with
> cwd. Imagine that the called program wants to resolve its own path:
> It joins cwd and argv[0] and gets 
> "C:\Users\Jenda\Bug reports\Python\subprocess\subdir\subdir\print_argv+cwd.exe"

A Windows program would call GetModuleFileName with hModule as NULL, which returns the path of the process executable. There's also the pseudo-environment variable __APPDIR__. 

Using argv[0] from the command line would be unreliable. For example:

    >>> _ = run('"spam & eggs" /c echo %__APPDIR__%',
    ...         executable=os.environ['ComSpec'])
    C:\Windows\system32\

    >>> _ = run('"spam & eggs" -m calendar 2017 2',
    ...         executable=sys.executable)
       February 2017
    Mo Tu We Th Fr Sa Su
           1  2  3  4  5
     6  7  8  9 10 11 12
    13 14 15 16 17 18 19
    20 21 22 23 24 25 26
    27 28

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

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

From report at bugs.python.org  Sat Feb  4 11:16:56 2017
From: report at bugs.python.org (Marco Buttu)
Date: Sat, 04 Feb 2017 16:16:56 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486225016.6.0.169682481504.issue29428@psf.upfronthosting.co.za>


Marco Buttu added the comment:

IMO if you would like to apply big changes to the current doc, as you wrote before, maybe is worth considering to propose a separate howto, instead of wide changes to the current page. I am suggesting this to you, because looking at the other modules of the standard library, I see they just explain the API, extending with examples when needed. When is worth adding extra documentation, in a different style, I see the usual solution is to extend with an howto. Look at the argparse module and related howto, for instance:

https://docs.python.org/3/library/argparse.html
https://docs.python.org/3/howto/argparse.html

I also think an howto in this case is appropriate, because there is more to say than only the API. If you want to follow the howto way, I would like to contribute. In any case, I am disposed to review your patch

----------

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

From report at bugs.python.org  Sat Feb  4 11:51:39 2017
From: report at bugs.python.org (Marco Buttu)
Date: Sat, 04 Feb 2017 16:51:39 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486227099.37.0.377048109282.issue29387@psf.upfronthosting.co.za>


Marco Buttu added the comment:

I think you are right about the TAB model (Parser/tokenizer.c:40 and Lib/tokenize.py:215), that is why the difference between the two cases.

In any case, I am not sure whether expliciting the type of the exeption is the best choice. So, to me +1 to just change "should report" with "reports" in the proposed patch, and +0 to indicate the exeption type.

----------

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

From report at bugs.python.org  Sat Feb  4 12:12:27 2017
From: report at bugs.python.org (Marco Buttu)
Date: Sat, 04 Feb 2017 17:12:27 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1486228347.89.0.970533183497.issue29414@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Even though the Terry suggestion is formally correct, we are just at the beginning of the tutorial, and unluckily the tuples have not been introduced yet. To avoid adding to much complication here, IMHO we can just left the preceding sentences as they are.

----------

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

From report at bugs.python.org  Sat Feb  4 12:24:45 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 04 Feb 2017 17:24:45 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486229085.27.0.734006204741.issue29387@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I would add the exception type after testing all versions patched.

----------

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

From report at bugs.python.org  Sat Feb  4 15:53:01 2017
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 04 Feb 2017 20:53:01 +0000
Subject: [docs] [issue18069] Subprocess searches special directories before
 PATH on Windows
In-Reply-To: <1369595742.19.0.584828873115.issue18069@psf.upfronthosting.co.za>
Message-ID: <1486241581.92.0.331275505468.issue18069@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at gmail.com>:


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

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

From report at bugs.python.org  Sat Feb  4 16:02:37 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sat, 04 Feb 2017 21:02:37 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486242157.53.0.265263592215.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Marco, thank you for the suggestion of a howto. That is a good idea. 

In parallel, I was thinking of some howto content that I would like to see documented. 

? How to decide what to test with doctests and what with unittests. I have a feeling that the sweet spot of doctests is functionality which you can invoke in one line, and which produces one line of output which you can match against a reference string. If it takes many lines to set up, or invoke, or checking for correctness is more than a test for string equality, then maybe unittest is a better tool.

? An effective way to write doctests. I suspect that some people write doctests by exercising the functionality in Python's interactive mode, then copy and paste the transcript from that session to the doctests. I don't do it that way, I author in the docstring. Maybe I'm not doing it the best way.

? How to author doctests so that they both prove the module correct, and provide clear and readable documentation. I imagine some effective tests for edge cases and error conditions are important to have, but are not readable documentation. Maybe such tests belong in a unittest framework instead of as doctests.

? How to run doctests from a unittest harness (your earlier note about the unittest API would be a part of this).

A problem for me is that I think I don't have the experience and wisdom to give good advice in these areas. I would be happy to start such a howto, and to accept feedback, and to edit it into good prose. I would need wiser people to contribute good ideas for the howto.

Also, Marco, thank you for being willing to review a patch.  That is helpful.

My next step is to check out the documentation source, to be in a position to make a patch.

----------

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

From report at bugs.python.org  Sat Feb  4 20:28:01 2017
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2017 01:28:01 +0000
Subject: [docs] [issue28489] Fix comment in tokenizer.c
In-Reply-To: <1476984216.11.0.150131580141.issue28489@psf.upfronthosting.co.za>
Message-ID: <20170205012756.7410.78101.55083777@psf.io>


Roundup Robot added the comment:

New changeset 8b20ed083a94 by Berker Peksag in branch '3.6':
Issue #28489: Fix comment in tokenizer.c
https://hg.python.org/cpython/rev/8b20ed083a94

New changeset 72ec2c599301 by Berker Peksag in branch 'default':
Issue #28489: Merge from 3.6
https://hg.python.org/cpython/rev/72ec2c599301

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

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

From report at bugs.python.org  Sat Feb  4 20:30:32 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 05 Feb 2017 01:30:32 +0000
Subject: [docs] [issue28489] Fix comment in tokenizer.c
In-Reply-To: <1476984216.11.0.150131580141.issue28489@psf.upfronthosting.co.za>
Message-ID: <1486258232.71.0.643824621079.issue28489@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I've applied Ryan's patch since it's been sitting in the 'commit review' queue. Thanks!

----------
nosy: +berker.peksag
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed
type:  -> behavior

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

From report at bugs.python.org  Sat Feb  4 21:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2017 02:00:23 +0000
Subject: [docs] [issue28489] Fix comment in tokenizer.c
In-Reply-To: <1476984216.11.0.150131580141.issue28489@psf.upfronthosting.co.za>
Message-ID: <1486260023.41.0.406345902912.issue28489@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset bc2b2193520cea1adc44d27c9f7721fc6ad37293 by Berker Peksag in branch '3.6':
Issue #28489: Fix comment in tokenizer.c
https://github.com/python/cpython/commit/bc2b2193520cea1adc44d27c9f7721fc6ad37293


----------

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

From report at bugs.python.org  Sat Feb  4 21:00:25 2017
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2017 02:00:25 +0000
Subject: [docs] [issue28489] Fix comment in tokenizer.c
In-Reply-To: <1476984216.11.0.150131580141.issue28489@psf.upfronthosting.co.za>
Message-ID: <1486260025.31.0.052700798951.issue28489@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset bc2b2193520cea1adc44d27c9f7721fc6ad37293 by Berker Peksag in branch 'master':
Issue #28489: Fix comment in tokenizer.c
https://github.com/python/cpython/commit/bc2b2193520cea1adc44d27c9f7721fc6ad37293

New changeset 9babb676a3c143099ab548ccc72c1ee897335e84 by Berker Peksag in branch 'master':
Issue #28489: Merge from 3.6
https://github.com/python/cpython/commit/9babb676a3c143099ab548ccc72c1ee897335e84


----------

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

From report at bugs.python.org  Sun Feb  5 00:37:42 2017
From: report at bugs.python.org (Marco Buttu)
Date: Sun, 05 Feb 2017 05:37:42 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486273061.94.0.165151539995.issue29428@psf.upfronthosting.co.za>


Marco Buttu added the comment:

> In parallel, I was thinking of some howto content that I would like to
> see documented.

Great :-)

> How to decide what to test with doctests and what with unittests.
> I have a feeling that the sweet spot of doctests is functionality
> which you can invoke in one line, and which produces one line of
> output which you can match against a reference string. If it takes
> many lines to set up, or invoke, or checking for correctness is
> more than a test for string equality, then maybe unittest is a
> better tool.

All your questions come up every time I speak about doctest, and these doubts are the main reason for my previous sentence: "there is more to say [about doctest] than only the API". That is why IMO an howto could be really helpful. What doctest checks is not one line of output, but the output as a string, and of course it could have multiple lines. Try to execute the doctest (with the -v option) for this docstring:

def foo():
    """ 
    >>> a = 33
    >>> a
    33
    >>> for i in range(2):
    ...   print(i)
    ...
    0
    1
    """

Three tests will be executed: one for `a=33`, expecting nothing, one for `a`, expecting 33 as output, and one test for the whole `for` block, expecting one output composed of two lines.

For several reasons IMO doctest is not a substitute for unittest. They are different tools for different purposes, as thier name point up. To have a wide view, usually it is a good idea to start from the beginning:

https://groups.google.com/forum/#!msg/comp.lang.python/DfzH5Nrt05E/Yyd3s7fPVxwJ

Anyway, IMO this is not the right place to discuss and explain the objectives of doctest. I propose you to open a repository on github, work and discuss there, and when all is ready, we can ask for a review. Please write here the link to the github repo, so anyone else wants to contribute can find it. Thanks again for your time

----------

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

From report at bugs.python.org  Sun Feb  5 00:59:16 2017
From: report at bugs.python.org (Marco Buttu)
Date: Sun, 05 Feb 2017 05:59:16 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <1486274356.01.0.0590348536808.issue29441@psf.upfronthosting.co.za>


Marco Buttu added the comment:

The patch is OK to me. I also executed the examples, and everything works fine :-)

----------
nosy: +marco.buttu

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

From report at bugs.python.org  Sun Feb  5 10:17:27 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Sun, 05 Feb 2017 15:17:27 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
Message-ID: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>


New submission from Jim Fasarakis-Hilliard:

Removes `keys = sorted(keywords.keys())` from function example and removes the text that describes why this was necessary. As per PEP 468, this note is obsolete for 3.6+

Also changes the ordering of the function call to match the previous output.

----------
assignee: docs at python
components: Documentation
files: controlflowdiff.patch
keywords: patch
messages: 287048
nosy: Jim Fasarakis-Hilliard, docs at python
priority: normal
severity: normal
status: open
title: Remove reference to undefined dictionary ordering in Tutorial
versions: Python 3.6, Python 3.7
Added file: http://bugs.python.org/file46524/controlflowdiff.patch

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

From report at bugs.python.org  Sun Feb  5 10:28:29 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Sun, 05 Feb 2017 15:28:29 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486308509.01.0.427481533866.issue29453@psf.upfronthosting.co.za>


Changes by Xiang Zhang <angwerzx at 126.com>:


----------
nosy: +xiang.zhang

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

From report at bugs.python.org  Sun Feb  5 10:42:37 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 05 Feb 2017 15:42:37 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486309357.48.0.195512427359.issue29453@psf.upfronthosting.co.za>


INADA Naoki added the comment:

LGTM

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

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

From report at bugs.python.org  Sun Feb  5 10:44:32 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 05 Feb 2017 15:44:32 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486309472.9.0.718441920463.issue29453@psf.upfronthosting.co.za>


R. David Murray added the comment:

It is not (yet) a language requirement that ordinary dictionaries be ordered.  This patch may become appropriate in 3.7, but that has not yet been determined.  It is not appropriate for 3.6.  In 3.6, the order of keys in an ordinary dictionary is still undefined, even though it is in practice consistent in CPython.

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

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

From report at bugs.python.org  Sun Feb  5 10:56:37 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Sun, 05 Feb 2017 15:56:37 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486310197.67.0.00662123551917.issue29453@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Isn't it a language requirement that `**kwargs` be ordered in 3.6, David? 

PEP 468 states that `**kwargs` is to be an ordered *mapping* and, if I'm not mistaken, that was done in order to not depend on the fact that dicts became ordered. I might have understood something wrong, though :-)

----------

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

From report at bugs.python.org  Sun Feb  5 11:01:55 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Sun, 05 Feb 2017 16:01:55 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486310515.62.0.382795492665.issue29453@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

David, actually I have the same thoughts as Jim. Ordered ordinary dicts is not a feature but ordered **kwargs is in 3.6. They seems not the same thing.

----------

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

From report at bugs.python.org  Sun Feb  5 11:22:18 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 Feb 2017 16:22:18 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486311738.12.0.355400838355.issue29453@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I would not change the order of keyword arguments, but rather change the output.

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

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

From report at bugs.python.org  Sun Feb  5 11:24:48 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Sun, 05 Feb 2017 16:24:48 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486311888.91.0.522823895041.issue29453@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

It was a random decision on my part, Serhiy, since I didn't see any difference. Why would you go the other way around?

----------

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

From report at bugs.python.org  Sun Feb  5 11:33:22 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 Feb 2017 16:33:22 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486312402.13.0.325616811319.issue29453@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Because it shows preserving the order of keyword arguments (rather than sorting by keyword name).

----------

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

From report at bugs.python.org  Sun Feb  5 11:41:05 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Sun, 05 Feb 2017 16:41:05 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486312865.3.0.598037753052.issue29453@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Indeed, good point. Changed it to the suggested way.

----------
Added file: http://bugs.python.org/file46525/controlflowdiff2.patch

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

From report at bugs.python.org  Sun Feb  5 11:46:42 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 Feb 2017 16:46:42 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486313202.44.0.653258272161.issue29453@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

LGTM. Thanks Jim.

But maybe it is worth to mention that the output corresponds to the order of passed keyword arguments.

----------
stage:  -> commit review

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

From report at bugs.python.org  Sun Feb  5 14:21:01 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 05 Feb 2017 19:21:01 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486322461.6.0.280206264057.issue29453@psf.upfronthosting.co.za>


R. David Murray added the comment:

You are correct, I didn't read the full context of the diff.  My apologies.

----------
versions: +Python 3.6

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

From report at bugs.python.org  Sun Feb  5 21:30:05 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 06 Feb 2017 02:30:05 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486348205.54.0.802213251751.issue29453@psf.upfronthosting.co.za>


Changes by Xiang Zhang <angwerzx at 126.com>:


----------
assignee: docs at python -> serhiy.storchaka

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

From report at bugs.python.org  Sun Feb  5 22:39:07 2017
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 06 Feb 2017 03:39:07 +0000
Subject: [docs] [issue29455] Mention coverage.py in trace module
 documentation
Message-ID: <1486352347.76.0.0578982981399.issue29455@psf.upfronthosting.co.za>


New submission from Brett Cannon:

In the trace module it would be nice to also mention that coverage.py is available.

----------
assignee: docs at python
components: Documentation
messages: 287075
nosy: brett.cannon, docs at python
priority: normal
severity: normal
status: open
title: Mention coverage.py in trace module documentation
type: enhancement

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

From report at bugs.python.org  Sun Feb  5 23:00:55 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 06 Feb 2017 04:00:55 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486353655.22.0.57094943961.issue29371@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Hi everyone,

I made a patch to clarify that "or'ed" here really means "bitwise-OR'ed", and made a reference to the section of the docs about bitwise OR.

Please review and let me know if this will work.

Thanks.

----------
keywords: +patch
Added file: http://bugs.python.org/file46534/issue29371.patch

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

From report at bugs.python.org  Sun Feb  5 23:01:29 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 06 Feb 2017 04:01:29 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486353689.6.0.119664007977.issue29371@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Mon Feb  6 02:34:55 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 06 Feb 2017 07:34:55 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486366495.89.0.942792518493.issue26355@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Feb  6 02:36:02 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 06 Feb 2017 07:36:02 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486366562.14.0.412603086828.issue29453@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Patch 2 looks fine to me.

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

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

From report at bugs.python.org  Mon Feb  6 02:59:45 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 06 Feb 2017 07:59:45 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486367985.39.0.590303519606.issue29371@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

This mostly looks correct.

I would change "bitwise-OR?ed" to "bitwise ORed".  That latter form without the hyphen or apostrophe matches what is used in library/winsound.rst.

Once that change is made (in two places), go ahead an apply the patch.

----------

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

From report at bugs.python.org  Mon Feb  6 03:54:28 2017
From: report at bugs.python.org (Marco Buttu)
Date: Mon, 06 Feb 2017 08:54:28 +0000
Subject: [docs] [issue29455] Mention coverage.py in trace module
 documentation
In-Reply-To: <1486352347.76.0.0578982981399.issue29455@psf.upfronthosting.co.za>
Message-ID: <1486371268.72.0.358662005865.issue29455@psf.upfronthosting.co.za>


Marco Buttu added the comment:

I added a "seealso" at the end of the page.

----------
keywords: +patch
nosy: +marco.buttu
Added file: http://bugs.python.org/file46538/issue29455.patch

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

From report at bugs.python.org  Mon Feb  6 05:03:25 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 06 Feb 2017 10:03:25 +0000
Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page
In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za>
Message-ID: <1486375405.08.0.213672526706.issue24459@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch and sorry for my late response. I did some tweaks and am planning to commit the tweaked version of your patch this week.

----------
Added file: http://bugs.python.org/file46540/issue24459_cleanup.diff

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

From report at bugs.python.org  Mon Feb  6 06:08:29 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 06 Feb 2017 11:08:29 +0000
Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page
In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za>
Message-ID: <1486379309.38.0.355535690733.issue24459@psf.upfronthosting.co.za>


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


Added file: http://bugs.python.org/file46541/issue24459_cleanup_2.diff

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

From eubillus at openorange.com  Fri Feb  3 12:21:14 2017
From: eubillus at openorange.com (Enrique Ubillus)
Date: Fri, 3 Feb 2017 12:21:14 -0500
Subject: [docs] round bug
Message-ID: <CAOVOCZh-S8Jf21UKUna7Wv_CL8CCQ+3DCASdyF+C7ph+L2M37w@mail.gmail.com>

Dear team,

I found a bug when using round.

it is using a number ending with .575 like: 2613.575 which when rounding it
shows 2613.575 but when adding 0.0000000001  it goes well. I am attaching a
example I on a test windows we use for python code.

and I found when it is a 2713.575 it goes well too. I was trying with
different number and remembert it went bad when it was a xxxxx.575 long
number but 6 (xxxxxx.575) long went ok again when rounding.

I thanks for the support. I am a 3 months python developer but I am getting
well with.

Greetings

Enrique


[image: Im?genes integradas 1]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/b7951d25/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pythonBug.jpg
Type: image/jpeg
Size: 38280 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170203/b7951d25/attachment-0001.jpg>

From report at bugs.python.org  Mon Feb  6 09:27:57 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Mon, 06 Feb 2017 14:27:57 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486391277.84.0.412602195918.issue29453@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

> But maybe it is worth to mention that the output corresponds to the order of passed keyword arguments
 
Should I add this note? It looks fine to me as is but I'm not the experienced one here :-)

----------

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

From report at bugs.python.org  Mon Feb  6 09:57:03 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 06 Feb 2017 14:57:03 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486393023.22.0.5392591321.issue26355@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Thanks Matthias!

Regarding 2v3, the layout differences aren't a problem, since the canonical URLs are separate (/2/* vs /3/*). That's one of the benefits I actually hope for with this change - due to PEP 430, deep links still go to the Python 2 documentation by default, and once this change is made in the Python 2.7 branch it should teach search engines that those should start being presented in results as "/2/*" qualified links.

We also don't tend to make wholesale changes to the URL layouts in the docs in X.Y releases, so I think the assumption of "the relative path of this page won't change" is fine.

Georg, Berker - any further thoughts before we make this change to 3.4+ and the 2.7 docs?

----------

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

From report at bugs.python.org  Mon Feb  6 12:38:57 2017
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 06 Feb 2017 17:38:57 +0000
Subject: [docs] [issue29455] Mention coverage.py in trace module
 documentation
In-Reply-To: <1486352347.76.0.0578982981399.issue29455@psf.upfronthosting.co.za>
Message-ID: <1486402737.58.0.561521627355.issue29455@psf.upfronthosting.co.za>


Brett Cannon added the comment:

Thanks for the patch, Marco! Typically we put the mention at the top to give the 3rd-party library a better chance of being noticed (see the urllib.request docs to see how requests is mentioned).

----------
assignee: docs at python -> brett.cannon

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

From report at bugs.python.org  Mon Feb  6 13:03:38 2017
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 06 Feb 2017 18:03:38 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <1486404218.42.0.362866919602.issue29441@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

LGTM. Thanks!

----------

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

From report at bugs.python.org  Mon Feb  6 13:05:14 2017
From: report at bugs.python.org (Marco Buttu)
Date: Mon, 06 Feb 2017 18:05:14 +0000
Subject: [docs] [issue29455] Mention coverage.py in trace module
 documentation
In-Reply-To: <1486352347.76.0.0578982981399.issue29455@psf.upfronthosting.co.za>
Message-ID: <1486404314.4.0.312790973046.issue29455@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Thank you Brett, here is another patch. I added the seealso directive right after the introduction of the trace module, in the same way as urllib.request does for requests.

----------
Added file: http://bugs.python.org/file46548/issue29455_2nd.patch

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

From report at bugs.python.org  Mon Feb  6 15:59:59 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 06 Feb 2017 20:59:59 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486414799.83.0.669413359946.issue29371@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Raymond. I have an updated patch there the hypen and apostrophe are removed.

----------
versions:  -Python 3.3, Python 3.4
Added file: http://bugs.python.org/file46552/issue29371v2.patch

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

From report at bugs.python.org  Mon Feb  6 23:19:03 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 04:19:03 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <20170207041900.96018.23768.9DF61DF0@psf.io>


Roundup Robot added the comment:

New changeset df62e833eeb1 by Mariatta Wijaya in branch '3.5':
Issue #29371: Clarify bitwise OR operation in doctest option flags.
https://hg.python.org/cpython/rev/df62e833eeb1

New changeset c3d779f96b20 by Mariatta Wijaya in branch '3.6':
Issue #29371: merge with 3.5
https://hg.python.org/cpython/rev/c3d779f96b20

New changeset e376d2bfde9b by Mariatta Wijaya in branch 'default':
Issue #29371: merge with 3.6
https://hg.python.org/cpython/rev/e376d2bfde9b

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

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

From report at bugs.python.org  Mon Feb  6 23:30:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 04:30:23 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <20170207043020.8248.87225.467A4FB8@psf.io>


Roundup Robot added the comment:

New changeset 3fd198b80f29 by Mariatta Wijaya in branch '2.7':
Issue #29371: Clarify bitwise OR operation in doctest option flags.
https://hg.python.org/cpython/rev/3fd198b80f29

----------

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

From report at bugs.python.org  Mon Feb  6 23:32:00 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 07 Feb 2017 04:32:00 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486441920.47.0.643107848489.issue29371@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Marco, Jim, and Raymond :)

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

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

From report at bugs.python.org  Mon Feb  6 23:59:50 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 07 Feb 2017 04:59:50 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486443590.83.0.639633099408.issue26355@psf.upfronthosting.co.za>


Matthias Bussonnier added the comment:

Thanks Nick, 

I can work on the similar patch for Python 2.7.
I'll wait for the migration to GitHub which IIRC should be soon.

Side question, is there some metrics (like google analytics) to know how much traffic there is on older Python docs and if it's worth patching ?

----------

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

From report at bugs.python.org  Tue Feb  7 00:00:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 05:00:26 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486443626.38.0.198877989109.issue29371@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset c36939b07c1275a6c3897a917c638b0ac48885c4 by Mariatta Wijaya in branch '3.5':
Issue #29371: Clarify bitwise OR operation in doctest option flags.
https://github.com/python/cpython/commit/c36939b07c1275a6c3897a917c638b0ac48885c4


----------

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

From report at bugs.python.org  Tue Feb  7 00:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 05:00:28 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486443628.44.0.896965496727.issue29371@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset c36939b07c1275a6c3897a917c638b0ac48885c4 by Mariatta Wijaya in branch 'master':
Issue #29371: Clarify bitwise OR operation in doctest option flags.
https://github.com/python/cpython/commit/c36939b07c1275a6c3897a917c638b0ac48885c4

New changeset 141e1ca9844b6efe71dc7acbb6c011e1b3a4ea19 by Mariatta Wijaya in branch 'master':
Issue #29371: merge with 3.5
https://github.com/python/cpython/commit/141e1ca9844b6efe71dc7acbb6c011e1b3a4ea19

New changeset bcc59e6131af582620c2db32e19d0a064d891a59 by Mariatta Wijaya in branch 'master':
Issue #29371: merge with 3.6
https://github.com/python/cpython/commit/bcc59e6131af582620c2db32e19d0a064d891a59


----------

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

From report at bugs.python.org  Tue Feb  7 00:00:31 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 05:00:31 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486443631.37.0.636672905527.issue29371@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset 2b20a37791e3cc4536db1f99fc85ffb6e20134ab by Mariatta Wijaya in branch '2.7':
Issue #29371: Clarify bitwise OR operation in doctest option flags.
https://github.com/python/cpython/commit/2b20a37791e3cc4536db1f99fc85ffb6e20134ab


----------

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

From report at bugs.python.org  Tue Feb  7 00:00:35 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 05:00:35 +0000
Subject: [docs] [issue29371] Typo in doctest documentation
In-Reply-To: <1485351369.68.0.185486175403.issue29371@psf.upfronthosting.co.za>
Message-ID: <1486443635.23.0.0163233895085.issue29371@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset c36939b07c1275a6c3897a917c638b0ac48885c4 by Mariatta Wijaya in branch '3.6':
Issue #29371: Clarify bitwise OR operation in doctest option flags.
https://github.com/python/cpython/commit/c36939b07c1275a6c3897a917c638b0ac48885c4

New changeset 141e1ca9844b6efe71dc7acbb6c011e1b3a4ea19 by Mariatta Wijaya in branch '3.6':
Issue #29371: merge with 3.5
https://github.com/python/cpython/commit/141e1ca9844b6efe71dc7acbb6c011e1b3a4ea19


----------

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

From berker.peksag at gmail.com  Tue Feb  7 02:35:51 2017
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Tue, 07 Feb 2017 07:35:51 -0000
Subject: [docs] Emit major version based canonical URLs for docs (issue
 26355)
Message-ID: <20170207073551.23420.40766@psf.upfronthosting.co.za>


http://bugs.python.org/review/26355/diff/19842/Doc/tools/templates/layout.html
File Doc/tools/templates/layout.html (right):

http://bugs.python.org/review/26355/diff/19842/Doc/tools/templates/layout.html#newcode41
Doc/tools/templates/layout.html:41: <link rel="canonical"
href="https://docs.python.org/3/{{pagename}}.html"/>
Can we add a space before '/>' to be consistent with the rest of file?

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

From report at bugs.python.org  Tue Feb  7 02:36:10 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 07 Feb 2017 07:36:10 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486452970.26.0.31256971561.issue26355@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Patch looks good to me too, thanks! Just left a super minor comment on Rietveld.

You might want to commit this to 3.5+ because we don't daily build 3.4 docs anymore: https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L30

I didn't see any links from 2.6 or older Python 2 versions in search results before so I don't have a strong opinion on backporting the patch to 2.7 (I probably wouldn't bother with Python 2 docs anymore :))

----------

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

From report at bugs.python.org  Tue Feb  7 03:22:57 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 08:22:57 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <20170207082254.15965.54283.BD423A5F@psf.io>


Roundup Robot added the comment:

New changeset 514571268743 by Berker Peksag in branch '3.5':
Issue #29441: Update examples to use async and await keywords in asyncio-task.rst
https://hg.python.org/cpython/rev/514571268743

New changeset 975e03b0aea6 by Berker Peksag in branch '3.6':
Issue #29441: Merge from 3.5
https://hg.python.org/cpython/rev/975e03b0aea6

New changeset ee074604bf0c by Berker Peksag in branch 'default':
Issue #29441: Merge from 3.6
https://hg.python.org/cpython/rev/ee074604bf0c

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

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

From report at bugs.python.org  Tue Feb  7 03:23:53 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 07 Feb 2017 08:23:53 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <1486455833.71.0.661089964298.issue29441@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the reviews!

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

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

From report at bugs.python.org  Tue Feb  7 03:40:04 2017
From: report at bugs.python.org (Marco Buttu)
Date: Tue, 07 Feb 2017 08:40:04 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486456804.08.0.201030004789.issue22594@psf.upfronthosting.co.za>


Marco Buttu added the comment:

IMHO the reference proposed in the patch is too verbose. Adding details like what is supported and how to use some features I think is out of the scope of the reference. Moreover, if the regex module changes the features we are reporting in the reference, we'll have an outdated reference.

In addition, as Brett Cannon pointed out in msg287159, the preferred way to mention a 3rd-party library should be by adding the reference at the top of the page, as in Doc/library/urllib.request.rst:19.

I propose to just add a more concise reference, at the beginning of the page, like the following:

.. seealso:: `regex <https://pypi.python.org/pypi/regex/>`_,
   a third-party alternative regular expression module.

----------
nosy: +marco.buttu

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

From report at bugs.python.org  Tue Feb  7 04:00:24 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 09:00:24 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <1486458024.67.0.332836508069.issue29441@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset dbfbdf9dce7889699e1eb7cc4644a911b16665ec by Berker Peksag in branch '3.6':
Issue #29441: Update examples to use async and await keywords in asyncio-task.rst
https://github.com/python/cpython/commit/dbfbdf9dce7889699e1eb7cc4644a911b16665ec

New changeset f76fb14796715fc5abb5a2b68428b29063c3d48e by Berker Peksag in branch '3.6':
Issue #29441: Merge from 3.5
https://github.com/python/cpython/commit/f76fb14796715fc5abb5a2b68428b29063c3d48e


----------

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

From report at bugs.python.org  Tue Feb  7 04:00:26 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 09:00:26 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <1486458026.56.0.61831974598.issue29441@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset dbfbdf9dce7889699e1eb7cc4644a911b16665ec by Berker Peksag in branch '3.5':
Issue #29441: Update examples to use async and await keywords in asyncio-task.rst
https://github.com/python/cpython/commit/dbfbdf9dce7889699e1eb7cc4644a911b16665ec


----------

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

From report at bugs.python.org  Tue Feb  7 04:00:28 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 Feb 2017 09:00:28 +0000
Subject: [docs] [issue29441] Update examples to use async and await keywords
 in asyncio-task.rst
In-Reply-To: <1486187392.27.0.919616068978.issue29441@psf.upfronthosting.co.za>
Message-ID: <1486458028.61.0.567297723983.issue29441@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset dbfbdf9dce7889699e1eb7cc4644a911b16665ec by Berker Peksag in branch 'master':
Issue #29441: Update examples to use async and await keywords in asyncio-task.rst
https://github.com/python/cpython/commit/dbfbdf9dce7889699e1eb7cc4644a911b16665ec

New changeset f76fb14796715fc5abb5a2b68428b29063c3d48e by Berker Peksag in branch 'master':
Issue #29441: Merge from 3.5
https://github.com/python/cpython/commit/f76fb14796715fc5abb5a2b68428b29063c3d48e

New changeset 38c1fd9055ad58738643325a2c7682d76496f9ed by Berker Peksag in branch 'master':
Issue #29441: Merge from 3.6
https://github.com/python/cpython/commit/38c1fd9055ad58738643325a2c7682d76496f9ed


----------

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

From report at bugs.python.org  Tue Feb  7 04:33:55 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 07 Feb 2017 09:33:55 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1486460035.71.0.373729782207.issue29453@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I don't know. David, Raymond, what are your thoughts?

----------

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

From report at bugs.python.org  Tue Feb  7 06:00:15 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 07 Feb 2017 11:00:15 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486465215.84.0.666997241854.issue26355@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

OK, I've marked 2.7 and 3.5+ as the minimal set of versions to get the change via the CPython source repo.

However, looking at the results of https://www.google.com/search?q=python+httplib and https://www.google.com/search?q=python+http+client I think it's going to be worth backfilling the old branches as well - having multiple different versions of the 3.x documentation showing up in search results isn't helpful to anyone.

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

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

From report at bugs.python.org  Tue Feb  7 06:45:32 2017
From: report at bugs.python.org (Matthew Barnett)
Date: Tue, 07 Feb 2017 11:45:32 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486467932.25.0.612284891914.issue22594@psf.upfronthosting.co.za>


Matthew Barnett added the comment:

I agree with Marco that it shouldn't be too verbose. I'd like to suggest that it says that it's compatible (i.e. has the same API), but with additional features.

----------

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

From artgoldberg at gmail.com  Mon Feb  6 11:09:36 2017
From: artgoldberg at gmail.com (Arthur Goldberg)
Date: Mon, 6 Feb 2017 11:09:36 -0500
Subject: [docs] Tiny typos in
 https://docs.python.org/3/library/weakref.html#weakref.WeakValueDictionary
Message-ID: <adfa0c66-7954-2b1e-7e7e-4dfe6a6f9a97@gmail.com>

s/have the following additional methods. These method have/have the 
following additional method. This method has/
s/ issues as the and|keyrefs()|/ issues as the|keyrefs()|/

HTH
A

-- 
Arthur Goldberg
https://www.linkedin.com/in/arthurgoldberg
artgoldberg at gmail.com

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

From report at bugs.python.org  Tue Feb  7 10:34:42 2017
From: report at bugs.python.org (Marco Buttu)
Date: Tue, 07 Feb 2017 15:34:42 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486481682.4.0.290991950071.issue22594@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Looking at the regex module and documentation, it is not clear to me whether its API behaves exactly as the re API. In addition, being a third-party module, things can change in the future.

To be defensive, IMO it is better to write as in the Ezio comment (in the review): "mostly compatible API". I propose a shorter patch, that adds the reference at the beginning of the page (right after the module introcution).

----------
Added file: http://bugs.python.org/file46561/regex_reference.patch

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

From report at bugs.python.org  Tue Feb  7 10:59:18 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 07 Feb 2017 15:59:18 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
Message-ID: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>


New submission from Mariatta Wijaya:

https://docs.python.org/3/library/weakref.html?highlight=weakref#weakref.WeakValueDictionary

There are grammatical errors in the sentence:

These method have the same issues as the and keyrefs() method of WeakKeyDictionary objects.

Reported by Arthur Goldberg in https://mail.python.org/pipermail/docs/2017-February/029957.html

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 287241
nosy: Mariatta, docs at python
priority: normal
severity: normal
status: open
title: Grammatical errors in weakref.WeakValueDictionary docs
versions: Python 3.5, Python 3.6, Python 3.7

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

From mariatta.wijaya at gmail.com  Tue Feb  7 11:00:14 2017
From: mariatta.wijaya at gmail.com (Mariatta Wijaya)
Date: Tue, 7 Feb 2017 08:00:14 -0800
Subject: [docs] Tiny typos in
 https://docs.python.org/3/library/weakref.html#weakref.WeakValueDictionary
In-Reply-To: <adfa0c66-7954-2b1e-7e7e-4dfe6a6f9a97@gmail.com>
References: <adfa0c66-7954-2b1e-7e7e-4dfe6a6f9a97@gmail.com>
Message-ID: <CAGbohnZCxNbBU6cz5ZXX9xfvkB_6xy-V1a=+aaO3HOOSiYdamA@mail.gmail.com>

Thanks for the report, Arthur :)

I filed a bug http://bugs.python.org/issue29474



Mariatta Wijaya

On Mon, Feb 6, 2017 at 8:09 AM, Arthur Goldberg <artgoldberg at gmail.com>
wrote:

> s/have the following additional methods. These method have/have the
> following additional method. This method has/
> s/ issues as the and keyrefs()/ issues as the keyrefs()/
>
> HTH
> A
>
> --
> Arthur Goldberghttps://www.linkedin.com/in/arthurgoldbergartgoldberg at gmail.com
>
>
> _______________________________________________
> 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/20170207/8080201a/attachment.html>

From report at bugs.python.org  Tue Feb  7 11:05:11 2017
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 07 Feb 2017 16:05:11 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486483511.14.0.490664408112.issue29474@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Would you mind to propose a patch? Thanks in advance.

Note: the sentence is also wrong in Python 2.7 doc, no?

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

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

From report at bugs.python.org  Tue Feb  7 11:15:56 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 07 Feb 2017 16:15:56 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486484156.96.0.102292234315.issue29474@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

You're right, Victor :)

The wording in 2.7 is a little bit different, but should be fixed too.

In 2.7:

These method have the same issues as the iterkeyrefs() and keyrefs() methods of WeakKeyDictionary objects.

Assigning this to myself.

----------
assignee: docs at python -> Mariatta
nosy: +rhettinger
versions: +Python 2.7

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

From report at bugs.python.org  Tue Feb  7 11:16:35 2017
From: report at bugs.python.org (Matthew Barnett)
Date: Tue, 07 Feb 2017 16:16:35 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486484195.37.0.974801324781.issue22594@psf.upfronthosting.co.za>


Matthew Barnett added the comment:

With the VERSION0 flag (the default behaviour), it should behave the same as the re module, and that's not going to change.

----------

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

From report at bugs.python.org  Tue Feb  7 13:02:52 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 07 Feb 2017 18:02:52 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486490572.05.0.67700988848.issue26355@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


Removed file: http://bugs.python.org/file46426/cannonical-doc-for-3.4plus.patch

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

From report at bugs.python.org  Tue Feb  7 13:04:39 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 07 Feb 2017 18:04:39 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486490679.79.0.457137360345.issue26355@psf.upfronthosting.co.za>


Matthias Bussonnier added the comment:

Updated patch to take comments into account (added space before /> for consistency). I'm still unfamiliar with hg so let me know if I did anything wrong.

----------
Added file: http://bugs.python.org/file46563/cannonical-doc-for-3.4plus.patch

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

From report at bugs.python.org  Tue Feb  7 13:21:29 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 07 Feb 2017 18:21:29 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486491689.4.0.108599895934.issue26355@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


Added file: http://bugs.python.org/file46564/cannonical-doc-for-2.7.patch

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

From report at bugs.python.org  Tue Feb  7 13:24:22 2017
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 07 Feb 2017 18:24:22 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486491862.29.0.709885930525.issue22594@psf.upfronthosting.co.za>


Brett Cannon added the comment:

How about "a mostly compatible API with more thorough Unicode support"? That focuses on the VERSION1 API which is a differentiator for regex.

----------

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

From report at bugs.python.org  Tue Feb  7 13:36:53 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 07 Feb 2017 18:36:53 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486492613.5.0.567643209032.issue26355@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


Added file: http://bugs.python.org/file46565/cannonical-doc-for-2.6.patch

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

From report at bugs.python.org  Tue Feb  7 19:40:41 2017
From: report at bugs.python.org (Eric Lafontaine)
Date: Wed, 08 Feb 2017 00:40:41 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486514441.04.0.909139698314.issue16011@psf.upfronthosting.co.za>


Eric Lafontaine added the comment:

Hi,

For user-defined class, it's up to the class to do the right implementation in my opinion. It's true the description is wrong though. 

x in y means that x exist inside of y (so that the execution of y.__contain__(x) is executed successfully and (I guess) doesn't return None,False or 0).

I'll modify the doc to be :
For user-defined classes which define the __contains__() method, x in y is false if y.__contains__(x) is returning either None,False or 0.  Otherwise, x in y return true.

Regards,
Eric Lafontaine

----------
nosy: +Eric Lafontaine

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

From report at bugs.python.org  Tue Feb  7 20:09:23 2017
From: report at bugs.python.org (R. David Murray)
Date: Wed, 08 Feb 2017 01:09:23 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486516163.4.0.0380278242786.issue16011@psf.upfronthosting.co.za>


R. David Murray added the comment:

Eric: that is not precise enough, I'm afraid :)  See msg171093 for the correct documentation update.  Specifically, in returns True if __contains__ returns a true value, and False otherwise (not the difference in case, it matters).  There are more things than just None, False, and 0 that are false in Python.

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

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

From report at bugs.python.org  Tue Feb  7 20:25:07 2017
From: report at bugs.python.org (Eric Lafontaine)
Date: Wed, 08 Feb 2017 01:25:07 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486517105.06.0.812064615771.issue16011@psf.upfronthosting.co.za>


Eric Lafontaine added the comment:

Hi all,

Here are the test I've made to understand the behavior :

class Foo_42(object):
    def __contains__(self,item): return 42 
    
class Foo_neg(object):
    def __contains__(self,item): return -42 
    
class Foo_None(object):
    def __contains__(self,item): return  
    
class Foo_false(object):
    def __contains__(self,item): return False 
    
class Foo_true(object):
    def __contains__(self,item): return True

for foo in [Foo_false(),Foo_None(),Foo_neg(),Foo_true(),Foo_42()]:
    print("3 in foo:" + str(3 in foo))
    print("foo.__contains__(3)" + str(foo.__contains__(3)))
    

which output this :
3 in foo:False
foo.__contains__(3)False
3 in foo:False
foo.__contains__(3)None
3 in foo:True
foo.__contains__(3)-42
3 in foo:True
foo.__contains__(3)True
3 in foo:True
foo.__contains__(3)42

So as long as __contains__ return False or None, the 'in' operator will be False.  Otherwise true.

----------

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

From report at bugs.python.org  Tue Feb  7 20:29:07 2017
From: report at bugs.python.org (Eric Lafontaine)
Date: Wed, 08 Feb 2017 01:29:07 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486517346.98.0.663407710543.issue16011@psf.upfronthosting.co.za>


Eric Lafontaine added the comment:

Hi David, sorry for the delay on my part for providing how I was getting to that conclusion.  I've also resurrected an old post as I want to start contributing more seriously :).

As this is documentation only (not changing the code behavior), I didn't take a look at the implementation of "in".

Could you enlighten me on what else would be considered "False" in this case?

Regards,
Eric Lafontaine

----------

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

From report at bugs.python.org  Tue Feb  7 20:34:45 2017
From: report at bugs.python.org (Eric Lafontaine)
Date: Wed, 08 Feb 2017 01:34:45 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486517685.55.0.986678037681.issue16011@psf.upfronthosting.co.za>


Eric Lafontaine added the comment:

oh, I've got what you meant!

Proposed change :
For user-defined classes which define the __contains__() method, the in operator will convert to False "x in y" if y.__contains__(x) return False, 0 or None.  Otherwise, the in operator will return True for any other value being returned by y.__contains__(x).


Would that make more sense?
Regards,
Eric Lafontaine

----------

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

From report at bugs.python.org  Tue Feb  7 21:10:39 2017
From: report at bugs.python.org (R. David Murray)
Date: Wed, 08 Feb 2017 02:10:39 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486519839.55.0.751174767562.issue16011@psf.upfronthosting.co.za>


R. David Murray added the comment:

>>> bool(())
False
>>> bool([])
False
>>> bool('')
False

What you want to say is that 'in' coerces the result returned by __contains__ to a boolean value.

----------

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

From report at bugs.python.org  Tue Feb  7 21:20:48 2017
From: report at bugs.python.org (Eric Lafontaine)
Date: Wed, 08 Feb 2017 02:20:48 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1486519839.55.0.751174767562.issue16011@psf.upfronthosting.co.za>
Message-ID: <CAAaADLKGxms-Bjriwp1F_tE+VR_u2BS_1eF6wAGHUzu4py5BBw@mail.gmail.com>


Eric Lafontaine added the comment:

(first time trying to reply through email)

thanks for the example and you are right :
class Foo_emptylist(object):
    def __contains__(self,item): return []

class Foo_emptydict(object):
    def __contains__(self,item): return {}

class Foo_emptystring(object):
    def __contains__(self,item): return ''

for foo in
[Foo_false(),Foo_None(),Foo_emptylist(),Foo_emptydict(),Foo_emptystring(),Foo_neg(),Foo_true(),Foo_42()]:
    print("3 in foo:" + str(3 in foo))
    print("foo.__contains__(3)" + str(foo.__contains__(3)))

3 in foo:False
foo.__contains__(3)False
3 in foo:False
foo.__contains__(3)None
3 in foo:False
foo.__contains__(3)[]
3 in foo:False
foo.__contains__(3){}
3 in foo:False
foo.__contains__(3)
3 in foo:True
foo.__contains__(3)-42
3 in foo:True
foo.__contains__(3)True
3 in foo:True
foo.__contains__(3)42

So the proposition should be this then?
For user-defined classes which define a __contains__() method, the in
operator will apply bool() on the __contains__() method.  In other words,  "x
in y" is equivalent to "bool(y.__contains__(x))" and will return False if
bool(y.__contains__(x)) is equivalent to false.

?ric Lafontaine |  Membre du Projet VUE, Groupe Contr?le
G?nie ?lectrique, 54?me promotion UdeS | ?tudiant en maitrise TI ? l'ETS
VAS OPS chez Bell Mobility

? Nous voulons proposer une alternative de transport en pr?sentant un
v?hicule ?lectrique sp?cifiquement con?u pour les d?placements urbains. ?

2017-02-07 21:10 GMT-05:00 R. David Murray <report at bugs.python.org>:

>
> R. David Murray added the comment:
>
> >>> bool(())
> False
> >>> bool([])
> False
> >>> bool('')
> False
>
> What you want to say is that 'in' coerces the result returned by
> __contains__ to a boolean value.
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue16011>
> _______________________________________
>

----------

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

From report at bugs.python.org  Wed Feb  8 00:05:01 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Feb 2017 05:05:01 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486530301.52.0.97649418421.issue29474@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Attached is the patch to fix the grammatical errors for versions 3.5+

----------
keywords: +patch
Added file: http://bugs.python.org/file46570/issue29474py3.patch

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

From report at bugs.python.org  Wed Feb  8 00:06:48 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Feb 2017 05:06:48 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486530408.02.0.522152237425.issue29474@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

And here is the patch that fixes the issue for python 2.7.

----------
Added file: http://bugs.python.org/file46571/issue29474py2.patch

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

From report at bugs.python.org  Wed Feb  8 00:07:18 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Feb 2017 05:07:18 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486530438.89.0.237849150477.issue29474@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Wed Feb  8 06:16:24 2017
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 08 Feb 2017 11:16:24 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486552583.93.0.869462425507.issue22594@psf.upfronthosting.co.za>


Marco Buttu added the comment:

> With the VERSION0 flag (the default behaviour), it should
> behave the same as the re module, and that's not going to change.

Thanks for the clarification Matthew. However, the default version will change, as the regex PyPI page points out: "In the short term this will be VERSION0, but in the longer term it will be VERSION1." I propose a patch that integrates the Brett suggestion.

----------
Added file: http://bugs.python.org/file46575/regex_reference.patch

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

From report at bugs.python.org  Wed Feb  8 06:30:36 2017
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 08 Feb 2017 11:30:36 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486553436.96.0.799909804973.issue29474@psf.upfronthosting.co.za>


Marco Buttu added the comment:

The second patch LGTM. In the first one there is a typo (see review).

----------
nosy: +marco.buttu

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

From report at bugs.python.org  Wed Feb  8 07:08:18 2017
From: report at bugs.python.org (R. David Murray)
Date: Wed, 08 Feb 2017 12:08:18 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1486555698.42.0.93138696432.issue16011@psf.upfronthosting.co.za>


R. David Murray added the comment:

You've got the right idea, but you are repeating yourself.  Keep it as short as possible while still conveying the correct information.  "coerce to boolean" is better than "apply bool", because the code may not in fact be using the bool function to do it.  Your "equivalent to" phrase would be OK as an alternative, but you only need to show the equivalence, no need to also explain it in words.

----------

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

From report at bugs.python.org  Wed Feb  8 07:53:06 2017
From: report at bugs.python.org (Guy Arad)
Date: Wed, 08 Feb 2017 12:53:06 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
Message-ID: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>


New submission from Guy Arad:

See:
- https://docs.python.org/3.6/library/typing.html#typing.Deque
- https://docs.python.org/3.5/library/typing.html#typing.Deque

`typing.Deque` is expected to be included in 3.6.1:
https://docs.python.org/3/whatsnew/changelog.html#python-3-6-1-release-candidate-1

Please remove or specify the version in which it's going to be included.

----------
assignee: docs at python
components: Documentation
messages: 287313
nosy: Guy Arad, docs at python
priority: normal
severity: normal
status: open
title: 3.6.0 doc describes 3.6.1 feature - typing.Deque
versions: Python 3.5, Python 3.6

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

From report at bugs.python.org  Wed Feb  8 09:02:40 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 08 Feb 2017 14:02:40 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1486562560.9.0.0299292295195.issue29481@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Feb  8 09:59:21 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Feb 2017 14:59:21 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486565961.63.0.664914673837.issue29474@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks for reviewing, Marco :)
Updated the patch.

----------
Added file: http://bugs.python.org/file46597/issue29474py3-2.patch

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

From report at bugs.python.org  Wed Feb  8 10:17:29 2017
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 08 Feb 2017 15:17:29 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486567049.37.0.787497787585.issue29474@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Thanks Mariatta, now it is OK to me

----------

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

From report at bugs.python.org  Wed Feb  8 14:55:25 2017
From: report at bugs.python.org (Matthew Barnett)
Date: Wed, 08 Feb 2017 19:55:25 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486583725.77.0.950171738659.issue22594@psf.upfronthosting.co.za>


Matthew Barnett added the comment:

Ah, well, if it hasn't changed after this many years, it never will. Expect one or two changes to the text. :-)

----------

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

From report at bugs.python.org  Wed Feb  8 17:02:44 2017
From: report at bugs.python.org (Pedro)
Date: Wed, 08 Feb 2017 22:02:44 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
Message-ID: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>


New submission from Pedro:

The docs for the copy module contain a bullet that says the following:

"Because deep copy copies everything it may copy too much, e.g., even administrative data structures that should be shared even between copies."

There should be a "not" between "should" and "be shared." I think the second "even" can be dropped, too.

----------
assignee: docs at python
components: Documentation
messages: 287367
nosy: docs at python, pgacv2
priority: normal
severity: normal
status: open
title: Incorrect documentation for the copy module
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Wed Feb  8 17:07:35 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Feb 2017 22:07:35 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486591655.16.0.223896025283.issue29506@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Wed Feb  8 17:14:56 2017
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 08 Feb 2017 22:14:56 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486592096.43.0.950699124495.issue29506@psf.upfronthosting.co.za>


Zachary Ware added the comment:

That line is correct, the point is that deep copy will duplicate even the things that you may *want* to be shared.

See also #27416.  I'm not sure what we can do to further clarify that line, but it is certainly easy to misread.

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

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

From report at bugs.python.org  Wed Feb  8 17:21:32 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Feb 2017 22:21:32 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486592492.53.0.635594338807.issue29506@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

How about

```
Because deep copy copies everything, it may copy too much, including the administrative data structures.
```

?

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

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

From report at bugs.python.org  Wed Feb  8 20:16:41 2017
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 09 Feb 2017 01:16:41 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486603000.43.0.230100414432.issue29506@psf.upfronthosting.co.za>


Steven D'Aprano added the comment:

What about "administrative data structures" that should be copied?

I think that "administrative data structures" is a red herring: there could be data that needs copying, and data that needs sharing and shouldn't be copied, independent of what the data is used for.

"Because deepcopy copies everything it may copy too much, such as data which is intended to be shared between copies."

----------
nosy: +steven.daprano

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

From report at bugs.python.org  Wed Feb  8 21:52:36 2017
From: report at bugs.python.org (Ma Lin)
Date: Thu, 09 Feb 2017 02:52:36 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1486608755.77.0.2943793605.issue22594@psf.upfronthosting.co.za>


Ma Lin added the comment:

How about this? Is it too long?
@Matthew Barnett, I'm animalize on your repository.

.. seealso::

    Third-party module `regex <https://pypi.python.org/pypi/regex>`_,

    is a substitute for re module, it offers some mainstream features 
    which re module lacks (Atomic grouping, Possessive quantifiers,
    Variable-length lookbehind, Recursive matching). It also has further
    Unicode support, some advanced grammars appears in other regular
    expression engines, and many facilitations.

----------
nosy: +Ma Lin

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

From report at bugs.python.org  Wed Feb  8 23:51:21 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Thu, 09 Feb 2017 04:51:21 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486615881.18.0.799106397296.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Marco:

> To have a wide view, usually it is a good idea to start from the beginning:
> 
> https://groups.google.com/forum/#!msg/comp.lang.python/DfzH5Nrt05E/Yyd3s7fPVxwJ

Thank you, that is a very interesting thread. Clearly the creator of doctests, Tim Peters, is a well-regarded person in the Python world. 

On the other hand, I was surprised to see some of the examples used in the present-day documentation in Tim's original 1999 message. I find it remarkable that in 18 years since then, no rewrite or editing has replaced those examples with better ones.

----------

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

From report at bugs.python.org  Thu Feb  9 05:27:50 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 09 Feb 2017 10:27:50 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486636070.4.0.541303322256.issue29506@psf.upfronthosting.co.za>


Marco Buttu added the comment:

+1 for the Steven's suggestion

----------
nosy: +marco.buttu

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

From report at bugs.python.org  Thu Feb  9 07:06:56 2017
From: report at bugs.python.org (Antti Haapala)
Date: Thu, 09 Feb 2017 12:06:56 +0000
Subject: [docs] [issue11726] clarify that linecache only works on files that
 can be decoded successfully
In-Reply-To: <1301566082.59.0.198488725536.issue11726@psf.upfronthosting.co.za>
Message-ID: <1486642016.2.0.0596575821708.issue11726@psf.upfronthosting.co.za>


Antti Haapala added the comment:

Every now and then there are new questions and answers regarding the use of `linecache` module on Stack Overflow for doing random access to text files, even though the documentation states that it is meant for Python source code files.

One problem is that the title still states: "11.9. linecache ? Random access to text lines"; the title should really be changed to "Random access to Python source code lines" so that the title wouldn't imply that this is a general-purpose random access library for text files.

----------
nosy: +ztane

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

From report at bugs.python.org  Thu Feb  9 07:50:48 2017
From: report at bugs.python.org (Pedro)
Date: Thu, 09 Feb 2017 12:50:48 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486644647.99.0.740249619509.issue29506@psf.upfronthosting.co.za>


Pedro added the comment:

"Because deepcopy copies everything it may copy too much, such as data which is intended to be shared (instead of duplicated) between copies."

A bit more explicit?

----------

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

From joaofguerreiro1992 at gmail.com  Thu Feb  9 07:35:20 2017
From: joaofguerreiro1992 at gmail.com (=?UTF-8?Q?Jo=C3=A3o_Guerreiro?=)
Date: Thu, 9 Feb 2017 12:35:20 +0000
Subject: [docs] =?utf-8?q?Minor_typo_in_12=2E4_zipfile_=E2=80=94_Work_with?=
	=?utf-8?q?_ZIP_archives_=28python_2=2E7?=
Message-ID: <CAAdqvAYmBjE-+j8y6KWojGbC-0P6_EENydyfTcPVpuR_aAdoNA@mail.gmail.com>

Hello everyone!

I've found a tiny typo in the documentation:
https://docs.python.org/2/library/zipfile.html#zipfile.BadZipfile

Where it says *exception *zipfile.BadZipfile
--
It should say *exception *zipfile.BadZipFile


Keep up with the great job.

My best regards,
Jo?o Guerreiro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170209/aea928b5/attachment.html>

From marco.buttu at gmail.com  Thu Feb  9 09:03:17 2017
From: marco.buttu at gmail.com (Marco Buttu)
Date: Thu, 09 Feb 2017 15:03:17 +0100
Subject: [docs] 
 =?windows-1252?q?Minor_typo_in_12=2E4_zipfile_=97_Work_wi?=
 =?windows-1252?q?th_ZIP_archives_=28python_2=2E7?=
In-Reply-To: <CAAdqvAYmBjE-+j8y6KWojGbC-0P6_EENydyfTcPVpuR_aAdoNA@mail.gmail.com>
References: <CAAdqvAYmBjE-+j8y6KWojGbC-0P6_EENydyfTcPVpuR_aAdoNA@mail.gmail.com>
Message-ID: <589C76A5.7060801@oa-cagliari.inaf.it>

On 09/02/2017 13:35, Jo?o Guerreiro wrote:

>
> I've found a tiny typo in the documentation:
> https://docs.python.org/2/library/zipfile.html#zipfile.BadZipfile
>
> Where it says /exception /|zipfile.||BadZipfile|
> |--|
> It should say /exception /|zipfile.||BadZipFile|

Thank you Jo?o. I think there is no typo, in Python 2 it is actually 
zipfile.BadZipfile(). It also is still exist in Python 3, for 
compatibility reasons.

In any way, thanks for your interest

-- 
Marco Buttu

INAF-Osservatorio Astronomico di Cagliari
Via della Scienza n. 5, 09047 Selargius (CA)
Phone: 070 711 80 217
Email: mbuttu at oa-cagliari.inaf.it


From report at bugs.python.org  Thu Feb  9 09:22:31 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 09 Feb 2017 14:22:31 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486650151.42.0.175482256471.issue26355@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> ncoghlan
stage: patch review -> commit review

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

From report at bugs.python.org  Thu Feb  9 09:23:47 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 09 Feb 2017 14:23:47 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486650227.16.0.285227091502.issue26355@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Looks good to me, so I'll apply these right now :)

----------

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

From report at bugs.python.org  Thu Feb  9 09:57:55 2017
From: report at bugs.python.org (R. David Murray)
Date: Thu, 09 Feb 2017 14:57:55 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486652275.27.0.623830307965.issue29506@psf.upfronthosting.co.za>


R. David Murray added the comment:

I prefer Steven's formulation.  The parenthetical is more distracting than clarifying, I think.  I agree that 'administrative' is confusing and unnecessary.

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

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

From report at bugs.python.org  Thu Feb  9 10:09:20 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2017 15:09:20 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <20170209150914.96198.62156.4F2C6AF9@psf.io>


Roundup Robot added the comment:

New changeset c63b09833141 by Nick Coghlan in branch '3.5':
Issue #26355: Specify canonical URLs in docs pages
https://hg.python.org/cpython/rev/c63b09833141

New changeset 80970cf56048 by Nick Coghlan in branch '3.6':
Merge issue #26355 fix from Python 3.5
https://hg.python.org/cpython/rev/80970cf56048

New changeset 26af402c291f by Nick Coghlan in branch 'default':
Merge issue #26355 fix from 3.6
https://hg.python.org/cpython/rev/26af402c291f

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

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

From report at bugs.python.org  Thu Feb  9 10:11:11 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 09 Feb 2017 15:11:11 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486653071.53.0.0236332112373.issue29506@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Current documentation looks correct to me. What is the problem with it?

Steven's formulation says about "deepcopy", but current documentation says about common issues of "deep copy" and describes how copy.deepcopy() solves them.

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

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

From report at bugs.python.org  Thu Feb  9 10:24:03 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 09 Feb 2017 15:24:03 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1486653843.53.0.568577184445.issue29506@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Serhiy is right about "deep copy" instead of "deepcopy", but IMO the Steven's proposal (with the "deep copy" correction) is much clearer than the current doc.

----------

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

From report at bugs.python.org  Thu Feb  9 11:00:34 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2017 16:00:34 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486656034.44.0.393621425.issue26355@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset a47e20b636d2a5559e5831c6805df3cba1ddb2a1 by Nick Coghlan in branch 'master':
Issue #26355: Specify canonical URLs in docs pages
https://github.com/python/cpython/commit/a47e20b636d2a5559e5831c6805df3cba1ddb2a1

New changeset 37150972faf660571a3ae7076a623087c06b8791 by Nick Coghlan in branch 'master':
Merge issue #26355 fix from Python 3.5
https://github.com/python/cpython/commit/37150972faf660571a3ae7076a623087c06b8791

New changeset d267bc695eaf9422668daedb9e44442696e01fe7 by Nick Coghlan in branch 'master':
Merge issue #26355 fix from 3.6
https://github.com/python/cpython/commit/d267bc695eaf9422668daedb9e44442696e01fe7


----------

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

From report at bugs.python.org  Thu Feb  9 11:00:37 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2017 16:00:37 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486656037.4.0.0340820928002.issue26355@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset a47e20b636d2a5559e5831c6805df3cba1ddb2a1 by Nick Coghlan in branch '3.5':
Issue #26355: Specify canonical URLs in docs pages
https://github.com/python/cpython/commit/a47e20b636d2a5559e5831c6805df3cba1ddb2a1


----------

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

From report at bugs.python.org  Thu Feb  9 11:00:51 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2017 16:00:51 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <20170209160040.8335.85376.C23C35CC@psf.io>


Roundup Robot added the comment:

New changeset b07d454e45a2 by Nick Coghlan in branch '2.7':
Issue #26355: Specify canonical URLs in docs pages
https://hg.python.org/cpython/rev/b07d454e45a2

----------

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

From report at bugs.python.org  Thu Feb  9 11:07:27 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 09 Feb 2017 16:07:27 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486656447.68.0.862246799411.issue26355@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

OK, I'm marking this as closed, since it's as resolved as we can make it through a *CPython* change.

Since the old branches aren't autobuilt anymore, adding a canonical URL reference to them would presumably be a matter of running a script over the built docs.

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

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

From report at bugs.python.org  Thu Feb  9 12:00:23 2017
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2017 17:00:23 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486659623.78.0.265861604561.issue26355@psf.upfronthosting.co.za>


Roundup Robot added the comment:


New changeset e8455e7137b9bd63d4c0183558161dba6ea00d32 by Nick Coghlan in branch '2.7':
Issue #26355: Specify canonical URLs in docs pages
https://github.com/python/cpython/commit/e8455e7137b9bd63d4c0183558161dba6ea00d32


----------

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

From report at bugs.python.org  Thu Feb  9 12:55:09 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Thu, 09 Feb 2017 17:55:09 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486662909.74.0.553564001237.issue26355@psf.upfronthosting.co.za>


Matthias Bussonnier added the comment:

> OK, I'm marking this as closed, since it's as resolved as we can make it through a *CPython* change.

Thanks you Nick, I appreciate the time you took to do that. ANd thank you Berker for the review.

----------

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

From report at bugs.python.org  Thu Feb  9 13:04:21 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 09 Feb 2017 18:04:21 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486663461.52.0.543056609963.issue26355@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Matthias - thanks for figuring out how to turn my "we should do this" idea into a change we've actually made :)

----------

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

From report at bugs.python.org  Thu Feb  9 13:07:45 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Thu, 09 Feb 2017 18:07:45 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1486663665.08.0.691340180102.issue26355@psf.upfronthosting.co.za>


Matthias Bussonnier added the comment:

> turn my "we should do this" idea into a change we've actually made :)

Looking forward to being able to do this more on GitHub as I am more familiar with git.

Good luck for the transition, I'm pretty sure there will be some hard time in the next few weeks.

----------

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

From report at bugs.python.org  Fri Feb 10 02:29:46 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 10 Feb 2017 07:29:46 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
Message-ID: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>


New submission from Jim DeLaHunt:

When I build the documentation on the current CPython code, there is a deprecation warning on the console. 

===== (beginning of output)
% make html
sphinx-build -b html -d build/doctrees -D latex_elements.papersize=  . build/html 
Running Sphinx v1.5.2
...[omitted irrelevant output]...
generating indices... genindex py-modindex
writing additional pages... download index
    WARNING: Now base template defindex.html is deprecated.
 search opensearch
copying images... [100%] faq/python-video-icon.png                                                          
...[omitted irrelevant output]...
build succeeded, 1 warning.

Build finished. The HTML pages are in build/html.
===== (end of output)

This is observed when building documentation from branch master, commit b1dc6b6d5fa20f63f9651df2e7986a066c88ff7d . 
The build command is "cd Doc; make html".

There are other warnings in the output, and I'm dealing with them in a different issue (number to follow). They are easier to fix than this one.

Diagnosis:
Sphinx config file Doc/conf.py:72 invokes the building of template 'indexcontent.html'. 
Doc/tools/templates/indexcontent.html:1 contains Sphinx directive 
`{% extends "defindex.html" %}`.
This invokes file sphinx/sphinx/themes/basic/defindex.html 
[See https://github.com/sphinx-doc/sphinx/blob/8ecd7ff08249739bbc6d900527fe9306592456ab/sphinx/themes/basic/defindex.html ]. Sure enough, it issues a deprecation warning. 

{{ warn('Now base template defindex.html is deprecated.') }}

There's a story behind this file.

Sphinx issue 2986 (https://github.com/sphinx-doc/sphinx/issues/2986) says that this is a very old file, from about the 0.2 version of Sphinx. It wasn't HTML 5 compatible, so they declared it obsolete and threw it out. Well, that lasted only about two weeks.  It became apparent that not only Python's docs, but thousands of other projects, seem to rely on it. So, defindex.html was restored, but with the deprecation warning.

Then, on 1. January 2017, Sphinx deleted defindex.html again. (See https://github.com/sphinx-doc/sphinx/commit/45d3f2e8b279efa9d42068d4109cd97eb3f2d899 ). I can only imagine that, once this change makes it into the public release of Sphinx, Python's documentation, and that of thousands of projects, will break again.

So, it seems like a good idea to proactively remove the dependence on this Sphinx file, before that new Sphinx release comes out. 

Options:

1. Copy the Sphinx defindex.html file into our source tree, and keep using it. Plus points: it's simple and easy. Minus points: the Sphinx licence terms may not permit this.  And, it is not HTML5 compatible, which we might care about.

2. Identify the template which Sphinx intends as a successor to defindex.html, and switch to using that.  I've done a bit of searching, and couldn't find out which template that might be.

3. Reimplement our Doc/tools/templates/indexcontent.html to rely on supported Sphinx template, and replace whatever intermediate content we were using from defindex.html with freshly-written code. 

I don't have a solution in mind for this issue. I just want to get it in the bug list, so we know about it.

----------
assignee: docs at python
components: Documentation
messages: 287478
nosy: JDLH, docs at python
priority: normal
severity: normal
status: open
title: Documentation uses deprecated "defindex.html" Sphinx template
type: compile error
versions: Python 3.7

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

From report at bugs.python.org  Fri Feb 10 03:14:19 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 10 Feb 2017 08:14:19 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
Message-ID: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>


New submission from Jim DeLaHunt:

When I build the documentation on the current CPython code, there are various error and warning messages on the console. 

Here's what my build output looks like. I've marked the messages I'm concerned about with a numbered >>0>> prefix.

===== (beginning of output)
% make html
sphinx-build -b html -d build/doctrees -D latex_paper_size=  . build/html 
Running Sphinx v1.5.2
loading pickled environment... done
>>1>> WARNING: latex_preamble is deprecated. Use latex_elements['preamble'] instead.
>>2>> WARNING: latex_paper_size is deprecated. Use latex_elements['papersize'] instead.
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 466 source files that are out of date
updating environment: 0 added, 1 changed, 0 removed
reading sources... [100%] whatsnew/changelog                                                                
>>3>> ../../Misc/NEWS:659: WARNING: Inline emphasis start-string without end-string.
>>4>> ../../Misc/NEWS:659: WARNING: Inline emphasis start-string without end-string.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [100%] whatsnew/index                                                                     
>>5>> /Users/jdlh/workspace/cpython_github/Doc/faq/windows.rst:303: WARNING: unknown option: -t
generating indices... genindex py-modindex
writing additional pages... download index
>>6>> WARNING: Now base template defindex.html is deprecated.
 search opensearch
copying images... [100%] using/win_installer.png                                                            
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 6 warnings.

Build finished. The HTML pages are in build/html.
===== (end of output)

This is observed when building documentation from branch master, commit b1dc6b6d5fa20f63f9651df2e7986a066c88ff7d . 
The build command is "cd Doc; make html".

Warning >>6>> is the subject of http://bugs.python.org/issue29520 . It's harder to fix, and I won't address it here.

The other five warnings are pretty easy to fix.

Warnings >>1>>, >>2>> are Sphinx warnings about names used in Doc/conf.py , namely `latex_preamble` and `latex_paper_size`. There are straightforward changes to build a dict latex_elements{}, with keys 'preamble' and 'papersize'. It turns out that makefiles Doc/Makefile and Doc/make.bat also referred to `latex_paper_size`. Those references are rewritten as `latex_elements.papersize`, per Sphinx syntax for external names.

Warnings >>3>>, >>4>> are Sphinx warnings about the text, in Misc/NEWS:661, 
  ```is now of type "const char *" rather of "char *".```
Put a backslash in front of the '*', and the warning disappears.
 
Warning >>5>> is a Sphinx warning about this text, in 
Doc/faq/windows.rst:303:

If you suspect mixed tabs and spaces are causing problems in leading whitespace, run Python with the :option:`-t` switch or run ``Tools/Scripts/tabnanny.py`` to check a directory tree in batch mode.

The notation :option:`-t` seems to need a corresponding ``.. cmdoption:: -t `` entry, perhaps in the same file. There is no such entry.

It turns out that the -t option has no function in Python 3.6, maybe in all of 3.x. Python swallows the option but does nothing. Thus, instead of trying to make the reference to '-t' work, I decided to cut the whole phrase. This paragraph now reads, 

If you suspect mixed tabs and spaces are causing problems in leading whitespace, run ``Tools/Scripts/tabnanny.py`` to check a directory tree in batch mode.

I am making a Pull Request with these fixes. I will shortly link to it from here.

----------
assignee: docs at python
components: Documentation
messages: 287480
nosy: JDLH, docs at python
priority: normal
severity: normal
status: open
title: Minor warning messages when compiling documentation
type: compile error
versions: Python 3.7

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

From report at bugs.python.org  Fri Feb 10 03:48:09 2017
From: report at bugs.python.org (Martin Panter)
Date: Fri, 10 Feb 2017 08:48:09 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486716489.89.0.453117860742.issue29521@psf.upfronthosting.co.za>


Martin Panter added the comment:

Jim, regarding Doc/faq/windows.rst, this warning lead me to open Issue 29387. We already have discussed a patch for that, and I think it is ready to commit (when it gets to the top of my list, if nobody else beats me to it).

Regarding Misc/NEWS, I think I was going to use ``backticks`` as quotes (Slightly more palatable than backslashes; this file is meant to be readable as plain text as well.)

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

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

From report at bugs.python.org  Fri Feb 10 03:48:28 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 10 Feb 2017 08:48:28 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1486716508.67.0.326934409809.issue29520@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

The other warnings in the "make html" output are the subject of http://bugs.python.org/issue29521 .

----------

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

From report at bugs.python.org  Fri Feb 10 03:50:10 2017
From: report at bugs.python.org (Martin Panter)
Date: Fri, 10 Feb 2017 08:50:10 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486716610.15.0.292872100467.issue29521@psf.upfronthosting.co.za>


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


----------
dependencies: +Tabs vs spaces FAQ out of date

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

From report at bugs.python.org  Fri Feb 10 04:42:54 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 10 Feb 2017 09:42:54 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486719774.75.0.857480954557.issue29521@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Thanks, Martin, for your suggestions.

In Misc/NEWS, I've respelled the ``char *`` as you suggested. 
In faq/windows.rst, I've used your wording from the discussion in http://bugs.python.org/issue29387 .

Pull Request 76 https://github.com/python/cpython/pull/76 ready for review.

----------
pull_requests: +27

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

From report at bugs.python.org  Fri Feb 10 04:46:49 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 10 Feb 2017 09:46:49 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486720008.91.0.164549007623.issue29387@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

I just created Pull Request 76 https://github.com/python/cpython/pull/76  to address http://bugs.python.org/issue29521 . 

In faq/windows.rst, I've used your wording from the discussion in of this bug. I may have address this issue completely, in fact.  I did not do the more careful "testing all versions patched" which Terry suggested.

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

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

From report at bugs.python.org  Fri Feb 10 05:27:01 2017
From: report at bugs.python.org (Marco Buttu)
Date: Fri, 10 Feb 2017 10:27:01 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486722420.97.0.348314244004.issue29387@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Thanks Jim. I tested thise exec() in Py2.7 and Py3 (3.5 - 3.7):

exec("if True:\n" + " "*width + "1\n" + "\t2\n")

* width == 0 raises a IndentationError both in Py2 and Py3
* width in range(1, 8) raises an IndentationError in Py2 and TabError in Py3
* width == 8 is OK in Py2, and raises a TabError in Python 3
* width > 8 is the same as width == 0

I think the most important case, is when width==4 or width==8, because they are the usual widths of the TAB. In these cases, the editor will show a "correct" level of indentation, but Python will raise an exception and a beginner user will not understand the reason. IMO is here that Lib/tabnanny.py really comes in handy. And in these cases (width== 4 or 8), Python 3 raises a TabError, but if we write in the doc that it raises an IndentationError, IMO the user perhaps will think there is an error in the doc, because IMO on the average he/she will not spot that TabError is a subclass of IndentationError. Thats why I think it is better to not specity the exeption type.

Anyway, it is really a minor issue, and currently is also related to other issues, so there is no need to discuss to much for such a detail. Finally, the wording in the pull request is good enough for me :) Thanks

----------

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

From report at bugs.python.org  Fri Feb 10 12:35:55 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 10 Feb 2017 17:35:55 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1486748155.74.0.150973552425.issue29481@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Feb 10 13:22:09 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 10 Feb 2017 18:22:09 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1486750929.8.0.830352271223.issue29481@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

The online docs are regenerated daily from the current repository, so the inclusion of typing.Deque in the doc is correct, given that it has been added to the module.  IDLE aside, new features in bugfix releases are limited to provisional modules, such as typing.  I believe this should get a 'New in 3.6.1' (or 3.5.?) note.

Some installations include a local frozen copy of the docs.  The frozen copy will not include the rare (and admittedly confusing) feature added for a future release.  But it will also not include the much more common corrections and clarifications added since the release.

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

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

From report at bugs.python.org  Fri Feb 10 16:27:40 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Fri, 10 Feb 2017 21:27:40 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486762060.59.0.875446104306.issue29521@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

My Pull Request was closed, because apparently  https://github.com/python/cpython/ will not be the new GitHub repo for Python. The actual repo will open on 11. Feb, I'm told. I will repeat the PR there. Please stand by.

----------

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

From report at bugs.python.org  Fri Feb 10 20:13:32 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sat, 11 Feb 2017 01:13:32 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486775610.39.0.009413827356.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

I've drafted some fairly restricted changes to the doctest documentation page. They are in my Github branch, https://github.com/JDLH/cpython/tree/Issue29428_doctest_docs . The diffs are at https://github.com/JDLH/cpython/commit/223ef8f8a6d2fbec6db774912028abb4d2ff88b6 . 

There currently is no official Python github repot against which to make a pull request. In a few days, once it appears, I'll make a pull request.

In the meantime, I can take review comments and improve it. If you are interested, please review.

----------

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

From report at bugs.python.org  Fri Feb 10 22:15:55 2017
From: report at bugs.python.org (Roger Sachan)
Date: Sat, 11 Feb 2017 03:15:55 +0000
Subject: [docs] [issue29531] Update Doc/README.txt to README.rst
Message-ID: <1486782955.84.0.790445340079.issue29531@psf.upfronthosting.co.za>


New submission from Roger Sachan:

I have simply updated the document and its references to README.rst (thanks to whoever formatted it).

----------
assignee: docs at python
components: Documentation
messages: 287590
nosy: Roger Sachan, docs at python
priority: normal
pull_requests: 29
severity: normal
status: open
title: Update Doc/README.txt to README.rst
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Fri Feb 10 22:38:48 2017
From: report at bugs.python.org (Roger Sachan)
Date: Sat, 11 Feb 2017 03:38:48 +0000
Subject: [docs] [issue29531] Update Doc/README.txt to README.rst
In-Reply-To: <1486782955.84.0.790445340079.issue29531@psf.upfronthosting.co.za>
Message-ID: <1486784328.57.0.460430742592.issue29531@psf.upfronthosting.co.za>


Changes by Roger Sachan <narayanroger at gmail.com>:


----------
pull_requests: +31

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

From report at bugs.python.org  Sat Feb 11 00:00:12 2017
From: report at bugs.python.org (Brett Cannon)
Date: Sat, 11 Feb 2017 05:00:12 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486789212.36.0.0452212729624.issue28929@psf.upfronthosting.co.za>


Brett Cannon added the comment:

Now that we have migrated to GitHub and Mariatta is a core dev I'm assigning this to her. :)

----------
assignee: docs at python -> Mariatta

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

From report at bugs.python.org  Sat Feb 11 10:34:11 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 11 Feb 2017 15:34:11 +0000
Subject: [docs] [issue26213] Document BUILD_*_UNPACK opcodes
In-Reply-To: <1453851645.07.0.698993321818.issue26213@psf.upfronthosting.co.za>
Message-ID: <1486827251.78.0.124709908959.issue26213@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

At the same time the semantic of the BUILD_MAP opcode was changed. However the documentation was not updated and currently it doesn't match the implementation. This caused an issue in third-party projects that operate with bytecode.

See also issue28810 for documenting bytecode changes in 3.6.

----------
priority: low -> high
type:  -> behavior
versions: +Python 3.5, Python 3.7

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

From report at bugs.python.org  Sat Feb 11 12:18:10 2017
From: report at bugs.python.org (Roger Sachan)
Date: Sat, 11 Feb 2017 17:18:10 +0000
Subject: [docs] [issue29531] Update Doc/README.txt to README.rst
In-Reply-To: <1486782955.84.0.790445340079.issue29531@psf.upfronthosting.co.za>
Message-ID: <1486833490.51.0.700716629857.issue29531@psf.upfronthosting.co.za>


Changes by Roger Sachan <narayanroger at gmail.com>:


----------
pull_requests:  -29

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

From report at bugs.python.org  Sat Feb 11 19:40:00 2017
From: report at bugs.python.org (Joakim Soderlund)
Date: Sun, 12 Feb 2017 00:40:00 +0000
Subject: [docs] [issue28739] PEP 498: docstrings as f-strings
In-Reply-To: <1479501831.35.0.531195928426.issue28739@psf.upfronthosting.co.za>
Message-ID: <1486860000.36.0.0915873277971.issue28739@psf.upfronthosting.co.za>


Joakim Soderlund added the comment:

I got slightly confused here while playing around.

Python 3.6.0 (default, Jan 31 2017, 11:39:39) 
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> class Huacaya:
...   f"""Huacaya!"""
... 
>>> class Suri:
...   f"""{'Suri!'}"""
... 
>>> Huacaya.__doc__ is None
False
>>> Suri.__doc__ is None
True

At first I thought f-strings *did* work as docstrings since it worked  just fine for the first class. But, the docstring suddenly vanished when putting an actual expression into it.

----------
nosy: +JockeTF

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

From report at bugs.python.org  Sat Feb 11 21:46:09 2017
From: report at bugs.python.org (Eric Appelt)
Date: Sun, 12 Feb 2017 02:46:09 +0000
Subject: [docs] [issue29026] time.time() documentation should mention UTC
 timezone
In-Reply-To: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
Message-ID: <1486867569.49.0.620202491333.issue29026@psf.upfronthosting.co.za>


Eric Appelt added the comment:

As we have moved to GitHub and mandatory reviews with Pull Requests, I have created a new patch in PR#34 which incorporates Victor's suggestions.

----------

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

From report at bugs.python.org  Sat Feb 11 22:48:06 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 03:48:06 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486871286.37.0.944750717366.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Sat Feb 11 22:59:49 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 03:59:49 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486871989.11.0.85580356018.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +35

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

From report at bugs.python.org  Sat Feb 11 23:00:05 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:00:05 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486872005.68.0.494804240007.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +36

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

From report at bugs.python.org  Sat Feb 11 23:00:20 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:00:20 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486872020.48.0.133811940768.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +37

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

From report at bugs.python.org  Sat Feb 11 23:06:08 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:06:08 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486872368.57.0.429955836739.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +38

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

From report at bugs.python.org  Sat Feb 11 23:08:14 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:08:14 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486872494.05.0.296442862466.issue29474@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +39

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

From report at bugs.python.org  Sat Feb 11 23:08:31 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:08:31 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486872511.31.0.560226165299.issue29474@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +40

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

From report at bugs.python.org  Sat Feb 11 23:08:41 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:08:41 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486872521.68.0.720144062096.issue29474@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +41

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

From report at bugs.python.org  Sat Feb 11 23:09:50 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:09:50 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486872590.24.0.592907566047.issue29474@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +42

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

From report at bugs.python.org  Sat Feb 11 23:13:07 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 04:13:07 +0000
Subject: [docs] [issue28941] Update the link to Source Code in Python Docs
 from hg to github
In-Reply-To: <1481513819.65.0.156579360966.issue28941@psf.upfronthosting.co.za>
Message-ID: <1486872787.95.0.730627667383.issue28941@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
assignee: docs at python -> Mariatta

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

From report at bugs.python.org  Sun Feb 12 00:58:55 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sun, 12 Feb 2017 05:58:55 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486879134.97.0.942557395177.issue29521@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

It looks like commit e7ffb99f842ebff97cffa0fc90b18be4e5abecf2 to the new GitHub python/cpython repo, by Ryan Gonzalez, fixed the problems in Doc/conf.py, Doc/Makefile, and Misc/NEWS . It did not fix the problems in Doc/make.bat or Doc/faq/windows.rst .  I'll make a new Pull Request on the new repo to fix these two parts.

That commit was related to https://github.com/python/cpython/pull/9. 

http://bugs.python.org/issue29527 talks about over 6000 warnings in the doc build, maybe including some of these. Another PR appeared to have fixed many of the warnings.

----------

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

From report at bugs.python.org  Sun Feb 12 01:41:26 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sun, 12 Feb 2017 06:41:26 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486881685.98.0.587256606511.issue29521@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

I submitted a PR https://github.com/python/cpython/pull/41 to the new Github repo which finishes clearing the warnings in this bug report.

I would appreciate review and committing.

----------
pull_requests: +43

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

From report at bugs.python.org  Sun Feb 12 01:45:29 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sun, 12 Feb 2017 06:45:29 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486881929.02.0.891213420145.issue29387@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

PR https://github.com/python/cpython/pull/41 to the new Github repo contains the following wording in Doc/faq/windows.rst:

Python raises :exc:`IndentationError` or :exc:`TabError` if mixed tabs 
and spaces are causing problems in leading whitespace.
You may also run the :mod:`tabnanny` module to check a directory tree 
in batch mode.

This is parallel wording with the contents of Martin's patch.

The PR may be enough to fix this issue.

----------
pull_requests: +44

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

From report at bugs.python.org  Sun Feb 12 03:02:30 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sun, 12 Feb 2017 08:02:30 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1486886550.8.0.948865554883.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Pull Request https://github.com/python/cpython/pull/45 submitted to new Github repo. 

I would appreciate a review.

I attempted to balance all the different opinions in the discussion below: stay concise, but also improve the clarity.

----------
pull_requests: +45

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

From richardipsum at fastmail.co.uk  Sun Feb 12 08:53:11 2017
From: richardipsum at fastmail.co.uk (Richard Ipsum)
Date: Sun, 12 Feb 2017 13:53:11 +0000
Subject: [docs] os.ftruncate documentation error
Message-ID: <1486907591.138669.878402544.5E488148@webmail.messagingengine.com>

Hi folks,

The documentation for os.ftruncate seems a little misleading,
for both 2.7[1] and 3.6[2] the docs for os.ftruncate say,

"Truncate the file corresponding to file descriptor fd, so that it is at
most length bytes in size."

os.ftruncate is implemented on Unix as a call to ftruncate(2), the man
page for which states:

"The truncate() and ftruncate() functions cause the regular file named
by path or referenced by fd to be truncated to a size of precisely
length bytes."

The distinction between 'at most' and 'precisely' is quite an important
one,
it's quite possible that there is some difference in behaviour on
certain platforms,
but if that is the case then I think the docs ought to make that clear.

I'll be quite happy to submit a patch to make the docs clearer,
if I can get a little direction on what sort of change would be best.

Hope this helps,
thanks,
Richard Ipsum

[1]:
https://docs.python.org/2.7/library/os.html?highlight=os.ftruncate#os.ftruncate
[2]:
https://docs.python.org/3.6/library/os.html?highlight=os.ftruncate#os.ftruncate

From richardipsum at fastmail.co.uk  Sun Feb 12 09:01:58 2017
From: richardipsum at fastmail.co.uk (Richard Ipsum)
Date: Sun, 12 Feb 2017 14:01:58 +0000
Subject: [docs] os.ftruncate documentation error
In-Reply-To: <1486907591.138669.878402544.5E488148@webmail.messagingengine.com>
References: <1486907591.138669.878402544.5E488148@webmail.messagingengine.com>
Message-ID: <1486908118.140268.878406808.7FA95ADD@webmail.messagingengine.com>

On Sun, Feb 12, 2017, at 01:53 PM, Richard Ipsum wrote:
> Hi folks,
> 
> The documentation for os.ftruncate seems a little misleading,
> for both 2.7[1] and 3.6[2] the docs for os.ftruncate say,
> 
> "Truncate the file corresponding to file descriptor fd, so that it is at
> most length bytes in size."

I just spotted
https://docs.python.org/2.7/library/stdtypes.html?highlight=truncate#file.truncate
so I guess I'm suggesting that this kind of statement should be included
for the truncate
functions in the os module as well.

Thanks,
Richard Ipsum

From report at bugs.python.org  Sun Feb 12 11:24:13 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 16:24:13 +0000
Subject: [docs] [issue29474] Grammatical errors in
 weakref.WeakValueDictionary docs
In-Reply-To: <1486483158.7.0.401706945265.issue29474@psf.upfronthosting.co.za>
Message-ID: <1486916653.65.0.992130079492.issue29474@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, everyone :)
The GitHub PRs have been merged.

Closing this issue.

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

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

From report at bugs.python.org  Sun Feb 12 16:19:51 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 12 Feb 2017 21:19:51 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1486934391.76.0.172286070339.issue28929@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks all :)
PRs have been merged on GitHub.
Closing this.

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

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

From report at bugs.python.org  Sun Feb 12 22:42:22 2017
From: report at bugs.python.org (Thomas Caswell)
Date: Mon, 13 Feb 2017 03:42:22 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1486957341.89.0.316212955585.issue29481@psf.upfronthosting.co.za>


Thomas Caswell added the comment:

I agree this is very confusing (and in fact confused me for about an hour between getting import errors, double checking the docs, checking I was in the right env, double checking the docs, checking the source of my env, double checking the docs, checking the git source and then tracking through these too issues).

----------
nosy: +tcaswell

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

From report at bugs.python.org  Mon Feb 13 00:00:09 2017
From: report at bugs.python.org (Thomas Caswell)
Date: Mon, 13 Feb 2017 05:00:09 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1486962009.42.0.659983498942.issue29481@psf.upfronthosting.co.za>


Changes by Thomas Caswell <tcaswell at gmail.com>:


----------
pull_requests: +50

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

From report at bugs.python.org  Mon Feb 13 08:57:15 2017
From: report at bugs.python.org (Brian Curtin)
Date: Mon, 13 Feb 2017 13:57:15 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1486994235.64.0.358662201209.issue29387@psf.upfronthosting.co.za>


Brian Curtin added the comment:


New changeset 3d707be950b387552585451071928e7b39cdfa53 by Brian Curtin in branch 'master':
bpo-29521 Fix two minor documentation build warnings (#41)
https://github.com/python/cpython/commit/3d707be950b387552585451071928e7b39cdfa53


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

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

From report at bugs.python.org  Mon Feb 13 09:19:10 2017
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 13 Feb 2017 14:19:10 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1486995550.59.0.231934877122.issue29521@psf.upfronthosting.co.za>


STINNER Victor added the comment:

The commit 3d707be950b387552585451071928e7b39cdfa53 broke the Docs buildbot slave. I proposed https://github.com/python/cpython/pull/68 to run the rstlint.py check on Travis as well, and to fix the 2 warnings.

http://buildbot.python.org/all/builders/Docs%203.x/builds/399/steps/lint/logs/stdio


python3 tools/rstlint.py -i tools -i venv
[1] faq/windows.rst:303: trailing whitespace
[1] faq/windows.rst:305: trailing whitespace
2 problems with severity 1 found.
Makefile:156: recipe for target 'check' failed

----------
nosy: +haypo
pull_requests: +52

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

From report at bugs.python.org  Mon Feb 13 10:31:56 2017
From: report at bugs.python.org (Sanket Dasgupta)
Date: Mon, 13 Feb 2017 15:31:56 +0000
Subject: [docs] [issue21056] csv documentation is incorrect
In-Reply-To: <1395720703.0.0.19592596057.issue21056@psf.upfronthosting.co.za>
Message-ID: <1486999916.05.0.991825834561.issue21056@psf.upfronthosting.co.za>


Sanket Dasgupta added the comment:

Hi, I am looking to fix this bug.

So as per the discussion, should I remove the documentation of __next__() ?

----------
nosy: +sanketdg

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

From report at bugs.python.org  Mon Feb 13 13:55:10 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 13 Feb 2017 18:55:10 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487012110.4.0.481234518611.issue29520@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
type: compile error -> enhancement
versions: +Python 3.5, Python 3.6

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

From report at bugs.python.org  Mon Feb 13 14:04:29 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 13 Feb 2017 19:04:29 +0000
Subject: [docs] [issue26213] Document BUILD_*_UNPACK opcodes
In-Reply-To: <1453851645.07.0.698993321818.issue26213@psf.upfronthosting.co.za>
Message-ID: <1487012669.95.0.288299862932.issue26213@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Feb 13 17:36:10 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 13 Feb 2017 22:36:10 +0000
Subject: [docs] [issue28941] Update the link to Source Code in Python Docs
 from hg to github
In-Reply-To: <1481513819.65.0.156579360966.issue28941@psf.upfronthosting.co.za>
Message-ID: <1487025370.5.0.820277038282.issue28941@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

This was addressed in the very first pull request on CPython GitHub (Thanks, Brett ) 

Backported to 2.7, 3.5, and 3.6

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

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

From report at bugs.python.org  Mon Feb 13 20:26:07 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 14 Feb 2017 01:26:07 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487035567.12.0.69824273701.issue29481@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Yes, we should put versionadded in the docs to augment the MISC/NEWS entries.

Mariatta, do you want to take a crack at the patch?  It should hit both 3.5 and 3.6 docs.

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

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

From report at bugs.python.org  Tue Feb 14 04:41:15 2017
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Tue, 14 Feb 2017 09:41:15 +0000
Subject: [docs] [issue11173] Undocumented public APIs in Python 3.2
In-Reply-To: <1297351155.94.0.957592646254.issue11173@psf.upfronthosting.co.za>
Message-ID: <1487065275.44.0.489068623741.issue11173@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

PyEval_CallObject wasn't removed. It's a macro now. And it was documented for a long time in Extending Python... in fact, the documentation was removed, not the API :-)

----------

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

From report at bugs.python.org  Tue Feb 14 05:03:38 2017
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Tue, 14 Feb 2017 10:03:38 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1487066618.68.0.267815242271.issue11165@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

The PyEval_Call*() APIs indeed predate the PyObject_Call*() ones. The PyObject_Call*() APIs came into existence when the abstract layer was added in Python 1.3.

The PyObject_Call*() APIs lacked a way to call an object with keyword arguments for a long time. I guess that's what most people continued to use the PyEval_Call*() ones. The latter also provide better protection against wrong parameters. The interpreter itself used them interchangeably.

----------
nosy: +lemburg

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

From report at bugs.python.org  Tue Feb 14 11:00:59 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 14 Feb 2017 16:00:59 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
Message-ID: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier:

profile .rst say:

> Each restriction is either an integer (to select a count of lines), or a decimal fraction between 0.0 and 1.0 inclusive (to select a percentage of lines), **or a regular expression**

Actually it accept a string that will be compiled to a regex.

Profile.py also mention:

> (i.e., in addition to the old -1, 0, 1, or 2)

Which is not really helpful, to newcomers to Python who do not know what these are meant to be. Either explaining (or removing if considered old behavior that should be stopped) seem to be better alternative.

See https://github.com/python/cpython/pull/88

----------
assignee: docs at python
components: Documentation
messages: 287778
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: profile/pstat doc clariification
versions: Python 3.7

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

From report at bugs.python.org  Tue Feb 14 11:20:44 2017
From: report at bugs.python.org (David Wilemski)
Date: Tue, 14 Feb 2017 16:20:44 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
Message-ID: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>


New submission from David Wilemski:

The binhex documentation has a line in it that says "As of this writing, hexbin() appears to not work in all cases."

This is a bit ambiguous and there is no context for what the bug may be. It appears this line is from the first commit to the hexbin function's documentation in 1995 (https://hg.python.org/cpython/rev/3911d4a89ab0#l4.40) but the commit also has no information about what this bug may be. I also see no current open bugs for the binhex module that seem related.

In 2009, there was a patch for the hexbin function but I have no idea if this is the bug from the original documentation or if it was something else entirely: https://bugs.python.org/issue6369

Given this, I believe the line should be removed unless more details about the referenced buggy behavior can be found.

----------
assignee: docs at python
components: Documentation
messages: 287781
nosy: David Wilemski, docs at python
priority: normal
pull_requests: 59
severity: normal
status: open
title: binhex documentation claims unknown bug
versions: Python 3.7

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

From report at bugs.python.org  Tue Feb 14 11:54:25 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 14 Feb 2017 16:54:25 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1487091265.48.0.0482235256443.issue29387@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 38c8354f3204441f6c6bd22213b449d2d8954fcc by GitHub in branch '3.5':
bpo-29521 Fix two minor documentation build warnings (#41) (#84)
https://github.com/python/cpython/commit/38c8354f3204441f6c6bd22213b449d2d8954fcc


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

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

From report at bugs.python.org  Tue Feb 14 15:13:10 2017
From: report at bugs.python.org (Mark Lawrence)
Date: Tue, 14 Feb 2017 20:13:10 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1487103190.53.0.174113061631.issue11165@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at gmail.com>:


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

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

From report at bugs.python.org  Tue Feb 14 17:37:52 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 14 Feb 2017 22:37:52 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487111872.33.0.827456687275.issue29557@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 6de2b7817fa9403e81dc38f13f3690f0bbf3d064 by Berker Peksag in branch 'master':
bpo-29557: Remove ambiguous line in binhex docs (#90)
https://github.com/python/cpython/commit/6de2b7817fa9403e81dc38f13f3690f0bbf3d064


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

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

From report at bugs.python.org  Tue Feb 14 17:40:10 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 14 Feb 2017 22:40:10 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487112010.79.0.344433647258.issue29557@psf.upfronthosting.co.za>


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


----------
stage:  -> patch review
type:  -> behavior
versions: +Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Feb 14 20:07:06 2017
From: report at bugs.python.org (Roger Sachan)
Date: Wed, 15 Feb 2017 01:07:06 +0000
Subject: [docs] [issue29531] Update Doc/README.txt to README.rst
In-Reply-To: <1486782955.84.0.790445340079.issue29531@psf.upfronthosting.co.za>
Message-ID: <1487120826.49.0.788769481576.issue29531@psf.upfronthosting.co.za>


Changes by Roger Sachan <narayanroger at gmail.com>:


----------
pull_requests: +67

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

From report at bugs.python.org  Tue Feb 14 20:07:21 2017
From: report at bugs.python.org (Roger Sachan)
Date: Wed, 15 Feb 2017 01:07:21 +0000
Subject: [docs] [issue29531] Update Doc/README.txt to README.rst
In-Reply-To: <1486782955.84.0.790445340079.issue29531@psf.upfronthosting.co.za>
Message-ID: <1487120841.72.0.242252959209.issue29531@psf.upfronthosting.co.za>


Changes by Roger Sachan <narayanroger at gmail.com>:


----------
pull_requests:  -31

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

From report at bugs.python.org  Tue Feb 14 21:46:18 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Wed, 15 Feb 2017 02:46:18 +0000
Subject: [docs] [issue29563] Update Devguide about building documentation.
Message-ID: <1487126778.41.0.112837375413.issue29563@psf.upfronthosting.co.za>


New submission from Jim DeLaHunt:

The Devguide section 7.5.1 "Building the documentation" / "Using make / make.bat" is out of date.  The document lists 10 documentation targets for `make`. The Doc/Makefile lists 17. 

One important omission is `make check`, which looks for errors in reStructuredText syntax, using `rstlint.py`. It's important for contributors to know about and to run `make check`, because with the move to GitHub, the project is running make check after pulling in new code.  If contributors haven't cleaned up their submissions, the build fails.

I suggest that the following improvements be made:

1. rewrite the bullet list "Available make targets are:" in 7.5.1 https://cpython-devguide.readthedocs.io/documenting.html#using-make-make-bat to match the list of targets in Doc/Makefile:21-38.

2. add a comment that `make help` will give the most up-to-date list of targets from the makefile, which might be better than the list in the Devguide.

3. add `make help` to both Doc/Makefile:21-38 and Devguide 7.5.1.

4. add to Devguide 6.3. "Helping with the Developer?s Guide" an instruction to run `make check` before submitting a pull request to the Devguide.

----------
assignee: docs at python
components: Documentation
messages: 287808
nosy: JDLH, docs at python
priority: normal
severity: normal
status: open
title: Update Devguide about building documentation.
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Tue Feb 14 21:46:24 2017
From: report at bugs.python.org (A.M. Kuchling)
Date: Wed, 15 Feb 2017 02:46:24 +0000
Subject: [docs] [issue18779] Misleading documentations and comments in
 regular expression HOWTO
In-Reply-To: <1376898316.85.0.0813282739116.issue18779@psf.upfronthosting.co.za>
Message-ID: <1487126783.86.0.506205084732.issue18779@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

Unfortunately making the sentences pedantically correct also makes them ungainly, and I think people generally assume that underscores are treated as a letter.

----------
nosy: +akuchling
resolution:  -> wont fix
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Feb 14 22:58:25 2017
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 15 Feb 2017 03:58:25 +0000
Subject: [docs] [issue29563] Update Devguide about building documentation.
In-Reply-To: <1487126778.41.0.112837375413.issue29563@psf.upfronthosting.co.za>
Message-ID: <1487131105.52.0.401446376978.issue29563@psf.upfronthosting.co.za>


Zachary Ware added the comment:

I'd suggest replacing as much as possible in the devguide with a link to Doc/README.rst (or Doc/README.txt, if that's what it still is).  Other improvements should be made in the README.

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

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

From report at bugs.python.org  Tue Feb 14 22:58:55 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 03:58:55 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487131135.73.0.471332203168.issue29521@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +69

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

From report at bugs.python.org  Tue Feb 14 23:26:28 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 04:26:28 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487132788.41.0.883899138939.issue29481@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +70

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

From report at bugs.python.org  Tue Feb 14 23:33:58 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 04:33:58 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487133238.55.0.0816500322038.issue29481@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +71

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

From report at bugs.python.org  Tue Feb 14 23:39:38 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 04:39:38 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487133578.14.0.219293505414.issue29481@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +72

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

From report at bugs.python.org  Tue Feb 14 23:43:54 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 04:43:54 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487133834.37.0.298020183846.issue29481@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Raymond :) I prepared the pull requests for 3.5, 3.6, and master branches.

Thomas, you mentioned about needing to go over CLA with your employer in your PR.

Not sure if you have any update on that? If your CLA is approved, I can merge and cherry-pick your PR instead.

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

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

From report at bugs.python.org  Tue Feb 14 23:48:10 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 04:48:10 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487134090.6.0.32886783456.issue29521@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +73

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

From report at bugs.python.org  Tue Feb 14 23:48:39 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 04:48:39 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487134119.9.0.720619435323.issue29521@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +74

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

From report at bugs.python.org  Wed Feb 15 00:09:13 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 05:09:13 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1487135353.91.0.0685497547122.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +75

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

From report at bugs.python.org  Wed Feb 15 00:27:58 2017
From: report at bugs.python.org (Thomas Caswell)
Date: Wed, 15 Feb 2017 05:27:58 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1487133834.37.0.298020183846.issue29481@psf.upfronthosting.co.za>
Message-ID: <CAA48SF8iAukJ2N919WH_5JjH0KVLFdJpcuWvKMXvNne0UBB-Ng@mail.gmail.com>


Thomas Caswell added the comment:

I am not optimistic about the speed at which my employer will get this
sorted out.

better to just fix it and drop my commit!

On Tue, Feb 14, 2017, 23:43 Mariatta Wijaya <report at bugs.python.org> wrote:

Mariatta Wijaya added the comment:

Thanks, Raymond :) I prepared the pull requests for 3.5, 3.6, and master
branches.

Thomas, you mentioned about needing to go over CLA with your employer in
your PR.

Not sure if you have any update on that? If your CLA is approved, I can
merge and cherry-pick your PR instead.

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

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

----------

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

From report at bugs.python.org  Wed Feb 15 00:38:13 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 05:38:13 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487137093.64.0.739016191146.issue29481@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Thomas :) I'll let you close your own PR on GitHub.

----------

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

From report at bugs.python.org  Wed Feb 15 01:02:35 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 15 Feb 2017 06:02:35 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487138555.37.0.649370269962.issue29557@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I think this should be read in the context of previous lines:

    If you code or decode textfiles on non-Macintosh platforms they will still use
    the old Macintosh newline convention (carriage-return as end of line).

And may be related to the in-code comment:

    # XXXX Do translation on non-mac systems

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

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

From report at bugs.python.org  Wed Feb 15 01:03:03 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 15 Feb 2017 06:03:03 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487138583.1.0.126890960227.issue29557@psf.upfronthosting.co.za>


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


----------
components: +macOS
nosy: +ned.deily, ronaldoussoren

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

From report at bugs.python.org  Wed Feb 15 04:37:41 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 15 Feb 2017 09:37:41 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487151461.82.0.587147548929.issue29557@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Georg, do remember why this admonition was present?

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

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

From report at bugs.python.org  Wed Feb 15 05:03:26 2017
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 15 Feb 2017 10:03:26 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1487153005.86.0.658065019872.issue11165@psf.upfronthosting.co.za>


INADA Naoki added the comment:

I think PyObject_Call* APIs should be preferred.

As discussed in #29548, we can't remove or deprecate PyEval_Call*.
But I don't think it's worth enough to document them.
How about keep them undocumented?

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

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

From report at bugs.python.org  Wed Feb 15 05:09:31 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 15 Feb 2017 10:09:31 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1487153371.42.0.832822864875.issue11165@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

While they are undocumented there is no a place for adding the recommendation of using corresponding PyObject_Call* functions and describing the way of porting from PyEval_Call* functions to PyObject_Call* functions.

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

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

From report at bugs.python.org  Wed Feb 15 05:11:54 2017
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 15 Feb 2017 10:11:54 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1487153514.03.0.501441440956.issue11165@psf.upfronthosting.co.za>


INADA Naoki added the comment:

In PR 75, I added a comment in Include/ceval.h, right before PyEval_Call* APIs.

https://github.com/python/cpython/pull/75/files#diff-da3df9def5eca3595399b0a5a7698eac

----------

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

From report at bugs.python.org  Wed Feb 15 08:48:53 2017
From: report at bugs.python.org (A.M. Kuchling)
Date: Wed, 15 Feb 2017 13:48:53 +0000
Subject: [docs] [issue23109] French quotes in the documentation are often
 ungrammatical
In-Reply-To: <1419421355.57.0.399831572163.issue23109@psf.upfronthosting.co.za>
Message-ID: <1487166532.87.0.250737834373.issue23109@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

It looks like there's nothing left to do for this ticket.

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

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

From report at bugs.python.org  Wed Feb 15 10:38:54 2017
From: report at bugs.python.org (Ronald Oussoren)
Date: Wed, 15 Feb 2017 15:38:54 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487173134.73.0.46858299884.issue29557@psf.upfronthosting.co.za>


Ronald Oussoren added the comment:

I think the comment about needing translation on non-mac systems is incorrect. Binhex is (or rather was) a textual encoding for binary files used on classic MacOS.  The encoded file is more likely to be binary data than a text file and replacing b'\r' by the line ending of the current platform could well corrupt that data.

----------

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

From report at bugs.python.org  Wed Feb 15 10:49:01 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 15 Feb 2017 15:49:01 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487173741.33.0.19346090769.issue29557@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

File flags are saved in binhex format, therefore it is possible to distinguish text files from binary files.

----------

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

From report at bugs.python.org  Wed Feb 15 11:54:27 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Wed, 15 Feb 2017 16:54:27 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487177667.05.0.455915657438.issue28814@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


----------
pull_requests: +83

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

From report at bugs.python.org  Wed Feb 15 11:56:04 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Wed, 15 Feb 2017 16:56:04 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487177764.93.0.396183929041.issue28814@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


----------
nosy: +mbussonn

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

From report at bugs.python.org  Wed Feb 15 12:29:12 2017
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 15 Feb 2017 17:29:12 +0000
Subject: [docs] [issue29557] binhex documentation claims unknown bug
In-Reply-To: <1487089244.04.0.406287394607.issue29557@psf.upfronthosting.co.za>
Message-ID: <1487179752.33.0.422974251113.issue29557@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I don't remember anything specific about this, sorry.

----------

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

From report at bugs.python.org  Wed Feb 15 12:45:19 2017
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 15 Feb 2017 17:45:19 +0000
Subject: [docs] [issue29563] Update Devguide about building documentation.
In-Reply-To: <1487126778.41.0.112837375413.issue29563@psf.upfronthosting.co.za>
Message-ID: <1487180719.61.0.264613973519.issue29563@psf.upfronthosting.co.za>


Brett Cannon added the comment:

Would you mind moving this issue over to https://github.com/python/devguide/issues where we track devguide issues, Jim?

----------
nosy: +brett.cannon

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

From report at bugs.python.org  Wed Feb 15 14:37:20 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 19:37:20 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487187440.85.0.5906591893.issue29481@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 36da1c3589e1bc4246cccf6bd0094a110416a43a by GitHub in branch 'master':
bpo-29481: add versionadded 3.6.1 to typing.Deque docs (#107)
https://github.com/python/cpython/commit/36da1c3589e1bc4246cccf6bd0094a110416a43a


----------

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

From report at bugs.python.org  Wed Feb 15 14:38:50 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 19:38:50 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487187530.52.0.647283185606.issue29481@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 7224a049b88ed37c510861528147e0db54911bb7 by GitHub in branch '3.6':
bpo-29481: add versionadded 3.6.1 to typing.Deque docs (#108)
https://github.com/python/cpython/commit/7224a049b88ed37c510861528147e0db54911bb7


----------

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

From report at bugs.python.org  Wed Feb 15 14:39:40 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 19:39:40 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487187580.13.0.00152825489746.issue29481@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset bb53a27a5d56a4f33c3fc8eebb486b34808c92b7 by GitHub in branch '3.5':
[cherry-pick for 3.5] bpo-29481: add versionadded 3.5.4 to typing.Deque docs (#109)
https://github.com/python/cpython/commit/bb53a27a5d56a4f33c3fc8eebb486b34808c92b7


----------

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

From report at bugs.python.org  Wed Feb 15 14:41:12 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 15 Feb 2017 19:41:12 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487187672.42.0.857677199659.issue29481@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Merged and backported to 3.5 and 3.6.

Thanks all :)

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

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

From report at bugs.python.org  Wed Feb 15 16:54:17 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Wed, 15 Feb 2017 21:54:17 +0000
Subject: [docs] [issue29563] Update Devguide about building documentation.
In-Reply-To: <1487126778.41.0.112837375413.issue29563@psf.upfronthosting.co.za>
Message-ID: <1487195657.59.0.644868396611.issue29563@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Per request from Brett Cannon, I've moved this issue to https://github.com/python/devguide/issues/116 . Please continue the discussion there.

----------

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

From report at bugs.python.org  Wed Feb 15 17:59:20 2017
From: report at bugs.python.org (Joachim)
Date: Wed, 15 Feb 2017 22:59:20 +0000
Subject: [docs] [issue29575] doc 17.2.1: basic Pool example is too basic
Message-ID: <1487199560.37.0.441891248359.issue29575@psf.upfronthosting.co.za>


New submission from Joachim:

The ?basic example of data parallelism using Pool? is too basic. It demonstrates the syntax, but otherwise makes no sense, and therefore is potentially confusing. It is blatant nonsense to run 5 processes when there are only 3 data to be treated. Let me suggest the following:


from multiprocessing import Pool
import time

def f(x):
    time.sleep(1)
    return x*x

if __name__ == '__main__':
    start_time = time.time()
    with Pool(4) as p:
        print(p.map(f, range(20)))
    print("elapsed wall time: ", time.time()-start_time)

The sleep command makes f representative for a function that takes significant time to execute. Printing the elapsed time shows the user that the 20 calls of f have indeed taken place in parallel.

----------
assignee: docs at python
components: Documentation
messages: 287895
nosy: docs at python, j5w6
priority: normal
severity: normal
status: open
title: doc 17.2.1: basic Pool example is too basic
versions: Python 3.7

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

From report at bugs.python.org  Wed Feb 15 18:08:43 2017
From: report at bugs.python.org (Roger Sachan)
Date: Wed, 15 Feb 2017 23:08:43 +0000
Subject: [docs] [issue29531] Update Doc/README.txt to README.rst
In-Reply-To: <1486782955.84.0.790445340079.issue29531@psf.upfronthosting.co.za>
Message-ID: <1487200123.38.0.434468079772.issue29531@psf.upfronthosting.co.za>


Changes by Roger Sachan <narayanroger at gmail.com>:


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

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

From report at bugs.python.org  Wed Feb 15 18:14:41 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 15 Feb 2017 23:14:41 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487200481.21.0.883593273938.issue29521@psf.upfronthosting.co.za>


STINNER Victor added the comment:


New changeset de553b8210882823d3df3f1ef6882eba3f8accf3 by Victor Stinner in branch '3.5':
bpo-29521 update Misc/ACKS (#111)
https://github.com/python/cpython/commit/de553b8210882823d3df3f1ef6882eba3f8accf3


----------

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

From report at bugs.python.org  Wed Feb 15 18:14:44 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 15 Feb 2017 23:14:44 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487200484.02.0.353733660019.issue29521@psf.upfronthosting.co.za>


STINNER Victor added the comment:


New changeset 02e3357e089f37c23d0f3d1ebee9aa3d7a1492a9 by Victor Stinner in branch '3.6':
bpo-29521 update Misc/ACKS (#110)
https://github.com/python/cpython/commit/02e3357e089f37c23d0f3d1ebee9aa3d7a1492a9


----------

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

From report at bugs.python.org  Wed Feb 15 18:16:26 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 15 Feb 2017 23:16:26 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487200586.8.0.412787625127.issue29521@psf.upfronthosting.co.za>


STINNER Victor added the comment:


New changeset 85064db281545d587992df61154e76439138319f by Victor Stinner in branch 'master':
bpo-29521 update Misc/ACKS (#106)
https://github.com/python/cpython/commit/85064db281545d587992df61154e76439138319f


----------

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

From report at bugs.python.org  Wed Feb 15 18:49:24 2017
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 15 Feb 2017 23:49:24 +0000
Subject: [docs] [issue29563] Update Devguide about building documentation.
In-Reply-To: <1487126778.41.0.112837375413.issue29563@psf.upfronthosting.co.za>
Message-ID: <1487202564.82.0.702173452584.issue29563@psf.upfronthosting.co.za>


Brett Cannon added the comment:

Thanks for moving the issue, Jim!

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

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

From report at bugs.python.org  Wed Feb 15 18:56:56 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 15 Feb 2017 23:56:56 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487203016.72.0.764788856183.issue29521@psf.upfronthosting.co.za>


STINNER Victor added the comment:


New changeset b300c660d34d2027d443098ea605a8e0eb51d383 by GitHub in branch '3.6':
Backport36 doc fixes: PR#68 and PR#124 (#125)
https://github.com/python/cpython/commit/b300c660d34d2027d443098ea605a8e0eb51d383


----------

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

From report at bugs.python.org  Wed Feb 15 20:27:35 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Thu, 16 Feb 2017 01:27:35 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
Message-ID: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier:

A couple of function in importlib are marked as deprecated in the documentation but do not raise deprecation warnings.

As the same time it would be great to improve some deprecation warnings and docstring to include the version since when this is deprecated. 

This should be take care of by https://github.com/python/cpython/pull/32

----------
assignee: docs at python
components: Documentation
messages: 287908
nosy: docs at python, mbussonn
priority: normal
pull_requests: 88
severity: normal
status: open
title: Improve some deprecations in the importlib
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Wed Feb 15 21:00:34 2017
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 16 Feb 2017 02:00:34 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1487210434.74.0.291803014631.issue29576@psf.upfronthosting.co.za>


Brett Cannon added the comment:


New changeset 1d4601c2c6952d03fc4dda2b041be9aa8713c0bc by Brett Cannon in branch 'master':
bpo-29576: add explicit deprecation for importlib.abc.find_loader() and find_module() (GH-32)
https://github.com/python/cpython/commit/1d4601c2c6952d03fc4dda2b041be9aa8713c0bc


----------
nosy: +brett.cannon

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

From report at bugs.python.org  Wed Feb 15 21:00:59 2017
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 16 Feb 2017 02:00:59 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1487210459.85.0.533650300028.issue29576@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Feb 16 04:43:18 2017
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 16 Feb 2017 09:43:18 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487238198.56.0.262983198689.issue29521@psf.upfronthosting.co.za>


STINNER Victor added the comment:


New changeset 5e04dfecec478db13031fa507d6b2e21adbce035 by GitHub in branch '3.5':
Backport35 doc fixes: PR#68 and PR#124 (#125) (#126)
https://github.com/python/cpython/commit/5e04dfecec478db13031fa507d6b2e21adbce035


----------

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

From report at bugs.python.org  Thu Feb 16 05:00:47 2017
From: report at bugs.python.org (Eric Appelt)
Date: Thu, 16 Feb 2017 10:00:47 +0000
Subject: [docs] [issue29026] time.time() documentation should mention UTC
 timezone
In-Reply-To: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
Message-ID: <1487239247.36.0.404311819451.issue29026@psf.upfronthosting.co.za>


Changes by Eric Appelt <eric.appelt at gmail.com>:


----------
pull_requests: +91

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

From report at bugs.python.org  Thu Feb 16 05:00:47 2017
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 16 Feb 2017 10:00:47 +0000
Subject: [docs] [issue29026] time.time() documentation should mention UTC
 timezone
In-Reply-To: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
Message-ID: <1487239247.86.0.0601946474666.issue29026@psf.upfronthosting.co.za>


STINNER Victor added the comment:


New changeset 23557d59b819f57800ddef0b1373acef8e024670 by Victor Stinner in branch 'master':
bpo-29026: Clarify documentation of time.time (#34)
https://github.com/python/cpython/commit/23557d59b819f57800ddef0b1373acef8e024670


----------

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

From report at bugs.python.org  Thu Feb 16 12:32:50 2017
From: report at bugs.python.org (Stefan Pochmann)
Date: Thu, 16 Feb 2017 17:32:50 +0000
Subject: [docs] [issue29580] "Built-in Functions" not being functions
Message-ID: <1487266370.66.0.0116645570203.issue29580@psf.upfronthosting.co.za>


New submission from Stefan Pochmann:

About https://docs.python.org/3/library/functions.html: The title "Built-in Functions", the table header "Built-in Functions" and the "functions" in the URL all suggest that what's on this page are functions. But many things on that page don't appear to be functions, like "range" or "dict". They appear to be callable types instead. For example "range":

    >>> type(range)
    <class 'type'>
    >>> import types
    >>> isinstance(range, types.FunctionType)
    False
    >>> isinstance(range, types.BuiltinFunctionType)
    False

Compare with "abs":

    >>> type(abs)
    <class 'builtin_function_or_method'>
    >>> isinstance(abs, types.FunctionType)
    False
    >>> isinstance(abs, types.BuiltinFunctionType)
    True

The text between title and table talks about "functions and types", but the title/tableheader/URL disagree.

Also, the table is wrong in saying that "abs()" etc are functions. Should say "abs" instead, i.e., remove the "()".

Many, like "abs", aren't even allowed to be called like that, as it results in "TypeError: abs() takes exactly one argument (0 given)".

----------
assignee: docs at python
components: Documentation
messages: 287961
nosy: Stefan Pochmann, docs at python
priority: normal
severity: normal
status: open
title: "Built-in Functions" not being functions
type: enhancement
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Thu Feb 16 12:43:13 2017
From: report at bugs.python.org (Stefan Pochmann)
Date: Thu, 16 Feb 2017 17:43:13 +0000
Subject: [docs] [issue29580] "Built-in Functions" not being functions
In-Reply-To: <1487266370.66.0.0116645570203.issue29580@psf.upfronthosting.co.za>
Message-ID: <1487266993.82.0.730039614083.issue29580@psf.upfronthosting.co.za>


Stefan Pochmann added the comment:

The page also contains many references like "As repr(), return a string containing..." where the "()" should be removed.

----------

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

From report at bugs.python.org  Thu Feb 16 13:00:48 2017
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Thu, 16 Feb 2017 18:00:48 +0000
Subject: [docs] [issue29580] "Built-in Functions" not being functions
In-Reply-To: <1487266370.66.0.0116645570203.issue29580@psf.upfronthosting.co.za>
Message-ID: <1487268048.69.0.640317926275.issue29580@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

While "functions" may not be accurate anymore, they are all callables.

Historically, those callables were functions. Later on some of the built-ins were replaced with type objects.

Regarding your last comment: It is common in Python to write "func()" for callables in Python. The "()" signal the callable property.

----------
nosy: +lemburg

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

From report at bugs.python.org  Thu Feb 16 14:30:54 2017
From: report at bugs.python.org (R. David Murray)
Date: Thu, 16 Feb 2017 19:30:54 +0000
Subject: [docs] [issue29580] "Built-in Functions" not being functions
In-Reply-To: <1487266370.66.0.0116645570203.issue29580@psf.upfronthosting.co.za>
Message-ID: <1487273454.58.0.827133383761.issue29580@psf.upfronthosting.co.za>


R. David Murray added the comment:

Agreed with Marc.  I don't think there is anything to do here.  The fact that python allows classes (which are callables) to be substituted for functions is a strength, but can lead to confusion (and people getting upset when classes end up with lowercase names :)

I think it would be more confusing than helpful to say "Built-in Callables".

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

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

From report at bugs.python.org  Thu Feb 16 15:15:52 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Thu, 16 Feb 2017 20:15:52 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487276152.12.0.622243757824.issue29453@psf.upfronthosting.co.za>


Changes by Jim Fasarakis-Hilliard <d.f.hilliard at gmail.com>:


----------
pull_requests: +100

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

From report at bugs.python.org  Fri Feb 17 05:48:03 2017
From: report at bugs.python.org (Adrian Chan)
Date: Fri, 17 Feb 2017 10:48:03 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
Message-ID: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>


New submission from Adrian Chan:

I uninstalled python 2.7 and 3.4, then performed a fresh install of 3.5.3.
Running pip with `python -m pip` as per https://docs.python.org/3.5/installing gives the following error:

C:\Python\Python35-32\python.exe: No module named pip.__main__; 'pip' is a package and cannot be directly executed

Installation details:
*  win 7 64 bit.
*  python 3.5.3 32 bit.
*  chose options for pip, tcl/tk/idle, test suite, py launcher, shortcuts, add to env, precompile std lib.
*  installed to non-standard directory.

----------
assignee: docs at python
components: Documentation, Installation, Windows
messages: 287986
nosy: Adrian Chan, docs at python, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Cannot run pip in fresh install of py 3.5.3
type: behavior
versions: Python 3.5

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

From report at bugs.python.org  Fri Feb 17 06:59:37 2017
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 17 Feb 2017 11:59:37 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487332777.71.0.971659155004.issue29586@psf.upfronthosting.co.za>


Eryk Sun added the comment:

Please provide the complete traceback. Copy and paste it from the command prompt. Also, include the fully-qualified path for what "python" runs, e.g. run `where python` in the command prompt. Also, include the value of the environment variables PYTHONHOME and PYTHONPATH, e.g. run `echo %PYTHONHOME% & echo %PYTHONPATH%` in the command prompt.

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

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

From report at bugs.python.org  Fri Feb 17 07:12:04 2017
From: report at bugs.python.org (Adrian Chan)
Date: Fri, 17 Feb 2017 12:12:04 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487333524.59.0.934793215956.issue29586@psf.upfronthosting.co.za>


Adrian Chan added the comment:

There is no traceback, that is the entirety of the output of the command.

Python bin is C:\Python\Python35-32\python.exe
PYTHONHOME is not set.
PYTHONPATH is C:\python27\lib\site-packages\

I don't know why PYTHONPATH was set.  I cleared it but it made no difference -- same error.

----------

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

From report at bugs.python.org  Fri Feb 17 07:53:23 2017
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 17 Feb 2017 12:53:23 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487336003.77.0.372373495445.issue29586@psf.upfronthosting.co.za>


Eryk Sun added the comment:

That error looks like __init__.py[c] was left in "C:\python27\lib\site-packages\pip". Just to be sure, since I don't know what you did to clear the value, please run `set PYTHONPATH=` to clear the value for the current shell. Then try `python -m pip`.

When you modify or remove an environment variable using the control panel dialog, it broadcasts a window message that causes Explorer to reload its environment. Generally console applications such as cmd.exe do not own a top-level window (the console window is owned by conhost.exe) and thus cannot see this broadcasted message. To get the updated environment, you have to run a new instance of cmd from Explorer.

----------

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

From report at bugs.python.org  Fri Feb 17 08:20:57 2017
From: report at bugs.python.org (Adrian Chan)
Date: Fri, 17 Feb 2017 13:20:57 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487337657.28.0.69321751787.issue29586@psf.upfronthosting.co.za>


Adrian Chan added the comment:

Thanks, but I know how to drive a terminal ;)

Your hunch was basically correct though.  I ran again with `python -v -m pip` (see with_pip_dir.txt), and see that python is attempting to import pip from my user directory (C:\Users\amc2\pip).  This is an empty directory, except for an old pip log file from 2.7.

If I rename the directory to something unrelated, `python -m pip` just fails with:

C:\Python\Python35-32\python.exe: No module named pip.

So mystery 1 is solved.

I've definitely selected the pip option in the python installer.  I also repaired the installation, with the pip option selected, and the error still remains.
Where is pip supposed to be located on a win7 install?

----------
Added file: http://bugs.python.org/file46642/import_logs.tar.gz

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

From report at bugs.python.org  Fri Feb 17 08:55:06 2017
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 17 Feb 2017 13:55:06 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487339706.14.0.803530601557.issue29586@psf.upfronthosting.co.za>


Eryk Sun added the comment:

pip should be installed in site-packages, which for you is "C:\Python\Python35-32\Lib\site-packages". Try manually running ensurepip to make sure pip is installed:

    python -m ensurepip --verbose --upgrade --default-pip

----------

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

From report at bugs.python.org  Fri Feb 17 09:13:09 2017
From: report at bugs.python.org (Adrian Chan)
Date: Fri, 17 Feb 2017 14:13:09 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487340789.88.0.13232730769.issue29586@psf.upfronthosting.co.za>


Adrian Chan added the comment:

It's all working fine now, thanks.

If one of the installer/windows guys wants to dig more into why this didn't install properly I'm happy to run things in my environment as necessary.

----------

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

From report at bugs.python.org  Fri Feb 17 09:22:18 2017
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 17 Feb 2017 14:22:18 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487341338.88.0.173691539885.issue29586@psf.upfronthosting.co.za>


Eryk Sun added the comment:

If you have the 3.5 installation logs in your %TEMP% directory, please zip them up and attach them to this issue.

----------

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

From report at bugs.python.org  Fri Feb 17 12:00:56 2017
From: report at bugs.python.org (Adrian Chan)
Date: Fri, 17 Feb 2017 17:00:56 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487350856.76.0.323158819118.issue29586@psf.upfronthosting.co.za>


Adrian Chan added the comment:

Install logs attached.
First set from initial install, second set from repair.

----------
Added file: http://bugs.python.org/file46645/py_install_logs.tar.gz

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

From report at bugs.python.org  Fri Feb 17 14:20:15 2017
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 17 Feb 2017 19:20:15 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487359215.84.0.158656761243.issue29586@psf.upfronthosting.co.za>


Eryk Sun added the comment:

The original install failed with the status code STATUS_DLL_NOT_FOUND (0xC0000135), as reported in "Python 3.5.3 (32-bit)_20170217102132_008_pip_JustForMe.log":

    MSI (s) (88:D8) [10:22:59:574]: Executing op: ActionStart(Name=UpdatePip,,)
    MSI (s) (88:D8) [10:22:59:575]: Executing op: CustomActionSchedule(
        Action=UpdatePip,ActionType=1089, Source=BinaryData,Target=CAQuietExec,
        CustomActionData="C:\Python\Python35-32\python.exe" -E -s -m ensurepip -U --default-pip)
    MSI (s) (88:C4) [10:22:59:588]: Invoking remote custom action.
        DLL: C:\Windows\Installer\MSI2C60.tmp,
        Entrypoint: CAQuietExec
    MSI (s) (88:B0) [10:22:59:588]: Generating random cookie.
    MSI (s) (88:B0) [10:22:59:590]: Created Custom Action Server with PID 6212 (0x1844).
    MSI (s) (88:A8) [10:22:59:630]: Running as a service.
    MSI (s) (88:A8) [10:22:59:631]: Hello, I'm your 32bit Impersonated custom action server.
    CAQuietExec:  Error 0xc0000135: Command line returned an error.
    CAQuietExec:  Error 0xc0000135: QuietExec Failed
    CAQuietExec:  Error 0xc0000135: Failed in ExecCommon method
    MSI (s) (88:D8) [10:22:59:658]: Executing op: End(Checksum=0,
        ProgressTotalHDWord=0,ProgressTotalLDWord=287056)
        CustomAction UpdatePip returned actual error code 1603 but will be
        translated to success due to continue marking

Did your system require a reboot for Python 3.5 to work?

>From what I can see in "Python 3.5.3 (32-bit)_20170217131555_007_pip_JustForMe.log", it looks like the repair skipped installing pip. 

    MSI (s) (D8:1C) [13:16:31:822]: Skipping action: SetRemovePipCommandLine (condition is false)
    MSI (s) (D8:1C) [13:16:31:822]: Skipping action: SetUpdatePipCommandLine (condition is false)
    MSI (s) (D8:1C) [13:16:31:822]: Skipping action: UpdatePip (condition is false)
    MSI (s) (D8:1C) [13:16:31:822]: Doing action: InstallFinalize
    MSI (s) (D8:1C) [13:16:31:822]: Note: 1: 2205 2:  3: ActionText 
    Action ended 13:16:31: PublishProduct. Return value 1.

Maybe Steve Dower can shed light on why a repair with pip selected didn't try to install pip.

----------

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

From report at bugs.python.org  Fri Feb 17 15:13:46 2017
From: report at bugs.python.org (Steve Dower)
Date: Fri, 17 Feb 2017 20:13:46 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487362426.21.0.657605703195.issue29586@psf.upfronthosting.co.za>


Steve Dower added the comment:

Depending on why the pip install failed, we may still have registered that it was installed. IIRC, we only trigger the install on a state change, which wouldn't happen in repair. That deserves its own bug (though maybe this one will suffice if we figure out the original failure - I haven't looked at the logs yet)

----------

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

From report at bugs.python.org  Fri Feb 17 18:18:47 2017
From: report at bugs.python.org (Camilla Montonen)
Date: Fri, 17 Feb 2017 23:18:47 +0000
Subject: [docs] [issue29575] doc 17.2.1: basic Pool example is too basic
In-Reply-To: <1487199560.37.0.441891248359.issue29575@psf.upfronthosting.co.za>
Message-ID: <1487373527.57.0.8897640259.issue29575@psf.upfronthosting.co.za>


Camilla Montonen added the comment:

Would you like to open a PR with a patch on GH? I think the docs could certainly do with another example for Pool.

----------
nosy: +Winterflower

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

From report at bugs.python.org  Fri Feb 17 18:21:10 2017
From: report at bugs.python.org (Camilla Montonen)
Date: Fri, 17 Feb 2017 23:21:10 +0000
Subject: [docs] [issue29247] Document return value of epoll.poll
In-Reply-To: <1484195034.62.0.718564451527.issue29247@psf.upfronthosting.co.za>
Message-ID: <1487373670.88.0.873914650213.issue29247@psf.upfronthosting.co.za>


Changes by Camilla Montonen <camillamon at gmail.com>:


----------
nosy: +Winterflower

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

From report at bugs.python.org  Fri Feb 17 20:12:00 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 18 Feb 2017 01:12:00 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487380320.23.0.864750747928.issue29453@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

>> But maybe it is worth to mention that the output 
>> corresponds to the order of passed keyword arguments
 
> Should I add this note? 

Yes, please.  This is a section on keyword arguments, making it the preferred place to mention the new guaranteed output order.

----------

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

From report at bugs.python.org  Fri Feb 17 20:12:12 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sat, 18 Feb 2017 01:12:12 +0000
Subject: [docs] [issue29596] Unfinished sentense in howto/clinic.rst
Message-ID: <1487380332.64.0.682733186171.issue29596@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier:

Around line 1400 of Doc/howto/clinic.rst

  ``two-pass``
    A buffer like ``buffer``.  However, a two-pass buffer can only
    be written once, and it prints out all text sent to it during
    all of processing, even from Clinic blocks *after* the

I've rarely be kept in such suspense ! Unless it's a reference to Monty Python's "The Man Who Finishes Other People's Sentences". In which case, I must say it's

----------
assignee: docs at python
components: Documentation
messages: 288048
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: Unfinished sentense in howto/clinic.rst
versions: Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Fri Feb 17 20:39:32 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 18 Feb 2017 01:39:32 +0000
Subject: [docs] [issue29580] "Built-in Functions" not being functions
In-Reply-To: <1487266370.66.0.0116645570203.issue29580@psf.upfronthosting.co.za>
Message-ID: <1487381971.98.0.454155655852.issue29580@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I concur with the other respondents and am going to mark this as closed.

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

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

From report at bugs.python.org  Sat Feb 18 00:13:18 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 05:13:18 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487394798.54.0.146220718066.issue29481@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 36da1c3589e1bc4246cccf6bd0094a110416a43a by GitHub in branch 'ncoghlan-devguide-link':
bpo-29481: add versionadded 3.6.1 to typing.Deque docs (#107)
https://github.com/python/cpython/commit/36da1c3589e1bc4246cccf6bd0094a110416a43a


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

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

From report at bugs.python.org  Sat Feb 18 00:13:18 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 05:13:18 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1487394798.83.0.642520591769.issue29576@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 1d4601c2c6952d03fc4dda2b041be9aa8713c0bc by Brett Cannon in branch 'ncoghlan-devguide-link':
bpo-29576: add explicit deprecation for importlib.abc.find_loader() and find_module() (GH-32)
https://github.com/python/cpython/commit/1d4601c2c6952d03fc4dda2b041be9aa8713c0bc


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

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

From report at bugs.python.org  Sat Feb 18 00:13:19 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 05:13:19 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487394799.01.0.9361690703.issue29521@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 85064db281545d587992df61154e76439138319f by Victor Stinner in branch 'ncoghlan-devguide-link':
bpo-29521 update Misc/ACKS (#106)
https://github.com/python/cpython/commit/85064db281545d587992df61154e76439138319f


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

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

From report at bugs.python.org  Sat Feb 18 00:13:19 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 05:13:19 +0000
Subject: [docs] [issue29026] time.time() documentation should mention UTC
 timezone
In-Reply-To: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
Message-ID: <1487394799.21.0.535706288737.issue29026@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 23557d59b819f57800ddef0b1373acef8e024670 by Victor Stinner in branch 'ncoghlan-devguide-link':
bpo-29026: Clarify documentation of time.time (#34)
https://github.com/python/cpython/commit/23557d59b819f57800ddef0b1373acef8e024670


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

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

From report at bugs.python.org  Sat Feb 18 00:26:46 2017
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2017 05:26:46 +0000
Subject: [docs] [issue29026] time.time() documentation should mention UTC
 timezone
In-Reply-To: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
Message-ID: <1487395606.39.0.68527257462.issue29026@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 00:26:53 2017
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2017 05:26:53 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487395613.81.0.964665088529.issue29521@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 00:27:04 2017
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2017 05:27:04 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1487395624.87.0.930499700801.issue29576@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 00:27:15 2017
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2017 05:27:15 +0000
Subject: [docs] [issue29481] 3.6.0 doc describes 3.6.1 feature - typing.Deque
In-Reply-To: <1486558386.24.0.953871145264.issue29481@psf.upfronthosting.co.za>
Message-ID: <1487395635.64.0.783963259883.issue29481@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 01:40:59 2017
From: report at bugs.python.org (Amit Kumar)
Date: Sat, 18 Feb 2017 06:40:59 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487400059.3.0.487315624358.issue29521@psf.upfronthosting.co.za>


Changes by Amit Kumar <dtu.amit at gmail.com>:


----------
pull_requests: +106

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

From report at bugs.python.org  Sat Feb 18 03:26:42 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 18 Feb 2017 08:26:42 +0000
Subject: [docs] [issue29575] doc 17.2.1: basic Pool example is too basic
In-Reply-To: <1487199560.37.0.441891248359.issue29575@psf.upfronthosting.co.za>
Message-ID: <1487406402.86.0.148766597964.issue29575@psf.upfronthosting.co.za>


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


----------
nosy: +davin

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

From report at bugs.python.org  Sat Feb 18 03:57:43 2017
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 18 Feb 2017 08:57:43 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <525144B9.3040305@python.org>
Message-ID: <1487408263.18.0.587095636593.issue19180@psf.upfronthosting.co.za>


Changes by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
pull_requests: +109

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

From report at bugs.python.org  Sat Feb 18 04:14:44 2017
From: report at bugs.python.org (Amit Kumar)
Date: Sat, 18 Feb 2017 09:14:44 +0000
Subject: [docs] [issue21056] csv documentation is incorrect
In-Reply-To: <1395720703.0.0.19592596057.issue21056@psf.upfronthosting.co.za>
Message-ID: <1487409284.11.0.676370164423.issue21056@psf.upfronthosting.co.za>


Changes by Amit Kumar <dtu.amit at gmail.com>:


----------
pull_requests: +110

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

From report at bugs.python.org  Sat Feb 18 04:15:46 2017
From: report at bugs.python.org (Chandan kumar)
Date: Sat, 18 Feb 2017 09:15:46 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <525144B9.3040305@python.org>
Message-ID: <1487409345.97.0.405264054836.issue19180@psf.upfronthosting.co.za>


Chandan kumar added the comment:

I have updated the RFC references from [0] to [2]. I am not able to find out the TLS links mentioned in the https://docs.python.org/3.4/library/ssl.html. I have attached the pull request.

----------
nosy: +chkumar246

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

From report at bugs.python.org  Sat Feb 18 04:35:33 2017
From: report at bugs.python.org (Subhendu Ghosh)
Date: Sat, 18 Feb 2017 09:35:33 +0000
Subject: [docs] [issue27470] -3 commandline option documented differently
 via man
In-Reply-To: <1467994985.16.0.513883147731.issue27470@psf.upfronthosting.co.za>
Message-ID: <1487410533.07.0.3529880287.issue27470@psf.upfronthosting.co.za>


Changes by Subhendu Ghosh <subho.prp at gmail.com>:


----------
pull_requests: +113

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

From report at bugs.python.org  Sat Feb 18 04:37:59 2017
From: report at bugs.python.org (Sanyam Khurana)
Date: Sat, 18 Feb 2017 09:37:59 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1487410679.29.0.379162754458.issue29506@psf.upfronthosting.co.za>


Changes by Sanyam Khurana <sanyam.khurana01 at gmail.com>:


----------
pull_requests: +114

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

From report at bugs.python.org  Sat Feb 18 04:53:29 2017
From: report at bugs.python.org (Amit Kumar)
Date: Sat, 18 Feb 2017 09:53:29 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1487411609.97.0.0483860226069.issue16011@psf.upfronthosting.co.za>


Changes by Amit Kumar <dtu.amit at gmail.com>:


----------
pull_requests: +116

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

From report at bugs.python.org  Sat Feb 18 05:47:14 2017
From: report at bugs.python.org (Chandan kumar)
Date: Sat, 18 Feb 2017 10:47:14 +0000
Subject: [docs] [issue10938] Provide links to system specific strftime/ptime
 docs
In-Reply-To: <1295378779.48.0.643087757109.issue10938@psf.upfronthosting.co.za>
Message-ID: <1487414834.16.0.834247114008.issue10938@psf.upfronthosting.co.za>


Changes by Chandan kumar <chkumar246 at gmail.com>:


----------
pull_requests: +119

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

From report at bugs.python.org  Sat Feb 18 06:12:13 2017
From: report at bugs.python.org (Sanyam Khurana)
Date: Sat, 18 Feb 2017 11:12:13 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1487416333.68.0.356174683.issue22702@psf.upfronthosting.co.za>


Changes by Sanyam Khurana <sanyam.khurana01 at gmail.com>:


----------
pull_requests: +120

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

From report at bugs.python.org  Sat Feb 18 06:25:14 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 18 Feb 2017 11:25:14 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1487417114.24.0.866736383638.issue22702@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Current documentation looks good to me and not needing changes (except fixing the doubled "iterable"). Proposed change looks incorrect to me. No parameter named "str" is provided in this method.

See also the docstring of str.join.

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

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

From report at bugs.python.org  Sat Feb 18 06:38:30 2017
From: report at bugs.python.org (Sanyam Khurana)
Date: Sat, 18 Feb 2017 11:38:30 +0000
Subject: [docs] [issue18423] Document limitations on -m
In-Reply-To: <1373461112.24.0.280779659137.issue18423@psf.upfronthosting.co.za>
Message-ID: <1487417910.34.0.2454890981.issue18423@psf.upfronthosting.co.za>


Changes by Sanyam Khurana <sanyam.khurana01 at gmail.com>:


----------
pull_requests: +122

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

From report at bugs.python.org  Sat Feb 18 06:45:37 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 11:45:37 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1487418337.1.0.0563780271773.issue29506@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 06:46:56 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 11:46:56 +0000
Subject: [docs] [issue10938] Provide links to system specific strftime/ptime
 docs
In-Reply-To: <1295378779.48.0.643087757109.issue10938@psf.upfronthosting.co.za>
Message-ID: <1487418416.15.0.610606599346.issue10938@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 07:41:21 2017
From: report at bugs.python.org (Subhendu Ghosh)
Date: Sat, 18 Feb 2017 12:41:21 +0000
Subject: [docs] [issue23890] assertRaises increases reference counter
In-Reply-To: <1428518225.53.0.665360255509.issue23890@psf.upfronthosting.co.za>
Message-ID: <1487421681.77.0.886794903054.issue23890@psf.upfronthosting.co.za>


Changes by Subhendu Ghosh <subho.prp at gmail.com>:


----------
nosy: +subho

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

From report at bugs.python.org  Sat Feb 18 07:46:34 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2017 12:46:34 +0000
Subject: [docs] [issue23890] assertRaises increases reference counter
In-Reply-To: <1428518225.53.0.665360255509.issue23890@psf.upfronthosting.co.za>
Message-ID: <1487421994.07.0.0319850201772.issue23890@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

As Robert noted, this is a straight up error, where the clear_frames() call and deleting the exception traceback from the saved object aren't enough to drop all references to `callable_obj`.

The trick is that the cleanup code isn't accounting for __cause__ and __context__: it's only clearing and dropping the traceback for the topmost exception in the chain.

In Vjacheslav's example, there are *two* tracebacks to worry about: both the top level one (which is getting cleaned up) and the inner one from exc.__context__ which isn't being touched.

We could likely use a "traceback.clear_all_frames()" helper that walks an exception tree clearing *all* the traceback frames, both on the original exception, and on all the __cause__ and __context__ attributes.

(We can't just clear __cause__ and __context__, since those can be accessed and tested when using the context manager form and the `exception` attribute)

----------
assignee: docs at python -> 
components:  -Documentation
nosy: +ncoghlan
type: enhancement -> behavior
versions: +Python 3.7

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

From report at bugs.python.org  Sat Feb 18 09:37:55 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Sat, 18 Feb 2017 14:37:55 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487428675.02.0.627764774527.issue29453@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Added the following short sentence to the PR, which I believe makes the point clear: 

Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call.

----------

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

From report at bugs.python.org  Sat Feb 18 12:47:58 2017
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 18 Feb 2017 17:47:58 +0000
Subject: [docs] [issue10938] Provide links to system specific strftime/ptime
 docs
In-Reply-To: <1295378779.48.0.643087757109.issue10938@psf.upfronthosting.co.za>
Message-ID: <1487440078.81.0.400004797927.issue10938@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at gmail.com>:


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

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

From report at bugs.python.org  Sat Feb 18 12:48:38 2017
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 18 Feb 2017 17:48:38 +0000
Subject: [docs] [issue18423] Document limitations on -m
In-Reply-To: <1373461112.24.0.280779659137.issue18423@psf.upfronthosting.co.za>
Message-ID: <1487440118.47.0.670022995362.issue18423@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at gmail.com>:


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

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

From report at bugs.python.org  Sat Feb 18 15:31:11 2017
From: report at bugs.python.org (Max)
Date: Sat, 18 Feb 2017 20:31:11 +0000
Subject: [docs] [issue29597] __new__ / __init__ calls during unpickling not
 documented correctly
Message-ID: <1487449871.91.0.908560924036.issue29597@psf.upfronthosting.co.za>


New submission from Max:

According to the [docs](https://docs.python.org/3/library/pickle.html#pickling-class-instances):

> Note: At unpickling time, some methods like `__getattr__()`, `__getattribute__()`, or `__setattr__()` may be called upon the instance. In case those methods rely on some internal invariant being true, the type should implement `__getnewargs__()` or `__getnewargs_ex__()` to establish such an invariant; otherwise, neither `__new__()` nor `__init__()` will be called.

It seems, however, that this note is incorrect. First, `__new__` is called even if `__getnewargs__` isn't implemented. Second, `__init__` is not called even if it is (while the note didn't say that `__init__` would be called when `__getnewargs__` is defined, the wording does seem to imply it).


class A:
    def __new__(cls, *args):
        print('__new__ called with', args)
        return object.__new__(cls)
    
    def __init__(self, *args):
        print('__init__ called with', args)
        self.args = args
        
    def __getnewargs__(self):
        print('called')
        return ()
    
a = A(1)
s = pickle.dumps(a)
a = pickle.loads(s) # __new__ called, not __init__
delattr(A, '__getnewargs__') 
a = A(1)
s = pickle.dumps(a)
a = pickle.loads(s) # __new__ called, not __init__

----------
assignee: docs at python
components: Documentation
messages: 288088
nosy: docs at python, max
priority: normal
severity: normal
status: open
title: __new__ / __init__ calls during unpickling not documented correctly
versions: Python 3.6

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

From report at bugs.python.org  Sat Feb 18 15:47:07 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 18 Feb 2017 20:47:07 +0000
Subject: [docs] [issue29597] __new__ / __init__ calls during unpickling not
 documented correctly
In-Reply-To: <1487449871.91.0.908560924036.issue29597@psf.upfronthosting.co.za>
Message-ID: <1487450827.71.0.993108603744.issue29597@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

This is a duplicate of issue27635.

----------
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> pickle documentation says that unpickling may not call __new__

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

From report at bugs.python.org  Sat Feb 18 15:47:59 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 18 Feb 2017 20:47:59 +0000
Subject: [docs] [issue27635] pickle documentation says that unpickling may
 not call __new__
In-Reply-To: <1469639245.7.0.966654223743.issue27635@psf.upfronthosting.co.za>
Message-ID: <1487450879.29.0.104227021348.issue27635@psf.upfronthosting.co.za>


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


----------
nosy: +alexandre.vassalotti, serhiy.storchaka
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.7 -Python 3.4

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

From report at bugs.python.org  Sat Feb 18 16:09:56 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 18 Feb 2017 21:09:56 +0000
Subject: [docs] [issue20823] Clarify copyreg.pickle() documentation
In-Reply-To: <1393749966.08.0.529137298895.issue20823@psf.upfronthosting.co.za>
Message-ID: <1487452196.77.0.944112931691.issue20823@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

The phrase "*function* should return either a string or a tuple containing two or three elements." de-facto is outdated too. Since Python 2.3 a tuple returned by the function must have two to five elements.

copyreg.constructor() no longer does anything useful, and the constructor parameter of copyreg.pickle() is virtually ignored.

----------
nosy: +serhiy.storchaka
stage:  -> patch review
type:  -> behavior
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3

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

From report at bugs.python.org  Sat Feb 18 16:10:23 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 18 Feb 2017 21:10:23 +0000
Subject: [docs] [issue11924] Pickle and copyreg modules don't document the
 interface
In-Reply-To: <1303766863.75.0.154822649898.issue11924@psf.upfronthosting.co.za>
Message-ID: <1487452223.93.0.761715878952.issue11924@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 16:43:17 2017
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 18 Feb 2017 21:43:17 +0000
Subject: [docs] [issue11924] Pickle and copyreg modules don't document the
 interface
In-Reply-To: <1303766863.75.0.154822649898.issue11924@psf.upfronthosting.co.za>
Message-ID: <1487454197.74.0.0576559922302.issue11924@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at gmail.com>:


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

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

From report at bugs.python.org  Sat Feb 18 21:57:32 2017
From: report at bugs.python.org (Jaysinh shukla)
Date: Sun, 19 Feb 2017 02:57:32 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487473052.18.0.300957330498.issue29520@psf.upfronthosting.co.za>


Jaysinh shukla added the comment:

Hello Jim,
    I tried to run `make html` on `/Doc` directory at latest master. I was not able to reproduce this warning message. I am attaching console output I got while building the documentation with this issue. I request you to check that once. Will you re-install the dependancy and check for this issue once again? Many thanks!

----------
nosy: +jaysinh.shukla
Added file: http://bugs.python.org/file46647/doc_logs_python.log

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

From report at bugs.python.org  Sat Feb 18 22:25:36 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 03:25:36 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487474736.36.0.364042783271.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:

I can reproduce it with Sphinx 1.5.2.
Additonally, "None" is shown at top.

----------
nosy: +inada.naoki
Added file: http://bugs.python.org/file46648/sphinx-1.5-pydoc.png

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

From report at bugs.python.org  Sat Feb 18 22:29:39 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 19 Feb 2017 03:29:39 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487474978.83.0.645159243475.issue29453@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Thanks for the revision.  Assigning to Mariatta so that she can apply the PR.

----------
assignee: serhiy.storchaka -> Mariatta
nosy: +Mariatta

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

From report at bugs.python.org  Sat Feb 18 22:30:12 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 03:30:12 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487475012.11.0.74493984424.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:

ref: https://github.com/sphinx-doc/sphinx/issues/2986

----------

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

From report at bugs.python.org  Sat Feb 18 23:17:06 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 04:17:06 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487477826.72.0.344531207447.issue29520@psf.upfronthosting.co.za>


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


----------
pull_requests: +128

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

From report at bugs.python.org  Sat Feb 18 23:20:42 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 04:20:42 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487478042.52.0.19860161939.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:

Could docs.python.org use new Sphinx, after fix this issue?

Travis checks doc with Sphinx 1.5.2, but docs.python.org seems using 1.3.3.  It's too old.

----------

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

From report at bugs.python.org  Sun Feb 19 00:12:02 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 19 Feb 2017 05:12:02 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487481122.13.0.383510106656.issue29521@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 3337d33a4518f7ab8a7ab6c9a75b8b92ba348b27 by Nick Coghlan in branch '3.6':
[backport to 3.6] bpo-29529: Add .travis.yml to 3.6 branch (#25)
https://github.com/python/cpython/commit/3337d33a4518f7ab8a7ab6c9a75b8b92ba348b27


----------

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

From report at bugs.python.org  Sun Feb 19 00:13:04 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 19 Feb 2017 05:13:04 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1487481184.52.0.10201014844.issue29521@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 24bfe15e83c24bf2c2e2654050da809553789002 by Nick Coghlan in branch '3.5':
[backport to 3.5] bpo-29529: Add .travis.yml to 3.5 branch (#26)
https://github.com/python/cpython/commit/24bfe15e83c24bf2c2e2654050da809553789002


----------

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

From report at bugs.python.org  Sun Feb 19 00:55:16 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 19 Feb 2017 05:55:16 +0000
Subject: [docs] [issue23890] assertRaises increases reference counter
In-Reply-To: <1428518225.53.0.665360255509.issue23890@psf.upfronthosting.co.za>
Message-ID: <1487483716.05.0.864910383037.issue23890@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I've been looking into this further, and a reproducer that's independent of assertRaises() is to just bind the function to a local variable name in an outer function:

    def outer():
        callable_obj = f
        try:
            callable_obj()
        except Exception as exc:
            return exc

That should make it easier to test a basic recursive "clear_all_frames" operation like:

    def clear_all_frames(exc):
        cause = exc.__cause__
        if cause is not None:
            clear_all_frames(cause)
        context = exc.__context__
        if context is not None:
            clear_all_frames(context)
        traceback.clear_frames(exc.__traceback__)

----------

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

From report at bugs.python.org  Sun Feb 19 02:16:16 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Sun, 19 Feb 2017 07:16:16 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487488576.85.0.801730041482.issue29520@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Jaysinh, thank you for checking.  From your log, I see you are using Sphinx version 1.3.6.  I am seeing this problem with Sphinx version 1.5.2.  I think you need Sphinx 1.5.2 or later to see the warning message.

I notice my original bug description didn't specify a Sphinx version. Now we know that it needs to be a fairly recent version of Sphinx.

>From the discussion in https://github.com/sphinx-doc/sphinx/issues/2986, it looks like the Sphinx team added the warning message at or shortly after the release of 1.5.0.

----------

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

From report at bugs.python.org  Sun Feb 19 02:24:47 2017
From: report at bugs.python.org (Jaysinh shukla)
Date: Sun, 19 Feb 2017 07:24:47 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487489087.16.0.794144551391.issue29520@psf.upfronthosting.co.za>


Changes by Jaysinh shukla <jaysinhp at gmail.com>:


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

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

From report at bugs.python.org  Sun Feb 19 02:25:00 2017
From: report at bugs.python.org (Jaysinh shukla)
Date: Sun, 19 Feb 2017 07:25:00 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487489100.18.0.102914423436.issue29520@psf.upfronthosting.co.za>


Changes by Jaysinh shukla <jaysinhp at gmail.com>:


----------
pull_requests: +136

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

From report at bugs.python.org  Sun Feb 19 03:35:29 2017
From: report at bugs.python.org (tomo cocoa)
Date: Sun, 19 Feb 2017 08:35:29 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487493328.94.0.30441064939.issue29520@psf.upfronthosting.co.za>


tomo cocoa added the comment:

As for CPython documents, these uses only one assignment statement (``{% set ... %}``) [1]_, one h1 element and one p element [2]_ of defindex.html.
These fragments are used to generate following sentences::

   Python 3.6.0 documentation

   Welcome! This is the documentation for Python 3.6.0, last updated Feb 19, 2017. 

.. [1] https://github.com/sphinx-doc/sphinx/blob/8ecd7ff08249739bbc6d900527fe9306592456ab/sphinx/themes/basic/defindex.html#L11

.. [2] https://github.com/sphinx-doc/sphinx/blob/8ecd7ff08249739bbc6d900527fe9306592456ab/sphinx/themes/basic/defindex.html#L13-L18


Therefore, I suggest that we should make indexcontent.html extend layout.html directly and insert the jinja2 code into indexcontent.html in order to generate the sentences above
(which is much the same option as mixture of JDLH's option 1 and 3).

After I wrote this comment, I notice inada.naoki had created `pull request #165 <https://github.com/python/cpython/pull/165>`_.

----------
nosy: +cocoatomo

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

From report at bugs.python.org  Sun Feb 19 06:37:36 2017
From: report at bugs.python.org (Sanyam Khurana)
Date: Sun, 19 Feb 2017 11:37:36 +0000
Subject: [docs] [issue29599] Github organization link is secret and not
 accessible from core-dev guide
Message-ID: <1487504256.78.0.675328219638.issue29599@psf.upfronthosting.co.za>


New submission from Sanyam Khurana:

On visiting link: https://docs.python.org/devguide/coredev.html#github

The first sentence is "You will be added to the Python core team on GitHub."

The ``Python core team`` refers to a link to Github which is not accessible to anyone except for those who are part of the organization.

I'd like to suggest to either remove the link from the documentation or make the team visible to public.

----------
assignee: docs at python
components: Documentation
messages: 288131
nosy: CuriousLearner, docs at python, ncoghlan
priority: normal
severity: normal
status: open
title: Github organization link is secret and not accessible from core-dev guide
type: behavior

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

From report at bugs.python.org  Sun Feb 19 08:05:23 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Feb 2017 13:05:23 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487509523.43.0.832406655813.issue29520@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Feb 19 08:47:23 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Feb 2017 13:47:23 +0000
Subject: [docs] [issue29599] Github organization link is secret and not
 accessible from core-dev guide
In-Reply-To: <1487504256.78.0.675328219638.issue29599@psf.upfronthosting.co.za>
Message-ID: <1487512043.6.0.562222854802.issue29599@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report. I agree that the link can be removed. We have a separate issue tracker for devguide at https://github.com/python/devguide/issues Please report this there.

----------
nosy: +berker.peksag
resolution:  -> third party
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Feb 19 09:24:29 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 19 Feb 2017 14:24:29 +0000
Subject: [docs] [issue10701] Error pickling objects with mutating
 __getstate__
In-Reply-To: <1292338436.19.0.0995184249123.issue10701@psf.upfronthosting.co.za>
Message-ID: <1487514269.54.0.109813677115.issue10701@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
status: open -> pending
type: behavior -> enhancement
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3, Python 3.4

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

From report at bugs.python.org  Sun Feb 19 09:40:46 2017
From: report at bugs.python.org (Sanyam Khurana)
Date: Sun, 19 Feb 2017 14:40:46 +0000
Subject: [docs] [issue29599] Github organization link is secret and not
 accessible from core-dev guide
In-Reply-To: <1487504256.78.0.675328219638.issue29599@psf.upfronthosting.co.za>
Message-ID: <1487515246.86.0.160695351721.issue29599@psf.upfronthosting.co.za>


Sanyam Khurana added the comment:

Thanks a lot Berker! I've reported the issue there at https://github.com/python/devguide/issues/124

----------

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

From report at bugs.python.org  Sun Feb 19 10:04:06 2017
From: report at bugs.python.org (Harshul)
Date: Sun, 19 Feb 2017 15:04:06 +0000
Subject: [docs] [issue28886] Move deprecated abc module decorators to
 separate section in docs
In-Reply-To: <1481031817.69.0.735601842725.issue28886@psf.upfronthosting.co.za>
Message-ID: <1487516646.54.0.750374747565.issue28886@psf.upfronthosting.co.za>


Changes by Harshul <harshulrobo at gmail.com>:


----------
pull_requests: +141

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

From report at bugs.python.org  Sun Feb 19 10:07:10 2017
From: report at bugs.python.org (Harshul)
Date: Sun, 19 Feb 2017 15:07:10 +0000
Subject: [docs] [issue28886] Move deprecated abc module decorators to
 separate section in docs
In-Reply-To: <1481031817.69.0.735601842725.issue28886@psf.upfronthosting.co.za>
Message-ID: <1487516830.57.0.343893067877.issue28886@psf.upfronthosting.co.za>


Changes by Harshul <harshulrobo at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file46651/bpo-28886_3.7.patch

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

From report at bugs.python.org  Sun Feb 19 12:07:34 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 17:07:34 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487524054.67.0.671959786178.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:


New changeset 3eea8c67fa870c6e2b7a521d292afe7fe3e95f58 by GitHub in branch 'master':
bpo-29520: doc: fix deprecation warning from 'defindex' template (GH-165)
https://github.com/python/cpython/commit/3eea8c67fa870c6e2b7a521d292afe7fe3e95f58


----------

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

From report at bugs.python.org  Sun Feb 19 12:08:14 2017
From: report at bugs.python.org (Barry A. Warsaw)
Date: Sun, 19 Feb 2017 17:08:14 +0000
Subject: [docs] [issue29601] Need reST markup for enum types
Message-ID: <1487524094.89.0.393871634605.issue29601@psf.upfronthosting.co.za>


New submission from Barry A. Warsaw:

Over in https://github.com/python/cpython/pull/138 I noticed that we don't currently have markup for enum types.  While class:: is technically still correct, it's not helpful because the html documentation should render this as `Enum SafeUUID` not `class SafeUUID`.

----------
assignee: docs at python
components: Documentation
messages: 288147
nosy: barry, berker.peksag, docs at python
priority: normal
severity: normal
status: open
title: Need reST markup for enum types
versions: Python 3.7

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

From report at bugs.python.org  Sun Feb 19 12:11:41 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 17:11:41 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487524301.33.0.786305417241.issue29520@psf.upfronthosting.co.za>


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


----------
pull_requests: +145

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

From report at bugs.python.org  Sun Feb 19 12:12:47 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 17:12:47 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487524367.5.0.18727784743.issue29520@psf.upfronthosting.co.za>


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


----------
pull_requests: +146

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

From report at bugs.python.org  Sun Feb 19 12:13:51 2017
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 19 Feb 2017 17:13:51 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487524431.53.0.982028927938.issue29520@psf.upfronthosting.co.za>


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


----------
pull_requests: +147

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

From report at bugs.python.org  Sun Feb 19 13:27:08 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 19 Feb 2017 18:27:08 +0000
Subject: [docs] [issue14124] _pickle.c comment/documentation improvement
In-Reply-To: <1330203362.98.0.289163571674.issue14124@psf.upfronthosting.co.za>
Message-ID: <1487528828.72.0.300639034253.issue14124@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Using absolute line numbers in comments looks bad idea to me. This becomes outdated very fast. The code of _pickle.c was changed many times since writing the patch.

----------
nosy: +serhiy.storchaka
status: open -> pending

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

From report at bugs.python.org  Sun Feb 19 14:09:18 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 19 Feb 2017 19:09:18 +0000
Subject: [docs] [issue29580] "Built-in Functions" not being functions
In-Reply-To: <1487266370.66.0.0116645570203.issue29580@psf.upfronthosting.co.za>
Message-ID: <1487531358.49.0.806915454469.issue29580@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

See also issue11975.

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

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

From report at bugs.python.org  Sun Feb 19 14:14:07 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 19 Feb 2017 19:14:07 +0000
Subject: [docs] [issue9267] Update pickle opcode documentation in
 pickletools for 3.x
In-Reply-To: <1279217581.88.0.294098163632.issue9267@psf.upfronthosting.co.za>
Message-ID: <1487531647.73.0.625901336917.issue9267@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Feb 19 14:44:28 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 19 Feb 2017 19:44:28 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487533468.7.0.333072816838.issue29554@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


----------
pull_requests: +148

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

From report at bugs.python.org  Sun Feb 19 14:44:28 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 19 Feb 2017 19:44:28 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487533468.74.0.618585876532.issue29554@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


----------
pull_requests: +148, 149

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

From report at bugs.python.org  Sun Feb 19 14:44:28 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 19 Feb 2017 19:44:28 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487533468.79.0.685571323266.issue29554@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


----------
pull_requests: +148, 149, 150

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

From report at bugs.python.org  Sun Feb 19 19:03:23 2017
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Mon, 20 Feb 2017 00:03:23 +0000
Subject: [docs] [issue29601] Need reST markup for enum types
In-Reply-To: <1487524094.89.0.393871634605.issue29601@psf.upfronthosting.co.za>
Message-ID: <1487549003.14.0.473955302772.issue29601@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

Is there some special treatment you think should be given to specific enum values as well?

----------
nosy: +fdrake

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

From report at bugs.python.org  Sun Feb 19 19:13:44 2017
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 20 Feb 2017 00:13:44 +0000
Subject: [docs] [issue29601] Need reST markup for enum types
In-Reply-To: <1487549003.14.0.473955302772.issue29601@psf.upfronthosting.co.za>
Message-ID: <20170219191340.1ceeae89@subdivisions.wooz.org>


Barry A. Warsaw added the comment:

On Feb 20, 2017, at 12:03 AM, Fred L. Drake, Jr. wrote:

>Is there some special treatment you think should be given to specific enum
>values as well?

The only thing I thought about was optionally provide the enum item's value,
when that's useful.  Usually you shouldn't care what the item's value is, but
maybe sometimes you do, and in that case it would be nice if there was a way
to express that.

----------

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

From report at bugs.python.org  Sun Feb 19 19:20:01 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 00:20:01 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487550001.14.0.212870521783.issue29520@psf.upfronthosting.co.za>


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


----------
pull_requests: +151

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

From report at bugs.python.org  Sun Feb 19 19:45:58 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 00:45:58 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487551558.11.0.801892017773.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:


New changeset cf44d957ec177be62f5349ef88515190dcfccbd6 by GitHub in branch '2.7':
bpo-29520: doc: fix deprecation warning from 'defindex' template (GH-180)
https://github.com/python/cpython/commit/cf44d957ec177be62f5349ef88515190dcfccbd6


----------

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

From report at bugs.python.org  Sun Feb 19 19:46:26 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 00:46:26 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487551586.88.0.890519162359.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:


New changeset f0174c69b7b8bd27ee32d96e890d665da29472af by GitHub in branch '3.5':
bpo-29520: doc: fix deprecation warning from 'defindex' template (GH-179)
https://github.com/python/cpython/commit/f0174c69b7b8bd27ee32d96e890d665da29472af


----------

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

From report at bugs.python.org  Sun Feb 19 19:46:49 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 00:46:49 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487551609.21.0.034142894399.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:


New changeset 7970cd483346dfd7723da214fb27399ecc574095 by GitHub in branch '3.6':
bpo-29520: doc: fix deprecation warning from 'defindex' template (GH-178)
https://github.com/python/cpython/commit/7970cd483346dfd7723da214fb27399ecc574095


----------

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

From report at bugs.python.org  Sun Feb 19 20:22:31 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 01:22:31 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487553751.31.0.0619924564474.issue29520@psf.upfronthosting.co.za>


INADA Naoki added the comment:


New changeset e395c4dbe19115aaab315c2a113b172e9fef307a by GitHub in branch 'master':
bpo-29520: doc: add missing dot (GH-182)
https://github.com/python/cpython/commit/e395c4dbe19115aaab315c2a113b172e9fef307a


----------

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

From report at bugs.python.org  Mon Feb 20 04:27:10 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 20 Feb 2017 09:27:10 +0000
Subject: [docs] [issue29596] Unfinished sentense in howto/clinic.rst
In-Reply-To: <1487380332.64.0.682733186171.issue29596@psf.upfronthosting.co.za>
Message-ID: <1487582830.59.0.719090442156.issue29596@psf.upfronthosting.co.za>


Changes by Xiang Zhang <angwerzx at 126.com>:


----------
nosy: +larry
stage:  -> needs patch

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

From report at bugs.python.org  Mon Feb 20 05:20:37 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 10:20:37 +0000
Subject: [docs] [issue29520] Documentation uses deprecated "defindex.html"
 Sphinx template
In-Reply-To: <1486711786.11.0.823688079421.issue29520@psf.upfronthosting.co.za>
Message-ID: <1487586037.63.0.0616928245889.issue29520@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Feb 20 05:45:50 2017
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 20 Feb 2017 10:45:50 +0000
Subject: [docs] [issue23890] assertRaises increases reference counter
In-Reply-To: <1428518225.53.0.665360255509.issue23890@psf.upfronthosting.co.za>
Message-ID: <1487587550.4.0.204065510515.issue23890@psf.upfronthosting.co.za>


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


----------
pull_requests: +160

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

From report at bugs.python.org  Mon Feb 20 06:20:06 2017
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 20 Feb 2017 11:20:06 +0000
Subject: [docs] [issue28331] "CPython implementation detail:" removed when
 content translated
In-Reply-To: <1475328552.4.0.631332821236.issue28331@psf.upfronthosting.co.za>
Message-ID: <1487589606.74.0.34818703721.issue28331@psf.upfronthosting.co.za>


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


----------
pull_requests: +162

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

From lifelonglearningtutorials at gmail.com  Fri Feb 17 21:58:30 2017
From: lifelonglearningtutorials at gmail.com (Ryan Noonan)
Date: Fri, 17 Feb 2017 21:58:30 -0500
Subject: [docs] Slice Example in Documentation
Message-ID: <3C2DD87F-CB24-4ABA-8FAE-29D505D42C4B@gmail.com>

Hello,

In the Python documentation for slice the following definition is given:
slice - An object usually containing a portion of a sequence. A slice is created using the subscript notation, [] with colons between numbers when several are given, such as in variable_name[1:3:5]. The bracket (subscript) notation uses slice objects internally.

If variable_name[1:3:5] = [start:stop:step]

How can you step or stride by 5 through a smaller number (slice of 1:3)?

Maybe this is a documentation error. If not, I apologize. I could not make sense of it.

Thanks,

Ryan

Sent from my iPad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170217/6c163f96/attachment-0001.html>

From lifelonglearningtutorials at gmail.com  Fri Feb 17 22:28:54 2017
From: lifelonglearningtutorials at gmail.com (Ryan Noonan)
Date: Fri, 17 Feb 2017 22:28:54 -0500
Subject: [docs] Fwd: Slice Example in Documentation
References: <3C2DD87F-CB24-4ABA-8FAE-29D505D42C4B@gmail.com>
Message-ID: <22BE7A02-3EA0-40D3-BDCF-03365C54885F@gmail.com>

Hello again,

Regarding the feedback below, I think I figured out how the variable_name[1:3:5] slice example could work. Please ignore my previous email.

Thanks,

Ryan

Sent from my iPad

Begin forwarded message:

> From: Ryan Noonan <lifelonglearningtutorials at gmail.com>
> Date: February 17, 2017 at 9:58:30 PM EST
> To: docs at python.org
> Subject: Slice Example in Documentation
> 
> Hello,
> 
> In the Python documentation for slice the following definition is given:
> slice - An object usually containing a portion of a sequence. A slice is created using the subscript notation, [] with colons between numbers when several are given, such as in variable_name[1:3:5]. The bracket (subscript) notation uses slice objects internally.
> 
> If variable_name[1:3:5] = [start:stop:step]
> 
> How can you step or stride by 5 through a smaller number (slice of 1:3)?
> 
> Maybe this is a documentation error. If not, I apologize. I could not make sense of it.
> 
> Thanks,
> 
> Ryan
> 
> Sent from my iPad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170217/988bffa5/attachment.html>

From waqaraphoto at gmail.com  Fri Feb 17 00:39:57 2017
From: waqaraphoto at gmail.com (Waqar Ahmad)
Date: Fri, 17 Feb 2017 00:39:57 -0500
Subject: [docs] A rather Odd error..
Message-ID: <CABiJbvt_c3QibS=k5nwHGRJvLY97cFoC5_atL8eA_1mo14Vm-g@mail.gmail.com>

Hi folks at Python.org,

Thank you so much for looking at my screenshot here. I'm seeing this odd
error whenever I try to run my new program (Hitting F5) it just doesnt run
it and highlights the 3.*6.*0 in the error screen in red. Please see
screenshot attached.


Id' really appreciate some guidance on this. I googled and it looked like
Windows 10 doesnt like Python 3.6.0.. perhaps this could be the reason? Or
I may be a complete noob I just started programming 3 weeks ago!

Thanks so much

Cheers!

Waqar[image: Inline image 1]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170217/794e9ca2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 205273 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170217/794e9ca2/attachment-0001.png>

From report at bugs.python.org  Mon Feb 20 08:31:25 2017
From: report at bugs.python.org (Adrian Chan)
Date: Mon, 20 Feb 2017 13:31:25 +0000
Subject: [docs] [issue29586] Cannot run pip in fresh install of py 3.5.3
In-Reply-To: <1487328483.09.0.366256272135.issue29586@psf.upfronthosting.co.za>
Message-ID: <1487597484.99.0.448651639324.issue29586@psf.upfronthosting.co.za>


Adrian Chan added the comment:

Ah, I'd forgotten about that.  When I first tried to run python I got an error complaining about a missing api-ms-win-crt-runtime-l1-1.0.dll
I installed the necessary VC redistributable and it solved that problem.  So that's why I could successfully ensurepip later on.

I'm surprised the manual runtime installation was necessary.  Between windows updates and installers for other programs I should already have it installed.  Perhaps it got corrupted?  That's out of scope for this issue anyway.

----------

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

From b.dunphy.342 at gmail.com  Mon Feb 20 09:32:28 2017
From: b.dunphy.342 at gmail.com (Bryan Dunphy)
Date: Mon, 20 Feb 2017 08:32:28 -0600
Subject: [docs] Improvement suggestion for docs of "plistlib"
Message-ID: <CABF9D8E-978A-406C-A07B-255E40813258@gmail.com>

In the segment on the Data class, add a suggestion to use ?Latin-1? encoding if they need to store TRUE binary data (such as a picture or sound clip) since it has 256 characters that correspond directly to the 256 possible values of a byte. Meaning that if the string is written out to a file in BINARY mode it will EXACTLY recreate the original file.

From report at bugs.python.org  Mon Feb 20 20:42:29 2017
From: report at bugs.python.org (Davin Potts)
Date: Tue, 21 Feb 2017 01:42:29 +0000
Subject: [docs] [issue29575] doc 17.2.1: basic Pool example is too basic
In-Reply-To: <1487199560.37.0.441891248359.issue29575@psf.upfronthosting.co.za>
Message-ID: <1487641348.84.0.844683633239.issue29575@psf.upfronthosting.co.za>


Davin Potts added the comment:

When passing judgement on what is "too basic", the initial example should be so basic as to be immediately digestible by as many people as possible.

Some background:
All too many examples mislead newcomers into believing that the number of processes should (a) match the number of processor cores, or (b) match the number of inputs to be processed.  This example currently attempts to dispel both notions.  In practice, and this depends upon what specific code is to be performed in parallel, it is not uncommon to find that slightly over-scheduling the number of processes versus the number of available cores can achieve superior throughput and performance.  In other cases, slightly under-scheduling may provide a win.  To help subtly encourage the newcomer, this example uses 5 processes as opposed to something which might be mistaken for a common number of cores available on current multi-core processors.  Likewise, the number of distinct inputs to be processed deliberately does not match the number of processes nor a multiple of the number of processes.  This hopefully encourages the newcomer to not feel obligated to only accept inputs of a particular size or multiple.  Granted, optimizing for performance motivates tuning such things but this is the first example / first glance at what functionality is available.

Considering the suggested change:
* range(20) will likely produce more output than can be comfortably accommodated and easily read in the available browser window where most will see this
* the addition of execution time measurement is an interesting choice here given how computationally trivial the f(x) function is, which is perhaps what motivated the introduction of a time.sleep(1) inside that function; a ThreadPool would be more appropriate for a sleepy function such as this

Ultimately these changes complicate the example while potentially undermining its value.  An interesting improvement to this example might be to introduce a computationally taxing function which more clearly demonstrates the benefit of using a process Pool but still achieving the ideal of being immediately digestible and understood by the largest reading audience.  Some of the topics/variations in the proposed change might be better introduced and addressed later in the documentation rather than unnecessarily complicating the first example.

----------
resolution:  -> works for me
stage:  -> resolved
status: open -> closed
type:  -> enhancement

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

From report at bugs.python.org  Mon Feb 20 23:07:47 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 21 Feb 2017 04:07:47 +0000
Subject: [docs] [issue10701] Error pickling objects with mutating
 __getstate__
In-Reply-To: <1292338436.19.0.0995184249123.issue10701@psf.upfronthosting.co.za>
Message-ID: <1487650066.92.0.378928809158.issue10701@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I agree with Antoine that, "As the name suggests, __getstate__ should probably not mutate anything."

Unless a problematic non-mutating example can be found, I suggest this be closed.  For the most part, our rule has been that pure python code doesn't have to (and possibly cannot) defend itself against mid-stream mutation, while C code only has to defend itself to the point of avoiding a segfault.  

IMO, "RuntimeError: dictionary changed size during iteration" is an informative error message in this case.

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

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

From report at bugs.python.org  Tue Feb 21 00:26:36 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 05:26:36 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487654796.11.0.392004422848.issue29554@psf.upfronthosting.co.za>


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


----------
nosy: +berker.peksag
stage:  -> patch review
type:  -> behavior
versions: +Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Feb 21 00:30:02 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 05:30:02 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487655002.91.0.848386374193.issue29554@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 8fb1f6e039cbdeb333d83b7a62f0f37af4ce6e02 by Berker Peksag in branch 'master':
bpo-29554: Improve docs for pstat module and profile. (#88)
https://github.com/python/cpython/commit/8fb1f6e039cbdeb333d83b7a62f0f37af4ce6e02


----------

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

From report at bugs.python.org  Tue Feb 21 01:20:26 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 21 Feb 2017 06:20:26 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487658026.04.0.905643933315.issue29453@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 32e8f9bdfd4324f1aa4fbbdf1ed8536f2b00cabb by Mariatta in branch 'master':
bpo-29453: Remove reference to undefined dictionary ordering in Tutorial (GH-140)
https://github.com/python/cpython/commit/32e8f9bdfd4324f1aa4fbbdf1ed8536f2b00cabb


----------

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

From report at bugs.python.org  Tue Feb 21 01:25:03 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 21 Feb 2017 06:25:03 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487658303.43.0.588470402094.issue29453@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +177

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

From report at bugs.python.org  Tue Feb 21 01:33:05 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 06:33:05 +0000
Subject: [docs] [issue10938] Provide links to system specific strftime/ptime
 docs
In-Reply-To: <1295378779.48.0.643087757109.issue10938@psf.upfronthosting.co.za>
Message-ID: <1487658785.22.0.889316681571.issue10938@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I agree with Jim's review comment at https://github.com/python/cpython/pull/155#pullrequestreview-22646534

Those links will quickly get outdated and I'm sure that we will get reports like "this link doesn't work for my $PLATFORM $PLATFORM_VERSION".

I suggest to close this as 'rejected'.

----------
nosy: +berker.peksag
stage: needs patch -> patch review
versions: +Python 3.6, Python 3.7 -Python 3.4

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

From report at bugs.python.org  Tue Feb 21 02:18:36 2017
From: report at bugs.python.org (Joachim)
Date: Tue, 21 Feb 2017 07:18:36 +0000
Subject: [docs] [issue29575] your closing of issue29575
In-Reply-To: <1487641348.84.0.844683633239.issue29575@psf.upfronthosting.co.za>
Message-ID: <5a9b5aea-422e-db0e-2bfb-eaa4ab360358@fz-juelich.de>


Joachim added the comment:

Dear Davin,

since I am new to the Python bug tracker, I have to asked
a stupid question: are you the benevolent dictator of the
Python Standard Library?

Otherwise, how can it be that one and the same person in
one and the same intervention adds new arguments to the
debate, conclude that theses arguments are winning,
declares that the current state ?works for me?, and closes
the issue, thereby cutting short any further debate?

I have several other issues with the current Python
documentation, but if defenders of the status quo are
acting that boldly, I would only waste my time to raise
them.

With best regards, Joachim

----------
title: doc 17.2.1: basic Pool example is too basic -> your closing of issue29575

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

From report at bugs.python.org  Tue Feb 21 02:39:39 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 07:39:39 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487662779.08.0.977231186948.issue28814@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Feb 21 02:54:34 2017
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 21 Feb 2017 07:54:34 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487663674.12.0.763922595747.issue29165@psf.upfronthosting.co.za>


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


----------
pull_requests: +179

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

From report at bugs.python.org  Tue Feb 21 03:14:14 2017
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 21 Feb 2017 08:14:14 +0000
Subject: [docs] [issue29575] your closing of issue29575
In-Reply-To: <1487199560.37.0.441891248359.issue29575@psf.upfronthosting.co.za>
Message-ID: <1487664854.03.0.294028845685.issue29575@psf.upfronthosting.co.za>


INADA Naoki added the comment:

I like current, minimum example to describe API.

No need to make it complex only for checking it's really executed in parallel.

Adding more and more "may be useful for someone" code in the doc make the document long, hard and tedious to read for everyone.

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

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

From report at bugs.python.org  Tue Feb 21 04:04:53 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 09:04:53 +0000
Subject: [docs] [issue29575] doc 17.2.1: basic Pool example is too basic
In-Reply-To: <1487199560.37.0.441891248359.issue29575@psf.upfronthosting.co.za>
Message-ID: <1487667893.83.0.347164365226.issue29575@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I agree with and Davin and Inada. Note that multiprocessing documentation is already too long and we'd like to be careful before adding another example.

If you could create a "multiprocessing cookbook" on wiki.python.org I'm pretty sure we'd be happy to consider adding a link to it in the documentation.

----------
nosy: +berker.peksag
title: your closing of issue29575 -> doc 17.2.1: basic Pool example is too basic

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

From report at bugs.python.org  Tue Feb 21 04:11:39 2017
From: report at bugs.python.org (Joachim)
Date: Tue, 21 Feb 2017 09:11:39 +0000
Subject: [docs] [issue29575] doc 17.2.1: basic Pool example is too basic
In-Reply-To: <1487667893.83.0.347164365226.issue29575@psf.upfronthosting.co.za>
Message-ID: <7fc0c475-c8ca-0317-a043-0a1ced6620f1@fz-juelich.de>


Joachim added the comment:

I never proposed to add a second example, but to make the one example more meaningful.

As a minimal solution, could we replace the numbers 3 (input data) and 5 (threads)
by a slightly more plausible choice? Davin explained why numbers should be
incommensurate. So what about 10 data, 3 threads?

----------
Added file: http://bugs.python.org/file46657/smime.p7s

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29575>
_______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5110 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20170221/cee4d752/attachment-0001.bin>

From report at bugs.python.org  Tue Feb 21 04:50:10 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 21 Feb 2017 09:50:10 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487670610.42.0.607248116425.issue29165@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

PyVarObject_HEAD_INIT() is more used in Python 3 code, but the code with PyObject_HEAD_INIT() doesn't look incompatible with Python 3. I don't see a need of this change.

PyObject_HEAD_INIT() also is used in .c files in Doc/includes/.

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

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

From report at bugs.python.org  Tue Feb 21 04:59:25 2017
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 21 Feb 2017 09:59:25 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487671165.01.0.676776346187.issue29165@psf.upfronthosting.co.za>


INADA Naoki added the comment:

> but the code with PyObject_HEAD_INIT() doesn't look incompatible with Python 3.

It's incompatible actually.

https://github.com/python/cpython/blob/2.7/Include/object.h

/* PyObject_HEAD defines the initial segment of every PyObject. */

#define PyObject_HEAD_INIT(type)        \
    _PyObject_EXTRA_INIT                \
    1, type,


https://github.com/python/cpython/blob/3.5/Include/object.h

#define PyObject_HEAD_INIT(type)        \
    { _PyObject_EXTRA_INIT              \
    1, type },


I noticed PyVarObject_HEAD_INIT is compatible, and simplified an extension I maintain.
https://github.com/PyMySQL/mysqlclient-python/commit/2feb5ed6850a3905edf0333e0cd11ea6218f0f4f


This small doc change helps people who writing Python 2's extension module now, and port it to Python 3 later.

----------

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

From report at bugs.python.org  Tue Feb 21 05:32:32 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 21 Feb 2017 10:32:32 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487673152.54.0.892134199679.issue29165@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Ah, now I see.

I think sample C files in Doc/includes/ should be updated too. And it seems to me that Doc/includes/shoddy.c in Python 3 is not correct.

----------

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

From report at bugs.python.org  Tue Feb 21 07:12:05 2017
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 21 Feb 2017 12:12:05 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487679125.55.0.408410430249.issue29165@psf.upfronthosting.co.za>


INADA Naoki added the comment:


New changeset 9436bbd87b7eed18dec4c32f25b88452fe282e1c by GitHub in branch '2.7':
bpo-29165: doc: make extending/newtypes more Python 3 friendly (GH-211)
https://github.com/python/cpython/commit/9436bbd87b7eed18dec4c32f25b88452fe282e1c


----------

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

From report at bugs.python.org  Tue Feb 21 07:12:30 2017
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 21 Feb 2017 12:12:30 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487679150.06.0.138747930238.issue29165@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Feb 21 07:14:16 2017
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 21 Feb 2017 12:14:16 +0000
Subject: [docs] [issue29165] Use forward compatible macro in example code
 for creating new type
In-Reply-To: <1483598879.57.0.52341008423.issue29165@psf.upfronthosting.co.za>
Message-ID: <1487679256.94.0.708207339252.issue29165@psf.upfronthosting.co.za>


INADA Naoki added the comment:

> And it seems to me that Doc/includes/shoddy.c in Python 3 is not correct.

I created another pull request PR 215.

----------

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

From report at bugs.python.org  Tue Feb 21 08:36:11 2017
From: report at bugs.python.org (Matthieu Dartiailh)
Date: Tue, 21 Feb 2017 13:36:11 +0000
Subject: [docs] [issue28810] Document bytecode changes in 3.6
In-Reply-To: <1480184644.53.0.660721117392.issue28810@psf.upfronthosting.co.za>
Message-ID: <1487684171.04.0.52577177559.issue28810@psf.upfronthosting.co.za>


Matthieu Dartiailh added the comment:

Anyone to review this. Working on bytecode manipulation for different projects I wish I had known this existed before.

----------
nosy: +mdartiailh

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

From bgailer at gmail.com  Tue Feb 21 11:47:06 2017
From: bgailer at gmail.com (Bob Gailer)
Date: Tue, 21 Feb 2017 11:47:06 -0500
Subject: [docs] A rather Odd error..
In-Reply-To: <CAP1rxO52CPqGb1X5HSn0eM=j8sMpPtTtYLCRGN-n8dMr+qqaRA@mail.gmail.com>
References: <CABiJbvt_c3QibS=k5nwHGRJvLY97cFoC5_atL8eA_1mo14Vm-g@mail.gmail.com>
 <CAP1rxO7+uOYtTcjz+fBoRK5Hr8iXexDNnqZWVTvkqh7c3Tvpeg@mail.gmail.com>
 <CAP1rxO52CPqGb1X5HSn0eM=j8sMpPtTtYLCRGN-n8dMr+qqaRA@mail.gmail.com>
Message-ID: <CAP1rxO4urJCP8hM9QqQmUYWpaKwdc3xXTrht_uoq6t8O9cFaTw@mail.gmail.com>

On Feb 20, 2017 8:12 AM, "Waqar Ahmad" <waqaraphoto at gmail.com> wrote:
>
> Hi folks at Python.org,
>
> Thank you so much for looking at my screenshot here. I'm seeing this odd
error whenever I try to run my new program (Hitting F5) it just doesnt run
it and highlights the 3.6.0 in the error screen in red. Please see
screenshot attached.

I assume you are using idle. Your screenshot shows you are running in the
interactive prompt. F5 is used to run a program you write in an idle
editor. You can open an editor from the file menu, type in your program,
press F5. Hope this helps, come back with more questions thought
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170221/b35d93c4/attachment.html>

From report at bugs.python.org  Tue Feb 21 13:30:10 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 21 Feb 2017 18:30:10 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487701810.25.0.528842052416.issue29453@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 9b49133082ec23b67e84d2589e66d7810018e424 by GitHub in branch '3.6':
bpo-29453: Remove reference to undefined dictionary ordering in Tutorial (GH-140) (#208)
https://github.com/python/cpython/commit/9b49133082ec23b67e84d2589e66d7810018e424


----------

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

From report at bugs.python.org  Tue Feb 21 13:32:36 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 21 Feb 2017 18:32:36 +0000
Subject: [docs] [issue29453] Remove reference to undefined dictionary
 ordering in Tutorial
In-Reply-To: <1486307847.14.0.0393957719878.issue29453@psf.upfronthosting.co.za>
Message-ID: <1487701955.99.0.132116745115.issue29453@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks everyone. PR has been merged and backported to 3.6 :)
Closing this issue.

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

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

From report at bugs.python.org  Tue Feb 21 18:25:54 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 23:25:54 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487719554.67.0.833691794231.issue29554@psf.upfronthosting.co.za>


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


----------
pull_requests: +190

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

From report at bugs.python.org  Tue Feb 21 18:28:20 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 21 Feb 2017 23:28:20 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487719700.9.0.606453056741.issue29554@psf.upfronthosting.co.za>


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


----------
pull_requests: +191

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

From report at bugs.python.org  Tue Feb 21 20:55:06 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 01:55:06 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487728505.95.0.728793863305.issue29554@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 6336f0d156feec0f109a8d01da108cf96e3d9c60 by GitHub in branch '3.5':
bpo-29554: Improve docs for pstat module and profile. (#88) (#228)
https://github.com/python/cpython/commit/6336f0d156feec0f109a8d01da108cf96e3d9c60


----------

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

From report at bugs.python.org  Tue Feb 21 20:55:35 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 01:55:35 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487728535.42.0.235800363947.issue29554@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset b067a5eef7fdf69264d3578654996fc3755df4ea by GitHub in branch '3.6':
bpo-29554: Improve docs for pstat module and profile. (#88) (#227)
https://github.com/python/cpython/commit/b067a5eef7fdf69264d3578654996fc3755df4ea


----------

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

From report at bugs.python.org  Tue Feb 21 20:56:40 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 01:56:40 +0000
Subject: [docs] [issue29554] profile/pstat doc clariification
In-Reply-To: <1487088059.45.0.492029112528.issue29554@psf.upfronthosting.co.za>
Message-ID: <1487728600.15.0.469305683407.issue29554@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Feb 21 21:06:01 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 02:06:01 +0000
Subject: [docs] [issue16011] "in" should be consistent with return value of
 __contains__
In-Reply-To: <1348445631.47.0.961273834435.issue16011@psf.upfronthosting.co.za>
Message-ID: <1487729161.56.0.373995541107.issue16011@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Feb 22 00:29:18 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 22 Feb 2017 05:29:18 +0000
Subject: [docs] [issue10701] Error pickling objects with mutating
 __getstate__
In-Reply-To: <1292338436.19.0.0995184249123.issue10701@psf.upfronthosting.co.za>
Message-ID: <1487741358.16.0.228415388308.issue10701@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Feb 22 00:45:53 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 05:45:53 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487742353.69.0.367023440675.issue28814@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 0899b9809547ec2894dcf88cf4bba732c5d47d0d by Berker Peksag in branch 'master':
bpo-28814: Undeprecate inadvertently deprecated inspect functions. (#122)
https://github.com/python/cpython/commit/0899b9809547ec2894dcf88cf4bba732c5d47d0d


----------

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

From report at bugs.python.org  Wed Feb 22 03:35:00 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 22 Feb 2017 08:35:00 +0000
Subject: [docs] [issue10938] Provide links to system specific strftime/ptime
 docs
In-Reply-To: <1295378779.48.0.643087757109.issue10938@psf.upfronthosting.co.za>
Message-ID: <1487752500.46.0.567887380841.issue10938@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

I agree with Berker and Jim here. I think the current doc is clear enough so mark this as rejected. :-(

----------
nosy: +xiang.zhang
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

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

From levkivskyi at gmail.com  Wed Feb 22 03:56:13 2017
From: levkivskyi at gmail.com (levkivskyi at gmail.com)
Date: Wed, 22 Feb 2017 08:56:13 -0000
Subject: [docs] Document bytecode changes in 3.6 (issue 28810)
Message-ID: <20170222085613.3796.46135@psf.upfronthosting.co.za>

I have only one comment, otherwise the patch LGTM.


http://bugs.python.org/review/28810/diff/19372/Doc/library/dis.rst
File Doc/library/dis.rst (right):

http://bugs.python.org/review/28810/diff/19372/Doc/library/dis.rst#newcode980
Doc/library/dis.rst:980: pushes the return value.
I think it is not completely clear what happens with

f(*x, *y, **z, **w)

As I understand, there will be always at most one element on the stack
built with BUILD_MAP_UNPACK_WITH_CALL, and only one element built by
BUILD_TUPLE_UNPACK_WITH_CALL. The latter two are not documented yet. I
think it would make sense to also document them, and mention them here.

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

From storchaka+cpython at gmail.com  Wed Feb 22 04:04:36 2017
From: storchaka+cpython at gmail.com (storchaka+cpython at gmail.com)
Date: Wed, 22 Feb 2017 09:04:36 -0000
Subject: [docs] Document bytecode changes in 3.6 (issue 28810)
Message-ID: <20170222090436.3796.85436@psf.upfronthosting.co.za>

Reviewers: levkivskyi,


http://bugs.python.org/review/28810/diff/19372/Doc/library/dis.rst
File Doc/library/dis.rst (right):

http://bugs.python.org/review/28810/diff/19372/Doc/library/dis.rst#newcode980
Doc/library/dis.rst:980: pushes the return value.
On 2017/02/22 09:56:13, levkivskyi wrote:
> I think it is not completely clear what happens with
> 
> f(*x, *y, **z, **w)
> 
> As I understand, there will be always at most one element on the stack
built
> with BUILD_MAP_UNPACK_WITH_CALL, and only one element built by
> BUILD_TUPLE_UNPACK_WITH_CALL. The latter two are not documented yet. I
think it
> would make sense to also document them, and mention them here.

You understand it correctly. There is separate issue26213 for
documenting bytecode changes in 3.5.



Please review this at http://bugs.python.org/review/28810/

Affected files:
  Doc/library/dis.rst


diff -r 5904d2ced3d8 Doc/library/dis.rst
--- a/Doc/library/dis.rst	Tue Dec 06 19:25:19 2016 +0200
+++ b/Doc/library/dis.rst	Wed Dec 07 01:28:00 2016 +0200
@@ -947,14 +947,39 @@ All of the following opcodes use their a
 
 .. opcode:: CALL_FUNCTION (argc)
 
-   Calls a function.  The low byte of *argc* indicates the number of positional
-   parameters, the high byte the number of keyword parameters. On the stack, the
-   opcode finds the keyword parameters first.  For each keyword argument, the
-   value is on top of the key.  Below the keyword parameters, the positional
-   parameters are on the stack, with the right-most parameter on top.  Below the
-   parameters, the function object to call is on the stack.  Pops all function
-   arguments, and the function itself off the stack, and pushes the return
-   value.
+   Calls a function.  *argc* indicates the number of positional arguments.
+   The positional arguments are on the stack, with the right-most argument
+   on top.  Below the arguments, the function object to call is on the stack.
+   Pops all function arguments, and the function itself off the stack, and
+   pushes the return value.
+
+   .. versionchanged:: 3.6
+
+
+.. opcode:: CALL_FUNCTION_KW (argc)
+
+   Calls a function.  *argc* indicates the number of arguments (positional
+   and keyword).  The top element on the stack contains a tuple of keyword
+   argument names.  Below the tuple, keyword arguments are on the stack, in
+   the order corresponding to the tuple.  Below the keyword arguments, the
+   positional arguments are on the stack, with the right-most parameter on
+   top.  Below the arguments, the function object to call is on the stack.
+   Pops all function arguments, and the function itself off the stack, and
+   pushes the return value.
+
+   .. versionchanged:: 3.6
+
+
+.. opcode:: CALL_FUNCTION_EX (flags)
+
+   Calls a function. The lowest bit of *flags* indicates whether the
+   var-keyword argument is placed at the top of the stack.  Below the
+   var-keyword argument, the var-positional argument is on the stack.
+   Below the arguments, the function object to call is on the stack.
+   Pops all function arguments, and the function itself off the stack, and
+   pushes the return value.
+
+   .. versionadded:: 3.6
 
 
 .. opcode:: MAKE_FUNCTION (argc)
@@ -987,28 +1012,6 @@ All of the following opcodes use their a
    two most-significant bytes.
 
 
-.. opcode:: CALL_FUNCTION_VAR (argc)
-
-   Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The
-   top element on the stack contains the variable argument list, followed by
-   keyword and positional arguments.
-
-
-.. opcode:: CALL_FUNCTION_KW (argc)
-
-   Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The
-   top element on the stack contains the keyword arguments dictionary, followed
-   by explicit keyword and positional arguments.
-
-
-.. opcode:: CALL_FUNCTION_VAR_KW (argc)
-
-   Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`.  The
-   top element on the stack contains the keyword arguments dictionary, followed
-   by the variable-arguments tuple, followed by explicit keyword and positional
-   arguments.
-
-
 .. opcode:: FORMAT_VALUE (flags)
 
    Used for implementing formatted literal strings (f-strings).  Pops



From report at bugs.python.org  Wed Feb 22 04:14:17 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 22 Feb 2017 09:14:17 +0000
Subject: [docs] [issue26213] Document BUILD_*_UNPACK opcodes
In-Reply-To: <1453851645.07.0.698993321818.issue26213@psf.upfronthosting.co.za>
Message-ID: <1487754857.69.0.507236344933.issue26213@psf.upfronthosting.co.za>


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


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

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

From levkivskyi at gmail.com  Wed Feb 22 05:50:41 2017
From: levkivskyi at gmail.com (levkivskyi at gmail.com)
Date: Wed, 22 Feb 2017 10:50:41 -0000
Subject: [docs] Document bytecode changes in 3.6 (issue 28810)
Message-ID: <20170222105041.12002.44470@psf.upfronthosting.co.za>

On 2017/02/22 10:04:36, storchaka wrote:
> http://bugs.python.org/review/28810/diff/19372/Doc/library/dis.rst
> File Doc/library/dis.rst (right):
> 
>
http://bugs.python.org/review/28810/diff/19372/Doc/library/dis.rst#newcode980
> Doc/library/dis.rst:980: pushes the return value.
> On 2017/02/22 09:56:13, levkivskyi wrote:
> > I think it is not completely clear what happens with
> > 
> > f(*x, *y, **z, **w)
> > 
> > As I understand, there will be always at most one element on the
stack built
> > with BUILD_MAP_UNPACK_WITH_CALL, and only one element built by
> > BUILD_TUPLE_UNPACK_WITH_CALL. The latter two are not documented yet.
I think
> it
> > would make sense to also document them, and mention them here.
> 
> You understand it correctly. There is separate issue26213 for
documenting
> bytecode changes in 3.5.

The situation is a bit more complex, according to
_bootstrap_external.py, BUILD_MAP_UNPACK_WITH_CALL was added in 3.5, but
BUILD_TUPLE_UNPACK_WITH_CALL was added in 3.6, also semantics of some
bytecodes has changed (e.g. BUILD_MAP), I will therefore make two
separate PRs (one then should be backported to 3.6, another to 3.5 and
3.6). I will reference issue #26213 in the PRs

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

From report at bugs.python.org  Wed Feb 22 07:48:44 2017
From: report at bugs.python.org (Arne de Laat)
Date: Wed, 22 Feb 2017 12:48:44 +0000
Subject: [docs] [issue28911] Clarify the behaviour of assert_called_once_with
In-Reply-To: <1481233700.68.0.637550951007.issue28911@psf.upfronthosting.co.za>
Message-ID: <1487767724.1.0.772948992008.issue28911@psf.upfronthosting.co.za>


Arne de Laat added the comment:

*ping*
Is this patch acceptable as is?

Perhaps a new issue can be made for a method to check at most one call with a specific signature i.e. `assert_one_call_with`.

----------

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

From sweavo at gmail.com  Tue Feb 21 11:10:36 2017
From: sweavo at gmail.com (Steve Carter)
Date: Tue, 21 Feb 2017 16:10:36 +0000
Subject: [docs] Argparse doc contribution
Message-ID: <CABTxiB1yFdN=PO=JMyqgb_u1tRx9X92EyOPdmUpAQykycsj7Xw@mail.gmail.com>

Hi all,

How would I go about submitting a rewrite to the argparse reference page?

I use argparse a lot (python 2.7) and find myself at the reference page
often, but it opens with an example that is far from a typical argument
parsing application.

It should open with reference material and illustrate the reference
material with realistic examples.

Would such a contribution be welcome? How should I start?

Thanks


Steve Carter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170221/a55a7cbd/attachment.html>

From report at bugs.python.org  Wed Feb 22 08:32:54 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 22 Feb 2017 13:32:54 +0000
Subject: [docs] [issue26213] Document BUILD_*_UNPACK opcodes
In-Reply-To: <1453851645.07.0.698993321818.issue26213@psf.upfronthosting.co.za>
Message-ID: <1487770374.12.0.0456572508695.issue26213@psf.upfronthosting.co.za>


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


----------
pull_requests: +200

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

From report at bugs.python.org  Wed Feb 22 09:15:21 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 22 Feb 2017 14:15:21 +0000
Subject: [docs] [issue28810] Document bytecode changes in 3.6
In-Reply-To: <1480184644.53.0.660721117392.issue28810@psf.upfronthosting.co.za>
Message-ID: <1487772921.25.0.379332439243.issue28810@psf.upfronthosting.co.za>


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


----------
pull_requests: +201

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

From report at bugs.python.org  Wed Feb 22 09:23:29 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 22 Feb 2017 14:23:29 +0000
Subject: [docs] [issue28810] Document bytecode changes in 3.6
In-Reply-To: <1480184644.53.0.660721117392.issue28810@psf.upfronthosting.co.za>
Message-ID: <1487773409.13.0.929990563707.issue28810@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for your patches Ivan. Feel free to rewrite my patch, I'm sure it uses poor English.

----------
dependencies: +Document BUILD_*_UNPACK opcodes

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

From report at bugs.python.org  Wed Feb 22 10:21:42 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 22 Feb 2017 15:21:42 +0000
Subject: [docs] [issue28911] Clarify the behaviour of assert_called_once_with
In-Reply-To: <1487767724.1.0.772948992008.issue28911@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwZS7vw8pdWyefupXvTf01faeBHtdO2Bwy8YKgui8gz26w@mail.gmail.com>


STINNER Victor added the comment:

Can you please try to write a pull request?
https://docs.python.org/devguide/pullrequest.html

----------

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

From report at bugs.python.org  Wed Feb 22 16:34:27 2017
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 22 Feb 2017 21:34:27 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1487799267.5.0.101823449187.issue22594@psf.upfronthosting.co.za>


Changes by Marco Buttu <marco.buttu at gmail.com>:


----------
pull_requests: +204

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

From report at bugs.python.org  Wed Feb 22 17:08:02 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 22:08:02 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487801282.58.0.418379731584.issue28814@psf.upfronthosting.co.za>


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


----------
pull_requests: +206

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

From report at bugs.python.org  Wed Feb 22 17:10:11 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 22:10:11 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487801411.71.0.380284783859.issue28814@psf.upfronthosting.co.za>


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


----------
pull_requests: +208

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

From report at bugs.python.org  Wed Feb 22 17:56:53 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 22 Feb 2017 22:56:53 +0000
Subject: [docs] [issue29098] document minimum sqlite version
In-Reply-To: <1482962930.74.0.760741820297.issue29098@psf.upfronthosting.co.za>
Message-ID: <1487804213.22.0.773062908683.issue29098@psf.upfronthosting.co.za>


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


----------
dependencies: +sqlite3: remove sqlite3_stmt_readonly()
type:  -> enhancement
versions: +Python 3.7

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

From report at bugs.python.org  Wed Feb 22 18:07:11 2017
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 22 Feb 2017 23:07:11 +0000
Subject: [docs] [issue15657] Error in Python 3 docs for PyMethodDef
In-Reply-To: <1344970966.7.0.115664419243.issue15657@psf.upfronthosting.co.za>
Message-ID: <1487804831.37.0.101043529198.issue15657@psf.upfronthosting.co.za>


Barry A. Warsaw added the comment:

I think this bug has been fixed.

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

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

From report at bugs.python.org  Thu Feb 23 02:57:44 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 23 Feb 2017 07:57:44 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1487836664.1.0.858190514361.issue22594@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Thu Feb 23 03:18:33 2017
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 23 Feb 2017 08:18:33 +0000
Subject: [docs] [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1487837913.2.0.875072140438.issue16575@psf.upfronthosting.co.za>


Changes by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


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

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

From report at bugs.python.org  Thu Feb 23 08:05:43 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Thu, 23 Feb 2017 13:05:43 +0000
Subject: [docs] [issue28810] Document bytecode changes in 3.6
In-Reply-To: <1480184644.53.0.660721117392.issue28810@psf.upfronthosting.co.za>
Message-ID: <1487855143.74.0.420340696525.issue28810@psf.upfronthosting.co.za>


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


----------
pull_requests: +217

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

From report at bugs.python.org  Thu Feb 23 08:42:44 2017
From: report at bugs.python.org (Arne de Laat)
Date: Thu, 23 Feb 2017 13:42:44 +0000
Subject: [docs] [issue28911] Clarify the behaviour of assert_called_once_with
In-Reply-To: <1481233700.68.0.637550951007.issue28911@psf.upfronthosting.co.za>
Message-ID: <1487857364.29.0.0566469884667.issue28911@psf.upfronthosting.co.za>


Changes by Arne de Laat <adelaat at leukeleu.nl>:


----------
pull_requests: +219

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

From report at bugs.python.org  Thu Feb 23 09:41:58 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Feb 2017 14:41:58 +0000
Subject: [docs] [issue18423] Document limitations on -m
In-Reply-To: <1373461112.24.0.280779659137.issue18423@psf.upfronthosting.co.za>
Message-ID: <1487860918.05.0.937444115896.issue18423@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

The limitation noted in #18422 was specific to 3.3, as the missing API was added to NamespaceLoader in 3.4.

So the current documentation is accurate for recent versions of Python.

----------
nosy: +ncoghlan
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed
versions: +Python 3.3 -Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Feb 23 10:12:14 2017
From: report at bugs.python.org (Arne de Laat)
Date: Thu, 23 Feb 2017 15:12:14 +0000
Subject: [docs] [issue28911] Clarify the behaviour of assert_called_once_with
In-Reply-To: <1481233700.68.0.637550951007.issue28911@psf.upfronthosting.co.za>
Message-ID: <1487862734.86.0.533926247719.issue28911@psf.upfronthosting.co.za>


Changes by Arne de Laat <adelaat at leukeleu.nl>:


----------
pull_requests: +220

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

From report at bugs.python.org  Thu Feb 23 10:15:29 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Feb 2017 15:15:29 +0000
Subject: [docs] [issue23890] assertRaises increases reference counter
In-Reply-To: <1428518225.53.0.665360255509.issue23890@psf.upfronthosting.co.za>
Message-ID: <1487862929.73.0.202001949078.issue23890@psf.upfronthosting.co.za>


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


----------
stage: needs patch -> commit review

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

From report at bugs.python.org  Thu Feb 23 10:20:20 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Feb 2017 15:20:20 +0000
Subject: [docs] [issue23890] assertRaises increases reference counter
In-Reply-To: <1428518225.53.0.665360255509.issue23890@psf.upfronthosting.co.za>
Message-ID: <1487863220.21.0.541421501523.issue23890@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Victor's PR takes a more pragmatic approach to address this problem: rather than adding the ability to clear the frames for an arbitrary exception tree, it just uses a try/finally in a couple of key unittest function definitions to clear the offending circular references by setting them to None.

----------

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

From report at bugs.python.org  Thu Feb 23 10:44:32 2017
From: report at bugs.python.org (Arne de Laat)
Date: Thu, 23 Feb 2017 15:44:32 +0000
Subject: [docs] [issue28911] Clarify the behaviour of assert_called_once_with
In-Reply-To: <1481233700.68.0.637550951007.issue28911@psf.upfronthosting.co.za>
Message-ID: <1487864672.27.0.787208115363.issue28911@psf.upfronthosting.co.za>


Changes by Arne de Laat <adelaat at leukeleu.nl>:


----------
pull_requests: +222

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

From report at bugs.python.org  Thu Feb 23 10:46:55 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 23 Feb 2017 15:46:55 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487864815.86.0.809682515028.issue28814@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Thanks mbusson, berker.peksag!

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

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

From report at bugs.python.org  Thu Feb 23 12:09:07 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Thu, 23 Feb 2017 17:09:07 +0000
Subject: [docs] [issue28814] Deprecation notice on inspect.getargvalues() is
 incorrect
In-Reply-To: <1480252052.94.0.16018093739.issue28814@psf.upfronthosting.co.za>
Message-ID: <1487869747.93.0.300823781377.issue28814@psf.upfronthosting.co.za>


Matthias Bussonnier added the comment:

Thanks Nick for finding this !

----------

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

From report at bugs.python.org  Thu Feb 23 13:22:57 2017
From: report at bugs.python.org (Garvit)
Date: Thu, 23 Feb 2017 18:22:57 +0000
Subject: [docs] [issue24024] str.__doc__ needs an update
In-Reply-To: <1429708426.75.0.208318155296.issue24024@psf.upfronthosting.co.za>
Message-ID: <1487874177.28.0.0621141584091.issue24024@psf.upfronthosting.co.za>


Changes by Garvit <garvitdelhi at gmail.com>:


----------
pull_requests: +227

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

From report at bugs.python.org  Thu Feb 23 14:29:23 2017
From: report at bugs.python.org (Garvit Khatri)
Date: Thu, 23 Feb 2017 19:29:23 +0000
Subject: [docs] [issue10379] locale.format() input regression
In-Reply-To: <1289345606.99.0.972407204822.issue10379@psf.upfronthosting.co.za>
Message-ID: <1487878163.53.0.539343355269.issue10379@psf.upfronthosting.co.za>


Changes by Garvit Khatri <garvitdelhi at gmail.com>:


----------
pull_requests: +229

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

From report at bugs.python.org  Thu Feb 23 16:06:00 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 23 Feb 2017 21:06:00 +0000
Subject: [docs] [issue29455] Mention coverage.py in trace module
 documentation
In-Reply-To: <1486352347.76.0.0578982981399.issue29455@psf.upfronthosting.co.za>
Message-ID: <1487883960.17.0.671476485601.issue29455@psf.upfronthosting.co.za>


Changes by Marco Buttu <marco.buttu at gmail.com>:


----------
pull_requests: +233

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

From report at bugs.python.org  Thu Feb 23 16:10:58 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 23 Feb 2017 21:10:58 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1487884258.1.0.224134100907.issue29414@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Hello Jim, do you have the time to make a pull request? Let me know, otherwise I will do it

----------

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

From report at bugs.python.org  Thu Feb 23 16:32:14 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 23 Feb 2017 21:32:14 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
 interactive shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1487885534.78.0.884042962771.issue16355@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Hello Vajrasky, the doc patch LGTM. Looking at the David's comment in Rietveld, it seems that he does not want the test patch to be applyed. Can you please make a pull request? Thank you very much

----------

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

From report at bugs.python.org  Fri Feb 24 02:07:11 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 24 Feb 2017 07:07:11 +0000
Subject: [docs] [issue26184] Add versionchanged note for error when
 create_module() is not defined by loaders
In-Reply-To: <1453501860.77.0.669534801782.issue26184@psf.upfronthosting.co.za>
Message-ID: <1487920031.54.0.0889003621671.issue26184@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

That should actually be a versionchanged note now - converting this to an easy documentation issue to cover that change.

----------
assignee:  -> docs at python
components: +Documentation -Interpreter Core
keywords: +easy
nosy: +docs at python
stage: test needed -> needs patch
title: raise an error when create_module() is not defined by exec_module() is for loaders -> Add versionchanged note for error when create_module() is not defined by loaders
versions: +Python 3.7

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

From report at bugs.python.org  Fri Feb 24 04:35:02 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Fri, 24 Feb 2017 09:35:02 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1487928902.89.0.103373458463.issue29414@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Go ahead with making the PR, marco. I'll take a look at it too when you do.

----------

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

From john at doubledog.org  Fri Feb 24 09:35:11 2017
From: john at doubledog.org (John Florian)
Date: Fri, 24 Feb 2017 09:35:11 -0500
Subject: [docs] Suggestion for improvement of NamedTemporaryFile
Message-ID: <1487946911.2177.2.camel@doubledog.org>

Please see http://bugs.python.org/issue14243#msg288473 and the few
subsequent responses.  In short, I think it would be helpful to mention
that calling flush() is suggested if an external process is going to
access the content.  Maybe that's true for other threads under the same
Python process too; I'm not in a position to know however.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170224/e8e2d6ef/attachment.html>

From report at bugs.python.org  Fri Feb 24 11:08:00 2017
From: report at bugs.python.org (Marco Buttu)
Date: Fri, 24 Feb 2017 16:08:00 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1487952480.85.0.683132466536.issue29414@psf.upfronthosting.co.za>


Changes by Marco Buttu <marco.buttu at gmail.com>:


----------
pull_requests: +245

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

From report at bugs.python.org  Fri Feb 24 15:08:29 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 24 Feb 2017 20:08:29 +0000
Subject: [docs] [issue26184] Add versionchanged note for error when
 create_module() is not defined by loaders
In-Reply-To: <1453501860.77.0.669534801782.issue26184@psf.upfronthosting.co.za>
Message-ID: <1487966909.05.0.67622733566.issue26184@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +247

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

From report at bugs.python.org  Fri Feb 24 15:33:42 2017
From: report at bugs.python.org (Steven Rumbalski)
Date: Fri, 24 Feb 2017 20:33:42 +0000
Subject: [docs] [issue29596] Unfinished sentense in howto/clinic.rst
In-Reply-To: <1487380332.64.0.682733186171.issue29596@psf.upfronthosting.co.za>
Message-ID: <1487968422.29.0.767960923105.issue29596@psf.upfronthosting.co.za>


Steven Rumbalski added the comment:

Truncated sentence was always truncated.

Introduced on commit bebf73511a1250fc768bcb7192b5b3c3fd04d8f2
from Issue #20287: Argument Clinic's output is now configurable, allowing
delaying its output or even redirecting it to a separate file.
https://github.com/python/cpython/commit/bebf73511a1250fc768bcb7192b5b3c3fd04d8f2

Another issue from the same commit that still exists today:

buffer
    Save up all most of the output from Clinic, to be written into your file near the end.
            ^^^^^^^^

Perhaps what was meant was 'almost all'?

----------
nosy: +Steven Rumbalski

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

From report at bugs.python.org  Fri Feb 24 22:38:46 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Feb 2017 03:38:46 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1487993926.0.0.849104266082.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +254

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

From report at bugs.python.org  Fri Feb 24 22:42:27 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Feb 2017 03:42:27 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1487994147.45.0.205601335389.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +255

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

From report at bugs.python.org  Fri Feb 24 22:46:16 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Feb 2017 03:46:16 +0000
Subject: [docs] [issue28929] Provide a link from documentation back to its
 source file
In-Reply-To: <1481331536.86.0.539237207001.issue28929@psf.upfronthosting.co.za>
Message-ID: <1487994376.18.0.74579882078.issue28929@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +256

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

From report at bugs.python.org  Sat Feb 25 11:58:35 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Feb 2017 16:58:35 +0000
Subject: [docs] [issue29648] Missed reference to create_module() in
 versionadded (import.rst)
In-Reply-To: <1488021728.97.0.531293750465.issue29648@psf.upfronthosting.co.za>
Message-ID: <1488041914.94.0.446547033419.issue29648@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks, Marco. Your change looks good to me.
I'm now wondering if this should have been 'versionchanged' instead of 'versionadded'. Perhaps other core devs can confirm this.

Thanks :)

----------
assignee:  -> docs at python
components: +Documentation
nosy: +Mariatta, docs at python
stage:  -> patch review

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

From report at bugs.python.org  Sat Feb 25 14:45:27 2017
From: report at bugs.python.org (Vasiliy Faronov)
Date: Sat, 25 Feb 2017 19:45:27 +0000
Subject: [docs] [issue29651] Inconsistent/undocumented urlsplit/urlparse
 behavior on invalid inputs
Message-ID: <1488051927.22.0.367579438822.issue29651@psf.upfronthosting.co.za>


New submission from Vasiliy Faronov:

There is a problem with the standard library's urlsplit and urlparse functions, in Python 2.7 (module urlparse) and 3.2+ (module urllib.parse).

The documentation for these functions [1] does not explain how they behave when given an invalid URL.

One could try invoking them manually and conclude that they tolerate anything thrown at them:

>>> urlparse('http:////::\\\\!!::!!++///')
ParseResult(scheme='http', netloc='', path='//::\\\\!!::!!++///',
params='', query='', fragment='')

>>> urlparse(os.urandom(32).decode('latin-1'))
ParseResult(scheme='', netloc='', path='\x7f??1gd??6\x82', params='',
query='', fragment='\n\xadJ\x18+fli\x9c?\x9ak*??\x02?F\x85?\x18')

Without studying the source code, it is impossible to know that there is a very narrow class of inputs on which they raise ValueError [2]:

>>> urlparse('http://[')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.5/urllib/parse.py", line 295, in urlparse
    splitresult = urlsplit(url, scheme, allow_fragments)
  File "/usr/lib/python3.5/urllib/parse.py", line 345, in urlsplit
    raise ValueError("Invalid IPv6 URL")
ValueError: Invalid IPv6 URL

This could be viewed as a documentation issue. But it could also be viewed as an implementation issue. Instead of raising ValueError on those square brackets, urlsplit could simply consider them *invalid* parts of an RFC 3986 reg-name, and lump them into netloc, as it already does with other *invalid* characters:

>>> urlparse('http://\0\0??\n/')
ParseResult(scheme='http', netloc='\x00\x00??\n', path='/', params='',
query='', fragment='')

Note that the raising behavior was introduced in Python 2.7/3.2.

See also issue 8721 [3].


[1] https://docs.python.org/3/library/urllib.parse.html
[2] https://github.com/python/cpython/blob/e32ec93/Lib/urllib/parse.py#L406-L408
[3] http://bugs.python.org/issue8721

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 288577
nosy: docs at python, vfaronov
priority: normal
severity: normal
status: open
title: Inconsistent/undocumented urlsplit/urlparse behavior on invalid inputs
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Sat Feb 25 16:38:15 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Feb 2017 21:38:15 +0000
Subject: [docs] [issue28587] list.index documentation missing start and stop
 arguments
In-Reply-To: <1478079143.84.0.85838744414.issue28587@psf.upfronthosting.co.za>
Message-ID: <1488058695.17.0.712142789742.issue28587@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +266

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

From report at bugs.python.org  Sat Feb 25 16:40:24 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Feb 2017 21:40:24 +0000
Subject: [docs] [issue28587] list.index documentation missing start and stop
 arguments
In-Reply-To: <1478079143.84.0.85838744414.issue28587@psf.upfronthosting.co.za>
Message-ID: <1488058823.89.0.642674981868.issue28587@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

I backported these changes to 3.5 branch.
Please let me know if this is ok.

Thanks.

----------
versions: +Python 3.5

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

From report at bugs.python.org  Sun Feb 26 02:31:42 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 26 Feb 2017 07:31:42 +0000
Subject: [docs] [issue29648] Missed reference to create_module() in
 versionadded (import.rst)
In-Reply-To: <1488021728.97.0.531293750465.issue29648@psf.upfronthosting.co.za>
Message-ID: <1488094302.11.0.454786574597.issue29648@psf.upfronthosting.co.za>


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


----------
nosy: +brett.cannon, eric.snow, ncoghlan

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

From report at bugs.python.org  Sun Feb 26 09:20:42 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 26 Feb 2017 14:20:42 +0000
Subject: [docs] [issue29648] Missed reference to create_module() in
 versionadded (import.rst)
In-Reply-To: <1488021728.97.0.531293750465.issue29648@psf.upfronthosting.co.za>
Message-ID: <1488118842.0.0.542644073216.issue29648@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Version added is correct here, as the "create_module()" methods are all new in 3.4, and the traditional granularity for deciding "addition or change?" is that new functions, methods, and attributes are always additions, even if they're being added to a class definition.

----------

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

From report at bugs.python.org  Sun Feb 26 10:23:46 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:23:46 +0000
Subject: [docs] [issue29648] Missed reference to create_module() in
 versionadded (import.rst)
In-Reply-To: <1488021728.97.0.531293750465.issue29648@psf.upfronthosting.co.za>
Message-ID: <1488122626.65.0.135188341393.issue29648@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +275

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

From report at bugs.python.org  Sun Feb 26 10:24:33 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:24:33 +0000
Subject: [docs] [issue29648] Missed reference to create_module() in
 versionadded (import.rst)
In-Reply-To: <1488021728.97.0.531293750465.issue29648@psf.upfronthosting.co.za>
Message-ID: <1488122673.98.0.0573358687172.issue29648@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +276

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

From report at bugs.python.org  Sun Feb 26 10:29:33 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:29:33 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1488122973.82.0.447321283472.issue22594@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +277

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

From report at bugs.python.org  Sun Feb 26 10:30:05 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:30:05 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1488123005.26.0.00446560705251.issue22594@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +278

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

From report at bugs.python.org  Sun Feb 26 10:38:53 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:38:53 +0000
Subject: [docs] [issue26184] Add versionchanged note for error when
 create_module() is not defined by loaders
In-Reply-To: <1453501860.77.0.669534801782.issue26184@psf.upfronthosting.co.za>
Message-ID: <1488123533.35.0.077143747652.issue26184@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +281

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

From report at bugs.python.org  Sun Feb 26 10:41:55 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:41:55 +0000
Subject: [docs] [issue29648] Missed reference to create_module() in
 versionadded (import.rst)
In-Reply-To: <1488021728.97.0.531293750465.issue29648@psf.upfronthosting.co.za>
Message-ID: <1488123715.7.0.315043037991.issue29648@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks for the clarification, Nick :)

Marco, I merged your PR, and backported to 3.5 and 3.6 branches.
Thanks!

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

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

From report at bugs.python.org  Sun Feb 26 10:48:23 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 15:48:23 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1488124103.7.0.600795162604.issue22594@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +282

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

From report at bugs.python.org  Sun Feb 26 11:04:49 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 26 Feb 2017 16:04:49 +0000
Subject: [docs] [issue29121] sqlite3 Controlling Transactions documentation
 not updated
In-Reply-To: <1483200295.1.0.801871810477.issue29121@psf.upfronthosting.co.za>
Message-ID: <1488125088.9.0.774875668346.issue29121@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the patch, Aviv!

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type:  -> behavior

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

From report at bugs.python.org  Sun Feb 26 11:14:07 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 26 Feb 2017 16:14:07 +0000
Subject: [docs] [issue29098] document minimum sqlite version
In-Reply-To: <1482962930.74.0.760741820297.issue29098@psf.upfronthosting.co.za>
Message-ID: <1488125647.0.0.577359976176.issue29098@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report, Carl! The patch for issue 28518 has been lifted the requirement for sqlite3_stmt_readonly() so you can now use and compile Python 3.6.1 without a warning at compile time.

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

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

From report at bugs.python.org  Sun Feb 26 16:08:47 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 21:08:47 +0000
Subject: [docs] [issue26184] Add versionchanged note for error when
 create_module() is not defined by loaders
In-Reply-To: <1453501860.77.0.669534801782.issue26184@psf.upfronthosting.co.za>
Message-ID: <1488143327.2.0.554474139817.issue26184@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +285

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

From report at bugs.python.org  Sun Feb 26 16:25:59 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 21:25:59 +0000
Subject: [docs] [issue26184] Add versionchanged note for error when
 create_module() is not defined by loaders
In-Reply-To: <1453501860.77.0.669534801782.issue26184@psf.upfronthosting.co.za>
Message-ID: <1488144359.92.0.0669625659249.issue26184@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +286

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

From report at bugs.python.org  Sun Feb 26 16:39:42 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Feb 2017 21:39:42 +0000
Subject: [docs] [issue26184] Add versionchanged note for error when
 create_module() is not defined by loaders
In-Reply-To: <1453501860.77.0.669534801782.issue26184@psf.upfronthosting.co.za>
Message-ID: <1488145181.92.0.261937442831.issue26184@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Merged and backported to 3.6.
Closing this issue :) 
Thanks.

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

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

From report at bugs.python.org  Sun Feb 26 20:21:39 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 27 Feb 2017 01:21:39 +0000
Subject: [docs] [issue29660] Document that print/format_exception ignore
 etype
Message-ID: <1488158499.0.0.645448196253.issue29660@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier:

As far as I can tell, http://bugs.python.org/issue17911 made a couple of function in traceback ignore their first arguments (etype) and infer the type from the second one (evalue). 

(In git 6bc2c1e7 and 2f0441f0 respectively).

At least print_exception and format_exception are affected.

This likely affect http://bugs.python.org/issue26389 (who wish to expand same API to remove these parameters).

And inconsistency with `format_exception_only` which does need `etype` should be checked. 

If etype is a deprecated parameter it should be noted, and should likely raise a DeprecationWarning as well when set.

----------
assignee: docs at python
components: Documentation
messages: 288617
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: Document that print/format_exception ignore etype
versions: Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Mon Feb 27 07:06:56 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 27 Feb 2017 12:06:56 +0000
Subject: [docs] [issue28911] Clarify the behaviour of assert_called_once_with
In-Reply-To: <1481233700.68.0.637550951007.issue28911@psf.upfronthosting.co.za>
Message-ID: <1488197216.53.0.408799596702.issue28911@psf.upfronthosting.co.za>


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


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

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

From francis.dalaudier at wanadoo.fr  Sun Feb 26 04:05:50 2017
From: francis.dalaudier at wanadoo.fr (Francis Dalaudier)
Date: Sun, 26 Feb 2017 10:05:50 +0100
Subject: [docs] Outdated FAQ in documentation for python3
Message-ID: <D4D858FE.64D7%francis.dalaudier@wanadoo.fr>

        Hello

In Programming FAQ (first item)
      .../faq/programming.html#is-there-a-source-code-level-debugger...
I read  Pydb is a version of the standard Python ...

The link http://bashdb.sourceforge.net/pydb/
    redirect toward "A rewrite of debugger"
    http://code.google.com/p/pydbgr/
        this page state (in intro)
            "Use pydb for Python earlier than 2.4."
            "Use trepan for Python 3.2 and up."
        and points to
            http://code.google.com/p/python3-trepan
        and finally to
            https://github.com/rocky/python3-trepan
 ____________________________________________________
| Francis Dalaudier   | francis.dalaudier at wanadoo.fr |
|_____________________|______________________________|




From alexis.lopezgarcia at gmail.com  Sun Feb 26 10:06:48 2017
From: alexis.lopezgarcia at gmail.com (Alexis Lopez-Garcia)
Date: Sun, 26 Feb 2017 16:06:48 +0100
Subject: [docs] Small mistake (maybe) in The pymalloc allocator doc.
Message-ID: <CAD4s32ssX077cF0BviVJLZxb_AWAsBz47X1b+tVVJ=kqaz_gxA@mail.gmail.com>

Hello,

I am not sure if this is right or not. So this email is a heads up for
informed people to check.

On

https://docs.python.org/3/c-api/memory.html#the-pymalloc-allocator

the line

pymalloc is the default allocator of the PYMEM_DOMAIN_MEM (ex:
PyObject_Malloc()) and PYMEM_DOMAIN_OBJ (ex: PyObject_Malloc())
domains.

Shouldn't it be:

pymalloc is the default allocator of the PYMEM_DOMAIN_MEM (ex:
PyMem_Malloc()) and PYMEM_DOMAIN_OBJ (ex: PyObject_Malloc()) domains.


-- 
Alexis Lopez Garcia
alexis.lopezgarcia at gmail.com

From m.holze at kabelmail.de  Sun Feb 26 17:03:17 2017
From: m.holze at kabelmail.de (=?UTF-8?Q?M._E._Holz=c3=a9?=)
Date: Sun, 26 Feb 2017 23:03:17 +0100
Subject: [docs] Python Tutorial,Release 3.6.0 / glitch
Message-ID: <25329f5f-20a2-a37c-cf31-940a4b55c6f5@kabelmail.de>

Hello,


just a glitch I guess,


page 49, example :


>>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 7678}
>>> for name, phone in table.items():
....
print('{0:10} ==> {1:10d}'.format(name, phone))
....
Jack ==> 4098
Dcab ==> 7678
Sjoerd ==> 4127

should read:

Dcab ==> 7678

Jack ==> 4098

Sjoerd ==> 4127


shouldn't it ?

(Youvn't used  FORTH  swap   before to manipulate the stack, have you?)



jm2?


Matthias E. Holz?




From songofacandy at gmail.com  Mon Feb 27 08:09:51 2017
From: songofacandy at gmail.com (INADA Naoki)
Date: Mon, 27 Feb 2017 22:09:51 +0900
Subject: [docs] Python Tutorial,Release 3.6.0 / glitch
In-Reply-To: <25329f5f-20a2-a37c-cf31-940a4b55c6f5@kabelmail.de>
References: <25329f5f-20a2-a37c-cf31-940a4b55c6f5@kabelmail.de>
Message-ID: <CAEfz+Tz6jO4q03rdRVrAhPCcoMUSiaSiAdnaaL=dKaRv+O7LtA@mail.gmail.com>

dict iteration order is not defined.  So both are correct.

(internal)
>From CPython 3.6, dict keeps insertion order. So output is stable and
it should be:

Sjoerd ==> 4127
Jack ==> 4098
Dcab ==> 7678

But this is CPython implementation detail.  When other Python
implemantation (e.g. Micropython)
catch Python 3.6 up, the order may be different.

On Mon, Feb 27, 2017 at 7:03 AM, M. E. Holz? <m.holze at kabelmail.de> wrote:
> Hello,
>
>
> just a glitch I guess,
>
>
> page 49, example :
>
>
>>>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 7678}
>>>> for name, phone in table.items():
> ....
> print('{0:10} ==> {1:10d}'.format(name, phone))
> ....
> Jack ==> 4098
> Dcab ==> 7678
> Sjoerd ==> 4127
>
> should read:
>
> Dcab ==> 7678
>
> Jack ==> 4098
>
> Sjoerd ==> 4127
>
>
> shouldn't it ?
>
> (Youvn't used  FORTH  swap   before to manipulate the stack, have you?)
>
>
>
> jm2?
>
>
> Matthias E. Holz?
>
>
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs

From songofacandy at gmail.com  Mon Feb 27 08:25:21 2017
From: songofacandy at gmail.com (INADA Naoki)
Date: Mon, 27 Feb 2017 22:25:21 +0900
Subject: [docs] Small mistake (maybe) in The pymalloc allocator doc.
In-Reply-To: <CAD4s32ssX077cF0BviVJLZxb_AWAsBz47X1b+tVVJ=kqaz_gxA@mail.gmail.com>
References: <CAD4s32ssX077cF0BviVJLZxb_AWAsBz47X1b+tVVJ=kqaz_gxA@mail.gmail.com>
Message-ID: <CAEfz+Txtbo0e1DbFe5kxd6YbmdQ=ABNhcL6gxdbHUPyMXC5dxA@mail.gmail.com>

Thanks for reporting!

I sent pull request for this.
https://github.com/python/cpython/pull/335

On Mon, Feb 27, 2017 at 12:06 AM, Alexis Lopez-Garcia
<alexis.lopezgarcia at gmail.com> wrote:
> Hello,
>
> I am not sure if this is right or not. So this email is a heads up for
> informed people to check.
>
> On
>
> https://docs.python.org/3/c-api/memory.html#the-pymalloc-allocator
>
> the line
>
> pymalloc is the default allocator of the PYMEM_DOMAIN_MEM (ex:
> PyObject_Malloc()) and PYMEM_DOMAIN_OBJ (ex: PyObject_Malloc())
> domains.
>
> Shouldn't it be:
>
> pymalloc is the default allocator of the PYMEM_DOMAIN_MEM (ex:
> PyMem_Malloc()) and PYMEM_DOMAIN_OBJ (ex: PyObject_Malloc()) domains.
>
>
> --
> Alexis Lopez Garcia
> alexis.lopezgarcia at gmail.com
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs

From report at bugs.python.org  Mon Feb 27 08:48:31 2017
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 27 Feb 2017 13:48:31 +0000
Subject: [docs] [issue29666] Issue in enum documentation
Message-ID: <1488203311.1.0.764284916797.issue29666@psf.upfronthosting.co.za>


New submission from STINNER Victor:

https://docs.python.org/dev/library/enum.html

"This module defines four enumeration classes that can be used to define unique sets of names and values: Enum, IntEnum, and IntFlags"

Enum, IntEnum, IntFlag: I count 3 classes, no 4?

Moreover, the correct class name is IntFlag, not IntFlags. Or did I miss something?

haypo at selma$ ./python
Python 3.7.0a0 (default, Feb 25 2017, 04:30:32) 
>>> import enum
>>> enum.IntFlags
...
AttributeError: module 'enum' has no attribute 'IntFlags'

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 288642
nosy: docs at python, haypo
priority: normal
severity: normal
status: open
title: Issue in enum documentation
versions: Python 3.7

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

From report at bugs.python.org  Mon Feb 27 09:08:53 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Mon, 27 Feb 2017 14:08:53 +0000
Subject: [docs] [issue29666] Issue in enum documentation
In-Reply-To: <1488203311.1.0.764284916797.issue29666@psf.upfronthosting.co.za>
Message-ID: <1488204533.36.0.616979596403.issue29666@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Yup, `IntFlags` is a typo, that's why the reference to it doesn't show too. 

Also, the fourth enum must be `Flag` which must of been omitted when it was added in `3.6`.

----------
nosy: +Jim Fasarakis-Hilliard

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

From report at bugs.python.org  Mon Feb 27 09:49:38 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 27 Feb 2017 14:49:38 +0000
Subject: [docs] [issue29455] Mention coverage.py in trace module
 documentation
In-Reply-To: <1486352347.76.0.0578982981399.issue29455@psf.upfronthosting.co.za>
Message-ID: <1488206978.65.0.838503085703.issue29455@psf.upfronthosting.co.za>


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


----------
stage:  -> patch review
versions: +Python 3.6, Python 3.7

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

From report at bugs.python.org  Mon Feb 27 09:52:19 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 27 Feb 2017 14:52:19 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1488207139.74.0.698137604601.issue29414@psf.upfronthosting.co.za>


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


----------
stage:  -> patch review
type:  -> enhancement

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

From report at bugs.python.org  Mon Feb 27 09:54:48 2017
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 27 Feb 2017 14:54:48 +0000
Subject: [docs] [issue22594] Add a link to the regex module in re
 documentation
In-Reply-To: <1412927285.57.0.392292696343.issue22594@psf.upfronthosting.co.za>
Message-ID: <1488207288.38.0.78215277114.issue22594@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Feb 27 10:37:37 2017
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 27 Feb 2017 15:37:37 +0000
Subject: [docs] [issue29660] Document that print/format_exception ignore
 etype
In-Reply-To: <1488158499.0.0.645448196253.issue29660@psf.upfronthosting.co.za>
Message-ID: <1488209857.26.0.631058297971.issue29660@psf.upfronthosting.co.za>


Changes by Matthias Bussonnier <bussonniermatthias at gmail.com>:


----------
pull_requests: +297

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

From report at bugs.python.org  Mon Feb 27 11:17:12 2017
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 27 Feb 2017 16:17:12 +0000
Subject: [docs] [issue29666] Issue in enum documentation
In-Reply-To: <1488203311.1.0.764284916797.issue29666@psf.upfronthosting.co.za>
Message-ID: <1488212232.05.0.406295942814.issue29666@psf.upfronthosting.co.za>


Ethan Furman added the comment:

`Flag` and `IntFlag` are indeed the correct (and missing) names.

----------
nosy: +ethan.furman

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

From report at bugs.python.org  Mon Feb 27 13:58:07 2017
From: report at bugs.python.org (Marco Buttu)
Date: Mon, 27 Feb 2017 18:58:07 +0000
Subject: [docs] [issue29669] Missing import of bisect in the documentation
 examples
Message-ID: <1488221887.03.0.391509219567.issue29669@psf.upfronthosting.co.za>


New submission from Marco Buttu:

There is no import of bisect.bisect() and bisect.bisect_left() in the documentation. IMHO the examples are clearer and more complete if we import these functions, as in the attached patch.

----------
assignee: docs at python
components: Documentation
files: import_bisect.patch
keywords: patch
messages: 288663
nosy: docs at python, marco.buttu
priority: normal
severity: normal
status: open
title: Missing import of bisect in the documentation examples
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file46676/import_bisect.patch

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

From report at bugs.python.org  Mon Feb 27 15:21:01 2017
From: report at bugs.python.org (Ned Batchelder)
Date: Mon, 27 Feb 2017 20:21:01 +0000
Subject: [docs] [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1488226861.63.0.0908338849053.issue17894@psf.upfronthosting.co.za>


Ned Batchelder added the comment:

I'm still interested in moving this forward. I can make a GitHub pull request if that would help.

----------

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

From songofacandy at gmail.com  Mon Feb 27 22:28:06 2017
From: songofacandy at gmail.com (INADA Naoki)
Date: Tue, 28 Feb 2017 12:28:06 +0900
Subject: [docs] Go Zanata or Pontoon,
 or continue Transifex (was Re: [Core-mentorship] CPython
 internationalization proposal (GSoC 2015)
Message-ID: <CAEfz+TxyetNamJPCaHCBL1nftCT7oY1Emqmocq6mDce8X2fjng@mail.gmail.com>

Hi, Nick.

On Thu, Mar 26, 2015 at 6:20 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 24 March 2015 at 15:53, Mariano Reingart <reingart at gmail.com> wrote:
...
>> This is my third attempt to advance with this project (since 2010 & 2012),
>> and I think it would be great for teachers and non-technical users around
>> the world that doesn't speak English.
>
> Would you be interested in including integrating CPython into the
> zanata.org translation management service within the scope of the
> project?
>
> I'd love to see exception message translation happen, but not without
> a clear concept on how we'd aim to build and sustain a translation
> community over the long term.
>
> The reason I suggest Zanata specifically is because I work out of the
> same office as the core Zanata team, our office is also home to many
> of the translators for Fedora & RHEL, and I'm a voting member in the
> Fedora Environments & Stacks working group. I can't *promise* I can
> get those folks to help, but if we target Zanata at a translation
> tooling level, I'd be prepared to mentor the project and at least
> provide introductions to some of the relevant Fedora folks.
>

Zanata team is still at same office?
Are there some Python fan in Zanata team?

We (Japanese Translation team) uses Transifex because there were no
Mozilla Pontoon and Red Hat Zanata when we started using sphinx'es
i18n feature.  Transifex is easier than Launchpad Rosetta so far.

Before we start advocating document translation to other languages,
I want to re-evaluate hosted translation service.  While Transifex can be
used free for OSS, it's FAQ says:

https://docs.transifex.com/faq/all#general-questions
> Transifex offers an Open Source Program to Open Source projects that have no funding, revenue, and/or commercialization model. The intent is to support small and independent Open Source projects. If your project does not fall in this category, please contact us to discuss the appropriate pricing.

I think it's OK for Japanese or French translation project.
But I don't know we can use it free for PSF official project in the future.
And I know Mozilla and Red Hat are very important Python contributor.
So I'm interested in Mozilla Pontoon and Red Hat Zanata.

As far as reading document, Zanata has all important features (team and role
management, review, TM).   And Zanata seems well documented than Pontoon.

I'll try to create project on Zanata, upload po files, and look it's UI.

Regards,

From report at bugs.python.org  Mon Feb 27 23:20:45 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 28 Feb 2017 04:20:45 +0000
Subject: [docs] [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1488255645.48.0.438208635588.issue17894@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I will work on it thank you.

----------
versions: +Python 3.7 -Python 3.4

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

From report at bugs.python.org  Mon Feb 27 23:23:23 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 28 Feb 2017 04:23:23 +0000
Subject: [docs] [issue29669] Missing import of bisect in the documentation
 examples
In-Reply-To: <1488221887.03.0.391509219567.issue29669@psf.upfronthosting.co.za>
Message-ID: <1488255803.62.0.590783928811.issue29669@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Sorry, but I think this is a waste.  A number of the example sections presume that the module under discussion has been imported.   Also, these docs have been around for a long time without the slightest indication of confusion.

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

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

From ncoghlan at gmail.com  Tue Feb 28 06:54:29 2017
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Tue, 28 Feb 2017 21:54:29 +1000
Subject: [docs] Go Zanata or Pontoon,
 or continue Transifex (was Re: [Core-mentorship] CPython
 internationalization proposal (GSoC 2015)
In-Reply-To: <CAEfz+TxyetNamJPCaHCBL1nftCT7oY1Emqmocq6mDce8X2fjng@mail.gmail.com>
References: <CAEfz+TxyetNamJPCaHCBL1nftCT7oY1Emqmocq6mDce8X2fjng@mail.gmail.com>
Message-ID: <CADiSq7fUckZWZkoMKfg=horQk=s8=ZjUSF15TVB5_6+9qBFvOQ@mail.gmail.com>

On 28 February 2017 at 13:28, INADA Naoki <songofacandy at gmail.com> wrote:

> Hi, Nick.
>
> On Thu, Mar 26, 2015 at 6:20 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> > The reason I suggest Zanata specifically is because I work out of the
> > same office as the core Zanata team, our office is also home to many
> > of the translators for Fedora & RHEL, and I'm a voting member in the
> > Fedora Environments & Stacks working group. I can't *promise* I can
> > get those folks to help, but if we target Zanata at a translation
> > tooling level, I'd be prepared to mentor the project and at least
> > provide introductions to some of the relevant Fedora folks.
> >
>
> Zanata team is still at same office?
>

I mostly work from home these days myself, but yes, I believe the Zanata
team is still mostly based in the Red Hat Brisbane office.


> Are there some Python fan in Zanata team?
>

I've pinged a couple of folks I know on the team to see if they or someone
else might be able to help with any questions you have about it :)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170228/2d2c8f30/attachment-0001.html>

From report at bugs.python.org  Tue Feb 28 07:38:42 2017
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 28 Feb 2017 12:38:42 +0000
Subject: [docs] [issue29677] 'round()' accepts a negative integer for ndigits
In-Reply-To: <1488285024.25.0.0499728148151.issue29677@psf.upfronthosting.co.za>
Message-ID: <1488285522.65.0.286425315513.issue29677@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Yep, it's (genuinely) a feature, not a bug, and being able to round to the nearest ten, hundred, thousand, etc. is useful. The docs could perhaps be improved to make it clearer that this is supported.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, mark.dickinson

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

From report at bugs.python.org  Tue Feb 28 07:45:52 2017
From: report at bugs.python.org (ChrisRands)
Date: Tue, 28 Feb 2017 12:45:52 +0000
Subject: [docs] [issue29677] 'round()' accepts a negative integer for ndigits
In-Reply-To: <1488285024.25.0.0499728148151.issue29677@psf.upfronthosting.co.za>
Message-ID: <1488285952.16.0.636380130693.issue29677@psf.upfronthosting.co.za>


ChrisRands added the comment:

Ah yes, you're both completely right of course. Perhaps the docs could still be clarified though. I managed to completely overlook this, and perhaps other non-expert Python users would too.

----------

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

From report at bugs.python.org  Tue Feb 28 07:50:19 2017
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 28 Feb 2017 12:50:19 +0000
Subject: [docs] [issue29677] 'round()' accepts a negative integer for ndigits
In-Reply-To: <1488285024.25.0.0499728148151.issue29677@psf.upfronthosting.co.za>
Message-ID: <1488286219.45.0.570699534041.issue29677@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Yes, I think the initial description could be clarified. It currently reads:

> Return the floating point value number rounded to ndigits digits after the decimal point.

... which doesn't make it clear what happens for negative ndigits. 

There's a line in the second paragraph:

> values are rounded to the closest multiple of 10 to the power minus ndigits

which technically *does* cover the case of negative ndigits correctly, but I think it would be good to have a clarification in the first paragraph of the description.

----------

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

From report at bugs.python.org  Tue Feb 28 07:53:06 2017
From: report at bugs.python.org (Gerrit Holl)
Date: Tue, 28 Feb 2017 12:53:06 +0000
Subject: [docs] [issue29677] 'round()' accepts a negative integer for ndigits
In-Reply-To: <1488285024.25.0.0499728148151.issue29677@psf.upfronthosting.co.za>
Message-ID: <1488286386.18.0.220193945813.issue29677@psf.upfronthosting.co.za>


Changes by Gerrit Holl <gerrit.holl at gmail.com>:


----------
pull_requests: +304

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

From report at bugs.python.org  Tue Feb 28 11:18:18 2017
From: report at bugs.python.org (Wolfgang Maier)
Date: Tue, 28 Feb 2017 16:18:18 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1488298697.58.0.865997701712.issue29414@psf.upfronthosting.co.za>


Wolfgang Maier added the comment:

I studied the github PR and thought about it carefully, and that made me come to believe that the chapter deserves a larger rewrite not just of one section, but of several.
I'm attaching my proposed change as a "classical" patch here for discussion. I hope that's still a valid way to do this as I did not want to mess with the original PR by Marco and, instead, wanted to see my proposal discussed first.

Some of the changes I made:
- I don't think range() really deserves its own section in a chapter about control flow, so I removed most of it and linked to the relevant stdtypes section instead
- moved the definition of an iterable up into the for loop section
- restructured the for loop section to discuss Python for loops first and only compare them to Pascal/C afterwards
- moved the example for modifying a list while iterating over it to the datastructures chapter

I find this new version much clearer, but lets see what people here think.

----------
nosy: +wolma
Added file: http://bugs.python.org/file46681/controlflow_datastructures.patch

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

From report at bugs.python.org  Tue Feb 28 13:43:31 2017
From: report at bugs.python.org (Kartik)
Date: Tue, 28 Feb 2017 18:43:31 +0000
Subject: [docs] [issue29666] Issue in enum documentation
In-Reply-To: <1488203311.1.0.764284916797.issue29666@psf.upfronthosting.co.za>
Message-ID: <1488307411.25.0.289337254672.issue29666@psf.upfronthosting.co.za>


Kartik added the comment:

Hi I've edited the documentation to correct this and submitted a PR.

----------
nosy: +exqu17
pull_requests: +305

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

From report at bugs.python.org  Tue Feb 28 16:46:36 2017
From: report at bugs.python.org (Marco Buttu)
Date: Tue, 28 Feb 2017 21:46:36 +0000
Subject: [docs] [issue29414] Change 'the for statement is such an iterator'
 in Tutorial
In-Reply-To: <1485976216.65.0.169866413965.issue29414@psf.upfronthosting.co.za>
Message-ID: <1488318396.63.0.191998283353.issue29414@psf.upfronthosting.co.za>


Marco Buttu added the comment:

Wolfgang, thanks for your contribution. However, I prefere the chapter as it currently is, because IMHO it introduces the concepts more gradually than your proposal. In addition the modification of the title section from "for Statements" to "for Loops" IMHO makes the title not consistent with the other section titles.

> - I don't think range() really deserves its own section
> in a chapter about control flow, so I removed most of it
> and linked to the relevant stdtypes section instead

-1 for me: the range() function is used in several examples in the chapter, that is why IMHO it is worth having the range() section as it is now.

> - moved the definition of an iterable up into the for
> loop section

-1 for me: IMHO the current definition/introdution of iterable is easier to understand for a beginner.

> - restructured the for loop section to discuss Python for loops
> first and only compare them to Pascal/C afterwards

+0. I think for a reader who is coming from another language is better to have the current introduction. But maybe it is not the same for a reader who is learning Python as a first programming language.

> - moved the example for modifying a list while iterating
> over it to the datastructures chapter

+0

----------

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

From m.holze at kabelmail.de  Mon Feb 27 09:50:20 2017
From: m.holze at kabelmail.de (=?UTF-8?Q?M._E._Holz=c3=a9?=)
Date: Mon, 27 Feb 2017 15:50:20 +0100
Subject: [docs] Python Tutorial,Release 3.6.0 / glitch
In-Reply-To: <CAEfz+Tz6jO4q03rdRVrAhPCcoMUSiaSiAdnaaL=dKaRv+O7LtA@mail.gmail.com>
References: <25329f5f-20a2-a37c-cf31-940a4b55c6f5@kabelmail.de>
 <CAEfz+Tz6jO4q03rdRVrAhPCcoMUSiaSiAdnaaL=dKaRv+O7LtA@mail.gmail.com>
Message-ID: <1ed31553-db15-9bae-01a9-d94e20a1239b@kabelmail.de>

Hugh,


when first defined as dict at page 35, assuming that it is not an
independant example, the content is:

>>> dict(sape=4139, guido=4127, jack=4098)
{'sape': 4139, 'jack': 4098, 'guido': 4127}

so I'd guess the result at page 49 wouldn't be correct neither, when
keeping the order as you describe.

So I conclude the example is meant to be independant. (Or I missed where
'sape' was dropped and 'Sjoerd' was added and the dict rearranged, and
the first char of the name set to caps...)

Here at page 49 we have a new table:

>>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 7678}

You point out, that dict keeps the insertion order. Fine, stack reading
from left to right in input order, that is  FIFO, delivers

Sjoerd ==> 4127
Jack ==> 4098
Dcab ==> 7678

agreed. ;-)

LIFO (stack order) would yield:

Dcab ==> 7678
Jack ==> 4098
Sjoerd ==> 4127

o.k., that's what I'm used to, working with FORTH. And the way 3.5 does
work at least on my system.

But how does Jack come first?  Combined number of characters and
numerical value of telephon-number?

Jack ==> 4098
Dcab ==> 7678
Sjoerd ==> 4127

Sorry, 

wonder how to work with an unpredictable order...


The Forth be with you




On 27.02.2017 14:09, INADA Naoki wrote:
> dict iteration order is not defined.  So both are correct.
>
> (internal)
> >From CPython 3.6, dict keeps insertion order. So output is stable and
> it should be:
>
> Sjoerd ==> 4127
> Jack ==> 4098
> Dcab ==> 7678
>
> But this is CPython implementation detail.  When other Python
> implemantation (e.g. Micropython)
> catch Python 3.6 up, the order may be different.
>
> On Mon, Feb 27, 2017 at 7:03 AM, M. E. Holz? <m.holze at kabelmail.de> wrote:
>> Hello,
>>
>>
>> just a glitch I guess,
>>
>>
>> page 49, example :
>>
>>
>>>>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 7678}
>>>>> for name, phone in table.items():
>> ....
>> print('{0:10} ==> {1:10d}'.format(name, phone))
>> ....
>> Jack ==> 4098
>> Dcab ==> 7678
>> Sjoerd ==> 4127
>>
>> should read:
>>
>> Dcab ==> 7678
>>
>> Jack ==> 4098
>>
>> Sjoerd ==> 4127
>>
>>
>> shouldn't it ?
>>
>> (Youvn't used  FORTH  swap   before to manipulate the stack, have you?)
>>
>>
>>
>> jm2?
>>
>>
>> Matthias E. Holz?
>>
>>
>>
>> _______________________________________________
>> docs mailing list
>> docs at python.org
>> https://mail.python.org/mailman/listinfo/docs
> .
>