From report at bugs.python.org  Wed May  1 06:47:02 2019
From: report at bugs.python.org (Kasra Vand)
Date: Wed, 01 May 2019 10:47:02 +0000
Subject: [docs] [issue36765] Invalid grammar for f_expression
Message-ID: <1556707622.28.0.558014565805.issue36765@roundup.psfhosted.org>


New submission from Kasra Vand <kasraavand at gmail.com>:

Due to the discussion in following SO question https://stackoverflow.com/questions/55933956/what-does-a-star-asterisk-do-in-f-string/55934472#55933956

and the inconsistency of the source behaviour with the documentation I think using `"*" or_expr` for f_expression is wrong or at least not what it meant to be and very vague. I was wondering if there's any reason for using `"*" or_expr`.

----------
assignee: docs at python
components: Documentation
messages: 341186
nosy: Kasra Vand, docs at python
priority: normal
severity: normal
status: open
title: Invalid grammar for f_expression
type: behavior
versions: Python 3.7

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

From report at bugs.python.org  Wed May  1 06:54:26 2019
From: report at bugs.python.org (Kasra Vand)
Date: Wed, 01 May 2019 10:54:26 +0000
Subject: [docs] [issue36765] Invalid grammar for f_expression
In-Reply-To: <1556707622.28.0.558014565805.issue36765@roundup.psfhosted.org>
Message-ID: <1556708066.13.0.142334689108.issue36765@roundup.psfhosted.org>


Kasra Vand <kasraavand at gmail.com> added the comment:

Due to the discussion in following SO question https://stackoverflow.com/questions/55933956/what-does-a-star-asterisk-do-in-f-string/55934472#55933956

and the inconsistency of the source behaviour with the documentation I think using `"*" or_expr` for f_expression is wrong or at least not what it meant to be and very vague. I was wondering if there's any reason for using `"*" or_expr` instead of let's say just `expr` which I think is what the `or_expr` identifier is intended to be.

----------

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

From report at bugs.python.org  Wed May  1 07:30:01 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 01 May 2019 11:30:01 +0000
Subject: [docs] [issue36765] Invalid grammar for f_expression
In-Reply-To: <1556707622.28.0.558014565805.issue36765@roundup.psfhosted.org>
Message-ID: <1556710201.25.0.163582932771.issue36765@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed May  1 07:36:08 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 01 May 2019 11:36:08 +0000
Subject: [docs] [issue36765] Invalid grammar for f_expression
In-Reply-To: <1556707622.28.0.558014565805.issue36765@roundup.psfhosted.org>
Message-ID: <1556710568.06.0.410086387592.issue36765@roundup.psfhosted.org>


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

I don't think this is a problem. There are plenty of things allowed by Python's grammar that are converted to errors in subsequent passes. For example:

>>> *[1]
  File "<stdin>", line 1
SyntaxError: can't use starred expression here
>>> *[1],*[2]
(1, 2)

----------

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

From report at bugs.python.org  Wed May  1 10:12:45 2019
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 01 May 2019 14:12:45 +0000
Subject: [docs] [issue36769] doc Document that fnmatch.filter supports any
 kind of iterable not just lists
Message-ID: <1556719965.28.0.191162970906.issue36769@roundup.psfhosted.org>


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

Documentation on fnmatch.filter says:

Return the subset of the list of names that match pattern. It is the same as [n for n in names if fnmatch(n, pattern)], but implemented more efficiently.

But the function actual accepts any kind of iterable. I think it should be documented.

----------
assignee: docs at python
components: Documentation
messages: 341198
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Document that fnmatch.filter supports any kind of iterable not just lists
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Wed May  1 10:13:09 2019
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 01 May 2019 14:13:09 +0000
Subject: [docs] [issue36769] doc Document that fnmatch.filter supports any
 kind of iterable not just lists
In-Reply-To: <1556719965.28.0.191162970906.issue36769@roundup.psfhosted.org>
Message-ID: <1556719989.0.0.574587769662.issue36769@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed May  1 10:57:15 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 01 May 2019 14:57:15 +0000
Subject: [docs] [issue36329] use the right python "make -C Doc/ serve"
In-Reply-To: <1556658299.65.0.382673742846.issue36329@roundup.psfhosted.org>
Message-ID: <20190501145700.jhlxqlltmt3wt3kk@xps>


St?phane Wirtel <stephane at wirtel.be> added the comment:

>Personally, I'd prefer removing the 'serve' target completely. make -C
>Doc htmlview should already cover most of its use cases. There is no
>deprecation period needed and there is already a replacement (and IMO
>better) for it.

Hi Berker,

When I have read your message, I was surprised because this target
already exists since 2010. It's true we can run the makefile with 

my current workflow is 

make -C Doc/ venv && make -C Doc/ html serve and open my browser at
http://localhost:8000

but with your suggestion, I think it's better for us and also for the
contributors, just make -C Doc/ venv htmlview. This target will open the
browser with the result of the html build.

So, I have discussed with @Julien Palard and he told me that he did not
use the 'serve' target and he discovered the target via my issue.

But there will be an other issue, in the devguide, there is also a
'serve' target in the Makefile with a copy of tools/serve.py.

But there is no htmlview target. 

For the moment, we have a common solution for the two project if we want
to show the result to the user, make serve.

We could:

* remove 'make serve' from CPython and Devguide
* remove tools/serve.py from CPython and Devguide
* add htmlview to the DevGuide
* update the documentation 

+1 for removing the serve.py script and use htmlview.

----------

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

From report at bugs.python.org  Wed May  1 11:23:08 2019
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 01 May 2019 15:23:08 +0000
Subject: [docs] [issue36329] use the right python "make -C Doc/ serve"
In-Reply-To: <20190501145700.jhlxqlltmt3wt3kk@xps>
Message-ID: <CAF4280+xekxnQcBQP7w=grUbwnAhopfKbG1-hsdzx2x6+UMzHA@mail.gmail.com>


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

Yeah, we can add htmlview to devguide. I?ve even added it to Django after I
discovered it in CPython :)
-- 
--Berker

----------

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

From report at bugs.python.org  Thu May  2 01:55:36 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 02 May 2019 05:55:36 +0000
Subject: [docs] [issue36765] Invalid grammar for f_expression
In-Reply-To: <1556707622.28.0.558014565805.issue36765@roundup.psfhosted.org>
Message-ID: <1556776536.34.0.833557060549.issue36765@roundup.psfhosted.org>


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

Concur with Eric. The formal definition of the Python grammar is wider than valid Python, because we do not want to make it too complex. Invalid constructions are filtered out later.

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

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

From report at bugs.python.org  Thu May  2 04:08:36 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 02 May 2019 08:08:36 +0000
Subject: [docs] [issue36765] Invalid grammar for f_expression
In-Reply-To: <1556707622.28.0.558014565805.issue36765@roundup.psfhosted.org>
Message-ID: <1556784516.83.0.507495161405.issue36765@roundup.psfhosted.org>


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

Thanks, Serhiy.

I suppose that we could add a note to the documentation, but I'm not sure it would be worth the confusion it would create. It's best to think of this is "it's just an expression,  like everywhere else in Python". If I ever decide I like PEP 536, maybe then things will become clearer (although possibly not: the same issue will still exist, but I think it will become more obvious that expressions are treated just like they are elsewhere).

So I'm going to close this.

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

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

From report at bugs.python.org  Fri May  3 02:07:00 2019
From: report at bugs.python.org (Martha Simons)
Date: Fri, 03 May 2019 06:07:00 +0000
Subject: [docs] [issue27409] List socket.SO_*, SCM_*, MSG_*,
 IPPROTO_* symbols
In-Reply-To: <1467168896.94.0.840314714269.issue27409@psf.upfronthosting.co.za>
Message-ID: <1556863620.36.0.681595242777.issue27409@roundup.psfhosted.org>


Martha Simons <marthasimons9999 at gmail.com> added the comment:

That patch was never updated nor comitted, but it sounds like this kind of addition might be https://goo.gl/LhppLn  acceptable.

----------
nosy: +Martha Simons

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

From report at bugs.python.org  Fri May  3 08:25:17 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 03 May 2019 12:25:17 +0000
Subject: [docs] [issue34848] range.index only takes one argument when it's
 documented as taking the usual 3
In-Reply-To: <1538279738.27.0.545547206417.issue34848@psf.upfronthosting.co.za>
Message-ID: <1556886317.61.0.680556022481.issue34848@roundup.psfhosted.org>


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


----------
pull_requests: +12989

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

From report at bugs.python.org  Fri May  3 08:27:51 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Fri, 03 May 2019 12:27:51 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1556886471.84.0.272219179719.issue36743@roundup.psfhosted.org>


Jeroen Demeyer <J.Demeyer at UGent.be> added the comment:

Personally, I have always found "instance" and "owner" very confusing names for these arguments. If you want to change the documentation, I would recommend changing those names too. Better names would be "obj" and "cls" or something like that.

----------
nosy: +jdemeyer

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

From report at bugs.python.org  Fri May  3 08:42:13 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Fri, 03 May 2019 12:42:13 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1556887333.18.0.351278677322.issue36743@roundup.psfhosted.org>


Jeroen Demeyer <J.Demeyer at UGent.be> added the comment:

> Perhaps the datamodel docs can be clarified to note that callers are allowed to omit the third argument

That's not true in general, only when __get__ is a slot wrapper (i.e. for classes implemented in C). When __get__ is a Python function, nothing special is done, it's just a Python function.

----------

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

From report at bugs.python.org  Fri May  3 09:51:55 2019
From: report at bugs.python.org (Paul Ganssle)
Date: Fri, 03 May 2019 13:51:55 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
Message-ID: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>


New submission from Paul Ganssle <p.ganssle at gmail.com>:

In Python 3.6, Time_FromTimeAndFold and PyDateTime_FromDateAndTimeAndFold were added as part of the PEP 495 implementation, but no documentation was added for the C API portions of this change: https://docs.python.org/3.7/c-api/datetime.html

The functions were added to this portion of the C API capsule: https://github.com/python/cpython/blob/master/Include/datetime.h#L173

Macros are here: https://github.com/python/cpython/blob/master/Include/datetime.h#L222

These functions should be documented, with `..versionadded:: 3.6`

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 341337
nosy: docs at python, p-ganssle
priority: low
severity: normal
status: open
title: No documentation for _FromXandFold C API functions
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Fri May  3 09:52:32 2019
From: report at bugs.python.org (Paul Ganssle)
Date: Fri, 03 May 2019 13:52:32 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1556891552.93.0.25488183364.issue36783@roundup.psfhosted.org>


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


----------
nosy: +Mariatta, cheryl.sabella

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

From report at bugs.python.org  Fri May  3 12:04:30 2019
From: report at bugs.python.org (Paul Ganssle)
Date: Fri, 03 May 2019 16:04:30 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1556899470.6.0.608578870554.issue36783@roundup.psfhosted.org>


Paul Ganssle <p.ganssle at gmail.com> added the comment:

This ticket should be reserved for the mentored sprint.

----------
assignee: docs at python -> Mariatta

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

From report at bugs.python.org  Fri May  3 12:44:31 2019
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 03 May 2019 16:44:31 +0000
Subject: [docs] [issue27409] List socket.SO_*, SCM_*, MSG_*,
 IPPROTO_* symbols
In-Reply-To: <1467168896.94.0.840314714269.issue27409@psf.upfronthosting.co.za>
Message-ID: <1556901871.67.0.897912293109.issue27409@roundup.psfhosted.org>


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


----------
Removed message: https://bugs.python.org/msg341325

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

From report at bugs.python.org  Fri May  3 12:53:27 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 May 2019 16:53:27 +0000
Subject: [docs] [issue33882] doc Mention breakpoint() in debugger-related FAQ
In-Reply-To: <1529192953.25.0.56676864532.issue33882@psf.upfronthosting.co.za>
Message-ID: <1556902406.98.0.871818082795.issue33882@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:


New changeset cf48e55f7f7718482fa712552f0cbc0aea1c826f by ?ric Araujo (Andre Delfino) in branch 'master':
bpo-33882: mention breakpoint() in debugger-related FAQ (GH-7759)
https://github.com/python/cpython/commit/cf48e55f7f7718482fa712552f0cbc0aea1c826f


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

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

From report at bugs.python.org  Fri May  3 12:53:40 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 03 May 2019 16:53:40 +0000
Subject: [docs] [issue33882] doc Mention breakpoint() in debugger-related FAQ
In-Reply-To: <1529192953.25.0.56676864532.issue33882@psf.upfronthosting.co.za>
Message-ID: <1556902420.49.0.411373664295.issue33882@roundup.psfhosted.org>


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


----------
pull_requests: +12991

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

From report at bugs.python.org  Fri May  3 20:00:17 2019
From: report at bugs.python.org (mbiggs)
Date: Sat, 04 May 2019 00:00:17 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
Message-ID: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>


New submission from mbiggs <pythonbugs at doubleplum.net>:

In the Unicode HOWTO: http://docs.python.org/3.3/howto/unicode.html

It says the following:


"UTF-8 has several convenient properties:
(...)
2. A Unicode string is turned into a sequence of bytes containing no embedded zero bytes. This avoids byte-ordering issues, and means UTF-8 strings can be processed by C functions such as strcpy() and sent through protocols that can?t handle zero bytes."

This is not right.  UTF-8 uses the zero byte to represent the Unicode codepoint U+0000 (the ASCII NULL character).  This is a valid character in UTF-8 and is handled just fine by python's UTF-8 string encoding/decoding.

----------
assignee: docs at python
components: Documentation
messages: 341363
nosy: docs at python, mbiggs
priority: normal
severity: normal
status: open
title: Unicode HOWTO incorrectly states that UTF-8 contains no zero bytes
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri May  3 20:06:45 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sat, 04 May 2019 00:06:45 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1556928405.4.0.629187646124.issue36789@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

This is right for 99.99% cases: utf8 doesn't encode any character except explicit zero with zero bytes.

UTF-16 for example encodes 'a' as b'\xff\xfea\x00'

----------
nosy: +asvetlov

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

From report at bugs.python.org  Sat May  4 10:20:06 2019
From: report at bugs.python.org (Mikhail Gerasimov)
Date: Sat, 04 May 2019 14:20:06 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
Message-ID: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>


New submission from Mikhail Gerasimov <Gerasimov-M-N at yandex.ru>:

Compare:
https://docs.python.org/3.6/library/asyncio-sync.html#asyncio.Lock
https://docs.python.org/3.8/library/asyncio-sync.html#asyncio.Lock

First version is much more detailed.
It allows to avoid confusions like one with unlocking order:
https://stackoverflow.com/q/55951233/1113207

----------
assignee: docs at python
components: Documentation, asyncio
messages: 341385
nosy: asvetlov, docs at python, germn, yselivanov
priority: normal
severity: normal
status: open
title: asyncio.Lock documentation in Py3.8 lacks parts presented in documentation in Py3.6
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Sat May  4 11:49:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 04 May 2019 15:49:55 +0000
Subject: [docs] [issue34848] range.index only takes one argument when it's
 documented as taking the usual 3
In-Reply-To: <1538279738.27.0.545547206417.issue34848@psf.upfronthosting.co.za>
Message-ID: <1556984995.11.0.947407376613.issue34848@roundup.psfhosted.org>


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

I merged the pull requests. Thanks.

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

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

From report at bugs.python.org  Sat May  4 13:39:18 2019
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Sat, 04 May 2019 17:39:18 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1556991558.73.0.526935541964.issue36794@roundup.psfhosted.org>


Hrvoje Nik?i? <hniksic at gmail.com> added the comment:

Also, the docstring of asyncio.Lock still states:

    When more than one coroutine is blocked in acquire() waiting for
    the state to turn to unlocked, only one coroutine proceeds when a
    release() call resets the state to unlocked; first coroutine which
    is blocked in acquire() is being processed.

----------
nosy: +hniksic

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

From report at bugs.python.org  Sat May  4 13:47:37 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 04 May 2019 17:47:37 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1556992057.68.0.429728827393.issue36794@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat May  4 13:48:38 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 04 May 2019 17:48:38 +0000
Subject: [docs] [issue36795] "make venv" failed in Docs
Message-ID: <1556992118.26.0.759759719454.issue36795@roundup.psfhosted.org>


New submission from Antoine Pitrou <pitrou at free.fr>:

$ make venv
python3 -m venv ./venv
./venv/bin/python3 -m pip install -U Sphinx blurb python-docs-theme
/home/antoine/cpython/default/Doc/venv/share/python-wheels/requests-2.18.4-py2.py3-none-any.whl/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.22) or chardet (2.3.0) doesn't match a supported version!
Collecting Sphinx
  Cache entry deserialization failed, entry ignored
Exception:
Traceback (most recent call last):
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/commands/install.py", line 353, in run
    wb.build(autobuilding=True)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/wheel.py", line 749, in build
    self.requirement_set.prepare_files(self.finder)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/req/req_set.py", line 380, in prepare_files
    ignore_dependencies=self.ignore_dependencies))
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/req/req_set.py", line 554, in _prepare_file
    require_hashes
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/req/req_install.py", line 278, in populate_link
    self.link = finder.find_requirement(self, upgrade)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 465, in find_requirement
    all_candidates = self.find_all_candidates(req.name)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 423, in find_all_candidates
    for page in self._get_pages(url_locations, project_name):
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 568, in _get_pages
    page = self._get_page(location)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 683, in _get_page
    return HTMLPage.get_page(link, session=self.session)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 811, in get_page
    inst = cls(resp.content, resp.url, resp.headers)
  File "/home/antoine/cpython/default/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 731, in __init__
    namespaceHTMLElements=False,
TypeError: parse() got an unexpected keyword argument 'transport_encoding'
Makefile:126: recipe for target 'venv' failed
make: *** [venv] Error 2

----------
assignee: docs at python
components: Documentation
messages: 341395
nosy: brett.cannon, docs at python, ned.deily, pitrou
priority: critical
severity: normal
stage: needs patch
status: open
title: "make venv" failed in Docs
type: behavior
versions: Python 3.8

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

From report at bugs.python.org  Sat May  4 14:07:09 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 04 May 2019 18:07:09 +0000
Subject: [docs] [issue36795] "make venv" failed in Docs
In-Reply-To: <1556992118.26.0.759759719454.issue36795@roundup.psfhosted.org>
Message-ID: <1556993229.91.0.412740222864.issue36795@roundup.psfhosted.org>


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


----------
nosy: +mdk

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

From report at bugs.python.org  Sat May  4 15:14:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 04 May 2019 19:14:00 +0000
Subject: [docs] [issue36795] "make venv" failed in Docs
In-Reply-To: <1556992118.26.0.759759719454.issue36795@roundup.psfhosted.org>
Message-ID: <1556997240.05.0.663375926626.issue36795@roundup.psfhosted.org>


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

Could it be a problem with pip and it's vendored html5lib version incompatibility? There is one bug report in pip repo about Anaconda patching pip that seems to cause this error : https://github.com/pypa/pip/issues/4902 .

Can you please share the pip and python version to see if I can reproduce this? Is the pip being used part of the one at 3.6 release?

./venv/bin/pip --version

I am using Python 3.6.4 from homebrew. I can reproduce this is by manually editing ./venv/lib/python3.6/site-packages/pip/_vendor/html5lib/_inputstream.py and removing transport_encoding from HTMLBinaryInputStream's constructor. 

./venv/lib/python3.6/site-packages/pip/_vendor/html5lib/__init__.py contains the version number of html5lib. Mine is 1.0b10. 

Sample error I got similar to the report : 

?  Doc git:(master) ? ./venv/bin/pip install sphinx
Collecting sphinx
Exception:
Traceback (most recent call last):
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/commands/install.py", line 324, in run
    requirement_set.prepare_files(finder)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/req/req_set.py", line 380, in prepare_files
    ignore_dependencies=self.ignore_dependencies))
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/req/req_set.py", line 554, in _prepare_file
    require_hashes
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/req/req_install.py", line 278, in populate_link
    self.link = finder.find_requirement(self, upgrade)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 465, in find_requirement
    all_candidates = self.find_all_candidates(req.name)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 423, in find_all_candidates
    for page in self._get_pages(url_locations, project_name):
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 568, in _get_pages
    page = self._get_page(location)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 683, in _get_page
    return HTMLPage.get_page(link, session=self.session)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 811, in get_page
    inst = cls(resp.content, resp.url, resp.headers)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/index.py", line 731, in __init__
    namespaceHTMLElements=False,
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/_vendor/html5lib/html5parser.py", line 35, in parse
    return p.parse(doc, **kwargs)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/_vendor/html5lib/html5parser.py", line 235, in parse
    self._parse(stream, False, None, *args, **kwargs)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/_vendor/html5lib/html5parser.py", line 85, in _parse
    self.tokenizer = _tokenizer.HTMLTokenizer(stream, parser=self, **kwargs)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/_vendor/html5lib/_tokenizer.py", line 36, in __init__
    self.stream = HTMLInputStream(stream, **kwargs)
  File "/Users/karthikeyansingaravelan/stuff/python/cpython/Doc/venv/lib/python3.6/site-packages/pip/_vendor/html5lib/_inputstream.py", line 151, in HTMLInputStream
    return HTMLBinaryInputStream(source, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'transport_encoding'
You are using pip version 9.0.1, however version 19.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

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

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

From report at bugs.python.org  Sat May  4 16:27:33 2019
From: report at bugs.python.org (Kojo Idrissa)
Date: Sat, 04 May 2019 20:27:33 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1557001653.64.0.755494565654.issue33071@roundup.psfhosted.org>


Kojo Idrissa <kojo.idrissa at gmail.com> added the comment:

I'm working on this (@kojoidrissa)

----------
nosy: +kojoidrissa

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

From report at bugs.python.org  Sat May  4 16:33:22 2019
From: report at bugs.python.org (Julia)
Date: Sat, 04 May 2019 20:33:22 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557002002.1.0.311538675771.issue11001@roundup.psfhosted.org>


Julia <julia.iluyk at gmail.com> added the comment:

Working on it at the moment

----------
nosy: +jiliuk

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

From report at bugs.python.org  Sat May  4 16:41:09 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 04 May 2019 20:41:09 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557002469.07.0.00394060542381.issue11001@roundup.psfhosted.org>


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


----------
pull_requests: +13000

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

From report at bugs.python.org  Sat May  4 16:50:28 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 04 May 2019 20:50:28 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557003028.81.0.801860693414.issue11001@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
versions: +Python 3.7, Python 3.8 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat May  4 16:57:12 2019
From: report at bugs.python.org (Kojo Idrissa)
Date: Sat, 04 May 2019 20:57:12 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1557003432.03.0.699598217972.issue33071@roundup.psfhosted.org>


Change by Kojo Idrissa <kojo.idrissa at gmail.com>:


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

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

From report at bugs.python.org  Sat May  4 21:27:28 2019
From: report at bugs.python.org (mbiggs)
Date: Sun, 05 May 2019 01:27:28 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557019648.92.0.555484204975.issue36789@roundup.psfhosted.org>


mbiggs <pythonbugs at doubleplum.net> added the comment:

So a correct statement would be "A UTF-8 string is turned into a sequence of bytes that contains embedded zero bytes only where they represent the NULL character (U+0000)."

I think it's important to correct this because the part about processing UTF-8 with C functions like strcpy(), was wrong and could cause bugs.

----------

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

From report at bugs.python.org  Sun May  5 01:54:52 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 May 2019 05:54:52 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557035692.66.0.722797616604.issue36789@roundup.psfhosted.org>


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

I agree that the documentation should be updated. Do you mind to create a pull request mbiggs?

There are UTF-8 variants which guarantee that the encoded text has no zero bytes (see Modified UTF-8), but Python only provides the standard UTF-8 and UTF-8 with BOM.

----------
keywords: +easy
nosy: +serhiy.storchaka
stage:  -> needs patch
versions:  -Python 3.5, Python 3.6

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

From report at bugs.python.org  Sun May  5 02:09:03 2019
From: report at bugs.python.org (Reuben Thomas)
Date: Sun, 05 May 2019 06:09:03 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
Message-ID: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>


New submission from Reuben Thomas <rrt at sc3d.org>:

"It is possible to defined" ? "It is possible to define"

----------
assignee: docs at python
components: Documentation
messages: 341419
nosy: docs at python, rrt
priority: normal
severity: normal
status: open
title: Typo in ctypes documentation
versions: Python 3.8

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

From report at bugs.python.org  Sun May  5 09:07:02 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 05 May 2019 13:07:02 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557061622.13.0.99926114777.issue36799@roundup.psfhosted.org>


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

Reuben, would you like to make a PR for this change? The change needs to be done in https://github.com/python/cpython/blob/master/Doc/library/ctypes.rst

?  cpython git:(master) ? rg 'It is possible to defined'
Doc/library/ctypes.rst
2379:      It is possible to defined sub-subclasses of structure types, they inherit
2427:   It is possible to defined sub-subclasses of structures, they inherit the

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

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

From report at bugs.python.org  Sun May  5 09:08:57 2019
From: report at bugs.python.org (Reuben Thomas)
Date: Sun, 05 May 2019 13:08:57 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557061737.67.0.399373754156.issue36799@roundup.psfhosted.org>


Reuben Thomas <rrt at sc3d.org> added the comment:

No, as I'm not an active Python contributor, do not aspire to be one, and don't really want to have to learn yet another contribution system to a major project just to fix a trivial typo. Sorry!

----------

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

From report at bugs.python.org  Sun May  5 09:11:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 05 May 2019 13:11:11 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557061871.13.0.616603822899.issue36799@roundup.psfhosted.org>


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

No problem, I have tagged it as easy and hope someone makes GitHub PR for the same.

Thank you for the report.

----------

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

From report at bugs.python.org  Sun May  5 09:58:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 05 May 2019 13:58:21 +0000
Subject: [docs] [issue36654] Add example to tokenize.tokenize
In-Reply-To: <1555559036.7.0.0522143852215.issue36654@roundup.psfhosted.org>
Message-ID: <1557064701.97.0.87049067699.issue36654@roundup.psfhosted.org>


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

I do not think a new example is needed. The existing example already demonstrates the use of file's readline method.

If you need an example for opening a file, the tokenize module documentation is not an appropriate place for this.

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

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

From report at bugs.python.org  Sun May  5 18:25:59 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Sun, 05 May 2019 22:25:59 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557095159.93.0.0240622174783.issue36789@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Minor bikeshed: If updating the documentation, refer to U+0000 as "the null character" or "NUL", not "NULL". Using "NULL" allows for confusion with NULL pointers; "the null character" (the name used in the Unicode standard) or "NUL" (the official three letter abbreviation in ASCII, Unicode too I think) has no such opportunity for confusion.

----------
nosy: +josh.r

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

From report at bugs.python.org  Sun May  5 21:44:48 2019
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 06 May 2019 01:44:48 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557107088.07.0.137391877214.issue36789@roundup.psfhosted.org>


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


----------
nosy: +ezio.melotti
type:  -> enhancement

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

From report at bugs.python.org  Sun May  5 23:49:48 2019
From: report at bugs.python.org (sehnsucht13)
Date: Mon, 06 May 2019 03:49:48 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557114588.17.0.0162898240833.issue36799@roundup.psfhosted.org>


Change by sehnsucht13 <ykonstantinov1 at gmail.com>:


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

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

From report at bugs.python.org  Mon May  6 00:06:23 2019
From: report at bugs.python.org (sehnsucht13)
Date: Mon, 06 May 2019 04:06:23 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557115583.83.0.272354140079.issue36799@roundup.psfhosted.org>


sehnsucht13 <ykonstantinov1 at gmail.com> added the comment:

I have made a PR for this. The only delay is that my CLA needs to be approved.

----------
nosy: +sehnsucht13

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

From theflossinformation at yandex.com  Sun May  5 16:34:48 2019
From: theflossinformation at yandex.com (The FLOSS Information)
Date: Sun, 05 May 2019 23:34:48 +0300
Subject: [docs] About translation
Message-ID: <20207201557088488@iva8-bad53723c646.qloud-c.yandex.net>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190505/26358943/attachment.html>

From report at bugs.python.org  Mon May  6 09:44:29 2019
From: report at bugs.python.org (Filip Bengtsson)
Date: Mon, 06 May 2019 13:44:29 +0000
Subject: [docs] [issue20906] Issues in Unicode HOWTO
In-Reply-To: <1394702187.81.0.00522221343959.issue20906@psf.upfronthosting.co.za>
Message-ID: <1557150269.17.0.92097644889.issue20906@roundup.psfhosted.org>


Change by Filip Bengtsson <filipbengtsson at live.se>:


----------
pull_requests: +13019

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

From report at bugs.python.org  Mon May  6 09:45:14 2019
From: report at bugs.python.org (Edison Abahurire)
Date: Mon, 06 May 2019 13:45:14 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557150314.36.0.656386104685.issue36783@roundup.psfhosted.org>


Edison Abahurire <abahedison at gmail.com> added the comment:

I'm working on this because I think it should be done complementarily with adding the test for PyDateTime_FromDateAndTimeAndFold at https://bugs.python.org/issue36782. 

#Pycon2019 sprints

----------
nosy: +edison.abahurire

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

From report at bugs.python.org  Mon May  6 09:46:57 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 06 May 2019 13:46:57 +0000
Subject: [docs] [issue35393] Typo in documentation
In-Reply-To: <1543865960.77.0.788709270274.issue35393@psf.upfronthosting.co.za>
Message-ID: <1557150417.7.0.021489860963.issue35393@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

This doc page was re-written as part of bpo-20906, so I am closing this as out of date.

----------
nosy: +cheryl.sabella
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Issues in Unicode HOWTO

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

From report at bugs.python.org  Mon May  6 10:02:00 2019
From: report at bugs.python.org (=?utf-8?q?R=C3=A9mi_Lapeyre?=)
Date: Mon, 06 May 2019 14:02:00 +0000
Subject: [docs] [issue33039] int() and math.trunc don't accept objects that
 only define __index__
In-Reply-To: <1520672231.04.0.467229070634.issue33039@psf.upfronthosting.co.za>
Message-ID: <1557151320.6.0.696132277555.issue33039@roundup.psfhosted.org>


Change by R?mi Lapeyre <remi.lapeyre at henki.fr>:


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

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

From report at bugs.python.org  Mon May  6 10:08:43 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 06 May 2019 14:08:43 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557151723.51.0.112510587253.issue34682@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

This is a good first issue even though there are multiple changes.  Some of the changes are no longer needed since the docs have changed, so please check the current comments and the current docs to see what still needs to be applied.

----------
keywords: +easy
nosy: +cheryl.sabella
type:  -> enhancement
versions:  -Python 2.7, Python 3.6

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

From report at bugs.python.org  Mon May  6 10:11:13 2019
From: report at bugs.python.org (=?utf-8?q?R=C3=A9mi_Lapeyre?=)
Date: Mon, 06 May 2019 14:11:13 +0000
Subject: [docs] [issue33039] int() and math.trunc don't accept objects that
 only define __index__
In-Reply-To: <1520672231.04.0.467229070634.issue33039@psf.upfronthosting.co.za>
Message-ID: <1557151873.07.0.266148452873.issue33039@roundup.psfhosted.org>


R?mi Lapeyre <remi.lapeyre at henki.fr> added the comment:

Hi Cheryl,

thanks for the ping.

I wasn't sure my patch was correct but reading typeobject.c:add_operators(), it is actually more straight-forward than I thought.


Serhiy Storchaka: This is indeed a duplicate of issue20092. I believe the solution proposed by Nick Coghlan is better than the one of Amitava Bhattacharyya, "adding a call to `nb_index` (if that slot exists) in `_PyLong_FromNbInt`" though.


One thing to note regarding the proposed patch: the following stops to work and raises a RecursionError since __index__ == __int__:

        class MyInt(int):
            def __index__(self):
                return int(self) + 1

I changed test_int_subclass_with_index() as `int(self) + 1` is the same thing as `self + 1` for int subclasses. I don't think this sort of code should appear in the wild but if you think it is important not to break compatibility here, I think I could check for number subclasses before overriding __index__.

----------

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

From report at bugs.python.org  Mon May  6 10:12:08 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 06 May 2019 14:12:08 +0000
Subject: [docs] [issue33340] Inaccurate docs on `import` behaviour
In-Reply-To: <1524477096.11.0.682650639539.issue33340@psf.upfronthosting.co.za>
Message-ID: <1557151928.9.0.0696911907687.issue33340@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
nosy: +brett.cannon
type: behavior -> enhancement
versions: +Python 3.8 -Python 3.6

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

From report at bugs.python.org  Mon May  6 10:23:12 2019
From: report at bugs.python.org (Divya Gorantla)
Date: Mon, 06 May 2019 14:23:12 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557152592.26.0.940207213548.issue34682@roundup.psfhosted.org>


Divya Gorantla <divyam9 at gmail.com> added the comment:

I'll be working on this issue

----------
nosy: +divyag

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

From report at bugs.python.org  Mon May  6 10:29:29 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 06 May 2019 14:29:29 +0000
Subject: [docs] [issue33039] int() and math.trunc don't accept objects that
 only define __index__
In-Reply-To: <1520672231.04.0.467229070634.issue33039@psf.upfronthosting.co.za>
Message-ID: <1557152969.16.0.410396517555.issue33039@roundup.psfhosted.org>


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

Then let to continue the discussion on the older issue which has larger discussion.

----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> type() constructor should bind __int__ to __index__ when __index__ is defined and __int__ is not

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

From report at bugs.python.org  Mon May  6 11:08:46 2019
From: report at bugs.python.org (redshiftzero)
Date: Mon, 06 May 2019 15:08:46 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557155326.79.0.976083817589.issue36789@roundup.psfhosted.org>


Change by redshiftzero <jen at redshiftzero.com>:


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

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

From report at bugs.python.org  Mon May  6 13:32:11 2019
From: report at bugs.python.org (Divya Gorantla)
Date: Mon, 06 May 2019 17:32:11 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557163931.81.0.170278486449.issue34682@roundup.psfhosted.org>


Change by Divya Gorantla <divyam9 at gmail.com>:


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

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

From report at bugs.python.org  Mon May  6 13:40:14 2019
From: report at bugs.python.org (Julien Palard)
Date: Mon, 06 May 2019 17:40:14 +0000
Subject: [docs] [issue28795] Misleading stating,
 that SIGINT handler is installed by default
In-Reply-To: <1480026357.5.0.735730414686.issue28795@psf.upfronthosting.co.za>
Message-ID: <1557164414.72.0.254053612312.issue28795@roundup.psfhosted.org>


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


----------
pull_requests: +13034
stage:  -> patch review

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

From report at bugs.python.org  Mon May  6 14:24:29 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 18:24:29 +0000
Subject: [docs] [issue26303] Shared execution context between doctests in a
 module
In-Reply-To: <1454774062.04.0.526927951264.issue26303@psf.upfronthosting.co.za>
Message-ID: <1557167069.47.0.347942567938.issue26303@roundup.psfhosted.org>


anthony shaw <anthonyshaw at apache.org> added the comment:

this issue would be good for pycon sprints

----------
nosy: +Mariatta, anthonypjshaw

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

From report at bugs.python.org  Mon May  6 14:27:22 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 18:27:22 +0000
Subject: [docs] [issue26303] Shared execution context between doctests in a
 module
In-Reply-To: <1454774062.04.0.526927951264.issue26303@psf.upfronthosting.co.za>
Message-ID: <1557167242.68.0.767005774825.issue26303@roundup.psfhosted.org>


Change by anthony shaw <anthonyshaw at apache.org>:


----------
assignee: docs at python -> Mariatta

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

From report at bugs.python.org  Mon May  6 14:32:22 2019
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 06 May 2019 18:32:22 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1557167542.01.0.710273279539.issue36675@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Mon May  6 14:43:18 2019
From: report at bugs.python.org (Dustin Mendoza)
Date: Mon, 06 May 2019 18:43:18 +0000
Subject: [docs] [issue36754] Remove smart quotes in pydoc text
In-Reply-To: <1556560405.97.0.464374588222.issue36754@roundup.psfhosted.org>
Message-ID: <1557168198.79.0.335641422175.issue36754@roundup.psfhosted.org>


Change by Dustin Mendoza <penguindustin at gmail.com>:


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

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

From report at bugs.python.org  Mon May  6 14:49:06 2019
From: report at bugs.python.org (Dustin Mendoza)
Date: Mon, 06 May 2019 18:49:06 +0000
Subject: [docs] [issue36754] Remove smart quotes in pydoc text
In-Reply-To: <1556560405.97.0.464374588222.issue36754@roundup.psfhosted.org>
Message-ID: <1557168546.08.0.963878808075.issue36754@roundup.psfhosted.org>


Dustin Mendoza <penguindustin at gmail.com> added the comment:

In my editor (VSCode) on windows it outputs correctly as a smart quote but if I write the output to a file or the console I get the "?" effect. A sent a PR to replace the smart quotes with escaped quotes but I wonder if we should also do a scan across everything to see if there are more smart quote instances (I'm still pretty new to the entire codebase so I can't say for sure if this is would even be necessary)

----------
nosy: +Giant_Robato

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

From report at bugs.python.org  Mon May  6 15:14:03 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 06 May 2019 19:14:03 +0000
Subject: [docs] [issue36754] Remove smart quotes in pydoc text
In-Reply-To: <1556560405.97.0.464374588222.issue36754@roundup.psfhosted.org>
Message-ID: <1557170043.17.0.227988661672.issue36754@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

So pydoc_topics.py is an auto-generated file, which means we need to fix the generator as well if we decide to go that route.

However, I suspect there's a problem somewhere else causing the console output to not go through stdout correctly. I'm not familiar enough with how help() works to know where.

----------

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

From report at bugs.python.org  Mon May  6 15:32:00 2019
From: report at bugs.python.org (Brian Quinlan)
Date: Mon, 06 May 2019 19:32:00 +0000
Subject: [docs] [issue26374] concurrent_futures Executor.map semantics
 better specified in docs
In-Reply-To: <1455711990.13.0.290959896018.issue26374@psf.upfronthosting.co.za>
Message-ID: <1557171120.4.0.498967315835.issue26374@roundup.psfhosted.org>


Brian Quinlan <brian at sweetapp.com> added the comment:

Can we close this bug then?

----------

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

From report at bugs.python.org  Mon May  6 15:42:01 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 06 May 2019 19:42:01 +0000
Subject: [docs] [issue26374] concurrent_futures Executor.map semantics
 better specified in docs
In-Reply-To: <1455711990.13.0.290959896018.issue26374@psf.upfronthosting.co.za>
Message-ID: <1557171721.15.0.427516586225.issue26374@roundup.psfhosted.org>


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

I would propose closing since the original doc issue regarding order and map in Python 3 is resolved. Just to add there is a PR to make map less eager : https://github.com/python/cpython/pull/707/

----------

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

From report at bugs.python.org  Mon May  6 15:43:33 2019
From: report at bugs.python.org (Brian Quinlan)
Date: Mon, 06 May 2019 19:43:33 +0000
Subject: [docs] [issue26374] concurrent_futures Executor.map semantics
 better specified in docs
In-Reply-To: <1455711990.13.0.290959896018.issue26374@psf.upfronthosting.co.za>
Message-ID: <1557171813.1.0.268496678268.issue26374@roundup.psfhosted.org>


Change by Brian Quinlan <brian at sweetapp.com>:


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

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

From report at bugs.python.org  Mon May  6 15:50:38 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 19:50:38 +0000
Subject: [docs] [issue33971] os.mknod is subject to "umask"
In-Reply-To: <1530020156.39.0.56676864532.issue33971@psf.upfronthosting.co.za>
Message-ID: <1557172238.13.0.293842604242.issue33971@roundup.psfhosted.org>


anthony shaw <anthonyshaw at apache.org> added the comment:

NB: This issue would be good for PyCon sprints

----------
nosy: +anthonypjshaw

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

From report at bugs.python.org  Mon May  6 15:50:59 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 19:50:59 +0000
Subject: [docs] [issue33971] os.mknod is subject to "umask"
In-Reply-To: <1530020156.39.0.56676864532.issue33971@psf.upfronthosting.co.za>
Message-ID: <1557172259.2.0.995427339815.issue33971@roundup.psfhosted.org>


Change by anthony shaw <anthonyshaw at apache.org>:


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

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

From report at bugs.python.org  Mon May  6 16:06:01 2019
From: report at bugs.python.org (Brian Quinlan)
Date: Mon, 06 May 2019 20:06:01 +0000
Subject: [docs] [issue24195] Add `Executor.filter` to concurrent.futures
In-Reply-To: <1431638802.0.0.167827013304.issue24195@psf.upfronthosting.co.za>
Message-ID: <1557173161.57.0.805130845843.issue24195@roundup.psfhosted.org>


Brian Quinlan <brian at sweetapp.com> added the comment:

Hey Ethan, I'm really sorry about dropping the ball on this. I've been burnt out on Python stuff for the last couple of years.

When we left this, it looked like the -1s were in the majority and no one new has jumped on to support `filter`.

If you wanted to add this, I wouldn't object. But I've been inactive so long that I don't think that I should make the decision.

----------

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

From report at bugs.python.org  Mon May  6 16:19:49 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 20:19:49 +0000
Subject: [docs] [issue32971] Docs on unittest.TestCase.assertRaises() should
 clarify context manager details
In-Reply-To: <1519840682.18.0.467229070634.issue32971@psf.upfronthosting.co.za>
Message-ID: <1557173990.0.0.499457648886.issue32971@roundup.psfhosted.org>


Change by anthony shaw <anthonyshaw at apache.org>:


----------
pull_requests:  -9605

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

From report at bugs.python.org  Mon May  6 16:20:48 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 20:20:48 +0000
Subject: [docs] [issue32971] Docs on unittest.TestCase.assertRaises() should
 clarify context manager details
In-Reply-To: <1519840682.18.0.467229070634.issue32971@psf.upfronthosting.co.za>
Message-ID: <1557174048.68.0.261903332709.issue32971@roundup.psfhosted.org>


Change by anthony shaw <anthonyshaw at apache.org>:


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

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

From report at bugs.python.org  Mon May  6 18:08:47 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 22:08:47 +0000
Subject: [docs] [issue31968] exec(): method's default arguments from
 dict-inherited globals
In-Reply-To: <1510058956.93.0.213398074469.issue31968@psf.upfronthosting.co.za>
Message-ID: <1557180527.21.0.805174278731.issue31968@roundup.psfhosted.org>


Change by anthony shaw <anthonyshaw at apache.org>:


----------
pull_requests: +13053

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

From report at bugs.python.org  Mon May  6 18:09:12 2019
From: report at bugs.python.org (anthony shaw)
Date: Mon, 06 May 2019 22:09:12 +0000
Subject: [docs] [issue31968] exec(): method's default arguments from
 dict-inherited globals
In-Reply-To: <1510058956.93.0.213398074469.issue31968@psf.upfronthosting.co.za>
Message-ID: <1557180551.96.0.538823789279.issue31968@roundup.psfhosted.org>


anthony shaw <anthonyshaw at apache.org> added the comment:

Added a PR for the documentation clarification.

----------
nosy: +anthonypjshaw

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

From report at bugs.python.org  Mon May  6 19:09:25 2019
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 06 May 2019 23:09:25 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1557184165.31.0.322339739379.issue33187@roundup.psfhosted.org>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

Hello Anjali,

This PR is still lurking for your updates from almost 11 months. Please let us know if you're still working on this, else, we'll get this in.

Thanks for your work!

----------

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

From report at bugs.python.org  Mon May  6 19:48:23 2019
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 06 May 2019 23:48:23 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
Message-ID: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>


New submission from Sanyam Khurana <sanyam.khurana01 at gmail.com>:

While working on translations, I saw a minor grammatical error in `Doc/glossary.rst`:

```
      * The default Python prompt of the interactive shell when entering 
        code for an indented code block ...
```

should be

```
      * The default Python prompt of the interactive shell when entering  the 
        code for an indented code block ...
```

Attaching the path with this.

----------
assignee: docs at python
components: Documentation
messages: 341665
nosy: CuriousLearner, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Minor grammatical fix in glossary.rst
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Mon May  6 19:50:18 2019
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 06 May 2019 23:50:18 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
In-Reply-To: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>
Message-ID: <1557186618.74.0.315454541866.issue36822@roundup.psfhosted.org>


Change by Sanyam Khurana <sanyam.khurana01 at gmail.com>:


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

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

From report at bugs.python.org  Mon May  6 22:27:11 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 07 May 2019 02:27:11 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557196031.85.0.185461856209.issue36783@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Mon May  6 23:19:49 2019
From: report at bugs.python.org (Edison Abahurire)
Date: Tue, 07 May 2019 03:19:49 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557199188.99.0.558615561687.issue36783@roundup.psfhosted.org>


Edison Abahurire <abahedison at gmail.com> added the comment:

I have submitted a PR to address this. Awaiting Review.

----------

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

From report at bugs.python.org  Tue May  7 01:49:12 2019
From: report at bugs.python.org (SilentGhost)
Date: Tue, 07 May 2019 05:49:12 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
In-Reply-To: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>
Message-ID: <1557208152.17.0.692905848266.issue36822@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
type: enhancement -> behavior
versions:  -Python 3.5, Python 3.6, Python 3.9

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

From report at bugs.python.org  Tue May  7 08:53:12 2019
From: report at bugs.python.org (keroru)
Date: Tue, 07 May 2019 12:53:12 +0000
Subject: [docs] [issue36830] Typo in collections.deque
Message-ID: <1557233592.36.0.483652950266.issue36830@roundup.psfhosted.org>


New submission from keroru <jmdtqj at gmail.com>:

https://docs.python.org/ja/3/library/collections.html#collections.deque

has a typo in description of "rotate(n=1)" in Japanese.
I suppose that "d.appendleft(d.popleft())" should be "d.append(d.popleft())".

Thank you!

----------
assignee: docs at python
components: Documentation
messages: 341715
nosy: docs at python, keroru
priority: normal
severity: normal
status: open
title: Typo in collections.deque
versions: Python 3.7

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

From report at bugs.python.org  Tue May  7 09:03:44 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 07 May 2019 13:03:44 +0000
Subject: [docs] [issue36830] Typo in collections.deque
In-Reply-To: <1557233592.36.0.483652950266.issue36830@roundup.psfhosted.org>
Message-ID: <1557234224.93.0.35503851059.issue36830@roundup.psfhosted.org>


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

Thank you for the report. English translation has the following text and I guess you are right at [0] . The tracker deals with English translation. Please consider reporting this to https://github.com/python/python-docs-ja which also accepts PR.

[0] https://docs.python.org/3/library/collections.html#collections.deque.rotate

    Rotate the deque n steps to the right. If n is negative, rotate to the left.

    When the deque is not empty, rotating one step to the right is equivalent to d.appendleft(d.pop()), and rotating one step to the left is equivalent to d.append(d.popleft()).

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

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

From report at bugs.python.org  Tue May  7 09:04:49 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 07 May 2019 13:04:49 +0000
Subject: [docs] [issue36830] Typo in collections.deque
In-Reply-To: <1557233592.36.0.483652950266.issue36830@roundup.psfhosted.org>
Message-ID: <1557234289.13.0.823216810939.issue36830@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi @keroru,

This is issue is related to the Japanese translation, not to the official documentation.

Please, try to contact the translators. 

I am adding Julien, maybe he has the contact of the translators.

----------
nosy: +matrixise, mdk
resolution:  -> wont fix
status: open -> pending

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

From report at bugs.python.org  Tue May  7 09:13:11 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 07 May 2019 13:13:11 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557234791.57.0.940749659673.issue36794@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi hniksic,

Could you add your Github Account to your BPO account, without that, we can't work on your PR, and you need to sign the CLA.

Thank you

----------
nosy: +matrixise

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

From report at bugs.python.org  Tue May  7 10:35:02 2019
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Tue, 07 May 2019 14:35:02 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557239702.89.0.42645991452.issue36794@roundup.psfhosted.org>


Hrvoje Nik?i? <hniksic at gmail.com> added the comment:

How do I connect the accounts?

Please note that I've previously submitted PRs which have been accepted, e.g. https://bugs.python.org/issue34476 and https://bugs.python.org/issue35465

----------

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

From report at bugs.python.org  Tue May  7 10:54:16 2019
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Tue, 07 May 2019 14:54:16 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557240856.85.0.470278812503.issue36794@roundup.psfhosted.org>


Hrvoje Nik?i? <hniksic at gmail.com> added the comment:

Ok, found it, and I've now updated the github name on my bpo account. I'll gladly sign the CLA if needed, I thought it wasn't necessary for small changes based on previous experience. Please advise whether it's necessary here.

----------

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

From report at bugs.python.org  Tue May  7 11:00:27 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 07 May 2019 15:00:27 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557241227.34.0.188613580756.issue36783@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset 5765ecf79fcee987f2f97c246c64b494324dfd33 by Cheryl Sabella (Edison A) in branch 'master':
bpo-36783: Added C API Documentation for Time_FromTimeAndFold and PyDateTime_FromDateAndTimeAndFold (GH-13147)
https://github.com/python/cpython/commit/5765ecf79fcee987f2f97c246c64b494324dfd33


----------

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

From report at bugs.python.org  Tue May  7 11:00:43 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 15:00:43 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557241243.13.0.375716323238.issue36783@roundup.psfhosted.org>


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


----------
pull_requests: +13073

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

From report at bugs.python.org  Tue May  7 11:04:59 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 07 May 2019 15:04:59 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557241499.55.0.311382222765.issue36783@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Tue May  7 11:06:54 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 07 May 2019 15:06:54 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557241614.53.0.253204696366.issue36783@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@edison.abahurire, thanks for the PR!

----------

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

From report at bugs.python.org  Tue May  7 11:06:54 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 07 May 2019 15:06:54 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557241614.56.0.901689503502.issue36794@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

If I read the Licensing section into the devguide, a contributor (me, your, etc..) has to sign the CLA. 

https://devguide.python.org/pullrequest/#cla

"To accept your change we must have your formal approval for distributing your work under the PSF license."

the verb is must -> required!

Thank you

----------

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

From report at bugs.python.org  Tue May  7 11:17:53 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 15:17:53 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557242272.98.0.835954432662.issue36783@roundup.psfhosted.org>


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


New changeset 146010ea42fb949a48a1b79a13503995a5176833 by Miss Islington (bot) in branch '3.7':
bpo-36783: Added C API Documentation for Time_FromTimeAndFold and PyDateTime_FromDateAndTimeAndFold (GH-13147)
https://github.com/python/cpython/commit/146010ea42fb949a48a1b79a13503995a5176833


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

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

From report at bugs.python.org  Tue May  7 11:27:53 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 15:27:53 +0000
Subject: [docs] [issue28795] Misleading stating,
 that SIGINT handler is installed by default
In-Reply-To: <1480026357.5.0.735730414686.issue28795@psf.upfronthosting.co.za>
Message-ID: <1557242873.02.0.103307780564.issue28795@roundup.psfhosted.org>


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


New changeset e85ef7a7eacdef2f43e6bf2e67f335100e7ef2da by Julien Palard in branch 'master':
bpo-28795: Signal documentation: Fix misleading statement. (GH-13121)
https://github.com/python/cpython/commit/e85ef7a7eacdef2f43e6bf2e67f335100e7ef2da


----------

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

From report at bugs.python.org  Tue May  7 11:28:00 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 15:28:00 +0000
Subject: [docs] [issue28795] Misleading stating,
 that SIGINT handler is installed by default
In-Reply-To: <1480026357.5.0.735730414686.issue28795@psf.upfronthosting.co.za>
Message-ID: <1557242880.33.0.334375927076.issue28795@roundup.psfhosted.org>


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


----------
pull_requests: +13075

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

From report at bugs.python.org  Tue May  7 11:28:21 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 15:28:21 +0000
Subject: [docs] [issue28795] Misleading stating,
 that SIGINT handler is installed by default
In-Reply-To: <1480026357.5.0.735730414686.issue28795@psf.upfronthosting.co.za>
Message-ID: <1557242901.55.0.309530235694.issue28795@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue May  7 11:29:33 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 15:29:33 +0000
Subject: [docs] [issue28795] Misleading stating,
 that SIGINT handler is installed by default
In-Reply-To: <1480026357.5.0.735730414686.issue28795@psf.upfronthosting.co.za>
Message-ID: <1557242973.05.0.0130169896212.issue28795@roundup.psfhosted.org>


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

Thanks for reporting Jan! It's finally merged \o/

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

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

From report at bugs.python.org  Tue May  7 11:48:17 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 07 May 2019 15:48:17 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557244097.13.0.388940276647.issue36794@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

I would say that unblock order is an implementation detail (which is unlikely be changed though).

I'm biased how should we document it.
Yuri, your opinion is very welcome.

----------

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

From report at bugs.python.org  Tue May  7 11:55:42 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 15:55:42 +0000
Subject: [docs] [issue28795] Misleading stating,
 that SIGINT handler is installed by default
In-Reply-To: <1480026357.5.0.735730414686.issue28795@psf.upfronthosting.co.za>
Message-ID: <1557244542.77.0.122630236571.issue28795@roundup.psfhosted.org>


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


New changeset 721729fca4fab9fd11861844880b3f3780015ae0 by Miss Islington (bot) in branch '3.7':
bpo-28795: Signal documentation: Fix misleading statement. (GH-13121)
https://github.com/python/cpython/commit/721729fca4fab9fd11861844880b3f3780015ae0


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

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

From report at bugs.python.org  Tue May  7 12:26:55 2019
From: report at bugs.python.org (Brian Quinlan)
Date: Tue, 07 May 2019 16:26:55 +0000
Subject: [docs] [issue22630]
 `concurrent.futures.Future.set_running_or_notify_cancel` does not notify
 cancel
In-Reply-To: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za>
Message-ID: <1557246415.53.0.405011722479.issue22630@roundup.psfhosted.org>


Brian Quinlan <brian at sweetapp.com> added the comment:

Ben, do you still think that your patch is relevant or shall we close this bug?

----------

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

From report at bugs.python.org  Tue May  7 13:05:27 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 17:05:27 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557248727.13.0.0565689276128.issue11001@roundup.psfhosted.org>


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


New changeset 91cc01f40eec03ece2d6b04ad9ea786e77707d8d by Miss Islington (bot) (Julia Iliuk) in branch 'master':
bpo-11001: updated cookie docs (GH-13086)
https://github.com/python/cpython/commit/91cc01f40eec03ece2d6b04ad9ea786e77707d8d


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

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

From report at bugs.python.org  Tue May  7 13:05:40 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 17:05:40 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557248740.57.0.865742429665.issue11001@roundup.psfhosted.org>


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


----------
pull_requests: +13080

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

From report at bugs.python.org  Tue May  7 13:32:48 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 07 May 2019 17:32:48 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557250368.66.0.0722391143652.issue11001@roundup.psfhosted.org>


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


New changeset 1fe722cf14db0f786d6df1ff4392f44d37a9f867 by Miss Islington (bot) in branch '3.7':
[3.7] bpo-11001: updated cookie docs (GH-13086) (GH-13161)
https://github.com/python/cpython/commit/1fe722cf14db0f786d6df1ff4392f44d37a9f867


----------

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

From report at bugs.python.org  Tue May  7 13:34:46 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 07 May 2019 17:34:46 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1557250486.88.0.827491165625.issue11001@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

Thanks Julia!

----------
nosy: +gregory.p.smith
resolution:  -> fixed
stage: patch review -> commit review
status: open -> closed

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

From report at bugs.python.org  Tue May  7 16:08:39 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 20:08:39 +0000
Subject: [docs] [issue31589] Links for French documentation PDF is broken:
 LaTeX issue with non-ASCII characters?
In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za>
Message-ID: <1557259719.39.0.296939329324.issue31589@roundup.psfhosted.org>


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

The download links are now working, EWDurbin upgraded the servers and it solved a few issues, also now when a build fail we do no longer erase the old PDF, so the links should always work.

Thanks for reporting and don't hesistate to open a new issue if problem happen again (but maybe on the https://github.com/python/docsbuild-scripts/ issue tracker).

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

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

From report at bugs.python.org  Tue May  7 16:13:54 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 20:13:54 +0000
Subject: [docs] [issue36830] Typo in collections.deque
In-Reply-To: <1557233592.36.0.483652950266.issue36830@roundup.psfhosted.org>
Message-ID: <1557260034.08.0.37889252813.issue36830@roundup.psfhosted.org>


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

I reopened the issue on the ja tracker: https://github.com/python/python-docs-ja/issues/20 and I'm closing it here.

Thanks a lot keroru for reporting!

----------
stage:  -> resolved
status: pending -> closed

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

From report at bugs.python.org  Tue May  7 16:42:36 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 20:42:36 +0000
Subject: [docs] [issue20709] os.utime(path_to_directory): wrong
 documentation for Windows.
In-Reply-To: <1392937056.04.0.541478480244.issue20709@psf.upfronthosting.co.za>
Message-ID: <1557261756.28.0.282246762043.issue20709@roundup.psfhosted.org>


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

Closing this issue, it has been fixed a year ago, thanks Jan-Philip for reporting, St?phane for fixing, and everybody! \o/ \o/

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

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

From report at bugs.python.org  Tue May  7 17:21:25 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 21:21:25 +0000
Subject: [docs] [issue24712] Docs page's sidebar vibrates on mouse wheel
 scroll on Chrome.
In-Reply-To: <1437780127.19.0.0270083299372.issue24712@psf.upfronthosting.co.za>
Message-ID: <1557264085.89.0.559932011923.issue24712@roundup.psfhosted.org>


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


----------
pull_requests: +13095
stage: needs patch -> patch review

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

From report at bugs.python.org  Tue May  7 17:23:06 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 21:23:06 +0000
Subject: [docs] [issue32393] nav menu jitter in old documentation
In-Reply-To: <1513810852.69.0.213398074469.issue32393@psf.upfronthosting.co.za>
Message-ID: <1557264186.71.0.0312129736416.issue32393@roundup.psfhosted.org>


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

I'm closing this as a duplicate of https://bugs.python.org/issue24712, for which I opened a pull request.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Docs page's sidebar vibrates on mouse wheel scroll on Chrome.

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

From report at bugs.python.org  Tue May  7 17:29:25 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 07 May 2019 21:29:25 +0000
Subject: [docs] [issue33948] doc truncated lines in PDF
In-Reply-To: <1529772775.32.0.56676864532.issue33948@psf.upfronthosting.co.za>
Message-ID: <1557264565.01.0.339936079607.issue33948@roundup.psfhosted.org>


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

We recentrly upgraded our PDF build toolchain and I don't see it happen again.

Don't hesitate to reopen if you find another occurence of it.

Thanks for reporting!

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

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

From report at bugs.python.org  Tue May  7 18:41:45 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 07 May 2019 22:41:45 +0000
Subject: [docs] [issue31589] Links for French documentation PDF is broken:
 LaTeX issue with non-ASCII characters?
In-Reply-To: <1557259719.39.0.296939329324.issue31589@roundup.psfhosted.org>
Message-ID: <CA+3bQGF3h=M4ysE_MYeJZXE7fUo_n7Mzk=dbD1QtRMqPDL3cxw@mail.gmail.com>


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

Thanks Julien for taking care of the documentation :-) It is good to have
you aboard.

----------

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

From report at bugs.python.org  Wed May  8 07:13:00 2019
From: report at bugs.python.org (mbiggs)
Date: Wed, 08 May 2019 11:13:00 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557313980.57.0.565174563986.issue36789@roundup.psfhosted.org>


Change by mbiggs <pythonbugs at doubleplum.net>:


----------
pull_requests: +13102

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

From report at bugs.python.org  Wed May  8 09:32:13 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 08 May 2019 13:32:13 +0000
Subject: [docs] [issue24712] Docs page's sidebar vibrates on mouse wheel
 scroll on Chrome.
In-Reply-To: <1437780127.19.0.0270083299372.issue24712@psf.upfronthosting.co.za>
Message-ID: <1557322333.26.0.78306364995.issue24712@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:


New changeset 8ab24b2ebcf99f703f00297cb3a0c3ff857eecf8 by St?phane Wirtel (Julien Palard) in branch '2.7':
[2.7] bpo-24712: Doc: Make sidebar sticky using browser support. (GH-13179)
https://github.com/python/cpython/commit/8ab24b2ebcf99f703f00297cb3a0c3ff857eecf8


----------
nosy: +matrixise

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

From report at bugs.python.org  Wed May  8 09:39:53 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 08 May 2019 13:39:53 +0000
Subject: [docs] [issue24712] Docs page's sidebar vibrates on mouse wheel
 scroll on Chrome.
In-Reply-To: <1437780127.19.0.0270083299372.issue24712@psf.upfronthosting.co.za>
Message-ID: <1557322793.48.0.233607256051.issue24712@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


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

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

From report at bugs.python.org  Wed May  8 12:02:41 2019
From: report at bugs.python.org (Julien Palard)
Date: Wed, 08 May 2019 16:02:41 +0000
Subject: [docs] [issue31873] Inconsistent capitalization of proper noun -
 Unicode.
In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za>
Message-ID: <1557331361.86.0.548165744798.issue31873@roundup.psfhosted.org>


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


New changeset 85225b6a58a516c50c055d5114668ed2fcdcda8c by Julien Palard (toonarmycaptain) in branch 'master':
bpo-31873: Update unicode.rst - 'unicode' capitalization (GH-4125)
https://github.com/python/cpython/commit/85225b6a58a516c50c055d5114668ed2fcdcda8c


----------

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

From report at bugs.python.org  Wed May  8 12:03:28 2019
From: report at bugs.python.org (Jason R. Coombs)
Date: Wed, 08 May 2019 16:03:28 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
Message-ID: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>


New submission from Jason R. Coombs <jaraco at jaraco.com>:

In working on some docs contributions, I've run into issues where docs builds are failing in CI differently than they're failing locally.

Locally, running `make venv` from `Docs/` results in Sphinx 2, whereas on Azure Pipelines, the docs are built with Sphinx 1.8.2 (https://github.com/python/cpython/blob/1d4b16051f8550fd7dada3670a3e83ae13b99d3b/.azure-pipelines/docs-steps.yml#L15).

When running with Sphinx 2, this error emerges when running `make suspicious` when a change is around that triggers suspicious code (such as this commit https://github.com/python/cpython/pull/12547/commits/9bde7faf6f051d4a7306ac8629d915ce069392f7):

Exception occurred:
  File "/Users/jaraco/code/public/cpython/Doc/tools/extensions/suspicious.py", line 154, in report_issue
    self.warn('[%s:%d] "%s" found in "%-.120s"' %
AttributeError: 'CheckSuspiciousMarkupBuilder' object has no attribute 'warn'

First, we probably want to make these processes consistent (define the dependencies in exactly one place).

Second, we should probably determine why the doc builds are failing on Sphinx 2 and update the `suspicious` code to support Sphinx 2.

----------
assignee: docs at python
components: Documentation
messages: 341897
nosy: docs at python, jaraco
priority: normal
severity: normal
status: open
title: inconsistencies in docs builds (Sphinx 2)
type: compile error
versions: Python 3.8

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

From report at bugs.python.org  Wed May  8 12:05:07 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 08 May 2019 16:05:07 +0000
Subject: [docs] [issue31873] Inconsistent capitalization of proper noun -
 Unicode.
In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za>
Message-ID: <1557331507.94.0.82900343741.issue31873@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +13105

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

From report at bugs.python.org  Wed May  8 12:07:04 2019
From: report at bugs.python.org (Julien Palard)
Date: Wed, 08 May 2019 16:07:04 +0000
Subject: [docs] [issue31873] Inconsistent capitalization of proper noun -
 Unicode.
In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za>
Message-ID: <1557331623.96.0.796433243371.issue31873@roundup.psfhosted.org>


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

I merged it, it's a small change that is consistent enough for me with the rest of the file and the doc. Marc-Andre is right though, and if anyone have the courage, the whole doc should be proofread to update accordingly, but let's make it a whole other PR.

Thanks David for your contribution and sorry for the delay.

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

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

From report at bugs.python.org  Wed May  8 12:34:15 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 08 May 2019 16:34:15 +0000
Subject: [docs] [issue31873] Inconsistent capitalization of proper noun -
 Unicode.
In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za>
Message-ID: <1557333255.67.0.283490403406.issue31873@roundup.psfhosted.org>


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


New changeset ed8860c5af87d78d312ae30dd2d6bedc60bd86e5 by Miss Islington (bot) in branch '3.7':
bpo-31873: Update unicode.rst - 'unicode' capitalization (GH-4125)
https://github.com/python/cpython/commit/ed8860c5af87d78d312ae30dd2d6bedc60bd86e5


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

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

From report at bugs.python.org  Wed May  8 13:52:03 2019
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 08 May 2019 17:52:03 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557337923.18.0.614542868394.issue36783@roundup.psfhosted.org>


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


----------
pull_requests: +13115

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

From report at bugs.python.org  Wed May  8 14:54:59 2019
From: report at bugs.python.org (Ying Wang)
Date: Wed, 08 May 2019 18:54:59 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1557341699.93.0.339073644984.issue36620@roundup.psfhosted.org>


Ying Wang <yingw787.personal at gmail.com> added the comment:

I would like to take a stab at this as a first-time CPython contributor.

----------
nosy: +Ying Wang

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

From report at bugs.python.org  Wed May  8 16:01:26 2019
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 08 May 2019 20:01:26 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1557345686.3.0.492850087914.issue36620@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed May  8 16:36:56 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 08 May 2019 20:36:56 +0000
Subject: [docs] [issue36858] f-string '=' debugging output needs to be
 documented
Message-ID: <1557347816.05.0.714667733239.issue36858@roundup.psfhosted.org>


New submission from Eric V. Smith <eric at trueblade.com>:

There are two problems here: what to call this feature, and where to put it.

The current f-string documentation is in Doc/reference/lexical_analysis.rst, which I'm not sure is the best place to add discussion about how this feature works. This feature is run-time behavior, and goes beyond what the lexer documentation should show.

----------
assignee: docs at python
components: Documentation
messages: 341941
nosy: docs at python, eric.smith
priority: normal
severity: normal
status: open
title: f-string '=' debugging output needs to be documented
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Wed May  8 17:46:59 2019
From: report at bugs.python.org (mbiggs)
Date: Wed, 08 May 2019 21:46:59 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1557352019.23.0.758380405055.issue36789@roundup.psfhosted.org>


mbiggs <pythonbugs at doubleplum.net> added the comment:

Ah sent a pull request but didn't realize that redshiftzero already had.  Their PR looks good to me.

Thanks for fixing this!

----------

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

From report at bugs.python.org  Wed May  8 21:07:47 2019
From: report at bugs.python.org (anthony shaw)
Date: Thu, 09 May 2019 01:07:47 +0000
Subject: [docs] [issue12188] PEP 7 (or guide) add C style policies and
 explanation
In-Reply-To: <1306433972.91.0.882585972593.issue12188@psf.upfronthosting.co.za>
Message-ID: <1557364067.63.0.139496896496.issue12188@roundup.psfhosted.org>


anthony shaw <anthonyshaw at apache.org> added the comment:

Hi,

This discussion came to a stop, but it doesn't seem conclusive.

PEP discussions are now in GitHub on https://github.com/python/peps/issues so I'm going to close this BPO issue.

There is no additional section in PEP 7 for this level of detail, there is also no tooling in place (afaik) to retroactively apply or inspect these types of issues, so this would need to be discussed in the PEP issue,

----------
nosy: +anthonypjshaw
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed May  8 23:40:43 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 09 May 2019 03:40:43 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1557373243.02.0.0730663254378.issue36620@roundup.psfhosted.org>


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

Sorry, I don't want to do this in the summary table.  The goal of the table is to provide a minimal overview to help select the appropriate itertool and to provide a fast link to the details given below.

----------
assignee: Mariatta -> rhettinger

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

From report at bugs.python.org  Wed May  8 23:46:20 2019
From: report at bugs.python.org (Ying Wang)
Date: Thu, 09 May 2019 03:46:20 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1557373580.25.0.259002912386.issue36620@roundup.psfhosted.org>


Ying Wang <yingw787.personal at gmail.com> added the comment:

@rhettinger should this issue be closed if no action is to be taken? If so, should I manually close the pull request referencing this issue, or will that be automatically handled by the Python bug tracker?

----------

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

From report at bugs.python.org  Thu May  9 07:54:49 2019
From: report at bugs.python.org (Jules Lasne)
Date: Thu, 09 May 2019 11:54:49 +0000
Subject: [docs] [issue36864] Double Spaces in the documentation
Message-ID: <1557402889.33.0.243843870102.issue36864@roundup.psfhosted.org>


New submission from Jules Lasne <jules.lasne at gmail.com>:

Hello,

I've come to open this issue today because of the apparent split there is in the documentation about double spaces after a period.

Here is a link to an article explaining some of the issue
https://www.writing-skills.com/one-space-two-full-stop

Anyway, the opinion isn't really important here but, when translating the documentation we waste a lot of time removing the double spaces that are ugly and useless in French.

I'd like to propose a PR to remove all double spaces after a period from the documentation as they serve no apparent purpose.

I'm open for discussion of course

----------
assignee: docs at python
components: Documentation
messages: 341977
nosy: docs at python, seluj78
priority: normal
severity: normal
status: open
title: Double Spaces in the documentation

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

From report at bugs.python.org  Thu May  9 08:11:18 2019
From: report at bugs.python.org (Jules Lasne)
Date: Thu, 09 May 2019 12:11:18 +0000
Subject: [docs] [issue36864] Double Spaces in the documentation
In-Reply-To: <1557402889.33.0.243843870102.issue36864@roundup.psfhosted.org>
Message-ID: <1557403878.35.0.649574058385.issue36864@roundup.psfhosted.org>


Change by Jules Lasne <jules.lasne at gmail.com>:


----------
nosy: +matrixise, mdk

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

From report at bugs.python.org  Thu May  9 10:15:44 2019
From: report at bugs.python.org (Julien Palard)
Date: Thu, 09 May 2019 14:15:44 +0000
Subject: [docs] [issue36864] Double Spaces in the documentation
In-Reply-To: <1557402889.33.0.243843870102.issue36864@roundup.psfhosted.org>
Message-ID: <1557411344.74.0.981623371992.issue36864@roundup.psfhosted.org>


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

Some people are liking the double space thing. Some are not.

It's in the documentation style guide [1] and there's arond 20k use of it.

I don't think we want to change it: modifing 18900 lines in the docs will make most opened PRs conflict, we don't want that. Also it'll pollute git blame a lot. Also it'll mark most translations as fuzzy in all languages, nobody want that.

You say it costs you time removing them from the translation, just don't remove them, and if you don't like them nobody will complain if you're not typing them both while translating.

[1]: https://devguide.python.org/documenting/#use-of-whitespace

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

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

From report at bugs.python.org  Thu May  9 14:15:47 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Thu, 09 May 2019 18:15:47 +0000
Subject: [docs] [issue36868] New behavior of OpenSSL hostname verification
 not exposed, incorrectly documented
Message-ID: <1557425747.49.0.948212766878.issue36868@roundup.psfhosted.org>


New submission from Josh Rosenberg <shadowranger+python at gmail.com>:

The What's New in 3.7 docs mention the change from #31399 to use OpenSSL's built-in hostname verification ( https://docs.python.org/3/whatsnew/3.7.html#ssl ), but aside from that, information about the change is largely undiscoverable and/or wrong.

Specific problems:

1. The What's New docs repeatedly mention SSLContext.host_flags as the means of modifying behavior. The actual property is underscore prefixed though, as SSLContext._host_flags. Since SSLContext supports the creation of arbitrary names via __dict__, assigning to context.host_flags silently "works", it just fails to *do* anything (nothing ever reads it).

2. None of the flags are documented anywhere; the only way to discover them is to import _ssl (they're not exposed on ssl itself, just the internal C extension), then scan through the exposed names (they're all prefixed with HOSTFLAG_ AFAICT)

3. All of the flags are raw numeric values, but it seems like they should be IntEnums, like the other flags exposed by SSL (among other things, it would make it much easier to interpret the default _host_flags (currently it's just 4, when it could display as <HostFlags.HOSTFLAG_NO_PARTIAL_WILDCARDS: 4>)

4. Nothing about this change, _host_flags/host_flags, or the values of the flags themselves is mentioned on the ssl docs at all.

5. This unintentionally made a behavioral change (one that bit me, and may bite other folks using docker swarm, NETBIOS hostnames, etc.). Python's match_hostname implementation was fine with host names containing underscores (e.g. if the cert was wildcarded to *.example.com, it would match a_b_c.example.com just fine); they're not technically legal by the strict reading of the specs for host names (they're apparently legal for domain names, but not host names, which differ in ways I don't fully understand), but stuff like docker swarm names their services that way automatically, most (all?) browsers support visiting them, etc. It looks like OpenSSL (at least the 1.1.0g my Python 3.7.2 was built against) treats underscores as unmatchable, so any attempt to connect to such a host name in Python 3.7.2 dies with a SSLCertVerificationError, claiming a "Hostname mismatch, certificate is not valid for 'name_with_underscores.example.com'."

I discovered all this because 3.7 broke some scripts I use to connect to docker swarm services. Before I realized the issue was underscores, I was trying to figure out how to tweak the host name checks (assuming maybe something was broken with wildcard matching), and stumbled across all the other issues with the docs, the lack of flag definition exposure, etc.

For the record, I think it's reasonable to require legal host names (it was easy enough to fix for my case; I just updated our docker DNS server to provide aliases using only hyphens and changed the script to use the alias host names), but it would be nice if it was explicitly documented, and ideally, that Python itself recognize that underscores won't work and explicitly raise an exception saying why, rather than letting OpenSSL perform the rejection with a (to someone who doesn't know about the underscore issue) confusing error message.

----------
assignee: docs at python
components: Documentation, Extension Modules, Library (Lib), SSL
keywords: 3.6regression
messages: 341990
nosy: christian.heimes, docs at python, josh.r, vstinner
priority: normal
severity: normal
status: open
title: New behavior of OpenSSL hostname verification not exposed, incorrectly documented
type: behavior
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu May  9 14:40:00 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 09 May 2019 18:40:00 +0000
Subject: [docs] [issue36868] New behavior of OpenSSL hostname verification
 not exposed, incorrectly documented
In-Reply-To: <1557425747.49.0.948212766878.issue36868@roundup.psfhosted.org>
Message-ID: <1557427200.51.0.563963557273.issue36868@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu May  9 14:45:30 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 09 May 2019 18:45:30 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
In-Reply-To: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>
Message-ID: <1557427530.75.0.584684720527.issue36853@roundup.psfhosted.org>


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


----------
nosy: +mdk

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

From report at bugs.python.org  Thu May  9 15:49:55 2019
From: report at bugs.python.org (Julien Palard)
Date: Thu, 09 May 2019 19:49:55 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
In-Reply-To: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>
Message-ID: <1557431395.96.0.749499369571.issue36853@roundup.psfhosted.org>


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

Hi Jaraco,

We're using sphinx 1.8 in production (docs.python.org) but we're ready for sphinx 2 so we should upgrade, and when we'll upgrade, we'll upgrade it everywhere.

You're right, `make venv` does not specify a version, at the sphinx 2 bump we'll have to pin it here too and try to get a single point of truth about which version we're using.

I've just locally ran sphinx 2.0.0 on 071cbd4ea1 (the current tip of your PR) and I'm not getting any error, which one are you getting?

----------

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

From report at bugs.python.org  Thu May  9 15:52:37 2019
From: report at bugs.python.org (Julien Palard)
Date: Thu, 09 May 2019 19:52:37 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1557431557.66.0.736690883798.issue32523@roundup.psfhosted.org>


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


New changeset 137be34180a20dba53948d126b961069f299f153 by Julien Palard in branch 'master':
bpo-32523: Simplifying news entries with multiple paragraphs. (GH-8154)
https://github.com/python/cpython/commit/137be34180a20dba53948d126b961069f299f153


----------

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

From report at bugs.python.org  Thu May  9 16:15:51 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 09 May 2019 20:15:51 +0000
Subject: [docs] [issue10536] Enhancements to gettext docs
In-Reply-To: <1290730924.88.0.289473332428.issue10536@psf.upfronthosting.co.za>
Message-ID: <1557432951.97.0.131773585842.issue10536@roundup.psfhosted.org>


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


----------
pull_requests: +13134
stage:  -> patch review

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

From report at bugs.python.org  Thu May  9 16:26:05 2019
From: report at bugs.python.org (SilentGhost)
Date: Thu, 09 May 2019 20:26:05 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
In-Reply-To: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>
Message-ID: <1557433565.81.0.437055792301.issue36853@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

> Second, we should probably determine why the doc builds are failing on Sphinx 2 and update the `suspicious` code to support Sphinx 2.

They're failing because in sphinx 2 old and deprecated (since 1.6) custom logging API was removed. So all Builder.warn calls will have to be changed to use logging module (this applies to other similar methods, luckily they had the same names as logging methods).

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

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

From report at bugs.python.org  Thu May  9 16:26:14 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 09 May 2019 20:26:14 +0000
Subject: [docs] [issue10536] Enhancements to gettext docs
In-Reply-To: <1290730924.88.0.289473332428.issue10536@psf.upfronthosting.co.za>
Message-ID: <1557433573.97.0.751028797372.issue10536@roundup.psfhosted.org>


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


New changeset 98b360e27b0be4646ed24c5a7ac07112ca020982 by Miss Islington (bot) in branch '3.7':
[3.7] bpo-10536: Enhancements to gettext docs (GH-10324) (GH-13224)
https://github.com/python/cpython/commit/98b360e27b0be4646ed24c5a7ac07112ca020982


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

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

From report at bugs.python.org  Thu May  9 16:26:53 2019
From: report at bugs.python.org (Julien Palard)
Date: Thu, 09 May 2019 20:26:53 +0000
Subject: [docs] [issue10536] Enhancements to gettext docs
In-Reply-To: <1290730924.88.0.289473332428.issue10536@psf.upfronthosting.co.za>
Message-ID: <1557433613.26.0.25966281948.issue10536@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu May  9 18:25:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 09 May 2019 22:25:53 +0000
Subject: [docs] [issue36868] New behavior of OpenSSL hostname verification
 not exposed, incorrectly documented
In-Reply-To: <1557425747.49.0.948212766878.issue36868@roundup.psfhosted.org>
Message-ID: <1557440753.21.0.507063990217.issue36868@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at redhat.com>:


----------
nosy:  -vstinner

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

From report at bugs.python.org  Thu May  9 20:22:58 2019
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 10 May 2019 00:22:58 +0000
Subject: [docs] [issue36858] f-string '=' debugging output needs to be
 documented
In-Reply-To: <1557347816.05.0.714667733239.issue36858@roundup.psfhosted.org>
Message-ID: <1557447778.6.0.763959071731.issue36858@roundup.psfhosted.org>


Mariatta Wijaya <mariatta at python.org> added the comment:

Related issue where the '=' debug mode was implemented: https://bugs.python.org/issue36817

----------
nosy: +Mariatta
stage:  -> needs patch

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

From benedic.cater at innogen-pharma.com  Thu May  9 20:36:22 2019
From: benedic.cater at innogen-pharma.com (Benedic Cater)
Date: Fri, 10 May 2019 08:36:22 +0800
Subject: [docs] Bugs in Python a,b=-6,-6
Message-ID: <CAKDC_f1RyA2jtVTbYhYS+iNhxhNO_PsCH33BvYCXPPf2jJsyXA@mail.gmail.com>

Good day!

I think I found a bug? it's suppose to be True, am I right?
a,b = -5,-5
id(a) == id(b)
*True*

a,b = -6,-6
id(a) == id(b)
*False*

[image: image.png]

*Benedic P. Cater*
*IT MANAGER*

*InnoGen Pharmaceuticals, Inc.*
*No. 124-126 Sct. Dr. Lazcano St.,*
*Brgy, Sacred Heart, Quezon City*

*Tel No: (02) 410-46-13 upto 22 Loc.114*
*Mobile No: +639167588883*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190510/0b59c0dc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 17701 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190510/0b59c0dc/attachment-0001.png>

From report at bugs.python.org  Thu May  9 22:36:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 10 May 2019 02:36:07 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1557455767.38.0.398644983025.issue36345@roundup.psfhosted.org>


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

Berker Peksag:
> Please revert 360e1e4c519cfc139de707bcdd1e6c871eec79ee. It's not a good example to put into the documentation.

I looked at other examples: they are nice but far from a "real application". I like the last example which combines multiple wsgiref features and is written like a real application: parse command line arguments, handle CTRL+c, etc.


> It uses different naming convention. It would only confuse users relatively new to the wsgiref module and WSGI protocol.

Would you mind to elaborate? I don't understand what you mean by "naming convention" here, sorry.


> FileWrapper was supposed to support __getitem__ and __iter__ protocols for compatibility with older Python versions, but its __getiem__ implementation is buggy and is already deprecated. It has no use case in modern Python code.

Do you mean that app() must not return FileWrapper? How do you return file content in that case?

Maybe FileWrapper API should be clarified? It's surprising to read Python 3.8 mentioning compatibility with Python 2.1 :-)


> It has zero exception handling and will return a cryptic traceback if mimetype cannot detect type of the file.

Which kind of exceptions do you expect? The example checks if the file exists for example.

----------

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

From report at bugs.python.org  Thu May  9 23:41:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 10 May 2019 03:41:31 +0000
Subject: [docs] [issue36873] http.server: Document explicitly that symbolic
 links are followed
Message-ID: <1557459691.12.0.556693975132.issue36873@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at redhat.com>:

http.server documentation starts with a red warning:

"Warning: http.server is not recommended for production. It only implements basic security checks."

https://docs.python.org/dev/library/http.server.html

It would help to be even more explicit on what it means. For example, document that symbolic links are followed and SimpleHTTPRequestHandler directory can be "escaped" following symbolic links.

----------
assignee: docs at python
components: Documentation
messages: 342054
nosy: docs at python, vstinner
priority: normal
severity: normal
status: open
title: http.server: Document explicitly that symbolic links are followed
type: security
versions: Python 3.8

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

From report at bugs.python.org  Fri May 10 04:00:27 2019
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 10 May 2019 08:00:27 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1557475227.77.0.241578615425.issue36345@roundup.psfhosted.org>


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

> I looked at other examples: they are nice but far from a "real application".

You can use the same argument for pretty much every example in the stdlib documentation :)

wsgiref is a low level module, users should use projects like WebOb instead. Also, a complete example would need to contain basic routing and middleware support (which is not easy to implement correctly)

> Would you mind to elaborate? I don't understand what you mean by "naming convention" here, sorry.

For example, the response() callable in the example is explicitly documented as start_response() in PEP 3333:

    https://www.python.org/dev/peps/pep-3333/#the-start-response-callable

You can read PEP 3333 for more details.

> Do you mean that app() must not return FileWrapper? How do you return file content in that case?
> Maybe FileWrapper API should be clarified? It's surprising to read Python 3.8 mentioning compatibility with Python 2.1 :-)

The whole point of the API was to support both __getitem__ and __iter__ protocols at the same time without breaking user code. I've already deprecated the support for __getitem__ protocol (84a13fbda0d79789e3c9efcc9f64752261ce1e8d) because it wasn't working as expected (it ignores its 'index' argument)

Its only valid use case is to read a file chunk by chunk by using its blksize argument, but there are much better ways to achieve the same thing (use os.sendfile() or nginx :))

> Which kind of exceptions do you expect? The example checks if the file exists for example.

I'm talking about exceptions that can be raised by the application code, such as the one that I've mentioned (i.e. mimetypes) in my earlier comment.

Sorry, but it's not really a good example to put into documentation and it would be much better if we could save our bikeshedding bandwidth to other issues :)

----------

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

From report at bugs.python.org  Fri May 10 04:45:23 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 10 May 2019 08:45:23 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1557477923.62.0.638219744322.issue33071@roundup.psfhosted.org>


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


----------
pull_requests: +13145

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

From report at bugs.python.org  Fri May 10 04:45:24 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 10 May 2019 08:45:24 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1557477924.2.0.274512970641.issue33071@roundup.psfhosted.org>


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


New changeset 1b4abcf302ff2c8f4d4881294510d48ba5186b53 by Nick Coghlan (Kojo Idrissa) in branch 'master':
bpo-33071: remove outdated PyPI docs (GH-13087)
https://github.com/python/cpython/commit/1b4abcf302ff2c8f4d4881294510d48ba5186b53


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

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

From report at bugs.python.org  Fri May 10 04:50:58 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 10 May 2019 08:50:58 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1557478258.43.0.75016243156.issue33071@roundup.psfhosted.org>


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


New changeset 069a5b48334a795d3abe3a512dd41aad7a532a73 by Miss Islington (bot) in branch '3.7':
bpo-33071: remove outdated PyPI docs (GH-13087)
https://github.com/python/cpython/commit/069a5b48334a795d3abe3a512dd41aad7a532a73


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

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

From report at bugs.python.org  Fri May 10 07:00:10 2019
From: report at bugs.python.org (kev levrone)
Date: Fri, 10 May 2019 11:00:10 +0000
Subject: [docs] [issue29254] Documentation Error
In-Reply-To: <1484239333.41.0.299474192201.issue29254@psf.upfronthosting.co.za>
Message-ID: <1557486010.48.0.0259861521982.issue29254@roundup.psfhosted.org>


kev levrone <kevlevrone6 at gmail.com> added the comment:

The nevents argument determines the size of eventlist.  When nevents is zero, kevent() will return immediately even if there is a timeout specified unlike select(2). https://goo.gl/KyvnZF

----------
nosy: +kevlevrone

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

From report at bugs.python.org  Fri May 10 07:04:39 2019
From: report at bugs.python.org (SilentGhost)
Date: Fri, 10 May 2019 11:04:39 +0000
Subject: [docs] [issue29254] Documentation Error
In-Reply-To: <1484239333.41.0.299474192201.issue29254@psf.upfronthosting.co.za>
Message-ID: <1557486279.79.0.42147436219.issue29254@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
Removed message: https://bugs.python.org/msg342070

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

From report at bugs.python.org  Fri May 10 13:26:34 2019
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 10 May 2019 17:26:34 +0000
Subject: [docs] [issue36858] f-string '=' debugging output needs to be
 documented
In-Reply-To: <1557347816.05.0.714667733239.issue36858@roundup.psfhosted.org>
Message-ID: <1557509194.13.0.282175960461.issue36858@roundup.psfhosted.org>


Mariatta Wijaya <mariatta at python.org> added the comment:

Perhaps it can be added under Tutorial?

https://docs.python.org/3/tutorial/inputoutput.html#formatted-string-literals

----------

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

From report at bugs.python.org  Fri May 10 13:36:39 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 10 May 2019 17:36:39 +0000
Subject: [docs] [issue30939] Sphinx 1.6.3 deprecation warning for
 sphinx.util.compat.Directive in docs builds
In-Reply-To: <1500146353.65.0.778877813503.issue30939@psf.upfronthosting.co.za>
Message-ID: <1557509799.1.0.649866387898.issue30939@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 3b3a5a5b70dc468dcfacb17a3d6b342820b480ff by larryhastings (Ned Deily) in branch '3.4':
bpo-30939: Avoid Sphinx deprecation warning in docs build. (#2721) (#2724)
https://github.com/python/cpython/commit/3b3a5a5b70dc468dcfacb17a3d6b342820b480ff


----------

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

From report at bugs.python.org  Fri May 10 14:16:15 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 10 May 2019 18:16:15 +0000
Subject: [docs] [issue30939] Sphinx 1.6.3 deprecation warning for
 sphinx.util.compat.Directive in docs builds
In-Reply-To: <1500146353.65.0.778877813503.issue30939@psf.upfronthosting.co.za>
Message-ID: <1557512175.48.0.105640342175.issue30939@roundup.psfhosted.org>


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


----------
Removed message: https://bugs.python.org/msg342095

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

From report at bugs.python.org  Fri May 10 17:25:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 10 May 2019 21:25:11 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1557523510.97.0.139468641638.issue36345@roundup.psfhosted.org>


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

Ok, thanks Berker for your longer answer. I have no opinion on this example anymore. St?phane and others: I let you decide how to handle it ;-)

----------

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

From report at bugs.python.org  Fri May 10 18:13:21 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 10 May 2019 22:13:21 +0000
Subject: [docs] [issue36879] bug with round() and "numpy floats"
In-Reply-To: <1557521461.62.0.231118714409.issue36879@roundup.psfhosted.org>
Message-ID: <1557526401.48.0.802587767266.issue36879@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> not a bug
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri May 10 19:31:51 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 10 May 2019 23:31:51 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1557531110.98.0.958259294453.issue36620@roundup.psfhosted.org>


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

I'll take care of it. Thank you.

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

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

From report at bugs.python.org  Sat May 11 00:53:36 2019
From: report at bugs.python.org (Dieter Weber)
Date: Sat, 11 May 2019 04:53:36 +0000
Subject: [docs] [issue32573] All sys attributes (.argv,
 ...) should exist in embedded environments
In-Reply-To: <1516131988.33.0.467229070634.issue32573@psf.upfronthosting.co.za>
Message-ID: <1557550416.5.0.739074813501.issue32573@roundup.psfhosted.org>


Change by Dieter Weber <dieter at uellue.de>:


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

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

From report at bugs.python.org  Sat May 11 02:07:07 2019
From: report at bugs.python.org (SilentGhost)
Date: Sat, 11 May 2019 06:07:07 +0000
Subject: [docs] [issue36879] bug with round() and "numpy floats"
In-Reply-To: <1557521461.62.0.231118714409.issue36879@roundup.psfhosted.org>
Message-ID: <1557554827.7.0.803801591387.issue36879@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
resolution: not a bug -> 
stage:  -> needs patch

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

From report at bugs.python.org  Sat May 11 06:02:23 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 11 May 2019 10:02:23 +0000
Subject: [docs] [issue36879] bug with round() and "numpy floats"
In-Reply-To: <1557521461.62.0.231118714409.issue36879@roundup.psfhosted.org>
Message-ID: <1557568943.12.0.531608229186.issue36879@roundup.psfhosted.org>


Change by Mark Dickinson <dickinsm at gmail.com>:


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

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

From report at bugs.python.org  Sat May 11 06:28:53 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 11 May 2019 10:28:53 +0000
Subject: [docs] [issue36879] bug with round() and "numpy floats"
In-Reply-To: <1557521461.62.0.231118714409.issue36879@roundup.psfhosted.org>
Message-ID: <1557570533.72.0.215381795955.issue36879@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> Maybe we should add something in the docs regarding the no-restriction point.

IMO, the docs are clear enough (and also long enough) already here. Just as with most other magic methods, classes from third-party packages can return whatever they like. It doesn't seem worth adding specific disclaimers about this everywhere that a magic method might be used. Otherwise, we should also add corresponding disclaimers about `__floor__`, `__ceil__`, `__trunc__`, `__pow__`, and so on, and I think that would just introduce an increase in documentation size without any overall increase in clarity or usefulness.

I'd prefer to stick to documenting that there _is_ a restriction where that's true (e.g., `__index__` or `__hash__`).

----------

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

From report at bugs.python.org  Sat May 11 06:30:45 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 11 May 2019 10:30:45 +0000
Subject: [docs] [issue36879] bug with round() and "numpy floats"
In-Reply-To: <1557521461.62.0.231118714409.issue36879@roundup.psfhosted.org>
Message-ID: <1557570645.41.0.255599373648.issue36879@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

BTW, there are various issues already open in the NumPy bug tracker, for example https://github.com/numpy/numpy/issues/11557

I propose closing this as "third party".

----------

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

From report at bugs.python.org  Sat May 11 10:59:05 2019
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Sat, 11 May 2019 14:59:05 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557586745.75.0.134923767192.issue36794@roundup.psfhosted.org>


Hrvoje Nik?i? <hniksic at gmail.com> added the comment:

@matrixise I've signed the CLA in the meantime, and it's now confirmed by https://check-python-cla.herokuapp.com/

Thanks for the pointer.

----------

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

From report at bugs.python.org  Sat May 11 11:46:31 2019
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 11 May 2019 15:46:31 +0000
Subject: [docs] [issue36868] New behavior of OpenSSL hostname verification
 not exposed, incorrectly documented
In-Reply-To: <1557425747.49.0.948212766878.issue36868@roundup.psfhosted.org>
Message-ID: <1557589591.13.0.405454511931.issue36868@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat May 11 12:03:07 2019
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 11 May 2019 16:03:07 +0000
Subject: [docs] [issue36868] New behavior of OpenSSL hostname verification
 not exposed, incorrectly documented
In-Reply-To: <1557425747.49.0.948212766878.issue36868@roundup.psfhosted.org>
Message-ID: <1557590587.79.0.515299528982.issue36868@roundup.psfhosted.org>


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

The entry in whatsnew is a documentation bug. Initially I wanted to expose host_flags and wrote the whatnew entry for it. Later we decided against the flag and an only implemented the hostname_checks_common_name switch (https://docs.python.org/3/library/ssl.html#ssl.SSLContext.hostname_checks_common_name).

1) SSLContext.host_flags in whatsnew is a bug. I'm updating the text.

2/3/4) The _host_flags attribute and the HOSTFLAG_* attributes are for internal use only to provide the hostname_checks_common_name flag.

5) Underscore is not a valid character for hostnames in A, AAAA, CNAME, and similar DNS record types. It's used in e.g. SRV record types, but an application will never directly connect to a SRV record address. It looks like OpenSSL interprets RFC 6125 (https://tools.ietf.org/html/rfc6125#section-6.4.3) strictly and requires valid DNS names.

I wonder, how did you get your DNS server to accept underscores? In theory you should run into a DNS exception earlier.

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

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

From report at bugs.python.org  Sat May 11 12:37:08 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Sat, 11 May 2019 16:37:08 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1557592628.47.0.0517704933201.issue36794@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi Hrvoje Nik?i?,

Thank you for the CLA, now, we need the opinion from Yury and their approval, I am not an expert of the asyncio.

Thank you,

----------

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

From report at bugs.python.org  Sat May 11 15:04:14 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 11 May 2019 19:04:14 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
In-Reply-To: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>
Message-ID: <1557601454.82.0.303411960515.issue36822@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 90fb04c1e23c0fddd438bd0f73e7c018cacef4bc by Pablo Galindo (Sanyam Khurana) in branch 'master':
bpo-36822: Fix minor grammatical error in glossary.rst (GH-13145)
https://github.com/python/cpython/commit/90fb04c1e23c0fddd438bd0f73e7c018cacef4bc


----------
nosy: +pablogsal

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

From report at bugs.python.org  Sat May 11 19:00:01 2019
From: report at bugs.python.org (musou1500)
Date: Sat, 11 May 2019 23:00:01 +0000
Subject: [docs] [issue36892] "Modules" section in Tutorial contains
 incorrect description about __init__.py
Message-ID: <1557615601.14.0.911128255467.issue36892@roundup.psfhosted.org>


New submission from musou1500 <musou1500 at gmail.com>:

"Modules" section in the tutorial says that
https://docs.python.org/3/tutorial/modules.html
"The __init__.py files are required to make Python treat directories containing the file as packages. "

But, thanks to PEP 420, __init__.py is not required after Python 3.3.
https://www.python.org/dev/peps/pep-0420/

----------
assignee: docs at python
components: Documentation
messages: 342228
nosy: docs at python, musou1500
priority: normal
severity: normal
status: open
title: "Modules" section in Tutorial contains incorrect description about __init__.py
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Sat May 11 20:03:13 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 12 May 2019 00:03:13 +0000
Subject: [docs] [issue36892] "Modules" section in Tutorial contains
 incorrect description about __init__.py
In-Reply-To: <1557615601.14.0.911128255467.issue36892@roundup.psfhosted.org>
Message-ID: <1557619393.7.0.843105777353.issue36892@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

In my experience, beginners have enough trouble getting packages right without complicating the tutorial with a rarely-used advanced feature like namespace packages.

I don't think this needs more than perhaps a footnote, if that.

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

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

From report at bugs.python.org  Sat May 11 21:30:23 2019
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 12 May 2019 01:30:23 +0000
Subject: [docs] [issue36892] "Modules" section in Tutorial contains
 incorrect description about __init__.py
In-Reply-To: <1557615601.14.0.911128255467.issue36892@roundup.psfhosted.org>
Message-ID: <1557624623.53.0.1292030758.issue36892@roundup.psfhosted.org>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I agree that implicit namespace packages don't deserve more than a footnote in that page.

However, since I often have to answer questions about packages, I'm thinking that perhaps it would be better to expand that page and maybe have a page dedicated to modules and one to packages, where PEP 420 and other common issues could be covered in more details.

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

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

From report at bugs.python.org  Sat May 11 23:31:53 2019
From: report at bugs.python.org (Sanyam Khurana)
Date: Sun, 12 May 2019 03:31:53 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
In-Reply-To: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>
Message-ID: <1557631913.03.0.941478212113.issue36822@roundup.psfhosted.org>


Change by Sanyam Khurana <sanyam.khurana01 at gmail.com>:


----------
pull_requests: +13170

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

From report at bugs.python.org  Sat May 11 23:53:06 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 12 May 2019 03:53:06 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
In-Reply-To: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>
Message-ID: <1557633186.01.0.610535449292.issue36822@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 4f5febdf955240b6064bb5647dec084feaa98376 by Pablo Galindo (Sanyam Khurana) in branch '3.7':
[3.7] bpo-36822: Fix minor grammatical error in glossary.rst (GH-13145). (GH-13260)
https://github.com/python/cpython/commit/4f5febdf955240b6064bb5647dec084feaa98376


----------

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

From report at bugs.python.org  Sat May 11 23:53:13 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 12 May 2019 03:53:13 +0000
Subject: [docs] [issue36822] Minor grammatical fix in glossary.rst
In-Reply-To: <1557186503.72.0.659127462032.issue36822@roundup.psfhosted.org>
Message-ID: <1557633193.36.0.912119323204.issue36822@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


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

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

From report at bugs.python.org  Sun May 12 18:03:30 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 12 May 2019 22:03:30 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
Message-ID: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>


New submission from Matthias Bussonnier <bussonniermatthias at gmail.com>:

>From bpo-36886, 

IT is unclear the FunctionTypes, CodeTypes ... etc are not stable between python versions, and the recent addition of `:=` change some of the signatures.  


This suggest 2 things: 
 - A CYA sentence in types.rst "These types are not supposed to be instantiated outside of CPython internals and constructor signatures will vary between python versions." or alike
 - As many people don't read online documentation but on the docstring via calling `help()`, to add something similar to all the docstrings of said-objects constructors.

----------
assignee: docs at python
components: Documentation
messages: 342271
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: clarify in types.rst that FunctionTypes & co  constructors don't have stable signature
versions: Python 3.8

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

From report at bugs.python.org  Sun May 12 20:25:44 2019
From: report at bugs.python.org (Windson Yang)
Date: Mon, 13 May 2019 00:25:44 +0000
Subject: [docs] [issue36689] docs: os.path.commonpath raises ValueError for
 different drives
In-Reply-To: <1555837758.83.0.507858438764.issue36689@roundup.psfhosted.org>
Message-ID: <1557707144.74.0.298556375984.issue36689@roundup.psfhosted.org>


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

An easy fix would be 

"Raise ValueError if paths contain (note: use contain instead of contains) both absolute and relative pathnames or the path are on the different drives."

----------
nosy: +Windson Yang

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

From report at bugs.python.org  Sun May 12 20:28:11 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 13 May 2019 00:28:11 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1557707291.88.0.000598979308063.issue36896@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun May 12 23:55:23 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 13 May 2019 03:55:23 +0000
Subject: [docs] [issue13474] Mention of "-m" Flag Missing From Doc on
 Execution Model
In-Reply-To: <1322165458.97.0.989343856998.issue13474@psf.upfronthosting.co.za>
Message-ID: <1557719723.47.0.493908626035.issue13474@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Mon May 13 03:23:43 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 07:23:43 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557732223.27.0.84406899836.issue36783@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:


New changeset d28772ab6967fea136c0707f0207673ebad66f61 by St?phane Wirtel (Edison A) in branch 'master':
bpo-36783: Add new references for C API Documentation changes (GH-13204)
https://github.com/python/cpython/commit/d28772ab6967fea136c0707f0207673ebad66f61


----------
nosy: +matrixise

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

From report at bugs.python.org  Mon May 13 03:25:25 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 07:25:25 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557732325.51.0.599665371637.issue36783@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Thank you for your PR.

@Cherryl, the PR 13204 was not merged and the issue was closed :/

----------

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

From report at bugs.python.org  Mon May 13 08:29:42 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 13 May 2019 12:29:42 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1557750582.86.0.443827799248.issue36008@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset 3e2afd78babe5bd270e7f3b9df8796eeabc79865 by Cheryl Sabella (Utkarsh Gupta) in branch 'master':
bpo-36008: Doc update for 3.8 migration (GH-12887)
https://github.com/python/cpython/commit/3e2afd78babe5bd270e7f3b9df8796eeabc79865


----------

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

From report at bugs.python.org  Mon May 13 08:31:08 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 13 May 2019 12:31:08 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1557750668.49.0.43101995771.issue36008@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Mon May 13 08:45:45 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 13 May 2019 12:45:45 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1557751545.88.0.612677570347.issue22021@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@giampaolo.rodola, would you be able to provide a review of this doc change?  Thanks!

----------
nosy: +cheryl.sabella, giampaolo.rodola
versions:  -Python 3.6

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

From report at bugs.python.org  Mon May 13 08:49:19 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 12:49:19 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1557751759.64.0.203407755465.issue36008@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

@Cheryl,

I was reading the last commits on master and I have seen the merge of that PR, but 3.8.0 is not yet in Beta2. Maybe we should fix that in an other PR for the same issue.

----------
nosy: +matrixise

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

From report at bugs.python.org  Mon May 13 08:53:45 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 12:53:45 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1557752025.62.0.0899153825348.issue36008@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

I suggest to remove b2+ and just keep 3.8.0

----------

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

From report at bugs.python.org  Mon May 13 08:57:06 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Mon, 13 May 2019 12:57:06 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1557752226.15.0.904446858377.issue36008@roundup.psfhosted.org>


Utkarsh Gupta <guptautkarsh2102 at gmail.com> added the comment:

Sure, but ultimately (soon enough) it is going to happen, no?

----------

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

From report at bugs.python.org  Mon May 13 09:03:13 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 13:03:13 +0000
Subject: [docs] [issue33882] doc Mention breakpoint() in debugger-related FAQ
In-Reply-To: <1529192953.25.0.56676864532.issue33882@psf.upfronthosting.co.za>
Message-ID: <1557752593.35.0.338266272814.issue33882@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:


New changeset af5ef3e1077bc2ed177a7c8598f8ecc756ecf6f9 by St?phane Wirtel (Miss Islington (bot)) in branch '3.7':
bpo-33882: mention breakpoint() in debugger-related FAQ (GH-7759) (GH-13077)
https://github.com/python/cpython/commit/af5ef3e1077bc2ed177a7c8598f8ecc756ecf6f9


----------
nosy: +matrixise

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

From report at bugs.python.org  Mon May 13 09:04:47 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 13:04:47 +0000
Subject: [docs] [issue33882] doc Mention breakpoint() in debugger-related FAQ
In-Reply-To: <1529192953.25.0.56676864532.issue33882@psf.upfronthosting.co.za>
Message-ID: <1557752687.45.0.144410373796.issue33882@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Thank you for your PR,

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

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

From report at bugs.python.org  Mon May 13 09:05:22 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 13 May 2019 13:05:22 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557752722.93.0.513899391433.issue34682@roundup.psfhosted.org>


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


New changeset 778a9107586e29421af3a08209cf0b557c1fe5bc by Miss Islington (bot) (divyag9) in branch 'master':
bpo-34682: Wording and grammatical changes to the doc(https://docs.python.org/3) (GH-13120)
https://github.com/python/cpython/commit/778a9107586e29421af3a08209cf0b557c1fe5bc


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

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

From report at bugs.python.org  Mon May 13 09:05:31 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 13 May 2019 13:05:31 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557752731.02.0.359036796098.issue34682@roundup.psfhosted.org>


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


----------
pull_requests: +13185

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

From report at bugs.python.org  Mon May 13 09:17:53 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Mon, 13 May 2019 13:17:53 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557753473.27.0.774204325889.issue34682@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
pull_requests: +13187

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

From report at bugs.python.org  Mon May 13 09:48:56 2019
From: report at bugs.python.org (Julien Palard)
Date: Mon, 13 May 2019 13:48:56 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557755335.96.0.65499820242.issue34682@roundup.psfhosted.org>


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


New changeset 074d7c44a474680122ed869bb6be89c1f4f18f12 by Julien Palard (St?phane Wirtel) in branch '3.7':
[3.7] bpo-34682: Wording and grammatical changes to the doc(https://docs.python.org/3) (GH-13120) (GH-13281)
https://github.com/python/cpython/commit/074d7c44a474680122ed869bb6be89c1f4f18f12


----------
nosy: +mdk

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

From report at bugs.python.org  Mon May 13 09:49:24 2019
From: report at bugs.python.org (Paul Ganssle)
Date: Mon, 13 May 2019 13:49:24 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1557755364.24.0.558085027552.issue36783@roundup.psfhosted.org>


Paul Ganssle <p.ganssle at gmail.com> added the comment:

@St?phane The reason this issue was closed before PR 13204 was merged is that PR 13147 was merged a bit prematurely due to a miscommunication, which is why Cheryl closed the issue. I was going to re-open it after we realized what happened, but since we were at sprints and I knew 13204 was coming soon, I didn't bother.

----------

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

From report at bugs.python.org  Mon May 13 11:33:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 13 May 2019 15:33:57 +0000
Subject: [docs] [issue32573] All sys attributes (.argv,
 ...) should exist in embedded environments
In-Reply-To: <1516131988.33.0.467229070634.issue32573@psf.upfronthosting.co.za>
Message-ID: <1557761637.19.0.577655215785.issue32573@roundup.psfhosted.org>


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

In Python 3.8, sys.argv is now always created. It's initialized to sys.argv = [""] if (argc, argv) are not set in _PyCoreConfig.

So PR 12463 looks useless to me, except if someone wants to change the behavior.

----------

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

From report at bugs.python.org  Mon May 13 11:36:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 13 May 2019 15:36:03 +0000
Subject: [docs] [issue32573] All sys attributes (.argv,
 ...) should exist in embedded environments
In-Reply-To: <1516131988.33.0.467229070634.issue32573@psf.upfronthosting.co.za>
Message-ID: <1557761763.33.0.959711721571.issue32573@roundup.psfhosted.org>


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

See also the PEP 587.

----------

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

From report at bugs.python.org  Mon May 13 11:36:14 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 13 May 2019 15:36:14 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
 should be documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1557761774.66.0.991472361916.issue13286@roundup.psfhosted.org>


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


----------
pull_requests: +13194

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

From report at bugs.python.org  Mon May 13 11:39:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 13 May 2019 15:39:15 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
 should be documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1557761955.54.0.676432885477.issue13286@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at redhat.com>:


----------
pull_requests:  -13194

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

From report at bugs.python.org  Mon May 13 11:48:50 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Mon, 13 May 2019 15:48:50 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1557762530.82.0.885234100457.issue22021@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

@cheryl.sabella don't have the bandwidth right now (traveling), sorry.

----------

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

From report at bugs.python.org  Mon May 13 12:08:51 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 13 May 2019 16:08:51 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
 should be documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1557763731.54.0.984281102066.issue13286@roundup.psfhosted.org>


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


----------
pull_requests: +13197

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

From report at bugs.python.org  Mon May 13 12:53:30 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 13 May 2019 16:53:30 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1557766410.05.0.0515838644344.issue22021@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@giampaolo.rodola, no problem.  I intended this more as a general request rather than something for right now.  If you do have any availability at some point, please keep this one in mind.  Thanks!

----------

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

From report at bugs.python.org  Mon May 13 15:27:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 13 May 2019 19:27:23 +0000
Subject: [docs] [issue35138] timeit documentation should have example with
 function arguments
In-Reply-To: <1541090734.49.0.788709270274.issue35138@psf.upfronthosting.co.za>
Message-ID: <1557775643.44.0.0242501854902.issue35138@roundup.psfhosted.org>


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


New changeset 8da5ebe11e0cb6599af682b22f7c2b2b7b9debd8 by Victor Stinner (Anders Hovm?ller) in branch 'master':
bpo-35138: Added an example for timeit.timeit with callable arguments (GH-9787)
https://github.com/python/cpython/commit/8da5ebe11e0cb6599af682b22f7c2b2b7b9debd8


----------
nosy: +vstinner

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

From report at bugs.python.org  Mon May 13 15:27:40 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 13 May 2019 19:27:40 +0000
Subject: [docs] [issue35138] timeit documentation should have example with
 function arguments
In-Reply-To: <1541090734.49.0.788709270274.issue35138@psf.upfronthosting.co.za>
Message-ID: <1557775660.59.0.122650011991.issue35138@roundup.psfhosted.org>


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


----------
pull_requests: +13205

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

From report at bugs.python.org  Mon May 13 15:41:35 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 13 May 2019 19:41:35 +0000
Subject: [docs] [issue35138] timeit documentation should have example with
 function arguments
In-Reply-To: <1541090734.49.0.788709270274.issue35138@psf.upfronthosting.co.za>
Message-ID: <1557776495.02.0.331236745213.issue35138@roundup.psfhosted.org>


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


New changeset 7f485ea4fc17c5afb38cd0478ff15326fb5a47fc by Miss Islington (bot) in branch '3.7':
bpo-35138: Added an example for timeit.timeit with callable arguments (GH-9787)
https://github.com/python/cpython/commit/7f485ea4fc17c5afb38cd0478ff15326fb5a47fc


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

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

From report at bugs.python.org  Mon May 13 17:15:22 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Mon, 13 May 2019 21:15:22 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
Message-ID: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>


New submission from Ned Batchelder <ned at nedbatchelder.com>:

The math and cmath modules say this in their docs: "This module is always available."  This lead a beginner to believe they didn't need to be imported.

Nearly the entire standard library is always available in this sense (they can be imported).  This sentence isn't useful.

Can we change the first paragraph of the math module to be:

"This module provides access to the mathematical functions defined by the C standard."

(and similarly for the cmath module.)

----------
assignee: docs at python
components: Documentation
messages: 342386
nosy: docs at python, nedbat
priority: normal
severity: normal
status: open
title: "This module is always available" is confusing

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

From report at bugs.python.org  Mon May 13 17:24:41 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Mon, 13 May 2019 21:24:41 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557782681.46.0.544336750463.issue36908@roundup.psfhosted.org>


Change by Ned Batchelder <ned at nedbatchelder.com>:


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

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

From report at bugs.python.org  Mon May 13 17:51:40 2019
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 13 May 2019 21:51:40 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557784300.23.0.276799657393.issue36908@roundup.psfhosted.org>


Mariatta Wijaya <mariatta at python.org> added the comment:

I agree the wording "is always available" is quite ambiguous. It's just that we use this phrase pretty much everywhere...

Example:
First paragraph of https://docs.python.org/3/library/sys.html
"It is always available."

https://docs.python.org/3/library/threading.html?highlight=threading#module-threading "This module used to be optional, it is now always available."

I wonder if it will be clearer if it says "is available across all platforms"?

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

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

From report at bugs.python.org  Mon May 13 17:53:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 13 May 2019 21:53:18 +0000
Subject: [docs] [issue35138] timeit documentation should have example with
 function arguments
In-Reply-To: <1541090734.49.0.788709270274.issue35138@psf.upfronthosting.co.za>
Message-ID: <1557784398.9.0.942565072625.issue35138@roundup.psfhosted.org>


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

Thanks Anders Hovm?ller! Example added to Python 3.7 and 3.8 documentation :-)

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

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

From report at bugs.python.org  Mon May 13 18:09:44 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Mon, 13 May 2019 22:09:44 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557785384.36.0.133612814371.issue36908@roundup.psfhosted.org>


Ned Batchelder <ned at nedbatchelder.com> added the comment:

If we want to keep it, how about "it can always be imported."? Though I still wonder whether this is worth it.  Are we going to annotate all of the always-available modules with this notation?

----------

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

From report at bugs.python.org  Mon May 13 18:17:02 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Mon, 13 May 2019 22:17:02 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557785822.22.0.253866195914.issue36908@roundup.psfhosted.org>


Ned Batchelder <ned at nedbatchelder.com> added the comment:

Looks like these modules describe themselves as always available: _thread, sys, threading, time.

Notice that the built-ins are also described as "always available", which is the meaning we're trying to move math away from (you can use them without importing anything).

----------

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

From report at bugs.python.org  Mon May 13 18:21:50 2019
From: report at bugs.python.org (wim glenn)
Date: Mon, 13 May 2019 22:21:50 +0000
Subject: [docs] [issue36909] LastUpdatedOrderedDict recipe uses super()
 unnecessarily
Message-ID: <1557786110.6.0.397786860144.issue36909@roundup.psfhosted.org>


New submission from wim glenn <wim.glenn at gmail.com>:

Section https://docs.python.org/3/library/collections.html#ordereddict-examples-and-recipes

    class LastUpdatedOrderedDict(OrderedDict):
        'Store items in the order the keys were last added'

        def __setitem__(self, key, value):
            super().__setitem__(key, value)
            super().move_to_end(key)

Why does it use super().move_to_end(key), isn't self.move_to_end(key) more direct/Pythonic?

----------
assignee: docs at python
components: Documentation
messages: 342395
nosy: docs at python, rhettinger, wim.glenn
priority: normal
pull_requests: 13209
severity: normal
status: open
title: LastUpdatedOrderedDict recipe uses super() unnecessarily

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

From report at bugs.python.org  Mon May 13 20:13:33 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 14 May 2019 00:13:33 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557792813.63.0.00386579446166.issue36908@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

I agree. What about create a section (or subsection?) or  note with 
the text:


```
The next modules: sys, math ...  are always available. This
mean that ...
```

?

----------
nosy: +eamanu

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

From report at bugs.python.org  Mon May 13 20:16:01 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Tue, 14 May 2019 00:16:01 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557792961.9.0.560026095012.issue36908@roundup.psfhosted.org>


Ned Batchelder <ned at nedbatchelder.com> added the comment:

There are hundreds of modules that are always importable.  The majority of the standard library is always importable.  More useful would be to annotate those modules that might not be importable, with a reason why.

----------

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

From report at bugs.python.org  Mon May 13 20:20:02 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 14 May 2019 00:20:02 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1557793202.07.0.779472240659.issue36908@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

> More useful would be to annotate those modules that might not be importable, with a reason why.

yes, that is more reasonable. :-D

----------

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

From report at bugs.python.org  Mon May 13 20:37:47 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 14 May 2019 00:37:47 +0000
Subject: [docs] [issue30535] Explicitly note that meta_path is not empty
In-Reply-To: <1496307550.81.0.122215532062.issue30535@psf.upfronthosting.co.za>
Message-ID: <1557794267.29.0.39303428507.issue30535@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Mon May 13 20:37:59 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 14 May 2019 00:37:59 +0000
Subject: [docs] [issue30535] Explicitly note that meta_path is not empty
In-Reply-To: <1496307550.81.0.122215532062.issue30535@psf.upfronthosting.co.za>
Message-ID: <1557794279.71.0.00938289815223.issue30535@roundup.psfhosted.org>


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

I created a PR for it. TBO, meta_path is not a good name since it doesn't contain any *path* at all.

----------
nosy: +Windson Yang

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

From report at bugs.python.org  Mon May 13 20:54:55 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 14 May 2019 00:54:55 +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: <1557795295.76.0.178178028422.issue9267@roundup.psfhosted.org>


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

Where are the documents actually?

----------
nosy: +Windson Yang

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

From report at bugs.python.org  Mon May 13 22:43:00 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 14 May 2019 02:43:00 +0000
Subject: [docs] [issue36909] LastUpdatedOrderedDict recipe uses super()
 unnecessarily
In-Reply-To: <1557786110.6.0.397786860144.issue36909@roundup.psfhosted.org>
Message-ID: <1557801780.57.0.0225235604749.issue36909@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue May 14 03:35:28 2019
From: report at bugs.python.org (Tomer Vromen)
Date: Tue, 14 May 2019 07:35:28 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
Message-ID: <1557819328.64.0.0474936169734.issue36913@roundup.psfhosted.org>


New submission from Tomer Vromen <tomerv at gmail.com>:

The documentation for decorators (for methods and classes) is pretty lacking.

Searching for "decorator" ( https://docs.python.org/3/search.html?q=decorator ) brings up a lot of libraries that use decorators, but no documentation explaining what they are and how they work. The documentation should have a dedicated page for explaining decorators, and this should be the 1st search result.

--

In the meantime, then search should give as a 1st result a link to the definition of decorator in the glossary: https://docs.python.org/3.7/glossary.html#glossary

Actually, it seems that there is no way to directly link to a paragraph in the glossary - so that should be added as well.

In general, it would be nice if a search for some term X would show as a 1st result the definition of X in the glossary (if it exists there).

Thanks!

----------
assignee: docs at python
components: Documentation
messages: 342435
nosy: docs at python, tomerv
priority: normal
severity: normal
status: open
title: Missing documentation for decorators
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Tue May 14 04:34:32 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 May 2019 08:34:32 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
In-Reply-To: <1557819328.64.0.0474936169734.issue36913@roundup.psfhosted.org>
Message-ID: <1557822872.56.0.353667716079.issue36913@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi,

Thank you for your feedback.

In fact, there is a limitation with the current search engine of Sphinx (because we use it for the documentation). For example, if you try to find the meaning of "for", for us it's a keyword but for the search engine, it will try to find all the sections containing "for" (formatter, platform, argparse.ArgumentParser.format_help, etc...).

For that, we could open an issue on the repository of Sphinx.

Now, about the decorators.

In the definition of a function, we explain the call of a decorator, See the grammar. https://docs.python.org/3/reference/compound_stmts.html#function-definitions

"""
A function definition may be wrapped by one or more decorator expressions. Decorator expressions are evaluated when the function is defined, in the scope that contains the function definition. The result must be a callable, which is invoked with the function object as the only argument. The returned value is bound to the function name instead of the function object. Multiple decorators are applied in a nested fashion. For example, the following code
"""

But because it's a specification of the language which has been described with 2 PEPs you can read it on the PEP Index page.

Function: https://www.python.org/dev/peps/pep-0318/ 
-> Introduced in 2.4 https://docs.python.org/3/whatsnew/2.4.html

Class: https://www.python.org/dev/peps/pep-3129/
-> Introduced in 3.0

Now, I suggest one thing, add a link to the PEPs in this section https://docs.python.org/3/reference/compound_stmts.html#function-definitions

----------
nosy: +matrixise

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

From report at bugs.python.org  Tue May 14 04:35:01 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 May 2019 08:35:01 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
In-Reply-To: <1557819328.64.0.0474936169734.issue36913@roundup.psfhosted.org>
Message-ID: <1557822901.59.0.962704610226.issue36913@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


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

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

From report at bugs.python.org  Tue May 14 04:53:32 2019
From: report at bugs.python.org (Tomer Vromen)
Date: Tue, 14 May 2019 08:53:32 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
In-Reply-To: <1557819328.64.0.0474936169734.issue36913@roundup.psfhosted.org>
Message-ID: <1557824012.14.0.590875050256.issue36913@roundup.psfhosted.org>


Tomer Vromen <tomerv at gmail.com> added the comment:

Thank you for the quick response.

Are PEPs considered de-facto documentation for language features? For example, string formatting was described in PEP 3101, but still has sections in the documentation dedicated to it. I believe that decorators should get a similar treatment :-)

I also think that describing decorators as part of the grammar definition is lacking. Why is there a whole chapter for Errors and Exceptions and it's not only discussed under the grammar definition for raise?

Decorators are a pretty unique (and cool!) feature of Python, and therefore new learners of the language need a better reference for learning about them.

I realize that this is a big request, as you would need some expert to write this documentation.

----------

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

From report at bugs.python.org  Tue May 14 05:13:40 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 May 2019 09:13:40 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
In-Reply-To: <1557824012.14.0.590875050256.issue36913@roundup.psfhosted.org>
Message-ID: <20190514091336.jse6mbixebwcjrtf@xps>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi Tomer,

>Thank you for the quick response.
Welcome
>
>Are PEPs considered de-facto documentation for language features? For
>example, string formatting was described in PEP 3101, but still has
>sections in the documentation dedicated to it. I believe that
>decorators should get a similar treatment :-)
Good catch for the string formatting.

For the decorator, it's different because a decorator is mainly a
function taking a function and returning a function.

Example you can write this decorator:

def my_decorator(func):
    return func

def my_awesome_function(*args, **kwargs):
    print(args)
    print(kwargs)

    return 42

my_awesome_function = my_decorator(my_awesome_function)

in this case, we don't need to document the decorator.

for the '@' syntax, it's described in the doc but it's syntactic sugar
for the decorator. I don't think we need to add a big description for
that, because everything is described in the PEP.

I would like to have the opinion of the other core-dev. @sizeof?

>
>I also think that describing decorators as part of the grammar
>definition is lacking. Why is there a whole chapter for Errors and
>Exceptions and it's not only discussed under the grammar definition for
>raise?
>
>Decorators are a pretty unique (and cool!) feature of Python, and
>therefore new learners of the language need a better reference for
>learning about them.
>
>I realize that this is a big request, as you would need some expert to
>write this documentation.
You can open a PR ;-)

----------

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

From report at bugs.python.org  Tue May 14 05:13:59 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 May 2019 09:13:59 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
In-Reply-To: <1557819328.64.0.0474936169734.issue36913@roundup.psfhosted.org>
Message-ID: <1557825239.02.0.179838989536.issue36913@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
nosy: +mdk

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

From report at bugs.python.org  Tue May 14 08:11:46 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 14 May 2019 12:11:46 +0000
Subject: [docs] [issue32995] Add a glossary entry for context variables
In-Reply-To: <1520244692.22.0.467229070634.issue32995@psf.upfronthosting.co.za>
Message-ID: <1557835906.13.0.914126707893.issue32995@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset c0a1a07c7e9814cad79cce3580c16284b2df7f52 by Cheryl Sabella (Vinodhini Balusamy) in branch 'master':
bpo-32995 - Added context variable in glossary (GH-9741)
https://github.com/python/cpython/commit/c0a1a07c7e9814cad79cce3580c16284b2df7f52


----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Tue May 14 08:11:52 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 14 May 2019 12:11:52 +0000
Subject: [docs] [issue32995] Add a glossary entry for context variables
In-Reply-To: <1520244692.22.0.467229070634.issue32995@psf.upfronthosting.co.za>
Message-ID: <1557835912.83.0.805883554554.issue32995@roundup.psfhosted.org>


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


----------
pull_requests: +13221

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

From report at bugs.python.org  Tue May 14 08:14:18 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 14 May 2019 12:14:18 +0000
Subject: [docs] [issue32995] Add a glossary entry for context variables
In-Reply-To: <1520244692.22.0.467229070634.issue32995@psf.upfronthosting.co.za>
Message-ID: <1557836058.88.0.693984567696.issue32995@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@vinu2003, thank you for the pull request!

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

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

From report at bugs.python.org  Tue May 14 08:24:50 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 14 May 2019 12:24:50 +0000
Subject: [docs] [issue32995] Add a glossary entry for context variables
In-Reply-To: <1520244692.22.0.467229070634.issue32995@psf.upfronthosting.co.za>
Message-ID: <1557836690.43.0.809816266929.issue32995@roundup.psfhosted.org>


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


New changeset 8b3823ae16d68cf17ad037e46d7e49d26929a13b by Miss Islington (bot) in branch '3.7':
bpo-32995 - Added context variable in glossary (GH-9741)
https://github.com/python/cpython/commit/8b3823ae16d68cf17ad037e46d7e49d26929a13b


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

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

From report at bugs.python.org  Tue May 14 10:35:54 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 May 2019 14:35:54 +0000
Subject: [docs] [issue2897] Deprecate structmember.h
In-Reply-To: <1210977912.97.0.641461512834.issue2897@psf.upfronthosting.co.za>
Message-ID: <1557844553.95.0.539858466769.issue2897@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

I move this issue to master (3.8)

----------
nosy: +matrixise, vstinner
versions: +Python 3.8 -Python 2.7, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Tue May 14 12:00:32 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 14 May 2019 16:00:32 +0000
Subject: [docs] [issue18478] Class bodies: when does a name become local?
In-Reply-To: <1374017954.45.0.193690883208.issue18478@psf.upfronthosting.co.za>
Message-ID: <1557849632.3.0.422847536715.issue18478@roundup.psfhosted.org>


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


----------
pull_requests: +13227

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

From report at bugs.python.org  Tue May 14 12:02:26 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 14 May 2019 16:02:26 +0000
Subject: [docs] [issue18478] Class bodies: when does a name become local?
In-Reply-To: <1374017954.45.0.193690883208.issue18478@psf.upfronthosting.co.za>
Message-ID: <1557849746.04.0.159169990767.issue18478@roundup.psfhosted.org>


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


----------
pull_requests:  -13227

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

From report at bugs.python.org  Tue May 14 14:04:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 14 May 2019 18:04:11 +0000
Subject: [docs] [issue18478] Class bodies: when does a name become local?
In-Reply-To: <1374017954.45.0.193690883208.issue18478@psf.upfronthosting.co.za>
Message-ID: <1557857051.32.0.454975991519.issue18478@roundup.psfhosted.org>


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


----------
pull_requests: +13235

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

From report at bugs.python.org  Tue May 14 14:06:10 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 14 May 2019 18:06:10 +0000
Subject: [docs] [issue18478] Class bodies: when does a name become local?
In-Reply-To: <1374017954.45.0.193690883208.issue18478@psf.upfronthosting.co.za>
Message-ID: <1557857170.25.0.03478757097.issue18478@roundup.psfhosted.org>


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


----------
pull_requests:  -13235

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

From report at bugs.python.org  Tue May 14 14:36:01 2019
From: report at bugs.python.org (A.M. Kuchling)
Date: Tue, 14 May 2019 18:36:01 +0000
Subject: [docs] [issue34484] Unicode HOWTO incorrectly refers to Private Use
 Area for surrogateescape
In-Reply-To: <1535058879.5.0.56676864532.issue34484@psf.upfronthosting.co.za>
Message-ID: <1557858961.22.0.251991112327.issue34484@roundup.psfhosted.org>


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

Yes, I think this issue can now be closed.

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

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

From report at bugs.python.org  Tue May 14 14:45:54 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 14 May 2019 18:45:54 +0000
Subject: [docs] [issue10108] ExpatError not property wrapped
In-Reply-To: <1287093270.3.0.510777453712.issue10108@psf.upfronthosting.co.za>
Message-ID: <1557859554.81.0.51476220164.issue10108@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi Scoder,

I am not sure if this issue is relevant for 3.7 and 3.8 but do you want to check this issue?

Thank you,

----------
nosy: +matrixise, scoder
versions: +Python 3.7, Python 3.8 -Python 3.1

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

From report at bugs.python.org  Tue May 14 21:34:47 2019
From: report at bugs.python.org (Windson Yang)
Date: Wed, 15 May 2019 01:34:47 +0000
Subject: [docs] [issue26124] shlex.quote and pipes.quote do not quote shell
 keywords
In-Reply-To: <1452863681.04.0.149848593597.issue26124@psf.upfronthosting.co.za>
Message-ID: <1557884087.64.0.404937688642.issue26124@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue May 14 22:32:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 15 May 2019 02:32:57 +0000
Subject: [docs] [issue26515] Update extending/embedding docs to new way to
 build modules in C
In-Reply-To: <1457491421.2.0.684118231911.issue26515@psf.upfronthosting.co.za>
Message-ID: <1557887577.34.0.660692432015.issue26515@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at redhat.com>:


----------
nosy: +petr.viktorin

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

From report at bugs.python.org  Tue May 14 23:03:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 15 May 2019 03:03:55 +0000
Subject: [docs] [issue21202] Naming a file` io.py` causes cryptic error
 message
In-Reply-To: <1397239551.94.0.578791540537.issue21202@psf.upfronthosting.co.za>
Message-ID: <1557889435.88.0.208267037741.issue21202@roundup.psfhosted.org>


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

No activity for 5 years, I close the issue.

----------
nosy: +vstinner
resolution:  -> out of date
stage: test needed -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed May 15 04:43:26 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 May 2019 08:43:26 +0000
Subject: [docs] [issue36345] Doc: make serve uses http.server instead of
 Tools/scripts/server.py
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1557909806.85.0.0947891710009.issue36345@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
title: Deprecate Tools/scripts/serve.py in favour of python -m http.server -d -> Doc: make serve uses http.server instead of Tools/scripts/server.py

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

From report at bugs.python.org  Wed May 15 07:24:32 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 15 May 2019 11:24:32 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1557919472.75.0.100175265011.issue36567@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

What is going to be our manpage site? Debian?

----------
nosy: +BTaskaya

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

From report at bugs.python.org  Wed May 15 07:35:47 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 15 May 2019 11:35:47 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1557920147.79.0.666546060101.issue36567@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


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

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

From report at bugs.python.org  Wed May 15 07:48:03 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 May 2019 11:48:03 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1557920883.21.0.844786427203.issue36567@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Is there another source than Debian?

there is this option: http://man7.org/linux/man-pages/index.html

Honestly, if you use the Debian source, there is an automatic redirect to the right man page.

----------
nosy: +matrixise

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

From report at bugs.python.org  Wed May 15 07:58:15 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 15 May 2019 11:58:15 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1557921495.42.0.549503829501.issue36567@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

I sent a proposal with debian default and can be altered through env variable called MANPAGES_URL

----------

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

From report at bugs.python.org  Wed May 15 07:59:23 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 15 May 2019 11:59:23 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1557921563.96.0.679283048899.issue36567@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

*ups propsal = pr

----------

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

From report at bugs.python.org  Wed May 15 07:59:42 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 15 May 2019 11:59:42 +0000
Subject: [docs] [issue34682] Typo reports on docs@
In-Reply-To: <1536943787.72.0.956365154283.issue34682@psf.upfronthosting.co.za>
Message-ID: <1557921582.2.0.665806422878.issue34682@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Thank you @divyag for the patch and thank you @matrixise for the backport!

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

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

From report at bugs.python.org  Wed May 15 11:02:30 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 May 2019 15:02:30 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557932550.07.0.648807771686.issue36799@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:


New changeset 133fc89ca02b51b8d5b87556d94f1382c4ed72c1 by St?phane Wirtel (Yavor Konstantinov) in branch 'master':
bpo-36799: Fix typo in ctypes.rst (GH-13104)
https://github.com/python/cpython/commit/133fc89ca02b51b8d5b87556d94f1382c4ed72c1


----------
nosy: +matrixise

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

From report at bugs.python.org  Wed May 15 11:17:57 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 May 2019 15:17:57 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557933477.27.0.68314321958.issue36799@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

If I have no news from miss-islington about the backport of this PR, I will do it manually.

----------

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

From report at bugs.python.org  Wed May 15 11:36:47 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 May 2019 15:36:47 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557934607.5.0.384582704977.issue36799@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
pull_requests: +13253

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

From report at bugs.python.org  Wed May 15 11:53:31 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 15 May 2019 15:53:31 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1557935611.05.0.518083884096.issue36799@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:


New changeset 4fd7f56ee78a07ebadf034affc2e36db14c85c00 by St?phane Wirtel in branch '3.7':
[3.7] bpo-36799: Fix typo in ctypes.rst (GH-13104) (GH-13341)
https://github.com/python/cpython/commit/4fd7f56ee78a07ebadf034affc2e36db14c85c00


----------

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

From report at bugs.python.org  Wed May 15 12:13:59 2019
From: report at bugs.python.org (Aaron Hall)
Date: Wed, 15 May 2019 16:13:59 +0000
Subject: [docs] [issue34648] Confirm the types of parameters of
 traceback.format_list and traceback.StackSummary.from_list post-3.5
In-Reply-To: <1536782604.59.0.956365154283.issue34648@psf.upfronthosting.co.za>
Message-ID: <1557936839.75.0.996644479988.issue34648@roundup.psfhosted.org>


Change by Aaron Hall <aaronchall at yahoo.com>:


----------
nosy: +Aaron Hall

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

From report at bugs.python.org  Wed May 15 13:04:46 2019
From: report at bugs.python.org (Aaron Hall)
Date: Wed, 15 May 2019 17:04:46 +0000
Subject: [docs] [issue36927] traceback docstrings should explicitly state
 return values instead of referring to other functions
Message-ID: <1557939885.98.0.0482711491834.issue36927@roundup.psfhosted.org>


New submission from Aaron Hall <aaronchall at yahoo.com>:

I've written three (or more) answers on Stack Overflow about how to use the functions in the traceback module, and I code Python all day long.

Embarrassing confession: I just recommended the wrong traceback function in email to fix the incorrect usage of another of these functions after pulling up the docs because. I corrected myself before anyone else could correct me, but I find these docstrings incredibly frustrating and problematic.

May I please give them a little more verbiage about their return values?

e.g.:

def format_tb(tb, limit=None):
    """A shorthand for 'format_list(extract_tb(tb, limit))'."""
    return extract_tb(tb, limit=limit).format()

should be:

def format_tb(tb, limit=None):
    """A shorthand for 'format_list(extract_tb(tb, limit))',
    which returns a list of strings ready for printing'.
    """
    return extract_tb(tb, limit=limit).format()


In fact, perhaps the "shorthand" part is an implementation detail that may not even be correct (it doesn't immediately seem to be) and should be removed.

----------
assignee: docs at python
components: Documentation
messages: 342588
nosy: Aaron Hall, docs at python
priority: normal
severity: normal
status: open
title: traceback docstrings should explicitly state return values instead of referring to other functions
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Wed May 15 13:21:10 2019
From: report at bugs.python.org (SilentGhost)
Date: Wed, 15 May 2019 17:21:10 +0000
Subject: [docs] [issue36927] traceback docstrings should explicitly state
 return values instead of referring to other functions
In-Reply-To: <1557939885.98.0.0482711491834.issue36927@roundup.psfhosted.org>
Message-ID: <1557940870.34.0.168782813067.issue36927@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

The doc strings were never updated in #17911. Would you like to submit a PR for these changes? (guidelines are available at https://devguide.python.org/pullrequest/) Perhaps, you could include similar changes in Doc/library/traceback.rst ?

----------
nosy: +SilentGhost
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.7 -Python 3.9

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

From report at bugs.python.org  Wed May 15 14:11:23 2019
From: report at bugs.python.org (=?utf-8?q?Stefan_H=C3=B6lzl?=)
Date: Wed, 15 May 2019 18:11:23 +0000
Subject: [docs] [issue36928] linkt threading.settrace to sys.settrace
Message-ID: <1557943883.68.0.641257607459.issue36928@roundup.psfhosted.org>


New submission from Stefan H?lzl <stefan.la at posteo.de>:

The documentation of sys.settrace suggest to call it from every created thread
to enable tracing within threads.

I would suggest to add a link to threading.settrace which automatically sets a trace function for every by threading module created thread.

link to docs:
https://docs.python.org/3.5/library/sys.html#sys.settrace
https://docs.python.org/3.5/library/threading.html#threading.settrace

----------
assignee: docs at python
components: Documentation
messages: 342591
nosy: docs at python, stefanhoelzl
priority: normal
severity: normal
status: open
title: linkt threading.settrace to sys.settrace
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Wed May 15 14:13:48 2019
From: report at bugs.python.org (SilentGhost)
Date: Wed, 15 May 2019 18:13:48 +0000
Subject: [docs] [issue36928] linkt threading.settrace to sys.settrace
In-Reply-To: <1557943883.68.0.641257607459.issue36928@roundup.psfhosted.org>
Message-ID: <1557944028.09.0.00837383711049.issue36928@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

Would you care to submit a PR implementing this fix? There are some guidelines available at https://devguide.python.org/pullrequest/

----------
nosy: +SilentGhost
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.7 -Python 3.9

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

From report at bugs.python.org  Wed May 15 14:14:16 2019
From: report at bugs.python.org (=?utf-8?q?Stefan_H=C3=B6lzl?=)
Date: Wed, 15 May 2019 18:14:16 +0000
Subject: [docs] [issue36928] linkt threading.settrace to sys.settrace
In-Reply-To: <1557943883.68.0.641257607459.issue36928@roundup.psfhosted.org>
Message-ID: <1557944056.2.0.678203052303.issue36928@roundup.psfhosted.org>


Change by Stefan H?lzl <stefan.la at posteo.de>:


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

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

From report at bugs.python.org  Wed May 15 18:46:12 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Wed, 15 May 2019 22:46:12 +0000
Subject: [docs] [issue36932] asyncio-task.rst could use proper
 deprecated-removed directive
In-Reply-To: <1557960053.75.0.0870422245475.issue36932@roundup.psfhosted.org>
Message-ID: <1557960372.89.0.724524697949.issue36932@roundup.psfhosted.org>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 3.8

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

From report at bugs.python.org  Wed May 15 23:11:47 2019
From: report at bugs.python.org (Windson Yang)
Date: Thu, 16 May 2019 03:11:47 +0000
Subject: [docs] [issue18911] minidom does not encode correctly when calling
 Document.writexml
In-Reply-To: <1378186619.58.0.930376227557.issue18911@psf.upfronthosting.co.za>
Message-ID: <1557976307.47.0.421086852426.issue18911@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed May 15 23:12:19 2019
From: report at bugs.python.org (Windson Yang)
Date: Thu, 16 May 2019 03:12:19 +0000
Subject: [docs] [issue18911] minidom does not encode correctly when calling
 Document.writexml
In-Reply-To: <1378186619.58.0.930376227557.issue18911@psf.upfronthosting.co.za>
Message-ID: <1557976339.18.0.545584521598.issue18911@roundup.psfhosted.org>


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

I added a PR for like this:

   .. note::

      You should specify the "xmlcharrefreplace" error handler when open a file with
      specified encoding::

         writer = open(
                filename, "w", encoding="utf-8",
                errors="xmlcharrefreplace")
         doc.writexml(writer, "", "  ", "utf-8")

----------
nosy: +Windson Yang

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

From report at bugs.python.org  Thu May 16 06:06:57 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Thu, 16 May 2019 10:06:57 +0000
Subject: [docs] [issue36927] traceback docstrings should explicitly state
 return values instead of referring to other functions
In-Reply-To: <1557939885.98.0.0482711491834.issue36927@roundup.psfhosted.org>
Message-ID: <1558001217.86.0.976904013429.issue36927@roundup.psfhosted.org>


Michele Angrisano <michele.angrisano at gmail.com> added the comment:

If Aaron can't working on it, I can do it. Just tell me.

Thanks.

----------
nosy: +Michele Angrisano

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

From report at bugs.python.org  Thu May 16 09:36:45 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Thu, 16 May 2019 13:36:45 +0000
Subject: [docs] [issue36927] traceback docstrings should explicitly state
 return values instead of referring to other functions
In-Reply-To: <1557939885.98.0.0482711491834.issue36927@roundup.psfhosted.org>
Message-ID: <1558013805.81.0.315894985179.issue36927@roundup.psfhosted.org>


Change by Michele Angrisano <michele.angrisano at gmail.com>:


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

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

From report at bugs.python.org  Thu May 16 10:45:36 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Thu, 16 May 2019 14:45:36 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1558017936.19.0.8463855017.issue36675@roundup.psfhosted.org>


Jeroen Demeyer <J.Demeyer at UGent.be> added the comment:

Isn't it a *feature* that those doctest directives are not shown? Those directives are meant for the doctest module only, not for the reader of the rendered documentation.

----------
nosy: +jdemeyer

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

From report at bugs.python.org  Thu May 16 11:05:24 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 16 May 2019 15:05:24 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1558019124.39.0.242923858599.issue36675@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:

OP is about the documentation page for doctest itself!

----------

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

From report at bugs.python.org  Thu May 16 11:25:40 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 16 May 2019 15:25:40 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1558020340.44.0.907247727413.issue36675@roundup.psfhosted.org>


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

Doctest directives in code examples should be suppressed everywhere *except* in the doctest.html examples showing how to use directives.  The patch only exposes them for doctest.html and not for ctypes or anywhere else.

They really should not be in the dir example code that I linked to.
https://docs.python.org/3/library/functions.html#dir
The problem there are the double comments with both a real comment and a directive.

https://devguide.python.org/documenting/#source-code does not say anything about '::' causing suppression of comments and ':' leaving them.  It is misleading in implying the '::' is required for a code block.

----------

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

From report at bugs.python.org  Thu May 16 11:44:03 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Thu, 16 May 2019 15:44:03 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1558021443.42.0.301116284986.issue36675@roundup.psfhosted.org>


Jeroen Demeyer <J.Demeyer at UGent.be> added the comment:

> Doctest directives in code examples should be suppressed everywhere *except* in the doctest.html examples showing how to use directives.

Thanks for clarifying. I missed that.

----------

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

From report at bugs.python.org  Thu May 16 13:38:34 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 16 May 2019 17:38:34 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1558020340.44.0.907247727413.issue36675@roundup.psfhosted.org>
Message-ID: <20190516173827.GA5163@ando.pearwood.info>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

> Doctest directives in code examples should be suppressed everywhere 
> *except* in the doctest.html examples showing how to use directives.  
> The patch only exposes them for doctest.html and not for ctypes or 
> anywhere else.

Thanks for the patch, and the extra information, but I disagree with the 
decision to suppress the directives.

The reason I found this problem in the first case was that I started 
with the ctypes documentation, where it says:

"Since some code samples behave differently under Linux, Windows, or Mac 
OS X, they contain doctest directives in comments."

and I was very keen to see those directives so I could learn the right 
way to deal with platform-dependent doctests. I was very confused that 
they weren't visible.

https://docs.python.org/3/library/ctypes.html

I think that doctest directives are as much a part of documenting 
correct usage as any other part of the example code, and they are 
(semi-)human readable and (almost) self-documenting.

Consider this example from ctypes:

    >>> c_wchar_p("Hello, World")
    c_wchar_p(140018365411392)

In the absence of a directive, but knowing that it may have been 
surpressed, I don't know how to interpret that. Is the output some 
arbitrarily chosen value that doctest ought to skip? Or is that the 
actual output that c_wchar_p("Hello, World") will return every single 
time without fail?

If I was a ctypes expert, it might be blindingly obvious to me, but I'm 
not, so I'm left in the dark. I don't know whether I should expect that 
precise output each and every time, or something platform and 
implementation specific.

If the directive #doctest:+SKIP was visible, I would know that it was an 
arbitrarily chosen example. 

My preference would be:

- keep the doctest directives visible, everywhere;

- make them a clickable link to the appropriate section 
  in the doctest documentation;

- and, if possible, on mouse-over, they should display a
  tooltip with a message like 

  "The output of this example is arbitrary."

Or similar wording.

> They really should not be in the dir example code that I linked to.
> https://docs.python.org/3/library/functions.html#dir

On the contrary: I think that the presence of the +SKIP directive helps 
demonstrate that the output shown is a made-up example, not normative.

(Of course it helps that I know doctest, but even if I didn't, the 
tooltip message would help.)

----------

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

From report at bugs.python.org  Thu May 16 16:05:17 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Thu, 16 May 2019 20:05:17 +0000
Subject: [docs] [issue26515] Update extending/embedding docs to new way to
 build modules in C
In-Reply-To: <1457491421.2.0.684118231911.issue26515@psf.upfronthosting.co.za>
Message-ID: <1558037117.16.0.321379298946.issue26515@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:

Correct usage of multi-phase init might now get users stuck when they start needing per-module state. See PEP 573 "Module State Access from C Extension Methods" for the (hopefully) last thing that prevents me from generally recommending multi-phase init.

That PEP is on my list for after PRP 590 is done.
Before it's implemented, I'm happy leaving PyModuleDef_Init to experts -- that is, have it in the reference docs only.

----------

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

From report at bugs.python.org  Fri May 17 02:32:12 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 06:32:12 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1558074732.3.0.134480351724.issue36799@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


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

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

From report at bugs.python.org  Fri May 17 04:55:29 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 May 2019 08:55:29 +0000
Subject: [docs] [issue36928] linkt threading.settrace to sys.settrace
In-Reply-To: <1557943883.68.0.641257607459.issue36928@roundup.psfhosted.org>
Message-ID: <1558083329.29.0.532153888451.issue36928@roundup.psfhosted.org>


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


----------
pull_requests: +13291

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

From report at bugs.python.org  Fri May 17 05:04:20 2019
From: report at bugs.python.org (SilentGhost)
Date: Fri, 17 May 2019 09:04:20 +0000
Subject: [docs] [issue36928] linkt threading.settrace to sys.settrace
In-Reply-To: <1557943883.68.0.641257607459.issue36928@roundup.psfhosted.org>
Message-ID: <1558083860.23.0.724047820136.issue36928@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


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

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

From report at bugs.python.org  Fri May 17 05:05:15 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 09:05:15 +0000
Subject: [docs] [issue36928] linkt threading.settrace to sys.settrace
In-Reply-To: <1557943883.68.0.641257607459.issue36928@roundup.psfhosted.org>
Message-ID: <1558083915.58.0.88924270151.issue36928@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Thank you for your contribution

----------
nosy: +matrixise

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

From report at bugs.python.org  Fri May 17 05:50:26 2019
From: report at bugs.python.org (Kushal Das)
Date: Fri, 17 May 2019 09:50:26 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1558086626.68.0.140793964965.issue36908@roundup.psfhosted.org>


Kushal Das <mail at kushaldas.in> added the comment:

In future we should do the similar change for any module. This will be helpful for new beginners.

----------
nosy: +kushal.das

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

From report at bugs.python.org  Fri May 17 05:59:17 2019
From: report at bugs.python.org (Kushal Das)
Date: Fri, 17 May 2019 09:59:17 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1558087157.72.0.354987067672.issue36908@roundup.psfhosted.org>


Kushal Das <mail at kushaldas.in> added the comment:


New changeset 6faad355db6c2bd4a0ade7868f245b42c04f5337 by Kushal Das (Ned Batchelder) in branch 'master':
bpo-36908: 'This module is always available' isn't helpful. (#13297)
https://github.com/python/cpython/commit/6faad355db6c2bd4a0ade7868f245b42c04f5337


----------

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

From report at bugs.python.org  Fri May 17 06:48:34 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 May 2019 10:48:34 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1558090114.94.0.44080166832.issue36789@roundup.psfhosted.org>


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


----------
pull_requests: +13294

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

From report at bugs.python.org  Fri May 17 07:05:14 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 17 May 2019 11:05:14 +0000
Subject: [docs] [issue36789] Unicode HOWTO incorrectly states that UTF-8
 contains no zero bytes
In-Reply-To: <1556928017.33.0.648089706151.issue36789@roundup.psfhosted.org>
Message-ID: <1558091114.25.0.682461482115.issue36789@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Fri May 17 08:30:13 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 17 May 2019 12:30:13 +0000
Subject: [docs] [issue10669] Document Deprecation Warnings and how to fix
In-Reply-To: <1291959647.89.0.597449973256.issue10669@psf.upfronthosting.co.za>
Message-ID: <1558096213.52.0.295859135799.issue10669@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

If this is change is still desirable, I think it might be a good issue for someone who had contributed a few patches and is looking for something a little more challenging to work on.

----------
nosy: +cheryl.sabella, mdk, willingc
stage:  -> needs patch
versions: +Python 3.8 -Python 2.7, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri May 17 08:52:34 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 17 May 2019 12:52:34 +0000
Subject: [docs] [issue19175] Erroneous reference to "integer" in format
 string grammar
In-Reply-To: <1381032864.93.0.113807397977.issue19175@psf.upfronthosting.co.za>
Message-ID: <1558097554.34.0.104231255926.issue19175@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Format mini-language integer definition is incorrect

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

From report at bugs.python.org  Fri May 17 10:31:52 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 14:31:52 +0000
Subject: [docs] [issue36947] Fix 3.3.3.1 Metaclasses Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558103512.51.0.380319825352.issue36947@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Thank you for your report

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

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

From report at bugs.python.org  Fri May 17 10:38:56 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 14:38:56 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558103936.71.0.859053722899.issue36947@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
keywords: +easy
title: Fix 3.3.3.1 Metaclasses Documentation -> [Good first issue] Fix 3.3.3.1 Metaclasses Documentation

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

From report at bugs.python.org  Fri May 17 10:48:35 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 14:48:35 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558104515.51.0.578004276372.issue36947@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

just one question, I don't find the paragraph with this text in the code. Could you share the link of this paragraph? Thank you

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

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

From report at bugs.python.org  Fri May 17 10:49:42 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 14:49:42 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558104582.1.0.224065256503.issue36947@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Found here: https://docs.python.org/3/reference/datamodel.html#metaclasses

Thank you

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

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

From report at bugs.python.org  Fri May 17 10:51:04 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 17 May 2019 14:51:04 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558104664.48.0.206444665133.issue36947@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

If you want to modify the text, please create a PR for this file: https://github.com/python/cpython/blob/master/Doc/reference/datamodel.rst#metaclasses

Don't forget to sign the CLA, 

Thank you

----------

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

From report at bugs.python.org  Fri May 17 10:59:21 2019
From: report at bugs.python.org (Nicholas Matthews)
Date: Fri, 17 May 2019 14:59:21 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558105161.31.0.527288470465.issue36947@roundup.psfhosted.org>


Nicholas Matthews <nmatthews at asapp.com> added the comment:

Ok, I will create a PR soon and update the issue.

----------

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

From report at bugs.python.org  Fri May 17 11:27:24 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Fri, 17 May 2019 15:27:24 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558106844.51.0.682110067093.issue36947@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Clarification is fine, but "MyClass and MySubclass are instances of Meta:" is 100% true. Declaring a class to have a metaclass (or inheriting from a class with a metaclass) means that the class itself is an instance of the metaclass.

New instances of the classes with metaclass Meta are not "created using Meta"; Meta modifies the creation of the classes themselves, not instances of the classes.

Point is, your suggested change is half wrong (new instances of MyClass and MySubclass aren't directly created using Meta), and half misunderstanding the current documentation ("MyClass is an instance of Meta" already means "MyClass has the metaclass Meta").

----------
nosy: +josh.r

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

From report at bugs.python.org  Fri May 17 11:35:13 2019
From: report at bugs.python.org (Nicholas Matthews)
Date: Fri, 17 May 2019 15:35:13 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558107313.66.0.151424556922.issue36947@roundup.psfhosted.org>


Nicholas Matthews <nmatthews at asapp.com> added the comment:

Thanks for the clarification. For the first point on the correctness of the original text, that makes sense, could you link me to any relevant documentation for further reading?

On the second point "Meta modifies the creation of the classes themselves, not instances of the classes." I think this is not 100% correct. When you create an instance of a class via "instance = MyClass()", the `__call__` method of the metaclass is invoked, so metaclasses can control both class definition and instance creation.

----------

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

From report at bugs.python.org  Fri May 17 16:51:33 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 May 2019 20:51:33 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1558126293.12.0.146491210893.issue36908@roundup.psfhosted.org>


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


----------
pull_requests: +13304

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

From report at bugs.python.org  Fri May 17 17:08:24 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 May 2019 21:08:24 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1558127304.65.0.934733723823.issue36908@roundup.psfhosted.org>


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


New changeset 740a7cde9c0af5a237a7f6525b38d65a83f4fbf1 by Miss Islington (bot) in branch '3.7':
bpo-36908: 'This module is always available' isn't helpful. (GH-13297)
https://github.com/python/cpython/commit/740a7cde9c0af5a237a7f6525b38d65a83f4fbf1


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

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

From report at bugs.python.org  Fri May 17 17:10:25 2019
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 17 May 2019 21:10:25 +0000
Subject: [docs] [issue36908] "This module is always available" is confusing
In-Reply-To: <1557782122.73.0.455327263081.issue36908@roundup.psfhosted.org>
Message-ID: <1558127425.42.0.384644834739.issue36908@roundup.psfhosted.org>


Mariatta Wijaya <mariatta at python.org> added the comment:

Thanks all. I've backported the change to 3.7. I think this is good to be closed.

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

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

From report at bugs.python.org  Fri May 17 20:56:43 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Sat, 18 May 2019 00:56:43 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1558141003.08.0.907228394507.issue36947@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Ah, you're right on __call__; I've never bothered to override it on a metaclass, but yes, since a class using a metaclass is an instance of the metaclass, like all instances, calling it invokes the __call__ of its type (it's just that the default metaclass, type, has a __call__ that turns around and calls the __new__ and __init__ of the "instance", which is a class). The nomenclature is hard here.

In any event, yes, overriding __call__ will let you hook into the construction of each individual instance of the classes using the metaclass. That's not generally true of all uses of metaclasses (if __call__ is inherited from type, then while new instances are technically created using the metaclass, the metaclass is just letting the normal __new__/__init__ calls take place without interference).

There is very little in the way of Python official documentation on metaclasses; the line you proposed to change is one of the few places it's mentioned (most references to metaclasses are on that Data Model page). There are a couple of mentions in the PEPs, and a lot of off-site tutorials, but it's a poorly documented feature in general.

It's pretty easy to demonstrate the current wording is correct though:

>>> class Meta(type):
...     pass
...
>>> class MyMeta(metaclass=Meta):
...     pass
...
>>> isinstance(MyMeta, Meta)
True

Note that we're using isinstance, not issubclass, and we're not constructing a MyMeta instance. MyMeta itself is an instance of Meta.

I really think the problem here is that the documentation is correct, but so bare it's easy to miss the implications of "MyClass and MySubclass are instances of Meta"; since the classes are instances of another class, the metaclass has the same power over them that normal classes have over their instances. That's why __call__ can hook the creation of instances, __new__ can hook the creation of the class itself, __getitem__ can be used to perform lookups on the child class (in at least of the few iterations of the typing framework, that's how List[int] and the like worked; not sure if it's still that way), and properties defined on the metaclass can be accessed on classes that use it, but not their instances. It's enormously powerful, but so complex that the Python docs tend to encourage simpler, more targeted ways of tweaking classes (e.g. decorators).

----------

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

From report at bugs.python.org  Sat May 18 08:39:24 2019
From: report at bugs.python.org (Pierre Glaser)
Date: Sat, 18 May 2019 12:39:24 +0000
Subject: [docs] [issue35933] python doc does not say that the state kwarg in
 Pickler.save_reduce can be a tuple (and not only a dict)
In-Reply-To: <1549562122.06.0.315178283617.issue35933@roundup.psfhosted.org>
Message-ID: <1558183164.84.0.0326810702406.issue35933@roundup.psfhosted.org>


Change by Pierre Glaser <pierreglaser at msn.com>:


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

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

From report at bugs.python.org  Sat May 18 16:17:58 2019
From: report at bugs.python.org (Brad Solomon)
Date: Sat, 18 May 2019 20:17:58 +0000
Subject: [docs] [issue36960] Make datetime docs more user-friendly
Message-ID: <1558210678.84.0.258939294256.issue36960@roundup.psfhosted.org>


New submission from Brad Solomon <brad.solomon.1124 at gmail.com>:

The datetime docs are chalk full of detail.  This is a positive aspect,
and represents a huge amount of work by Tim Peters and A.M. Kuchling.
However, it also may function as an obstacle for beginner readers and
those simply seeking to answer a basic question or see a straightforward
usage example.  Rather than seeing an example-based explanation of
a common use-case, they are bombarded with technical detail and
edge cases.

I propose some restructuring of the datetime docs with the goal of
making them more reader-friendly.  The goal is not to eliminate any
of the detail, but to restructure things so as to bring the "everyday"
parts into more prominent real estate.

The changes here all make an effort to reflect what's espoused by
"Documenting Python" at https://devguide.python.org/documenting/.

I have some additional changes in mind but wanted to put this here now
to gauge receptiveness to the existing changes.

----------
assignee: docs at python
components: Documentation
messages: 342813
nosy: bsolomon1124, docs at python
priority: normal
pull_requests: 13321
severity: normal
status: open
title: Make datetime docs more user-friendly
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Sat May 18 16:25:30 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 18 May 2019 20:25:30 +0000
Subject: [docs] [issue36960] Make datetime docs more user-friendly
In-Reply-To: <1558210678.84.0.258939294256.issue36960@roundup.psfhosted.org>
Message-ID: <1558211130.23.0.905198361723.issue36960@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
nosy: +belopolsky, p-ganssle

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

From report at bugs.python.org  Sat May 18 16:27:21 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 18 May 2019 20:27:21 +0000
Subject: [docs] [issue36960] Make datetime docs more user-friendly
In-Reply-To: <1558210678.84.0.258939294256.issue36960@roundup.psfhosted.org>
Message-ID: <1558211241.23.0.741603510787.issue36960@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

See also issue8822.

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Sat May 18 16:36:22 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 18 May 2019 20:36:22 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
 Feb 29 if the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1558211782.67.0.437161636168.issue19376@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset 56027ccd6b9dab4a090e4fef8574933fb9a36ff2 by Cheryl Sabella (Abhishek Kumar Singh) in branch 'master':
bpo-19376: Added doc mentioning `datetime.strptime()` without a year fails for Feb 29. (GH-10243)
https://github.com/python/cpython/commit/56027ccd6b9dab4a090e4fef8574933fb9a36ff2


----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Sat May 18 16:39:32 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 18 May 2019 20:39:32 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
 Feb 29 if the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1558211972.08.0.465522361274.issue19376@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Sat May 18 17:53:56 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 18 May 2019 21:53:56 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1558216436.72.0.759838244993.issue36567@roundup.psfhosted.org>


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


New changeset eab99650799699f766c2660f4cfa8ff3f9e8457f by Berker Peksag (Batuhan Ta?kaya) in branch 'master':
bpo-36567: Use manpages_url to create links for man pages (GH-13339)
https://github.com/python/cpython/commit/eab99650799699f766c2660f4cfa8ff3f9e8457f


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

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

From report at bugs.python.org  Sat May 18 22:06:20 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 May 2019 02:06:20 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1558231580.48.0.836589264978.issue36783@roundup.psfhosted.org>


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


----------
pull_requests: +13324

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

From report at bugs.python.org  Sat May 18 22:12:04 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 May 2019 02:12:04 +0000
Subject: [docs] [issue36783] No documentation for _FromXandFold C API
 functions
In-Reply-To: <1556891515.33.0.269336043459.issue36783@roundup.psfhosted.org>
Message-ID: <1558231924.43.0.868228713111.issue36783@roundup.psfhosted.org>


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


New changeset 951b161857a840d4d14de0a5a6610e212d78ab68 by Miss Islington (bot) in branch '3.7':
bpo-36783: Add new references for C API Documentation changes (GH-13204)
https://github.com/python/cpython/commit/951b161857a840d4d14de0a5a6610e212d78ab68


----------

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

From report at bugs.python.org  Sun May 19 09:43:21 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 May 2019 13:43:21 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
In-Reply-To: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>
Message-ID: <1558273401.51.0.881229854384.issue36567@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun May 19 17:20:23 2019
From: report at bugs.python.org (Geoff Shannon)
Date: Sun, 19 May 2019 21:20:23 +0000
Subject: [docs] [issue22865] Document how to make pty.spawn not copy data
In-Reply-To: <1415901686.09.0.50650588621.issue22865@psf.upfronthosting.co.za>
Message-ID: <1558300823.94.0.850153711812.issue22865@roundup.psfhosted.org>


Geoff Shannon <earthlingzephyr at gmail.com> added the comment:

@martin.panter I removed the mention of inserting null bytes and restricted the documentation updates to more fully documenting the current behaviour.

----------

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

From report at bugs.python.org  Sun May 19 17:52:23 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 May 2019 21:52:23 +0000
Subject: [docs] [issue34580] sqlite doc: clarify the scope of the context
 manager
In-Reply-To: <1536074196.75.0.56676864532.issue34580@psf.upfronthosting.co.za>
Message-ID: <1558302743.59.0.291029446605.issue34580@roundup.psfhosted.org>


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


New changeset 287b84de939db47aa8c6f30734ceb8aba9d1db29 by Berker Peksag (Xtreak) in branch 'master':
bpo-34580: Update sqlite3 examples to call close() explicitly (GH-9079)
https://github.com/python/cpython/commit/287b84de939db47aa8c6f30734ceb8aba9d1db29


----------

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

From report at bugs.python.org  Sun May 19 17:52:39 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 May 2019 21:52:39 +0000
Subject: [docs] [issue34580] sqlite doc: clarify the scope of the context
 manager
In-Reply-To: <1536074196.75.0.56676864532.issue34580@psf.upfronthosting.co.za>
Message-ID: <1558302759.53.0.722965422672.issue34580@roundup.psfhosted.org>


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


----------
pull_requests: +13339

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

From report at bugs.python.org  Sun May 19 18:36:50 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 May 2019 22:36:50 +0000
Subject: [docs] [issue34580] sqlite doc: clarify the scope of the context
 manager
In-Reply-To: <1536074196.75.0.56676864532.issue34580@psf.upfronthosting.co.za>
Message-ID: <1558305410.65.0.999274740789.issue34580@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun May 19 18:36:52 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 May 2019 22:36:52 +0000
Subject: [docs] [issue34580] sqlite doc: clarify the scope of the context
 manager
In-Reply-To: <1536074196.75.0.56676864532.issue34580@psf.upfronthosting.co.za>
Message-ID: <1558305412.03.0.533323944585.issue34580@roundup.psfhosted.org>


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


New changeset 205c1f0e36e00e6e7cb7fbabaab4f52732859f9e by Berker Peksag (Miss Islington (bot)) in branch '3.7':
bpo-34580: Update sqlite3 examples to call close() explicitly (GH-9079)
https://github.com/python/cpython/commit/205c1f0e36e00e6e7cb7fbabaab4f52732859f9e


----------

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

From report at bugs.python.org  Sun May 19 23:36:04 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 20 May 2019 03:36:04 +0000
Subject: [docs] [issue24653] Mock.assert_has_calls([]) is surprising for
 users
In-Reply-To: <1437126004.09.0.453747784975.issue24653@psf.upfronthosting.co.za>
Message-ID: <1558323364.2.0.141702647197.issue24653@roundup.psfhosted.org>


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

I concur with Serhiy.  Current document and example describe clearly
that this API is for checking inclusion, not equality.

Current example:

"""
>>> mock = Mock(return_value=None)
>>> mock(1)
>>> mock(2)
>>> mock(3)
>>> mock(4)
>>> calls = [call(2), call(3)]
>>> mock.assert_has_calls(calls)
>>> calls = [call(4), call(2), call(3)]
>>> mock.assert_has_calls(calls, any_order=True)
"""

Empty list is allowed by same rule.  There are no exception.

And when people understand this API checks inclusion, calling with
empty list doesn't make sense at all.  So I don't think it is worth enough.

----------
nosy: +inada.naoki
resolution:  -> wont fix
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon May 20 11:06:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 20 May 2019 15:06:32 +0000
Subject: [docs] [issue22865] Document how to make pty.spawn not copy data
In-Reply-To: <1415901686.09.0.50650588621.issue22865@psf.upfronthosting.co.za>
Message-ID: <1558364792.41.0.396678750613.issue22865@roundup.psfhosted.org>


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


New changeset 522ccef8690970fc4f78f51a3adb995f2547871a by Victor Stinner (Geoff Shannon) in branch 'master':
bpo-22865: Expand on documentation for the pty.spawn function (GH-11980)
https://github.com/python/cpython/commit/522ccef8690970fc4f78f51a3adb995f2547871a


----------
nosy: +vstinner

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

From report at bugs.python.org  Mon May 20 11:14:09 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Mon, 20 May 2019 15:14:09 +0000
Subject: [docs] [issue36971] Add subsections in C API "Common Object
 Structures" page
Message-ID: <1558365249.02.0.267009483185.issue36971@roundup.psfhosted.org>


New submission from Jeroen Demeyer <J.Demeyer at UGent.be>:

The page https://docs.python.org/3/c-api/structures.html could be better structured by arranging the content in sub-sections.

----------
assignee: docs at python
components: Documentation
messages: 342911
nosy: docs at python, jdemeyer
priority: normal
severity: normal
status: open
title: Add subsections in C API "Common Object Structures" page
versions: Python 3.8

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

From report at bugs.python.org  Mon May 20 11:26:21 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Mon, 20 May 2019 15:26:21 +0000
Subject: [docs] [issue36971] Add subsections in C API "Common Object
 Structures" page
In-Reply-To: <1558365249.02.0.267009483185.issue36971@roundup.psfhosted.org>
Message-ID: <1558365981.71.0.725394935843.issue36971@roundup.psfhosted.org>


Change by Jeroen Demeyer <J.Demeyer at UGent.be>:


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

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

From report at bugs.python.org  Mon May 20 18:45:08 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 20 May 2019 22:45:08 +0000
Subject: [docs] [issue35563] Doc: warnings.rst - add links to references
In-Reply-To: <1545503608.31.0.0770528567349.issue35563@roundup.psfhosted.org>
Message-ID: <1558392308.69.0.406171046788.issue35563@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset 6220c02e09e9f3a7458d32ad774ada0ba1571cb8 by Cheryl Sabella in branch 'master':
bpo-35563: Add reference links to warnings.rst (GH-11289)
https://github.com/python/cpython/commit/6220c02e09e9f3a7458d32ad774ada0ba1571cb8


----------

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

From report at bugs.python.org  Mon May 20 18:45:38 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 20 May 2019 22:45:38 +0000
Subject: [docs] [issue35563] Doc: warnings.rst - add links to references
In-Reply-To: <1545503608.31.0.0770528567349.issue35563@roundup.psfhosted.org>
Message-ID: <1558392338.82.0.873885708626.issue35563@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Mon May 20 19:41:22 2019
From: report at bugs.python.org (Geoff Shannon)
Date: Mon, 20 May 2019 23:41:22 +0000
Subject: [docs] [issue22865] Document how to make pty.spawn not copy data
In-Reply-To: <1415901686.09.0.50650588621.issue22865@psf.upfronthosting.co.za>
Message-ID: <1558395682.26.0.254070242825.issue22865@roundup.psfhosted.org>


Change by Geoff Shannon <earthlingzephyr at gmail.com>:


----------
pull_requests: +13364

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

From report at bugs.python.org  Mon May 20 21:16:02 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 21 May 2019 01:16:02 +0000
Subject: [docs] [issue31163] Return destination path in Path.rename and
 Path.replace
In-Reply-To: <1502292744.48.0.627996317333.issue31163@psf.upfronthosting.co.za>
Message-ID: <1558401362.82.0.262378761478.issue31163@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

I've closed the original pull request as the Github user account that created it no longer exists.

----------
keywords: +easy -patch
nosy: +berker.peksag, cheryl.sabella
stage: patch review -> needs patch
versions: +Python 3.8 -Python 3.6

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

From report at bugs.python.org  Tue May 21 01:20:35 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Tue, 21 May 2019 05:20:35 +0000
Subject: [docs] [issue36984] typing docs "versionadded" is inaccurate for
 many attributes
Message-ID: <1558416035.31.0.248938950481.issue36984@roundup.psfhosted.org>


New submission from Anthony Sottile <asottile at umich.edu>:

expanding on https://bugs.python.org/issue36983

the docs are also a bit out of date in places

I'm not sure how to document something that appeared in two versions, but I'll leave that part to review.

Using data generated / collected in https://github.com/asottile/flake8-typing-imports via this script: https://github.com/asottile/flake8-typing-imports/blob/master/bin/build-generated

and then analyzed with this script:

from flake8_typing_imports import SYMBOLS

ALL = set().union(*(v for _, v in SYMBOLS))

for k in sorted(ALL):
    state = False
    for i, (v, ks) in enumerate(SYMBOLS):
        if state is False and k in ks:
            print(f'{k}: new in {v}')
            state = True
        elif state is True and k not in ks:
            print(f'=> {k}: removed in {v}')
            state = False


I've found the following:

$ python3 t.py | grep -v 'new in 3\.5\.0'
AsyncContextManager: new in 3.5.4
=> AsyncContextManager: removed in 3.6.0
AsyncContextManager: new in 3.6.2
AsyncGenerator: new in 3.6.1
AsyncIterable: new in 3.5.2
AsyncIterator: new in 3.5.2
Awaitable: new in 3.5.2
ChainMap: new in 3.5.4
=> ChainMap: removed in 3.6.0
ChainMap: new in 3.6.1
ClassVar: new in 3.5.3
Collection: new in 3.6.0
ContextManager: new in 3.5.4
Coroutine: new in 3.5.3
Counter: new in 3.5.4
=> Counter: removed in 3.6.0
Counter: new in 3.6.1
DefaultDict: new in 3.5.2
Deque: new in 3.5.4
=> Deque: removed in 3.6.0
Deque: new in 3.6.1
ForwardRef: new in 3.7.0
GenericMeta: new in 3.5.4
=> GenericMeta: removed in 3.6.0
GenericMeta: new in 3.6.1
=> GenericMeta: removed in 3.7.0
NewType: new in 3.5.2
NoReturn: new in 3.5.4
=> NoReturn: removed in 3.6.0
NoReturn: new in 3.6.2
OrderedDict: new in 3.7.2
TYPE_CHECKING: new in 3.5.2
Text: new in 3.5.2
Type: new in 3.5.2

----------
assignee: docs at python
components: Documentation
messages: 342978
nosy: Anthony Sottile, docs at python
priority: normal
severity: normal
status: open
title: typing docs "versionadded" is inaccurate for many attributes
versions: Python 3.8

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

From report at bugs.python.org  Tue May 21 01:22:57 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Tue, 21 May 2019 05:22:57 +0000
Subject: [docs] [issue36984] typing docs "versionadded" is inaccurate for
 many attributes
In-Reply-To: <1558416035.31.0.248938950481.issue36984@roundup.psfhosted.org>
Message-ID: <1558416177.76.0.400756996621.issue36984@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


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

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

From report at bugs.python.org  Tue May 21 01:35:02 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Tue, 21 May 2019 05:35:02 +0000
Subject: [docs] [issue36985] typing.ForwardRef is undocumented
Message-ID: <1558416902.0.0.868432422236.issue36985@roundup.psfhosted.org>


New submission from Anthony Sottile <asottile at umich.edu>:

- New since 3.7.0
- is exposed by some public apis:
    - the `__doc__` attribute of `typing` mentions `ForwardRef`
    - `get_type_hints` can expose an instance of it: https://bugs.python.org/issue35834

Should this be documented? including in __all__?

----------
assignee: docs at python
components: Documentation
messages: 342979
nosy: Anthony Sottile, docs at python
priority: normal
severity: normal
status: open
title: typing.ForwardRef is undocumented
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue May 21 02:20:25 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 21 May 2019 06:20:25 +0000
Subject: [docs] [issue36932] asyncio-task.rst could use proper
 deprecated-removed directive
In-Reply-To: <1557960053.75.0.0870422245475.issue36932@roundup.psfhosted.org>
Message-ID: <1558419625.97.0.64304562387.issue36932@roundup.psfhosted.org>


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


New changeset d0ebf13e50dd736cdb355fa42c23837abbb88127 by Miss Islington (bot) (Matthias Bussonnier) in branch 'master':
bpo-36932: use proper deprecation-removed directive (GH-13349)
https://github.com/python/cpython/commit/d0ebf13e50dd736cdb355fa42c23837abbb88127


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

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

From report at bugs.python.org  Tue May 21 02:33:08 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 21 May 2019 06:33:08 +0000
Subject: [docs] [issue36932] asyncio-task.rst could use proper
 deprecated-removed directive
In-Reply-To: <1557960053.75.0.0870422245475.issue36932@roundup.psfhosted.org>
Message-ID: <1558420388.36.0.48118973756.issue36932@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


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

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

From report at bugs.python.org  Tue May 21 05:37:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 21 May 2019 09:37:15 +0000
Subject: [docs] [issue22865] Document how to make pty.spawn not copy data
In-Reply-To: <1415901686.09.0.50650588621.issue22865@psf.upfronthosting.co.za>
Message-ID: <1558431435.21.0.758534858996.issue22865@roundup.psfhosted.org>


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


New changeset cdb2dbfe92b95dcd19ccab1a1e9b8c39263c54b0 by Victor Stinner (Geoff Shannon) in branch '3.7':
[3.7] bpo-22865: Expand on documentation for the pty.spawn function (GH-11980) (GH-13455)
https://github.com/python/cpython/commit/cdb2dbfe92b95dcd19ccab1a1e9b8c39263c54b0


----------

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

From report at bugs.python.org  Tue May 21 05:38:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 21 May 2019 09:38:34 +0000
Subject: [docs] [issue22865] Document how to make pty.spawn not copy data
In-Reply-To: <1415901686.09.0.50650588621.issue22865@psf.upfronthosting.co.za>
Message-ID: <1558431514.96.0.380003447701.issue22865@roundup.psfhosted.org>


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

Thanks Geoff Shannon for the doc enhancement!

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

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

From samtowers08 at gmail.com  Tue May 21 06:49:25 2019
From: samtowers08 at gmail.com (Sam Towers)
Date: Tue, 21 May 2019 20:49:25 +1000
Subject: [docs] https://docs.python.org/3/library/decimal.html documentation
 issue
Message-ID: <CAM=FQWo2PyO7a09Q7i7fds-+PDHNAfJeewZbBoBX-2NMF-VH8A@mail.gmail.com>

my python version is 3.7, running in Pycharm.

on the doc page there is:

>>> Decimal('7.325').quantize(Decimal('.01'), rounding=ROUND_DOWN)

but "name 'ROUND_DOWN' is not defined"

This worked though :)

>>> Decimal('7.325').quantize(Decimal('.01'), rounding='ROUND_DOWN')

Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190521/0b4f4feb/attachment-0001.html>

From julien at palard.fr  Tue May 21 08:46:45 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 21 May 2019 12:46:45 +0000
Subject: [docs] https://docs.python.org/3/library/decimal.html
 documentation issue
In-Reply-To: <CAM=FQWo2PyO7a09Q7i7fds-+PDHNAfJeewZbBoBX-2NMF-VH8A@mail.gmail.com>
References: <CAM=FQWo2PyO7a09Q7i7fds-+PDHNAfJeewZbBoBX-2NMF-VH8A@mail.gmail.com>
Message-ID: <vRyN616zmlu3UcqhziYn2Rn7qcoYz7EC8NRxQqY8LfUxhrHP2b-LHBtHPtQ3fAIaS4aeUNzxbH8bzUlgjTXv20ZfUySt7s4EapfEmj92AfY=@palard.fr>

Hi Sam! Thanks for reporting!

> on the doc page there is:
>
> >>> Decimal('7.325').quantize(Decimal('.01'), rounding=ROUND_DOWN)
>
> but "name 'ROUND_DOWN' is not defined"
>
> This worked though :)
>
> >>> Decimal('7.325').quantize(Decimal('.01'), rounding='ROUND_DOWN')

If you search ROUND_DOWN in the page you'll find it's a constant of the decimal module, so you're missing a:

from decimal import ROUND_DOWN

Your solution works because ROUND_DOWN is defined as "ROUND_DOWN", but you should use the constant instead :)
--?
Julien Palard
https://mdk.fr



From julien at palard.fr  Tue May 21 08:55:34 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 21 May 2019 12:55:34 +0000
Subject: [docs] Bugs in Python a,b=-6,-6
In-Reply-To: <CAKDC_f1RyA2jtVTbYhYS+iNhxhNO_PsCH33BvYCXPPf2jJsyXA@mail.gmail.com>
References: <CAKDC_f1RyA2jtVTbYhYS+iNhxhNO_PsCH33BvYCXPPf2jJsyXA@mail.gmail.com>
Message-ID: <TE9qsVPKASh-oMirsntPn3BAsKUZ9dhALUwCNUXc3NQ8V6_El-UBDx4L5fnXcz0SSt2YZX2Kp7UauJ7HqY-WPj60BZvd92DSPIc7aHZRUf8=@palard.fr>

Hi Benedic,

the id function returns an "identity of an object.", which is implementation dependent. In cpython it's the memory address, that's why it's huge numbers.

Also cpython can (and do) reuses some integers (from -5 and 256, but it's an implementation detail, this could change).

So -5 is always the same object in memory, but there can be two distinct -6 in memory, in the current implementation of cpython.

that's why id(-5) is always the same and id(-6) can vary in the same run.

This does not change anything, from a semantic point of view, as long as you're not comparing integers by using the id() or the is keyword, which you should not.

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190521/12fb113c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 17701 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190521/12fb113c/attachment-0001.png>

From julien at palard.fr  Tue May 21 09:36:59 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 21 May 2019 13:36:59 +0000
Subject: [docs] misbehaving functionality of all() function
In-Reply-To: <CAAiJ6EWr978chcu6HWs-4tML6rNyZfDAGVVAeYUDQPD_JQv1NQ@mail.gmail.com>
References: <CAAiJ6EWr978chcu6HWs-4tML6rNyZfDAGVVAeYUDQPD_JQv1NQ@mail.gmail.com>
Message-ID: <GiFFKw7epDsItHuETOHJXD4sqnold5FwQpiqhgKAvmrPBPOMM_x2nPkvDGt61lNPnwMX4XFtZV03dJbvg4ZLJY6C4J8ftGCXKvbiaNkoMpg=@palard.fr>

Hi Sai,

> I was going through python 3.6 docs and i am finding all function is behaving differently when working with variables and lists.
>
> The all() function is not iterable for complex numbers. but when I am passing complex number in list, the all function returns True.
> l = [1,2,1+12.1j]
>
> all(l)

I'm not sure to understand your question.

all() tells you if all elements of the given iterable are truthy.

So in your case all([1, 2, 1+12.1j]) returns True because at least one (in fact all) elements are truthy.

In Python, empty things, None, False, and zeroes are False, everything else is True, so 1 is truthy, 2 is truthy, also 1+12.1j. see:

>>> bool(1), bool(2), bool(1+12.1j)
(True, True, True)

When you say "behaving differently when working with variables and lists", as long as you're speaking with variable pointing to lists, it should be false, so:

x = [type anything here]
all(x) == [type the same thing here]

is always true, all does not sees the difference when passed a variable or the actual list (it sees a list object in both cases).

Bests,
--?
Julien Palard
https://mdk.fr


From julien at palard.fr  Tue May 21 09:48:15 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 21 May 2019 13:48:15 +0000
Subject: [docs] I can't read your pdf file!!!
In-Reply-To: <CAG6Bo-sSxC9oKTU-8o4MTVw_wsNExLm+6xu3f1zpawnZgtYP1w@mail.gmail.com>
References: <CAG6Bo-sSxC9oKTU-8o4MTVw_wsNExLm+6xu3f1zpawnZgtYP1w@mail.gmail.com>
Message-ID: <OpFkFuJ6cpygHom2Q8qKfVoisESkSC-e5SqlO31LqrLpwAVoW-QwRRvcKv7AI8xlP2fn7hehqA3ZPaO3dsfJ6qU8t-6ObrRdjEGFqT_AdEU=@palard.fr>

Hi,

> I want to download and view a Korean version of pdf file.
> When I open it using adobe acrobat on windows 10, English or numbers are normal, but the part written in Korean is blank.

I reported your issue here: https://github.com/python/python-docs-ko/issues/595

Feel free to subscribe to the issue for further notifications

--?
Julien Palard
https://mdk.fr


From report at bugs.python.org  Tue May 21 09:59:53 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 21 May 2019 13:59:53 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1558447193.78.0.594444036061.issue33071@roundup.psfhosted.org>


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

This has been merged for 3.8 and 3.7, but not for 2.7, since the docs have diverged far enough that the automatic backport didn't work: https://github.com/python/cpython/pull/13087#issuecomment-494402704

Given the proximity to the general end of life of the Python 2.7 documentation anyway, I'm inclined to just close this based on the 3.x changes, and not worry about the 2.7 version of the docs.

Thoughts?

----------
stage: patch review -> backport needed
versions:  -Python 3.6

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

From A.E.S.Kubba at bham.ac.uk  Tue May 21 09:52:00 2019
From: A.E.S.Kubba at bham.ac.uk (Archie Kubba)
Date: Tue, 21 May 2019 14:52:00 +0100
Subject: [docs] paperback
Message-ID: <CAMyb+yALNweMSVdY+cVcgW7jcUTu4u1EmLj7Xxfw5gzau1iAqg@mail.gmail.com>

Dear Sir/Madam,

I hope this finds you well.

I am trying to learn Python and have been looking for a book to read
throughout and learn as this is my convenient way of learning and it has
proved successful in the past when I learnt other programming languages. I
have been told that your online resources are pretty good so I was
wondering if you ever consider offering a paperback version of Python docs
or if my only option is to print them out?! I'd really appreciate it if you
can assist me in that matter.

Looking forward to hearing from you.

Best regards,

Archie

-- 
Dr A. Kubba
Associate of the Higher Education Academy
Knowledge Exchange Fellow at the Quantum Hub, School of Physics and
Astronomy, University of Birmingham
Honorary Research Fellow, Mechanical Engineering, University of Birmingham
Institute of Research and Development
97 Vincent Drive
Edgbaston
Birmingham
B15 2SQ
UK
0121 414 8376
UoB <https://www.birmingham.ac.uk/staff/profiles/mechanical/kubba-ali.aspx>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190521/b78329a8/attachment.html>

From julien at palard.fr  Tue May 21 10:46:34 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 21 May 2019 14:46:34 +0000
Subject: [docs] paperback
In-Reply-To: <CAMyb+yALNweMSVdY+cVcgW7jcUTu4u1EmLj7Xxfw5gzau1iAqg@mail.gmail.com>
References: <CAMyb+yALNweMSVdY+cVcgW7jcUTu4u1EmLj7Xxfw5gzau1iAqg@mail.gmail.com>
Message-ID: <fk7R2-qtVJw1IMTc0aNwtFDZfGReiJlfb3Ds5kppzNvdPlt1U57fazLeke5Y37afpivdj9qSfAuboPE0XQ0DOjFoJ_AxJ6eCi1pf5y7Oub8=@palard.fr>

Hi Archie,

I don't think we though about printing the documentation, but there's PDF, HTML, plaintext, and EPUB versions of them to download if of any help.

If you really want to print it, just print the PDF of the tutorial part (tutorial.pdf in the PDF archive here: [https://docs.python.org/3/download.html)](https://docs.python.org/3/download.html), it's enough to start.

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190521/13f80c3b/attachment.html>

From julien at palard.fr  Tue May 21 11:03:29 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 21 May 2019 15:03:29 +0000
Subject: [docs] Kindle version
In-Reply-To: <B298207D-9CAC-473A-BFF0-8BFE5DC1EE89@dav3.net>
References: <B298207D-9CAC-473A-BFF0-8BFE5DC1EE89@dav3.net>
Message-ID: <Fe87d0bOuJQWPTbkRKrWm4CCI1PUWKtJt8jcl0Uxi3PHO_L6-TJLYnjNfvSXeKr7Pkwx-vpZr3iUneWvaoZvjiwGkDtQmLmSku5fTFbZalQ=@palard.fr>

Hi Dave,

> Is it possible to create a version nicely viewable for the kindle?

We're building PDF versions of the documentation, downloadable here: https://docs.python.org/3/download.html is it enough to view them on your proprietary device?

Bests,
--?
Julien Palard
https://mdk.fr


From report at bugs.python.org  Tue May 21 14:55:59 2019
From: report at bugs.python.org (Tal Einat)
Date: Tue, 21 May 2019 18:55:59 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
 Feb 29 if the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1558464959.23.0.677712154914.issue19376@roundup.psfhosted.org>


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


----------
pull_requests: +13381

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

From report at bugs.python.org  Tue May 21 14:59:22 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 21 May 2019 18:59:22 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1558465162.31.0.205546241166.issue33071@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:

My preference would be to have 2.7 doc accurate.

Let?s wait a little bit to see if someone picks this up?

----------

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

From report at bugs.python.org  Tue May 21 15:01:59 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 21 May 2019 19:01:59 +0000
Subject: [docs] [issue24653] Mock.assert_has_calls([]) is surprising for
 users
In-Reply-To: <1437126004.09.0.453747784975.issue24653@psf.upfronthosting.co.za>
Message-ID: <1558465319.28.0.732713490723.issue24653@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:

> And when people understand this API checks inclusion, calling with
empty list doesn't make sense at all. 

I can see a thought process being ?all my other tests use thing.assert_has_calls([call0, call1]), here let?s check there are no calls with thing2.assert_has_calls([])?.

Are the correct methods advertised in the right place?  (I don?t use mock so I forgot if there is a method to assert not called or if it?s assertEqual(mock calls count, 0) or some False property)

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

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

From report at bugs.python.org  Tue May 21 15:04:02 2019
From: report at bugs.python.org (Tal Einat)
Date: Tue, 21 May 2019 19:04:02 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
 Feb 29 if the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1558465442.3.0.416261279339.issue19376@roundup.psfhosted.org>


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


New changeset 390d88e49c55c15fac7cdf60b649a4b9b15d189b by Tal Einat in branch '3.7':
[3.7] bpo-19376: Added doc mentioning `datetime.strptime()` without a year fails for Feb 29. (GH-10243)
https://github.com/python/cpython/commit/390d88e49c55c15fac7cdf60b649a4b9b15d189b


----------

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

From report at bugs.python.org  Tue May 21 15:05:34 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 21 May 2019 19:05:34 +0000
Subject: [docs] [issue24653] Mock.assert_has_calls([]) is surprising for
 users
In-Reply-To: <1437126004.09.0.453747784975.issue24653@psf.upfronthosting.co.za>
Message-ID: <1558465534.16.0.853196290706.issue24653@roundup.psfhosted.org>


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

> Are the correct methods advertised in the right place?  (I don?t use mock so I forgot if there is a method to assert not called or if it?s assertEqual(mock calls count, 0) or some False property)

There is assert_not_called https://docs.python.org/3/library/unittest.mock.html#unittest.mock.Mock.assert_not_called

>>> from unittest.mock import Mock
>>> m = Mock()
>>> m.assert_not_called()

----------

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

From report at bugs.python.org  Tue May 21 17:09:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 21 May 2019 21:09:58 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
 Feb 29 if the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1558472997.94.0.836850127551.issue19376@roundup.psfhosted.org>


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

Thanks Abhishek Kumar Singh! more doc is really helpful, handling date and time is hard :-(

----------

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

From report at bugs.python.org  Tue May 21 21:32:31 2019
From: report at bugs.python.org (Paul Monson)
Date: Wed, 22 May 2019 01:32:31 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1558488751.14.0.967325311228.issue36799@roundup.psfhosted.org>


Change by Paul Monson <paulmons at gmail.com>:


----------
pull_requests: +13393

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

From report at bugs.python.org  Tue May 21 22:09:15 2019
From: report at bugs.python.org (Dennis Sweeney)
Date: Wed, 22 May 2019 02:09:15 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
Message-ID: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>


New submission from Dennis Sweeney <sweeney.dennis650 at gmail.com>:

I understand that the SequenceMatcher's ratio method does not guarantee that SequenceMatcher(None, a, b).ratio() == SequenceMatcher(None, b, a).ratio(). Below is a counterexample:

    # Example from https://mail.python.org/pipermail/python-list/2010-November/593063.html
    >>> SequenceMatcher(None, 'BRADY', 'BYRD').ratio()
    0.6666666666666666
    >>> SequenceMatcher(None, 'BYRD', 'BRADY').ratio()
    0.4444444444444444

I was recently solving a problem that required a textual similarity ratio function and I wrongly assumed that SequenceMatcher treated both input strings symmetrically, which was an extremely difficult bug to find, especially because for many simple tests, the ratio IS symmetric:

    >>> SequenceMatcher(None, 'apple', 'banana').ratio()
    0.18181818181818182
    >>> SequenceMatcher(None, 'banana', 'apple').ratio()
    0.18181818181818182

I would like to see a clearer warning of this asymmetry in the documentation for the difflib module. Perhaps something like

      .. note::

         Caution: The result of a :meth:`ratio` call is *NOT* symmetric with 
         respect to the order of the arguments. For instance::
            
            >>> SequenceMatcher(None, 'brady', 'byrd').ratio()
            0.6666666666666666
            >>> SequenceMatcher(None, 'byrd', 'brady').ratio()
            0.4444444444444444

Without such a note near the ratio methods' documentations, it is far too easy to google for a Python stdlib functionality for computing text similarity, skip straight to the ratio method, look at the examples given, try some of your own simple examples, and accidentally convince oneself that this symmetry exists.

----------
messages: 343138
nosy: Dennis Sweeney, docs at python
priority: normal
severity: normal
status: open
title: SequenceMatcher.ratio() noncommutativity not well-documented

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

From report at bugs.python.org  Tue May 21 22:20:04 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 22 May 2019 02:20:04 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1558491604.01.0.911866587433.issue37004@roundup.psfhosted.org>


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


----------
nosy: +tim.peters

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

From report at bugs.python.org  Tue May 21 22:21:34 2019
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 22 May 2019 02:21:34 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1558491694.55.0.266897519777.issue37004@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed May 22 02:45:37 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 22 May 2019 06:45:37 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1558507537.82.0.651047957077.issue36799@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
pull_requests:  -13393

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

From report at bugs.python.org  Wed May 22 02:45:59 2019
From: report at bugs.python.org (Paul Monson)
Date: Wed, 22 May 2019 06:45:59 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1558507559.66.0.635030353811.issue36799@roundup.psfhosted.org>


Change by Paul Monson <paulmons at gmail.com>:


----------
pull_requests: +13400

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

From report at bugs.python.org  Wed May 22 04:07:08 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Wed, 22 May 2019 08:07:08 +0000
Subject: [docs] [issue36799] Typo in ctypes documentation
In-Reply-To: <1557036542.96.0.672219946485.issue36799@roundup.psfhosted.org>
Message-ID: <1558512428.22.0.232967303013.issue36799@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
pull_requests:  -13400

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

From jorgeminguet at gmail.com  Tue May 21 22:25:49 2019
From: jorgeminguet at gmail.com (Jorge Minguet)
Date: Tue, 21 May 2019 23:25:49 -0300
Subject: [docs] It may be a bug
Message-ID: <CAPXhNyTaCcPgRHO9yoThtEb3bJuAXwQW59VZmN7U201Fs3R2OQ@mail.gmail.com>

 Hi
just to report last lines results seems to obtain some extra numbers. it
may be a bug
>>> v[0:5]=6,7,8,9,0
>>> v
[6, 7, 8, 9, 0]
>>> v[-1]=6,7
>>> v
[6, 7, 8, 9, (6, 7)]
>>> v[-1:-5]=6,7,9,0,5
>>> v
[6, 7, 8, 9, 6, 7, 9, 0, 5, (6, 7)]
>>> v[-5:-1]=6,7,9,0,5
>>> v
[6, 7, 8, 9, 6, 6, 7, 9, 0, 5, (6, 7)]
>>>
if it is not disregard this message

Saludos cordiales,
Jorge Minguet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190521/3c4413cc/attachment-0001.html>

From julien at palard.fr  Wed May 22 05:29:43 2019
From: julien at palard.fr (Julien Palard)
Date: Wed, 22 May 2019 09:29:43 +0000
Subject: [docs] It may be a bug
In-Reply-To: <CAPXhNyTaCcPgRHO9yoThtEb3bJuAXwQW59VZmN7U201Fs3R2OQ@mail.gmail.com>
References: <CAPXhNyTaCcPgRHO9yoThtEb3bJuAXwQW59VZmN7U201Fs3R2OQ@mail.gmail.com>
Message-ID: <uuN3RWpDgqj1VUj8Ti1Sr1HW0c7De6bcnSQtShtG0cYo6empqC87h8ysY09KoKMEf_sCSp6pQRKy-NqijzPG0LuHVrB7Lz7_B4RF_hO2Mi0=@palard.fr>

Hi Jorge,

> just to report last lines results seems to obtain some extra numbers. it may be a bug

Slices in Python starts with an inclusive bound and end with an exclusive bound.
Quoting the documentations, s[i:j] is:
> The slice of s from i to j is defined as the sequence of items with index k such that `i <= k < j`

Given:

??? alist = list(range(10))

We can see that:

??? >>> alist[2:5]
??? [2, 3, 4]
??? >>> alist[5:2]
??? []

Note that the second one, "from 5 to 2" is empty, yet starts at position 5, so when we assign to it, it will "erase" no values, yet have a place to put new values:

In this case, we're replacing all items of index k such as 2 <= k < 5, so index 2, 3, 4, so we're replacing 3 items by two items, the resulting length is 9:

??? >>> alist = list(range(10))
??? >>> alist[2:5] = 'a', 'b'
??? >>> alist
??? [0, 1, 'a', 'b', 5, 6, 7, 8, 9]

Here we're replacing all items of index k such as 5 <= k < 2, which can't exist, so we're replacing 0 items by two items, the resulting length is 12, note that they are not inserted randomly, they are inserted at the index where the empty slice starts:

??? >>> alist = list(range(10))
??? >>> alist[5:2] = 'a', 'b'
??? >>> alist
??? [0, 1, 2, 3, 4, 'a', 'b', 5, 6, 7, 8, 9]

In your example:

>>> v = []
>>> v[0:5]=6,7,8,9,0
>>> v[-1]=6,7
>>> v
[6, 7, 8, 9, (6, 7)]
>>> v[-1:-5]? # An empty slice, so assigning to it will only add elements at position -1
[]
>>> v[-1:-5]='a','b','c','d','e'
>>> v
[6, 7, 8, 9, 'a', 'b', 'c', 'd', 'e', (6, 7)]
>>> v[-5:-1]? # A non empty slice, so assigning to it will replace b, c, d, and e with A, B, C, D and E
['b', 'c', 'd', 'e']
>>> v[-5:-1]='A','B','C','D','E'
>>> v
[6, 7, 8, 9, 'a', 'A', 'B', 'C', 'D', 'E', (6, 7)]

Does it helps?

Bests,
--?
Julien Palard
https://mdk.fr


From julien at palard.fr  Wed May 22 05:38:29 2019
From: julien at palard.fr (Julien Palard)
Date: Wed, 22 May 2019 09:38:29 +0000
Subject: [docs] Python.remove() function working on all list instead of
 one.
In-Reply-To: <KL1PR0201MB2117AB45470D7CEA444E8D88FE250@KL1PR0201MB2117.apcprd02.prod.outlook.com>
References: <KL1PR0201MB2117AB45470D7CEA444E8D88FE250@KL1PR0201MB2117.apcprd02.prod.outlook.com>
Message-ID: <LcqkX7d0XYrYdvNNkm_e_A-N5ynkUF4WI7Qj3YpO2Asym6oJb2mqDVmx-jUjQacBnAiyS83p4g0wcdC6GEzWVrKHXM9qXx6Q0b4XVIPmF9o=@palard.fr>

Hi Shayer,

Thanks for reporting!

In this case, you're having a single list, but three names to name it: The list is [1, 2, 3, 4, 5] and the list names are a, b, and c.

So when you modify a list by one of its name, you can see the modification thrue the other names. Not only for deletions:

>>> a = list(range(10))
>>> b = a
>>> a.append('foo')
>>> b
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 'foo']

If you want two lists you can create two distinct lists, or use the copy method:

>>> a = list(range(10))
>>> b = a.copy()
>>> a.append(42)
>>> b
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

Hope it helps!
Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190522/ad0c959f/attachment.html>

From report at bugs.python.org  Wed May 22 05:54:07 2019
From: report at bugs.python.org (Robert Collins)
Date: Wed, 22 May 2019 09:54:07 +0000
Subject: [docs] [issue24653] Mock.assert_has_calls([]) is surprising for
 users
In-Reply-To: <1437126004.09.0.453747784975.issue24653@psf.upfronthosting.co.za>
Message-ID: <1558518847.47.0.837942727118.issue24653@roundup.psfhosted.org>


Robert Collins <robertc at robertcollins.net> added the comment:

I'm reopening this because I don't agree.

I opened the bug because we have evidence that users find the current documentation confusing. Saying that its not confusing to us doesn't fix the confusion.

Why should we mention the special case of an empty set? Because its the only special case.

A simple single sentence: "Note:  to assert that no calls were made see `assert_not_called`" would probably both cover the special case and direct users to the right place for that use case.

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

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

From report at bugs.python.org  Wed May 22 06:00:21 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 22 May 2019 10:00:21 +0000
Subject: [docs] [issue24653] Mock.assert_has_calls([]) is surprising for
 users
In-Reply-To: <1437126004.09.0.453747784975.issue24653@psf.upfronthosting.co.za>
Message-ID: <1558519221.59.0.612599342535.issue24653@roundup.psfhosted.org>


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

> I opened the bug because we have evidence that users find the current documentation confusing. Saying that its not confusing to us doesn't fix the confusion.

Is there evidence people get confused by the document?

I suppose people get confused because they guessed behavior from existing assert_has_calls usages, without reading docs.
If they guess without reading doc, adding anything in doc doesn't help them.

The document describe well it tests inclusion, not equality.  There are no confusion about it.

----------

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

From julien at palard.fr  Wed May 22 07:17:04 2019
From: julien at palard.fr (Julien Palard)
Date: Wed, 22 May 2019 11:17:04 +0000
Subject: [docs] Clean up dead links in the docs
In-Reply-To: <31f485e7-216c-ca27-dca7-cd6d1c4a2305@kth.se>
References: <31f485e7-216c-ca27-dca7-cd6d1c4a2305@kth.se>
Message-ID: <0sXtPuz3cmGjBR88a_WeUdw57mh9UIvSuwGpuPhjvV2g-wUBiYaaeoFS7JMPv6U2ctpDu5HbBKCKTHCsHtHqBs1XGO6RnKHzs3LuXcig-1E=@palard.fr>

Hi Ashwin, thanks for your work!

> I took some time to filter out all the links and check them using cURL
> with the script attached.

Here's what I got:

> https://pythonhosted.org/pyobjc/ 404

Found https://pypi.org/project/pyobjc/.

> https://www.jwz.org/doc/content-length.html 403
> https://www.jwz.org/doc/content-length.html 403
> https://www.jwz.org/doc/content-length.html 403

Only blocks curl, works with graphical user agents.

> http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html 000

Works for me.

> https://cnswww.cns.cwru.edu/php/chet/readline/rluserman.html#SEC9 000

Found https://tiswww.cwru.edu/php/chet/readline/rluserman.html#SEC9

> http://tcl.activestate.com/ 000

Found https://tcl.tk

> http://www.tldp.org/HOWTO/XML-RPC-HOWTO/index.html 000

Works for me.

> https://www.microsoft.com/com/ 404

Found https://docs.microsoft.com/en-us/windows/desktop/com/component-object-model--com--portal

> http://oldwiki.mingw.org/index.php/Python 0.000000e+00xtensions 404

Found http://www.mingw.org/wiki/FAQ#toc14

> http://catb.org/~esr/trove/ 000

Works for me.

> http://sphinx-doc.org/examples.html 404

Found http://www.sphinx-doc.org/en/master/examples.html

> https://hg.python.org/cpython/file/3.2/Misc/NEWS 504

Found https://github.com/python/cpython/blob/260a788767ff6dadd04ecf9e9e26b363ca28c8ae/Misc/NEWS

> https://parlab.eecs.berkeley.edu/wiki/_media/patterns/paraplop_g1_3.pdf 500

Found http://osl.cs.illinois.edu/media/papers/karmani-2009-barrier_synchronization_pattern.pdf

> http://greenteapress.com/semaphores/downey08semaphores.pdf 404

Found https://greenteapress.com/semaphores/LittleBookOfSemaphores.pdf

> http://hginit.com 000

Found https://www.mercurial-scm.org/wiki/QuickStart

I created a PR to reflect those changes here: https://github.com/python/cpython/pull/13491
You can proofread it :)

Bests,
--?
Julien Palard
https://mdk.fr


From report at bugs.python.org  Wed May 22 08:46:46 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 22 May 2019 12:46:46 +0000
Subject: [docs] [issue24653] Mock.assert_has_calls([]) is surprising for
 users
In-Reply-To: <1437126004.09.0.453747784975.issue24653@psf.upfronthosting.co.za>
Message-ID: <1558529206.75.0.659690966321.issue24653@roundup.psfhosted.org>


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

alist.extend([]) is also a special case, but it is not explicitly documented, because it is not exceptional.

----------

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

From julien at palard.fr  Wed May 22 10:12:41 2019
From: julien at palard.fr (Julien Palard)
Date: Wed, 22 May 2019 14:12:41 +0000
Subject: [docs] Please document sqlite3 return values
In-Reply-To: <fb1961fa-5ca6-cbd7-1f0e-4c3a1885d683@adversary.io>
References: <fb1961fa-5ca6-cbd7-1f0e-4c3a1885d683@adversary.io>
Message-ID: <pZoM08ruhG9Fuigu7BgbYFxVxRxUYwYyWc9Pz4m_nOIlwtmfbile_6IgG6yZYn_s0VASM6cEg88FgAHJ4cc9kKx9OkHftyRO9g8TlxswHho=@palard.fr>

Hi Bjartur, thanks for reporting,

> when I use the Python 3.7 from the public Docker image 2afe3d389ba0, fetchone seems to return (0,) when no row matches the query. Confusingly, fetchmany and fetchall are only documented as returnig "a list". A more specific type declaration or description of the hierarchical return type would be appreciated.

Do you have a script to reproduce the issue?

Here what I have tested (out of docker):

>>> import sqlite3
>>> con = sqlite3.connect(":memory:")
>>> cur = con.cursor()
>>> cur.executescript("""
...???? create table person(
...???????? firstname,
...???????? lastname,
...???????? age
...???? );
...
...???? create table book(
...???????? title,
...???????? author,
...???????? published
...???? );
...
...???? insert into book(title, author, published)
...???? values (
...???????? 'Dirk Gently''s Holistic Detective Agency',
...???????? 'Douglas Adams',
...???????? 1987
...???? );
...???? """)
<sqlite3.Cursor object at 0x7f53c5c645e0>
>>> cur.execute("select * from book").fetchall()
[("Dirk Gently's Holistic Detective Agency", 'Douglas Adams', 1987)]
>>> cur.execute("select * from book").fetchone()
("Dirk Gently's Holistic Detective Agency", 'Douglas Adams', 1987)
>>> cur.execute("select * from book")
<sqlite3.Cursor object at 0x7f53c5c645e0>
>>> cur.fetchone()
("Dirk Gently's Holistic Detective Agency", 'Douglas Adams', 1987)
>>> cur.fetchone()
>>> cur.fetchone() is None
True
>>> cur.execute("select * from book where title = 'pouette'")
<sqlite3.Cursor object at 0x7f53c5c645e0>
>>> cur.fetchone()
>>> cur.fetchone() is None
True

--?
Julien Palard
https://mdk.fr


From julien at palard.fr  Wed May 22 10:36:20 2019
From: julien at palard.fr (Julien Palard)
Date: Wed, 22 May 2019 14:36:20 +0000
Subject: [docs] Consultation: Free publication of the Chinese simplified
 version of python documents, whether I need to be authorized
In-Reply-To: <238fa84f.2423.16a243b113e.Coremail.15061116790@163.com>
References: <238fa84f.2423.16a243b113e.Coremail.15061116790@163.com>
Message-ID: <OGuWBl2EfvTlSAhQGocqMMfnLxcwGa0VDlSTDJlL7V1yzCjiV9TKqqK-xuaAzx_TnaqG56-r09DzJbWMhaAyLRmFA17X9WjKVpHe9YPmrSA=@palard.fr>

Hi!

> I am writing a letter to you. I want to know if I translate the python's document into Chinese and publish it freely. Do I need to be authorized?

There's an official translation of the Python documentation in Chinese : https://github.com/python/python-docs-zh-cn and https://github.com/python/python-docs-zh-tw

--?
Julien Palard
https://mdk.fr


From iris.lapinski at appsforgood.org  Wed May 22 09:25:46 2019
From: iris.lapinski at appsforgood.org (Iris Lapinski)
Date: Wed, 22 May 2019 15:25:46 +0200
Subject: [docs] Turtle 24.5.1. Introduction
Message-ID: <CAEq=Qcs-Rz5Yk5vS+46J5nLnHBSWqpM3GL+FNnHo64rTOPZkMA@mail.gmail.com>

Dear Python community,

I would like to flag a documentation bug to you in
https://docs.python.org/2/library/turtle.html

It says right now:
"Turtle graphics is a popular way for introducing programming to kids. It
was part of the original Logo programming language developed by Wally
Feurzig and Seymour Papert in 1966."

The Wikipedia entry says this: "Logo is an educational programming
language, designed in 1967 by Wally Feurzeig, Seymour Papert, and Cynthia
Solomon. " I can see three mistakes:

   - Wally Feuerzeig is misspelled
   - the year is wrong
   - Cynthia Solomon is not credited

Can you please correct this?

Thanks,
Iris

-- 
Iris Lapinski
Founder & CEO
Apps for Good

iris.lapinski at appsforgood.org
M: +49 162 8203566
W: appsforgood.org <http://www.appsforgood.org/>
<http://www.appsforgood.org/>
Follow us: LinkedIn <http://linkd.in/appsforgood-linkedin> / Twitter
<https://twitter.com/appsforgood> / Facebook
<https://www.facebook.com/appsforgood>

Apps for Good registered in England and Wales Co. Reg. No. 6560779; UK
Registered Charity No. 1133656
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190522/e5a7c43f/attachment.html>

From julien at palard.fr  Wed May 22 11:02:59 2019
From: julien at palard.fr (Julien Palard)
Date: Wed, 22 May 2019 15:02:59 +0000
Subject: [docs] ntuple forward reference
In-Reply-To: <a10fce76-1842-a9fc-ab0f-70167be893ce@lancaster.ac.uk>
References: <a10fce76-1842-a9fc-ab0f-70167be893ce@lancaster.ac.uk>
Message-ID: <9Nawu92EtNIA2Mei0gD1H_BilFRUlSbSvLt1Pu2PVObGDrPJoMmiHV5BID8FJPF4yn0PTilY-xDgR1WXfT9_M1Ennas_0KS3PFn_vVT6bvo=@palard.fr>

Hi Finch, thanks for reporting!

>  In the Python Tutorial, the  term "tuple" is used a number of times long  before it is defined.

I opened a PR to add a forward reference:
https://github.com/python/cpython/pull/13499

For the other missing forward reference of tuple being mentionned in List Comprehensions before being introduced I think we should move 5.3 Tuples before 5.1.3 List Comprehensions, what do you think?

--?
Julien Palard
https://mdk.fr


From report at bugs.python.org  Wed May 22 13:26:07 2019
From: report at bugs.python.org (Grant Wu)
Date: Wed, 22 May 2019 17:26:07 +0000
Subject: [docs] [issue37014] fileinput module should document that openhook
 and mode are ignored when reading from stdin
Message-ID: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>


New submission from Grant Wu <grant.wu at petuum.com>:

https://github.com/python/cpython/blob/master/Lib/fileinput.py#L326 shows that the openhook and mode are ignored when reading from stdin.

Since part of fileinput's functionality is to abstract over whether one is reading from stdin or over a file, I think this abstraction leak should be documented.  One common use case where this might break is when attempting to set the file encoding using the included fileinput.hook_encoded functionality.

----------
assignee: docs at python
components: Documentation
messages: 343221
nosy: Grant Wu2, docs at python
priority: normal
severity: normal
status: open
title: fileinput module should document that openhook and mode are ignored when reading from stdin
versions: Python 3.7

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

From stephane at wirtel.be  Thu May 23 02:54:13 2019
From: stephane at wirtel.be (=?utf-8?B?U3TDqXBoYW5l?= Wirtel)
Date: Thu, 23 May 2019 08:54:13 +0200
Subject: [docs] Turtle 24.5.1. Introduction
In-Reply-To: <CAEq=Qcs-Rz5Yk5vS+46J5nLnHBSWqpM3GL+FNnHo64rTOPZkMA@mail.gmail.com>
References: <CAEq=Qcs-Rz5Yk5vS+46J5nLnHBSWqpM3GL+FNnHo64rTOPZkMA@mail.gmail.com>
Message-ID: <20190523065413.ov5rus2oxnypnwyt@xps>

Thank you Iris,

I have proposed a Pull Request for this change, 

https://github.com/python/cpython/pull/13520

I have asked to Inada Naoki and Julien Palard to review my PR.

Have a nice day,

St?phane

On 05/22, Iris Lapinski wrote:
>Dear Python community,
>
>I would like to flag a documentation bug to you in
>https://docs.python.org/2/library/turtle.html
>
>It says right now:
>"Turtle graphics is a popular way for introducing programming to kids. It
>was part of the original Logo programming language developed by Wally
>Feurzig and Seymour Papert in 1966."
>
>The Wikipedia entry says this: "Logo is an educational programming
>language, designed in 1967 by Wally Feurzeig, Seymour Papert, and Cynthia
>Solomon. " I can see three mistakes:
>
>   - Wally Feuerzeig is misspelled
>   - the year is wrong
>   - Cynthia Solomon is not credited
>
>Can you please correct this?
>
>Thanks,
>Iris
>
>-- 
>Iris Lapinski
>Founder & CEO
>Apps for Good
>
>iris.lapinski at appsforgood.org
>M: +49 162 8203566
>W: appsforgood.org <http://www.appsforgood.org/>
><http://www.appsforgood.org/>
>Follow us: LinkedIn <http://linkd.in/appsforgood-linkedin> / Twitter
><https://twitter.com/appsforgood> / Facebook
><https://www.facebook.com/appsforgood>
>
>Apps for Good registered in England and Wales Co. Reg. No. 6560779; UK
>Registered Charity No. 1133656

>_______________________________________________
>docs mailing list
>docs at python.org
>https://mail.python.org/mailman/listinfo/docs


-- 
St?phane Wirtel - https://wirtel.be - @matrixise

From report at bugs.python.org  Thu May 23 03:35:01 2019
From: report at bugs.python.org (SilentGhost)
Date: Thu, 23 May 2019 07:35:01 +0000
Subject: [docs] [issue37019] Create symlinks relative to cwd
In-Reply-To: <1558595342.46.0.940919584419.issue37019@roundup.psfhosted.org>
Message-ID: <1558596901.94.0.723877153718.issue37019@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

This would be backward incompatible change. I just wanted to point out that the symlink was only broken because the file did not exist, and one might want to legitimately create a link relative to the target's location. I'd imagine creating a link in the same directory is one such example. I think the issue you're raising can be addressed in documentation, by making clear that the relative link will be relative to target. This is already done in the given example for symlink_to, but could be improved using a target in subdirectory and a clarifying note.

The relative_to issue does indeed deserve a separate issue (if there isn't one already).

----------
assignee:  -> docs at python
components: +Documentation
nosy: +SilentGhost, docs at python, serhiy.storchaka
title: using pathlib objects to create symlinks produces broken links -> Create symlinks relative to cwd
versions: +Python 3.8

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

From report at bugs.python.org  Thu May 23 04:01:14 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Thu, 23 May 2019 08:01:14 +0000
Subject: [docs] [issue37014] [First easy issue] fileinput module should
 document that openhook and mode are ignored when reading from stdin
In-Reply-To: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>
Message-ID: <1558598474.71.0.520503103331.issue37014@roundup.psfhosted.org>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi Grant,

Thank you for your bug report,

Would you interested to propose a Pull Request for a fix? You can read the devguide for more info https://devguide.python.org/

Thank you

----------
nosy: +matrixise
title: fileinput module should document that openhook and mode are ignored when reading from stdin -> [First easy issue] fileinput module should document that openhook and mode are ignored when reading from stdin

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

From report at bugs.python.org  Thu May 23 04:01:26 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Thu, 23 May 2019 08:01:26 +0000
Subject: [docs] [issue37014] [First easy issue] fileinput module should
 document that openhook and mode are ignored when reading from stdin
In-Reply-To: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>
Message-ID: <1558598486.91.0.181734167153.issue37014@roundup.psfhosted.org>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
keywords: +easy

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

From stockenscott at gmail.com  Thu May 23 03:43:16 2019
From: stockenscott at gmail.com (Scott stocken)
Date: Thu, 23 May 2019 00:43:16 -0700
Subject: [docs] For getting more information about python project in beginner
Message-ID: <CAMhtLcV-js9OBETK=_DKEHdxqgJdGDAjaaC8UkvU30KGz-oZZQ@mail.gmail.com>

Hello sir
I want to get some information about the python project please help me
I am the beginner python programmer  okay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190523/989013ba/attachment-0001.html>

From julien at palard.fr  Thu May 23 04:55:20 2019
From: julien at palard.fr (Julien Palard)
Date: Thu, 23 May 2019 08:55:20 +0000
Subject: [docs] For getting more information about python project in
 beginner
In-Reply-To: <CAMhtLcV-js9OBETK=_DKEHdxqgJdGDAjaaC8UkvU30KGz-oZZQ@mail.gmail.com>
References: <CAMhtLcV-js9OBETK=_DKEHdxqgJdGDAjaaC8UkvU30KGz-oZZQ@mail.gmail.com>
Message-ID: <qMnAoBz2m2PKSyE4IiAhu2LdONDqbfKyGA03k50_eiBpe-RqjbY-jEiLOb-vQMcZM6QYDwHWusPqy1JEx7cXrN3qmmoAS6DbVA_T0I1g-MU=@palard.fr>

Hi Scott,

> I want to get some information about the python project please help me
> I am the beginner python programmer  okay

You can start by reading the official Python Tutorial here: https://docs.python.org/3/tutorial/

Hope it helps,
--?
Julien Palard
https://mdk.fr


From jorgeminguet at gmail.com  Thu May 23 10:26:40 2019
From: jorgeminguet at gmail.com (Jorge Minguet)
Date: Thu, 23 May 2019 11:26:40 -0300
Subject: [docs] It may be a bug
In-Reply-To: <uuN3RWpDgqj1VUj8Ti1Sr1HW0c7De6bcnSQtShtG0cYo6empqC87h8ysY09KoKMEf_sCSp6pQRKy-NqijzPG0LuHVrB7Lz7_B4RF_hO2Mi0=@palard.fr>
References: <CAPXhNyTaCcPgRHO9yoThtEb3bJuAXwQW59VZmN7U201Fs3R2OQ@mail.gmail.com>
 <uuN3RWpDgqj1VUj8Ti1Sr1HW0c7De6bcnSQtShtG0cYo6empqC87h8ysY09KoKMEf_sCSp6pQRKy-NqijzPG0LuHVrB7Lz7_B4RF_hO2Mi0=@palard.fr>
Message-ID: <CAPXhNyRnRoBJQu5FaR8NL3Q0=5=9kypwEtB6SEa8z4GYdpxkaw@mail.gmail.com>

Hi Julien,
Thank you for your answer. Cristal clear your explanation! I understand now
what I was doing wrong, thanks very much!
Best regards
Jorge Minguet

El mi?., 22 may. 2019 a las 6:29, Julien Palard (<julien at palard.fr>)
escribi?:

> Hi Jorge,
>
> > just to report last lines results seems to obtain some extra numbers. it
> may be a bug
>
> Slices in Python starts with an inclusive bound and end with an exclusive
> bound.
> Quoting the documentations, s[i:j] is:
> > The slice of s from i to j is defined as the sequence of items with
> index k such that `i <= k < j`
>
> Given:
>
>     alist = list(range(10))
>
> We can see that:
>
>     >>> alist[2:5]
>     [2, 3, 4]
>     >>> alist[5:2]
>     []
>
> Note that the second one, "from 5 to 2" is empty, yet starts at position
> 5, so when we assign to it, it will "erase" no values, yet have a place to
> put new values:
>
> In this case, we're replacing all items of index k such as 2 <= k < 5, so
> index 2, 3, 4, so we're replacing 3 items by two items, the resulting
> length is 9:
>
>     >>> alist = list(range(10))
>     >>> alist[2:5] = 'a', 'b'
>     >>> alist
>     [0, 1, 'a', 'b', 5, 6, 7, 8, 9]
>
> Here we're replacing all items of index k such as 5 <= k < 2, which can't
> exist, so we're replacing 0 items by two items, the resulting length is 12,
> note that they are not inserted randomly, they are inserted at the index
> where the empty slice starts:
>
>     >>> alist = list(range(10))
>     >>> alist[5:2] = 'a', 'b'
>     >>> alist
>     [0, 1, 2, 3, 4, 'a', 'b', 5, 6, 7, 8, 9]
>
> In your example:
>
> >>> v = []
> >>> v[0:5]=6,7,8,9,0
> >>> v[-1]=6,7
> >>> v
> [6, 7, 8, 9, (6, 7)]
> >>> v[-1:-5]  # An empty slice, so assigning to it will only add elements
> at position -1
> []
> >>> v[-1:-5]='a','b','c','d','e'
> >>> v
> [6, 7, 8, 9, 'a', 'b', 'c', 'd', 'e', (6, 7)]
> >>> v[-5:-1]  # A non empty slice, so assigning to it will replace b, c,
> d, and e with A, B, C, D and E
> ['b', 'c', 'd', 'e']
> >>> v[-5:-1]='A','B','C','D','E'
> >>> v
> [6, 7, 8, 9, 'a', 'A', 'B', 'C', 'D', 'E', (6, 7)]
>
> Does it helps?
>
> Bests,
> --
> Julien Palard
> https://mdk.fr
>
>

-- 
Saludos cordiales,
Jorge Minguet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190523/2491093e/attachment.html>

From report at bugs.python.org  Thu May 23 12:00:10 2019
From: report at bugs.python.org (Grant Wu)
Date: Thu, 23 May 2019 16:00:10 +0000
Subject: [docs] [issue37014] [First easy issue] fileinput module should
 document that openhook and mode are ignored when reading from stdin
In-Reply-To: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>
Message-ID: <1558627210.77.0.240071933425.issue37014@roundup.psfhosted.org>


Change by Grant Wu <grant.wu at petuum.com>:


----------
nosy: +grantwu -Grant Wu2

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

From report at bugs.python.org  Thu May 23 22:32:15 2019
From: report at bugs.python.org (Shannon)
Date: Fri, 24 May 2019 02:32:15 +0000
Subject: [docs] [issue37019] Create symlinks relative to cwd
In-Reply-To: <1558595342.46.0.940919584419.issue37019@roundup.psfhosted.org>
Message-ID: <1558665135.89.0.587115865605.issue37019@roundup.psfhosted.org>


Shannon <shannonjkeough at googlemail.com> added the comment:

I can see how this change would be backward incompatible, however the current behaviour seems inconsistent with the way pathlib functions otherwise. Within two lines of code, the same path object can be pointing to two completely different locations simply because it's being used as the src argument to create a symlimk. That's counter to my understanding of the whole point of pathlib.

With regard to relative_to, I've found this issue, which doesn't seem to have been touched since 2016. https://bugs.python.org/issue20012
I'm new here, what's the best way to bump an issue?

----------

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

From report at bugs.python.org  Fri May 24 04:17:25 2019
From: report at bugs.python.org (SilentGhost)
Date: Fri, 24 May 2019 08:17:25 +0000
Subject: [docs] [issue37019] Create symlinks relative to cwd
In-Reply-To: <1558595342.46.0.940919584419.issue37019@roundup.psfhosted.org>
Message-ID: <1558685845.82.0.140152319602.issue37019@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

Shannon, what you're suggesting is prone to the same issue (creating a broken symlink) if a given destination does not exist relative to cwd. I think your current solution is better as it explicitly provides the paths, but it's not generalised enough to warrant a change in behaviour.

If you have anything new to add or would like to add a PR, just post on that issue. As you note, the core developer stated that the current behaviour is by design.

----------

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

From report at bugs.python.org  Fri May 24 04:41:42 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 24 May 2019 08:41:42 +0000
Subject: [docs] [issue37019] Create symlinks relative to cwd
In-Reply-To: <1558595342.46.0.940919584419.issue37019@roundup.psfhosted.org>
Message-ID: <1558687302.16.0.588188142763.issue37019@roundup.psfhosted.org>


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

Yes, the current behavior is by design. It is consistent with the os.symlink(), the "ln -s" command, and with any other way of creating symbolic links in other programming languages.

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

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

From report at bugs.python.org  Fri May 24 05:05:56 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Fri, 24 May 2019 09:05:56 +0000
Subject: [docs] [issue37014] [First easy issue] fileinput module should
 document that openhook and mode are ignored when reading from stdin
In-Reply-To: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>
Message-ID: <1558688756.49.0.416892031741.issue37014@roundup.psfhosted.org>


Michele Angrisano <michele.angrisano at gmail.com> added the comment:

The Python's version chosen for this issue is 3.7. I think the suggest can be useful for 3.8 as well. Am I right?

----------
nosy: +mangrisano

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

From report at bugs.python.org  Fri May 24 06:43:34 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 24 May 2019 10:43:34 +0000
Subject: [docs] [issue20285] Improve object.__doc__ and help(object) output
In-Reply-To: <1389920351.63.0.12805701843.issue20285@psf.upfronthosting.co.za>
Message-ID: <1558694614.65.0.269114033405.issue20285@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset c95c93d4eb0519beaa06e6b6e0ecca7c2a58f69c by Cheryl Sabella in branch 'master':
bpo-20285: Improve help docs for object (GH-4759)
https://github.com/python/cpython/commit/c95c93d4eb0519beaa06e6b6e0ecca7c2a58f69c


----------

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

From report at bugs.python.org  Fri May 24 06:44:12 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 24 May 2019 10:44:12 +0000
Subject: [docs] [issue20285] Improve object.__doc__ and help(object) output
In-Reply-To: <1389920351.63.0.12805701843.issue20285@psf.upfronthosting.co.za>
Message-ID: <1558694652.38.0.350770190423.issue20285@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From julien at palard.fr  Fri May 24 08:07:28 2019
From: julien at palard.fr (Julien Palard)
Date: Fri, 24 May 2019 12:07:28 +0000
Subject: [docs] Please document sqlite3 return values
In-Reply-To: <6ad9611e-aa18-0bb3-df73-9e600723c3d8@adversary.io>
References: <fb1961fa-5ca6-cbd7-1f0e-4c3a1885d683@adversary.io>
 <pZoM08ruhG9Fuigu7BgbYFxVxRxUYwYyWc9Pz4m_nOIlwtmfbile_6IgG6yZYn_s0VASM6cEg88FgAHJ4cc9kKx9OkHftyRO9g8TlxswHho=@palard.fr>
 <6ad9611e-aa18-0bb3-df73-9e600723c3d8@adversary.io>
Message-ID: <lqhE2FCTlacxUfAw8dLsCArE5hOGwmmgmgAX1MPFbdaHQYgU2gPMMieUF5-48aLGxE10IoDX9Xrm2uKyIa1Zgfhp9Cs6-qNj156HTfCyXU4=@palard.fr>

Hi Bjartur,

fetchone returns None when no result are found but in your case (COUNT(*)) there's one result: the count, being equal to zero. A count will always return one result, the result being the actual count, so if there's one match you'll get (1, ) instead of (0, ), and so on.

To get no result, let's change the COUNT(*) to *:

>>> result = database_cursor.execute("SELECT * FROM users WHERE username=? AND password=?;", (username, password)).fetchone()
>>> print result
None

and you're getting None as documented.

It's the same behavior in Python 2 and 3. BTW you should think about upgrading to Python 3: Python 2 end of life is in 7 months, and Python 3 is more than 10 years old.

Bests,
--?
Julien Palard
https://mdk.fr


From report at bugs.python.org  Fri May 24 08:19:09 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Fri, 24 May 2019 12:19:09 +0000
Subject: [docs] [issue37014] [First easy issue] fileinput module should
 document that openhook and mode are ignored when reading from stdin
In-Reply-To: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>
Message-ID: <1558700349.27.0.253179663407.issue37014@roundup.psfhosted.org>


Change by Michele Angrisano <michele.angrisano at gmail.com>:


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

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

From report at bugs.python.org  Fri May 24 08:19:56 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Fri, 24 May 2019 12:19:56 +0000
Subject: [docs] [issue37014] [First easy issue] fileinput module should
 document that openhook and mode are ignored when reading from stdin
In-Reply-To: <1558545967.04.0.906137299955.issue37014@roundup.psfhosted.org>
Message-ID: <1558700396.96.0.276099563345.issue37014@roundup.psfhosted.org>


Michele Angrisano <michele.angrisano at gmail.com> added the comment:

I've just made a PR for this issue.

----------

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

From bjartur at adversary.io  Fri May 24 07:48:11 2019
From: bjartur at adversary.io (Bjartur Thorlacius)
Date: Fri, 24 May 2019 11:48:11 +0000
Subject: [docs] Please document sqlite3 return values
In-Reply-To: <pZoM08ruhG9Fuigu7BgbYFxVxRxUYwYyWc9Pz4m_nOIlwtmfbile_6IgG6yZYn_s0VASM6cEg88FgAHJ4cc9kKx9OkHftyRO9g8TlxswHho=@palard.fr>
References: <fb1961fa-5ca6-cbd7-1f0e-4c3a1885d683@adversary.io>
 <pZoM08ruhG9Fuigu7BgbYFxVxRxUYwYyWc9Pz4m_nOIlwtmfbile_6IgG6yZYn_s0VASM6cEg88FgAHJ4cc9kKx9OkHftyRO9g8TlxswHho=@palard.fr>
Message-ID: <6ad9611e-aa18-0bb3-df73-9e600723c3d8@adversary.io>

Salut Julien.

Let's take a step back, and run Python 2.7 (not 3.7) in a MSYS2 
(MinGW+Cygwin) Bash shell on Windows 10. Python 2 fetchone is documented 
as returning None, just like Python 3 fetchone.

M?therji at Lappi MINGW64 /tmp/pysql
$ python -V
Python 2.7.15

M?therji at Lappi MINGW64 /tmp/pysql
$ cat users.db
cat: users.db: No such file or directory

M?therji at Lappi MINGW64 /tmp/pysql
$ cat users.py
from sqlite3 import connect as database

username='Nonexistant'; password='should not match'

user_database = database('users.db', isolation_level=None)
database_cursor = user_database.cursor()
database_cursor.execute('CREATE TABLE users(username text, password text)')
result = database_cursor.execute("SELECT count(*) FROM users WHERE 
username=? AND password=?;", (username, password)).fetchone()
print(result)
print(result[0])
print(result[0] > 0)

M?therji at Lappi MINGW64 /tmp/pysql
$ python users.py
(0,)
0
False

So even without Python 3 and Docker, I see the same mismatch between 
documenation and behaviour on my laptop.

Meilleures salutations,
Bjartur


From report at bugs.python.org  Fri May 24 12:25:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 24 May 2019 16:25:28 +0000
Subject: [docs] [issue32573] All sys attributes (.argv,
 ...) should exist in embedded environments
In-Reply-To: <1516131988.33.0.467229070634.issue32573@psf.upfronthosting.co.za>
Message-ID: <1558715128.6.0.923491252236.issue32573@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at redhat.com>:


----------
pull_requests: +13464

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

From stockenscott at gmail.com  Fri May 24 09:04:53 2019
From: stockenscott at gmail.com (Scott stocken)
Date: Fri, 24 May 2019 06:04:53 -0700
Subject: [docs] For getting more information about python project in
 beginner
In-Reply-To: <qMnAoBz2m2PKSyE4IiAhu2LdONDqbfKyGA03k50_eiBpe-RqjbY-jEiLOb-vQMcZM6QYDwHWusPqy1JEx7cXrN3qmmoAS6DbVA_T0I1g-MU=@palard.fr>
References: <CAMhtLcV-js9OBETK=_DKEHdxqgJdGDAjaaC8UkvU30KGz-oZZQ@mail.gmail.com>
 <qMnAoBz2m2PKSyE4IiAhu2LdONDqbfKyGA03k50_eiBpe-RqjbY-jEiLOb-vQMcZM6QYDwHWusPqy1JEx7cXrN3qmmoAS6DbVA_T0I1g-MU=@palard.fr>
Message-ID: <CAMhtLcVPcuZTGeRH5jN5TFb5166K3xvhTM05xMH0Q4=wy+vMYw@mail.gmail.com>

Thanks, I'll check it out.

On Thu, May 23, 2019 at 1:55 AM Julien Palard <julien at palard.fr> wrote:

> Hi Scott,
>
> > I want to get some information about the python project please help me
> > I am the beginner python programmer  okay
>
> You can start by reading the official Python Tutorial here:
> https://docs.python.org/3/tutorial/
>
> Hope it helps,
> --
> Julien Palard
> https://mdk.fr
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190524/ba416b98/attachment.html>

From report at bugs.python.org  Fri May 24 16:27:33 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 24 May 2019 20:27:33 +0000
Subject: [docs] [issue36985] typing.ForwardRef is undocumented
In-Reply-To: <1558416902.0.0.868432422236.issue36985@roundup.psfhosted.org>
Message-ID: <1558729653.25.0.731964318655.issue36985@roundup.psfhosted.org>


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


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

From dylan at pagefreezer.com  Fri May 24 17:55:24 2019
From: dylan at pagefreezer.com (Dylan Kirby)
Date: Fri, 24 May 2019 14:55:24 -0700
Subject: [docs] https://docs.python.org/3/library/asyncio-eventloop.html
Message-ID: <CAJiqO0dR7H_TcpGOH0M1YeZSmPOSjMtEUpPGx2V836dWTOigRg@mail.gmail.com>

Hello,

I'm suggesting a minor tweak to the documentation around the Asyncio event
loop, specifically the run_until_complete method.

The run_forever method explicitly states that the loop will run until stop
is called which is great.

In run_until_complete, there is no mention of it, but stop will be called
once the loop is done processing the future/coroutine it's passed.

A colleague and I ran into some issues around this, and after digging
through the source code determined that run_until_complete will in fact
call run_forever, and subsequently call stop.

It would be beneficial if that was reference to this in the documentation
for that method.

Regards,

Dylan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190524/2d98f710/attachment.html>

From andrew.svetlov at gmail.com  Sat May 25 04:27:41 2019
From: andrew.svetlov at gmail.com (Andrew Svetlov)
Date: Sat, 25 May 2019 11:27:41 +0300
Subject: [docs] https://docs.python.org/3/library/asyncio-eventloop.html
In-Reply-To: <CAJiqO0dR7H_TcpGOH0M1YeZSmPOSjMtEUpPGx2V836dWTOigRg@mail.gmail.com>
References: <CAJiqO0dR7H_TcpGOH0M1YeZSmPOSjMtEUpPGx2V836dWTOigRg@mail.gmail.com>
Message-ID: <CAL3CFcW25ayMVWF+Q8tSpkeRhnxUrC5K=GZmCmuizNp+tRB30A@mail.gmail.com>

Pull Request is welcome!

On Sat, May 25, 2019 at 10:43 AM Dylan Kirby <dylan at pagefreezer.com> wrote:
>
> Hello,
>
> I'm suggesting a minor tweak to the documentation around the Asyncio event loop, specifically the run_until_complete method.
>
> The run_forever method explicitly states that the loop will run until stop is called which is great.
>
> In run_until_complete, there is no mention of it, but stop will be called once the loop is done processing the future/coroutine it's passed.
>
> A colleague and I ran into some issues around this, and after digging through the source code determined that run_until_complete will in fact call run_forever, and subsequently call stop.
>
> It would be beneficial if that was reference to this in the documentation for that method.
>
> Regards,
>
> Dylan
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs



-- 
Thanks,
Andrew Svetlov

From report at bugs.python.org  Sat May 25 17:10:53 2019
From: report at bugs.python.org (John Riehl)
Date: Sat, 25 May 2019 21:10:53 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
Message-ID: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>


New submission from John Riehl <john.riehl at outlook.com>:

The entry in the glossary for "hashable" (https://docs.python.org/3/glossary.html#term-hashable) states "All of Python?s immutable built-in objects are hashable." Tuples are described as immutable sequence types (https://docs.python.org/3/library/stdtypes.html#immutable-sequence-types), but they are not hashable unless all of their elements are hashable. Suggest updating the glossary to reflect this.

----------
assignee: docs at python
components: Documentation
messages: 343514
nosy: docs at python, john.riehl
priority: normal
severity: normal
status: open
title: Glossary item "hashable" incorrect
type: behavior
versions: Python 3.7

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

From report at bugs.python.org  Sat May 25 18:25:08 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sat, 25 May 2019 22:25:08 +0000
Subject: [docs] [issue34613] asyncio.StreamReader initialization
 documentation incorrectly declare limit as None
In-Reply-To: <1536476439.55.0.56676864532.issue34613@psf.upfronthosting.co.za>
Message-ID: <1558823108.8.0.0438402893816.issue34613@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


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

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

From report at bugs.python.org  Sun May 26 03:51:03 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 26 May 2019 07:51:03 +0000
Subject: [docs] [issue37052] Add examples for mocking async for and async
 context manager in unittest.mock docs
Message-ID: <1558857063.08.0.951093658338.issue37052@roundup.psfhosted.org>


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

Since issue26467 implemented AsyncMock along with async dunder methods for MagicMock it enables users to mock async for and async with statements. Currently examples of how to use this is present only in tests and would be good to add it to docs. There is a docs page for mock that contains similar cookbook style examples [0] where I hope these can be added. I can raise a PR with these examples if it's okay. Do you think it's worthy enough to add these examples? Any additional examples you find around asyncio and mock that can be documented ?

An example of mocking async for statement by setting return value for __aiter__ method : 

# aiter_example.py

import asyncio
from unittest.mock import MagicMock

mock = MagicMock()
mock.__aiter__.return_value = range(3)

async def main(): 
    print([i async for i in mock])

asyncio.run(main())

$ ./python.exe aiter_example.py
[0, 1, 2]

An example of mocking async with statement by implementing __aenter__ and __aexit__ method. In this example __aenter__ and __aexit__ are not called. __aenter__ and __aexit__ implementations are tested to have been called in the test at [1]. These tests work since MagicMock is returned during attribute access (mock_instance.entered) which is always True in boolean context under assertTrue. I will raise a separate PR to discuss this since normally while mocking __enter__ and __exit__ the class's __enter__ and __exit__ are not used as a side_effect for the mock calls unless they are set explicitly.

# aenter_example.py

import asyncio
from unittest.mock import MagicMock

class WithAsyncContextManager:

    async def __aenter__(self, *args, **kwargs):
        return self

    async def __aexit__(self, *args, **kwargs):
        pass

instance = WithAsyncContextManager()
mock_instance = MagicMock(instance)

async def main():
    async with mock_instance as result:
        print("entered")

asyncio.run(main())

./python.exe aenter_example.py
entered

[0] https://docs.python.org/3/library/unittest.mock-examples.html
[1] https://github.com/python/cpython/blob/47dd2f9fd86c32a79e77fef1fbb1ce25dc929de6/Lib/unittest/test/testmock/testasync.py#L306

----------
assignee: docs at python
components: Documentation
messages: 343536
nosy: asvetlov, cjw296, docs at python, lisroach, mariocj89, michael.foord, xtreak, yselivanov
priority: normal
severity: normal
status: open
title: Add examples for mocking async for and async context manager in unittest.mock docs
type: enhancement
versions: Python 3.8

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

From dannyyurei at gmail.com  Sat May 25 21:45:18 2019
From: dannyyurei at gmail.com (=?UTF-8?Q?Dannyy_Y=C5=ABrei?=)
Date: Sat, 25 May 2019 20:45:18 -0500
Subject: [docs] Printing
Message-ID: <CAAcPNsUEs0WJEgEChC0=FGpnebGK0y2P12A2Zms5EQGzfnuYkw@mail.gmail.com>

i have a question:
?How do I send through python a file to be printed?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190525/20a14101/attachment.html>

From report at bugs.python.org  Sun May 26 04:55:00 2019
From: report at bugs.python.org (shangdahao)
Date: Sun, 26 May 2019 08:55:00 +0000
Subject: [docs] [issue31163] Return destination path in Path.rename and
 Path.replace
In-Reply-To: <1502292744.48.0.627996317333.issue31163@psf.upfronthosting.co.za>
Message-ID: <1558860900.16.0.857328187346.issue31163@roundup.psfhosted.org>


Change by shangdahao <shangdahao at gmail.com>:


----------
keywords: +patch
pull_requests: +13489
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/13582

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

From julien at palard.fr  Sun May 26 05:03:50 2019
From: julien at palard.fr (Julien Palard)
Date: Sun, 26 May 2019 09:03:50 +0000
Subject: [docs] misbehaving functionality of all() function
In-Reply-To: <CAAiJ6EXaXObRr6YbO3bMr_Z6t6Brwk+vWP=aULhfEoUtpwxPPQ@mail.gmail.com>
References: <CAAiJ6EWr978chcu6HWs-4tML6rNyZfDAGVVAeYUDQPD_JQv1NQ@mail.gmail.com>
 <GiFFKw7epDsItHuETOHJXD4sqnold5FwQpiqhgKAvmrPBPOMM_x2nPkvDGt61lNPnwMX4XFtZV03dJbvg4ZLJY6C4J8ftGCXKvbiaNkoMpg=@palard.fr>
 <CAAiJ6EXaXObRr6YbO3bMr_Z6t6Brwk+vWP=aULhfEoUtpwxPPQ@mail.gmail.com>
Message-ID: <2oAXrRlOqvl3m0QJPkt2eIQcktl_9DStyCmGJ2j_Qn-p2yLIDLEuoJQIAGMHPryhZmBzcLuDJQ2-stb2ewKoCia9Ke5H5DczirEeeIjtDpI=@palard.fr>

Hi Sai,

> if one of the element(1+12.1j) is not iterable

This does not make sense to me, 1+12.1j does not have "elements", it's a single value.

> TypeError: 'complex' object is not iterable

As I just said, 1+12.1j is not iterable (it does not have elements), Python agree with me.

> My concern is why all([1,2,1+12.1j]) is returning True if all elements are not iterable.

all expects a single iterable, which is the list of three values, (starting with [ and ending with ]).
all returns true if all values (in this case the value 1, the value 2, and the value 1+12.1j) are truthy, which is the case.

You can imagine all being implemented like this (it is not, as the builtin all is implemented in C, but they behave the same):

def all(iterable):
    for element in iterable:
        if not element:
            return False
    return True

So when you call all(1+12.1j) you're basically asking Python to do:

for element in 1+12.1j:
    ...

which does not work, 1+12.1j is not iterable, it's a single value, not a collection of values.

when you call all([1,2,1+12.1j]) you're basically asking Python to do:

for element in [1,2,1+12.1j]:
    if not element:  # Tested with 1, then with 2, then with 1+12.1j, all are True, so no return False.
        return False
return True  # This line will be reached, the result of all([1,2,1+12.1j]) will be True.

Hope it helps.
--?
Julien Palard
https://mdk.fr

From julien at palard.fr  Sun May 26 05:12:20 2019
From: julien at palard.fr (Julien Palard)
Date: Sun, 26 May 2019 09:12:20 +0000
Subject: [docs] Printing
In-Reply-To: <CAAcPNsUEs0WJEgEChC0=FGpnebGK0y2P12A2Zms5EQGzfnuYkw@mail.gmail.com>
References: <CAAcPNsUEs0WJEgEChC0=FGpnebGK0y2P12A2Zms5EQGzfnuYkw@mail.gmail.com>
Message-ID: <qkduYnOOsWTHcSHcwj04JUdBxKvxjBupgLHdI6iaBnk_XH_E5b0igbQRaUog-o447QtPu3lHgp8Bd7ND6g_cUnn5V5kpN9yEJlqf9b4TGfA=@palard.fr>

Hi Dannyy,

> ?How do I send through python a file to be printed?

This mailing list is to report bugs and propose enhancements in Python documentation, you may find an answer by searching in a search engine or stackoverflow for "Python printer", or "Python printing document"/

It may also depend on your OS or the graphical toolkit you're using, I bet most graphical toolkits have a printer selection window.

On Linux I'll typically just call lpr using the subprocess module. On windows there's a module for it, see : http://timgolden.me.uk/python/win32_how_do_i/print.html

--?
Julien Palard
https://mdk.fr


From majotito at gmail.com  Sun May 26 10:10:02 2019
From: majotito at gmail.com (mars)
Date: Sun, 26 May 2019 10:10:02 -0400
Subject: [docs] illegal code samples
Message-ID: <CACOyec4jsNK24A2sCT-8SLJOMY8POhsJbfPGZLtkbk+p-CdcfA@mail.gmail.com>

Hi--
    I have a suggestions but I have no idea if someone suggested it before.
    In the sample code blocks, I typically look back-and-forth between the
description above to the sample code below, trying to see the correct use
of the function in the topic illustrated. But, sometimes you have illegal
code in the sample box, which makes comprehension difficult for me along
the way. In my mind, starting off, these samples are "correct", and I am
trying in my mind to link the illustrated code to the explanation above.
Only, sometimes, down below in the paragraph, one line in the text is says
"the following is illegal", which to me is yet another thing I need to hold
in my head while trying to stuff more info in there. It would be helpful,
perhaps, to color the box of the illegal code another way, or, in the
interest of eventual printout, a double-frame box, an "ILLEGAL" text block,
or some other visual cue.
   Specifically, this occurs in the third paragraph in this section:
https://docs.python.org/3/reference/compound_stmts.html#compound-statements
  Thank you for the consideration. I am finding this documentation very
helpful, and I really appreciate the efforts to make this clear and easy to
read. I hope this suggestion might help others in the same boat I am. I
know a smattering of programming, mostly BASIC from back-in-the-day, and
dabbled in assembly and C++, mostly adapting others' programs, learning
just enough to bend the program enough. Moving on to Python, I am looking
to gain a deeper and more comprehensive understanding of this language. I
am really liking it so far, and looking forward to learning more.
--Mario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190526/e51bfafd/attachment.html>

From report at bugs.python.org  Sun May 26 13:34:49 2019
From: report at bugs.python.org (SilentGhost)
Date: Sun, 26 May 2019 17:34:49 +0000
Subject: [docs] [issue37057] suspicious.py sphinx extension access
 non-existing attribute.
In-Reply-To: <1558891805.96.0.441991162477.issue37057@roundup.psfhosted.org>
Message-ID: <1558892089.11.0.627602430487.issue37057@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

This looks like a duplicate of #36853. Do you happen to have sphinx 2 installed?

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

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

From report at bugs.python.org  Sun May 26 13:37:49 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 26 May 2019 17:37:49 +0000
Subject: [docs] [issue37057] suspicious.py sphinx extension access
 non-existing attribute.
In-Reply-To: <1558891805.96.0.441991162477.issue37057@roundup.psfhosted.org>
Message-ID: <1558892269.18.0.412980030954.issue37057@roundup.psfhosted.org>


Matthias Bussonnier <bussonniermatthias at gmail.com> added the comment:

Oh yeah, I do... and you are right this is duplicate.

----------

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

From report at bugs.python.org  Sun May 26 13:37:55 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 26 May 2019 17:37:55 +0000
Subject: [docs] [issue37057] suspicious.py sphinx extension access
 non-existing attribute.
In-Reply-To: <1558891805.96.0.441991162477.issue37057@roundup.psfhosted.org>
Message-ID: <1558892275.52.0.728806731926.issue37057@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun May 26 13:38:37 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 26 May 2019 17:38:37 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
In-Reply-To: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>
Message-ID: <1558892317.76.0.0272221013492.issue36853@roundup.psfhosted.org>


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


----------
nosy: +mbussonn

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

From report at bugs.python.org  Sun May 26 13:50:11 2019
From: report at bugs.python.org (SilentGhost)
Date: Sun, 26 May 2019 17:50:11 +0000
Subject: [docs] [issue37057] suspicious.py sphinx extension access
 non-existing attribute.
In-Reply-To: <1558891805.96.0.441991162477.issue37057@roundup.psfhosted.org>
Message-ID: <1558893011.67.0.640401507769.issue37057@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
superseder:  -> inconsistencies in docs builds (Sphinx 2)

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

From report at bugs.python.org  Sun May 26 13:57:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 26 May 2019 17:57:11 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
In-Reply-To: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>
Message-ID: <1558893431.34.0.708497875905.issue36853@roundup.psfhosted.org>


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

See also https://github.com/python/cpython/pull/13579 that replaces self.warn with self.logger.warn in Doc/tools/extensions/suspicious.py

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

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

From report at bugs.python.org  Sun May 26 15:02:14 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 26 May 2019 19:02:14 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1558897334.71.0.900874694963.issue33071@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
pull_requests: +13491
stage: backport needed -> patch review
pull_request: https://github.com/python/cpython/pull/13584

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

From report at bugs.python.org  Sun May 26 15:11:52 2019
From: report at bugs.python.org (Jason R. Coombs)
Date: Sun, 26 May 2019 19:11:52 +0000
Subject: [docs] [issue36853] inconsistencies in docs builds (Sphinx 2)
In-Reply-To: <1557331408.26.0.606381835406.issue36853@roundup.psfhosted.org>
Message-ID: <1558897912.76.0.933535536429.issue36853@roundup.psfhosted.org>


Jason R. Coombs <jaraco at jaraco.com> added the comment:

> I've just locally ran sphinx 2.0.0 on 071cbd4ea1 (the current tip of your PR) and I'm not getting any error, which one are you getting?

The issue occurs on 2347d3ae36 with `make suspicious` with Sphinx 2.0.0 and 2.0.1.

```
Doc 2347d3ae36 $ make suspicious                                                                                                                                               
mkdir -p build
Building NEWS from Misc/NEWS.d with blurb
PATH=./venv/bin:$PATH sphinx-build -b suspicious -d build/doctrees -D latex_elements.papersize=  -W . build/suspicious 
Running Sphinx v2.0.1
loading ignore rules... done, 352 rules loaded
building [mo]: targets for 0 po files that are out of date
building [suspicious]: targets for 476 source files that are out of date
updating environment: 476 added, 0 changed, 0 removed
/Users/jaraco/code/public/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
reading sources... [100%] whatsnew/index                                                                                                                                       
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 53%] library/importlib.metadata                                                                                                                            
Exception occurred:
  File "/Users/jaraco/code/public/cpython/Doc/tools/extensions/suspicious.py", line 154, in report_issue
    self.warn('[%s:%d] "%s" found in "%-.120s"' %
AttributeError: 'CheckSuspiciousMarkupBuilder' object has no attribute 'warn'
The full traceback has been saved in /var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/sphinx-err-g3i65y10.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make[1]: *** [build] Error 2
make: *** [suspicious] Error 1
Suspicious check complete; look for any errors in the above output or in build/suspicious/suspicious.csv.  If all issues are false positives, append that file to tools/susp-ignored.csv.
```

----------

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

From report at bugs.python.org  Sun May 26 15:15:52 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 26 May 2019 19:15:52 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558898152.8.0.83459635175.issue37051@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun May 26 15:21:45 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 26 May 2019 19:21:45 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558898505.79.0.380783373902.issue37051@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +13494
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/13587

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

From report at bugs.python.org  Sun May 26 15:28:40 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 26 May 2019 19:28:40 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1558898920.96.0.650278276469.issue33071@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

hi, everyone. I am a freshman,so let me do it from easy issues:)

----------
nosy: +shihai1991

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

From report at bugs.python.org  Sun May 26 16:28:30 2019
From: report at bugs.python.org (Erika)
Date: Sun, 26 May 2019 20:28:30 +0000
Subject: [docs] [issue37059] Pre-compile Directive to Remind Coders that Men
 are Pigs
Message-ID: <1558902510.44.0.685577940512.issue37059@roundup.psfhosted.org>


New submission from Erika <sailingbigfoot at outlook.com>:

Guido Van Rossum recently let the community know that sexism is keeping women away from Python. A simple directive at the top of each py file would help remind us.

Throw an error unless #MenArePigs is not in line-1 of the file.

----------
assignee: docs at python
components: Documentation
messages: 343580
nosy: docs at python, erika1998
priority: normal
severity: normal
status: open
title: Pre-compile Directive to Remind Coders that Men are Pigs
versions: Python 3.7

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

From report at bugs.python.org  Sun May 26 20:56:38 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Mon, 27 May 2019 00:56:38 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558918598.7.0.825781309314.issue37051@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

For that matter, slices are immutable built-ins, but they're not hashable (presumably to avoid silently working with dictionaries in a non-slice capacity).

----------
nosy: +josh.r

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

From report at bugs.python.org  Sun May 26 21:34:54 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 27 May 2019 01:34:54 +0000
Subject: [docs] [issue21314] Document '/' in signatures
In-Reply-To: <1397988439.5.0.703056699862.issue21314@psf.upfronthosting.co.za>
Message-ID: <1558920894.19.0.0991304715494.issue21314@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I think we can revisit this now that PEP570 is accepted

----------
nosy: +pablogsal

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

From report at bugs.python.org  Sun May 26 23:15:43 2019
From: report at bugs.python.org (Michael Blahay)
Date: Mon, 27 May 2019 03:15:43 +0000
Subject: [docs] [issue36913] Missing documentation for decorators
In-Reply-To: <1557819328.64.0.0474936169734.issue36913@roundup.psfhosted.org>
Message-ID: <1558926943.68.0.991608976046.issue36913@roundup.psfhosted.org>


Michael Blahay <mblahay at gmail.com> added the comment:

The PEP is not the first place I go looking for information on Python topics, just my two cents.

----------
nosy: +mblahay

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

From report at bugs.python.org  Mon May 27 02:03:00 2019
From: report at bugs.python.org (Reuben Thomas)
Date: Mon, 27 May 2019 06:03:00 +0000
Subject: [docs] [issue37062] `AutoNumber` class in enum documentation:
 support *args in constructor
Message-ID: <1558936980.63.0.0585299344314.issue37062@roundup.psfhosted.org>


New submission from Reuben Thomas <rrt at sc3d.org>:

By changing one line of AutoNumber:

    def __new__(cls):

to

    def __new__(cls, *args):

Enums derived from AutoNumber can now support constructors that take named arguments; for example:

class Color(AutoNumber):
    def __init__(self, pantone=None):
        self.pantone = pantone or 'unknown'

class Swatch(Color):
    AUBURN = ('3497')
    SEA_GREEN = ('1246')
    BLEACHED_CORAL = () # New color, no Pantone code yet!

Without the change, one gets the error:

TypeError: __new__() takes 1 positional argument but 2 were given

I attach runnable demonstration code.

----------
assignee: docs at python
components: Documentation
files: foo.py
messages: 343607
nosy: docs at python, rrt
priority: normal
severity: normal
status: open
title: `AutoNumber` class in enum documentation: support *args in constructor
versions: Python 3.8
Added file: https://bugs.python.org/file48365/foo.py

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

From report at bugs.python.org  Mon May 27 02:03:35 2019
From: report at bugs.python.org (Reuben Thomas)
Date: Mon, 27 May 2019 06:03:35 +0000
Subject: [docs] [issue37062] `AutoNumber` class in enum documentation:
 support *args in constructor
In-Reply-To: <1558936980.63.0.0585299344314.issue37062@roundup.psfhosted.org>
Message-ID: <1558937015.64.0.802909270511.issue37062@roundup.psfhosted.org>


Reuben Thomas <rrt at sc3d.org> added the comment:

Just to be clear, the proposed change to the documentation is simply to add ", *args" to the argument list of AutoNumber.__new__.

----------

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

From report at bugs.python.org  Mon May 27 02:04:29 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 27 May 2019 06:04:29 +0000
Subject: [docs] [issue37062] `AutoNumber` class in enum documentation:
 support *args in constructor
In-Reply-To: <1558936980.63.0.0585299344314.issue37062@roundup.psfhosted.org>
Message-ID: <1558937069.13.0.210586088529.issue37062@roundup.psfhosted.org>


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


----------
nosy: +ethan.furman

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

From report at bugs.python.org  Mon May 27 10:51:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 27 May 2019 14:51:32 +0000
Subject: [docs] [issue14956] custom PYTHONPATH may break apps embedding
 Python
In-Reply-To: <1338321412.45.0.331737203349.issue14956@psf.upfronthosting.co.za>
Message-ID: <1558968692.62.0.0878230207231.issue14956@roundup.psfhosted.org>


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

This issue has been fixed in 36763 by the PEP 587 which provides a new "Isolated Configuration" and a way to tune the Python configuration without impacting subprocesses. For example, the Isolated Configuration ignores environment variables by default.

In Python 3.7 and older, you can set Py_IgnoreEnvironmentFlag to 1 (the flag exists also in Python 2.7), or even set Py_IsolatedFlag to 1 (new in Python 3.4).

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

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

From report at bugs.python.org  Mon May 27 13:21:43 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 27 May 2019 17:21:43 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558977703.55.0.743752567832.issue37051@roundup.psfhosted.org>


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


----------
pull_requests: +13502
pull_request: https://github.com/python/cpython/pull/13595

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

From report at bugs.python.org  Mon May 27 13:21:56 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 27 May 2019 17:21:56 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558977716.94.0.604358006725.issue37051@roundup.psfhosted.org>


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


New changeset cc1c582f6fe450ce1c7de849137039e9b5fab8eb by Raymond Hettinger in branch 'master':
bpo-37051: Refine note on what objects are hashable (GH-13587)
https://github.com/python/cpython/commit/cc1c582f6fe450ce1c7de849137039e9b5fab8eb


----------

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

From report at bugs.python.org  Mon May 27 13:43:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 27 May 2019 17:43:25 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558979005.2.0.249800110831.issue37051@roundup.psfhosted.org>


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


New changeset e8318f31f35dc851684c094b268e4a85d7f357c9 by Raymond Hettinger (Miss Islington (bot)) in branch '3.7':
bpo-37051: Refine note on what objects are hashable (GH-13587) (GH-13595)
https://github.com/python/cpython/commit/e8318f31f35dc851684c094b268e4a85d7f357c9


----------

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

From report at bugs.python.org  Mon May 27 13:43:57 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 27 May 2019 17:43:57 +0000
Subject: [docs] [issue37051] Glossary item "hashable" incorrect
In-Reply-To: <1558818653.08.0.592312048855.issue37051@roundup.psfhosted.org>
Message-ID: <1558979037.78.0.144493684876.issue37051@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Mon May 27 14:39:05 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 27 May 2019 18:39:05 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1558982345.45.0.745918509905.issue33071@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:

I?m concerned that not only references to register command were deleted, but also useful general intro to PyPI.

----------

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

From report at bugs.python.org  Mon May 27 15:20:21 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 27 May 2019 19:20:21 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1558984821.2.0.00646752115609.issue33071@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

I think you are right, so i remain meaningful intro. Anyone else has an thought?

----------
versions:  -Python 3.7, Python 3.8

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

From yuqinju at hotmail.com  Mon May 27 22:31:40 2019
From: yuqinju at hotmail.com (leo freesand)
Date: Tue, 28 May 2019 02:31:40 +0000
Subject: [docs] a broken link in docs
Message-ID: <DM5PR13MB1498786DE50445BAA8F5F92BAA1E0@DM5PR13MB1498.namprd13.prod.outlook.com>

https://docs.python.org/3.7/library/asyncio-protocol.html#transports
Transport objects are always instantiated by an ref:asyncio event loop <asyncio-event-loop>.

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

From report at bugs.python.org  Tue May 28 03:18:04 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 28 May 2019 07:18:04 +0000
Subject: [docs] [issue37073] clarify functions docs in IO modules and Bytes
 Objects
Message-ID: <1559027884.63.0.0963085588001.issue37073@roundup.psfhosted.org>


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

> PyBytes_FromStringAndSize(const char *v, Py_ssize_t len): 
> Return a new bytes object with a copy of the string v as value and length len on success, and NULL on failure. If v is NULL, the contents of the bytes object are uninitialized.

The function actually copies `len` bytes from string v instead of the whole string. (link 1) I suggested we can change to 

> Return a new bytes object with a copy of the first len bytes of string v as value and length len on success...

> readinto(b)
> Read bytes into a pre-allocated, writable bytes-like object b and return the number of bytes read. For example, b might be a bytearray.

The function will call _bufferediobase_readinto_generic(link 2) which may return NULL. Maybe we can change to 

> and return the number of bytes that read succeed (it may be smaller than b or NULL if failed)...

1. https://github.com/python/cpython/blob/master/Objects/bytesobject.c#L126

2. https://github.com/python/cpython/blob/master/Modules/_io/bufferedio.c#L962

----------
assignee: docs at python
components: Documentation
messages: 343741
nosy: Windson Yang, docs at python
priority: normal
severity: normal
status: open
title: clarify functions docs in IO modules and Bytes Objects
type: enhancement
versions: Python 3.8

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

From julien at palard.fr  Tue May 28 05:06:36 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 28 May 2019 09:06:36 +0000
Subject: [docs] illegal code samples
In-Reply-To: <CACOyec4jsNK24A2sCT-8SLJOMY8POhsJbfPGZLtkbk+p-CdcfA@mail.gmail.com>
References: <CACOyec4jsNK24A2sCT-8SLJOMY8POhsJbfPGZLtkbk+p-CdcfA@mail.gmail.com>
Message-ID: <X6cji_UTtYzGhmkFKim6luI2_kUp2wmoGs0BAj120L_U737o89nsoeQXj1LbkA-fYwkloXplFohhNCF1GNd-PObjIvjTgVoZ3O-7FkI_Vgs=@palard.fr>

Hi Mario,

> It would be helpful, perhaps, to color the box of the illegal code another way, or, in the interest of eventual printout, a double-frame box, an "ILLEGAL" text block, or some other visual cue.

I like the idea, would you mind opening an issue on bugs.python.org to keep track of it? And if you feel trying to implement it, don't hesitate to open a PR :)

--?
Julien Palard
https://mdk.fr


From julien at palard.fr  Tue May 28 05:09:09 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 28 May 2019 09:09:09 +0000
Subject: [docs] a broken link in docs
In-Reply-To: <DM5PR13MB1498786DE50445BAA8F5F92BAA1E0@DM5PR13MB1498.namprd13.prod.outlook.com>
References: <DM5PR13MB1498786DE50445BAA8F5F92BAA1E0@DM5PR13MB1498.namprd13.prod.outlook.com>
Message-ID: <GzG0Y-IxUrBDWFWKiLyq01kWW7rrJuKtMQRvelKdouohBmsEW5tToR59FSuiTU9dSixfNl3Bg_sVqxSuXydWNiQY8pWjT3t59BMNdJQlmzk=@palard.fr>

Hi!

> https://docs.python.org/3.7/library/asyncio-protocol.html#transports
>
> Transport objects are always instantiated by an ref:asyncio event loop <asyncio-event-loop>.

Thanks for reporting Leo! It has been fixed on Feb 10 2019, are you sure you're still seeing it? What's the "Last updated on" date on the bottom right of the page?
Bests,
--?
Julien Palard
https://mdk.fr



From report at bugs.python.org  Tue May 28 13:50:25 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 28 May 2019 17:50:25 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559065825.55.0.961106743509.issue36373@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

*Passing* loop to gather should be deprecated.

*Using* loop by *internal logic* is pretty fine, we do it in asyncio everywhere.

Yuri, I think we should deprecate explicit loop everywhere in non-deprecated asyncio API by Python 3.8.

We can do it even in Python beta I think.

----------

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

From report at bugs.python.org  Tue May 28 13:52:43 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 28 May 2019 17:52:43 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559065963.57.0.609647097451.issue36373@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> Yuri, I think we should deprecate explicit loop everywhere in non-deprecated asyncio API by Python 3.8.

+1

----------

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

From report at bugs.python.org  Tue May 28 14:26:23 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 28 May 2019 18:26:23 +0000
Subject: [docs] [issue37082] Assignment expression operator (walrus) not in
 built-in help()
Message-ID: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>


New submission from Matthias Bussonnier <bussonniermatthias at gmail.com>:

Do the following at a Python prompt: 
```
>>> help()

Welcome to Python 3.8's help utility!

[...]SNIP

help> symbols

Here is a list of the punctuation symbols which Python assigns special meaning
to. Enter any symbol to get more help.

!=                  +                   <=                  __
"                   +=                  <>                  `
"""                 ,                   ==                  b"
%                   -                   >                   b'
%=                  -=                  >=                  f"
&                   .                   >>                  f'
&=                  ...                 >>=                 j
'                   /                   @                   r"
'''                 //                  J                   r'
(                   //=                 [                   u"
)                   /=                  \                   u'
*                   :                   ]                   |
**                  <                   ^                   |=
**=                 <<                  ^=                  ~
*=                  <<=                 _
```

Oh no ! Our favorite `:=` is missing :-(

----------
assignee: docs at python
components: Documentation
messages: 343813
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: Assignment expression operator (walrus) not in built-in help()
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Tue May 28 14:46:27 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 28 May 2019 18:46:27 +0000
Subject: [docs] [issue37082] Assignment expression operator (walrus) not in
 built-in help()
In-Reply-To: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>
Message-ID: <1559069187.78.0.646540126258.issue37082@roundup.psfhosted.org>


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


----------
nosy: +emilyemorehouse

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

From report at bugs.python.org  Tue May 28 17:37:48 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 28 May 2019 21:37:48 +0000
Subject: [docs] [issue37083] Document TYPE_COMMENT in documentation
 reference for compound statements
Message-ID: <1559079468.64.0.0790187408059.issue37083@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

The last changes in the grammar regarding TYPE_COMMENTS should be added to this section:

https://docs.python.org/3/reference/compound_stmts.html#function-definitions

----------
assignee: docs at python
components: Documentation
messages: 343820
nosy: docs at python, gvanrossum, levkivskyi, pablogsal
priority: normal
severity: normal
stage: needs patch
status: open
title: Document TYPE_COMMENT in documentation reference for compound statements
type: behavior
versions: Python 3.8

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

From report at bugs.python.org  Tue May 28 17:39:30 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 28 May 2019 21:39:30 +0000
Subject: [docs] [issue37083] Document TYPE_COMMENT in documentation
 reference for compound statements
In-Reply-To: <1559079468.64.0.0790187408059.issue37083@roundup.psfhosted.org>
Message-ID: <1559079570.84.0.893225658104.issue37083@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I will make a PR after https://github.com/python/cpython/pull/13202 is merged.

----------

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

From report at bugs.python.org  Tue May 28 19:47:37 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 28 May 2019 23:47:37 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559087257.12.0.0197402607096.issue36373@roundup.psfhosted.org>


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


----------
nosy: +mbussonn

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

From report at bugs.python.org  Tue May 28 19:50:46 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 28 May 2019 23:50:46 +0000
Subject: [docs] [issue37082] Assignment expression operator (walrus) not in
 built-in help()
In-Reply-To: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>
Message-ID: <1559087446.09.0.521897631459.issue37082@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +pablogsal

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

From report at bugs.python.org  Tue May 28 20:07:27 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 29 May 2019 00:07:27 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1559088447.31.0.548314946112.issue19184@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

The original PR appears to have been abandoned, so this issue available for someone to submit a new PR.

----------
nosy: +cheryl.sabella
versions: +Python 3.8 -Python 2.7, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Tue May 28 21:36:18 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 01:36:18 +0000
Subject: [docs] [issue33006] docstring of filter function is incorrect
In-Reply-To: <1520300191.48.0.467229070634.issue33006@psf.upfronthosting.co.za>
Message-ID: <1559093778.63.0.281474481022.issue33006@roundup.psfhosted.org>


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


New changeset 09ba83330b495afedbb6b27853506fe15a85b461 by Miss Islington (bot) (Tony Flury) in branch '2.7':
[2.7] bpo-33006 - Correct filter doc string to clarify 2nd argument can be iterable (GH-6015)
https://github.com/python/cpython/commit/09ba83330b495afedbb6b27853506fe15a85b461


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

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

From report at bugs.python.org  Tue May 28 22:04:01 2019
From: report at bugs.python.org (Ned Deily)
Date: Wed, 29 May 2019 02:04:01 +0000
Subject: [docs] [issue33006] docstring of filter function is incorrect
In-Reply-To: <1520300191.48.0.467229070634.issue33006@psf.upfronthosting.co.za>
Message-ID: <1559095441.84.0.777087315321.issue33006@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the docstring improvement!  It looks like the Library Reference entry for filter has similar wording in 3.x and 2.7 with regard to "items are removed".  If soneone feels strongly that that is not precise enough, suggest supplying a separate doc PR.

----------
nosy: +ned.deily
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue May 28 23:38:09 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 03:38:09 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1559101089.5.0.915272840714.issue36739@roundup.psfhosted.org>


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


New changeset e1f95e77e0647aff602e0660ba3c282b71045875 by Miss Islington (bot) (pbhd) in branch 'master':
bpo-36739: Update controlflow.rst (GH-12983)
https://github.com/python/cpython/commit/e1f95e77e0647aff602e0660ba3c282b71045875


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

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

From report at bugs.python.org  Tue May 28 23:40:23 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 03:40:23 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1559101223.65.0.887834416442.issue36739@roundup.psfhosted.org>


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


----------
pull_requests: +13540
pull_request: https://github.com/python/cpython/pull/13644

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

From report at bugs.python.org  Tue May 28 23:41:04 2019
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 29 May 2019 03:41:04 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1559101264.46.0.312924573796.issue36739@roundup.psfhosted.org>


Mariatta Wijaya <mariatta at python.org> added the comment:

Thanks!

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

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

From report at bugs.python.org  Tue May 28 23:48:16 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 03:48:16 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1559101696.93.0.11300241681.issue36739@roundup.psfhosted.org>


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


New changeset cee95fe1825dfeb52d7074c8209b5884a079f06c by Miss Islington (bot) in branch '3.7':
bpo-36739: Update controlflow.rst (GH-12983)
https://github.com/python/cpython/commit/cee95fe1825dfeb52d7074c8209b5884a079f06c


----------

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

From report at bugs.python.org  Wed May 29 03:22:40 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 29 May 2019 07:22:40 +0000
Subject: [docs] [issue37082] Assignment expression operator (walrus) not in
 built-in help()
In-Reply-To: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>
Message-ID: <1559114560.35.0.795107216419.issue37082@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Looks like that list could do with some attention:

- I don't see regular assignment there, either.
- And "`" shouldn't be in that list.
- Neither should "<>"
- "->" (for function annotations) is missing.

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

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

From report at bugs.python.org  Wed May 29 03:23:42 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 29 May 2019 07:23:42 +0000
Subject: [docs] [issue37082] Assignment expression operator (walrus) not in
 built-in help()
In-Reply-To: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>
Message-ID: <1559114622.84.0.767548948745.issue37082@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

@= is also missing. Looks like we need to go through the grammar and reconcile what's there with the symbols help.

----------

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

From report at bugs.python.org  Wed May 29 03:57:48 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 29 May 2019 07:57:48 +0000
Subject: [docs] [issue37082] Assignment expression operator (walrus) not in
 built-in help()
In-Reply-To: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>
Message-ID: <1559116668.47.0.967135920539.issue37082@roundup.psfhosted.org>


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

Seems this was added in db7b6b95828c25df6f428bc21a5d6d1cb68287a0 (2009) and wasn't updated from then.

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

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

From report at bugs.python.org  Wed May 29 06:18:55 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Wed, 29 May 2019 10:18:55 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1559125135.37.0.0323111466752.issue19184@roundup.psfhosted.org>


Michele Angrisano <michele.angrisano at gmail.com> added the comment:

I'm working on it.

----------
nosy: +mangrisano

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

From report at bugs.python.org  Wed May 29 07:42:21 2019
From: report at bugs.python.org (Michele Angrisano)
Date: Wed, 29 May 2019 11:42:21 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1559130141.39.0.601508317089.issue19184@roundup.psfhosted.org>


Change by Michele Angrisano <michele.angrisano at gmail.com>:


----------
keywords: +patch
pull_requests: +13544
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/13652

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

From report at bugs.python.org  Wed May 29 08:14:34 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 29 May 2019 12:14:34 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559132074.69.0.429957886896.issue36373@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

A champion is welcome :)

----------

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

From report at bugs.python.org  Wed May 29 10:43:34 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Wed, 29 May 2019 14:43:34 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559141014.92.0.326739535651.issue36373@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

hello, I will work on it, if there are no objection. :-)

----------

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

From report at bugs.python.org  Wed May 29 10:47:52 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 29 May 2019 14:47:52 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559141272.85.0.618189547349.issue36373@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

Thank you.

The change is pretty straightforward.

There is no need to jumbo PR, you can split the work into PR-per-module if it is more comfortable to you.

I'm ok with reviewing any approach.

----------

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

From report at bugs.python.org  Wed May 29 10:50:43 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 29 May 2019 14:50:43 +0000
Subject: [docs] [issue36373] Deprecate explicit loop parameter in all public
 asyncio APIs
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559141443.81.0.781359025326.issue36373@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


----------
title: asyncio.gather: no docs for deprecated loop parameter -> Deprecate explicit loop parameter in all public asyncio APIs

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

From report at bugs.python.org  Wed May 29 10:50:49 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 29 May 2019 14:50:49 +0000
Subject: [docs] [issue36373] Deprecate explicit loop parameter in all public
 asyncio APIs
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559141449.28.0.528688585002.issue36373@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


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

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

From report at bugs.python.org  Wed May 29 10:52:48 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Wed, 29 May 2019 14:52:48 +0000
Subject: [docs] [issue36373] asyncio.gather: no docs for deprecated loop
 parameter
In-Reply-To: <1559141272.85.0.618189547349.issue36373@roundup.psfhosted.org>
Message-ID: <10ee377b-682d-b5c7-6c68-09b0b1cabc93@gmail.com>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

Hi
> There is no need to jumbo PR, you can split the work into PR-per-module if it is more comfortable to you.
Yes, I think that is better split I will try it.
> I'm ok with reviewing any approach.
Thanks!

----------
title: Deprecate explicit loop parameter in all public asyncio APIs -> asyncio.gather: no docs for deprecated loop parameter

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

From report at bugs.python.org  Wed May 29 10:55:09 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 29 May 2019 14:55:09 +0000
Subject: [docs] [issue36373] Deprecate explicit loop parameter in all public
 asyncio APIs
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559141709.28.0.544508773578.issue36373@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


----------
title: asyncio.gather: no docs for deprecated loop parameter -> Deprecate explicit loop parameter in all public asyncio APIs

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

From majotito at gmail.com  Wed May 29 10:27:05 2019
From: majotito at gmail.com (mars)
Date: Wed, 29 May 2019 10:27:05 -0400
Subject: [docs] illegal code samples
In-Reply-To: <X6cji_UTtYzGhmkFKim6luI2_kUp2wmoGs0BAj120L_U737o89nsoeQXj1LbkA-fYwkloXplFohhNCF1GNd-PObjIvjTgVoZ3O-7FkI_Vgs=@palard.fr>
References: <CACOyec4jsNK24A2sCT-8SLJOMY8POhsJbfPGZLtkbk+p-CdcfA@mail.gmail.com>
 <X6cji_UTtYzGhmkFKim6luI2_kUp2wmoGs0BAj120L_U737o89nsoeQXj1LbkA-fYwkloXplFohhNCF1GNd-PObjIvjTgVoZ3O-7FkI_Vgs=@palard.fr>
Message-ID: <CACOyec4_Foh70vrh+5HcSJriSSgAJC1N_RU5z4jHLupgF2O07w@mail.gmail.com>

Hi Julien--
    Thanks for getting back to me. I'm not sure how to open an issue on
there; I am new to this. Even more so, I would not know how to begin to
implement it. Also, I don't know what a "PR" is. However, I'm willing to
give it a shot, though it will take some time.
--Mario
 - - -


On Tue, May 28, 2019 at 5:06 AM Julien Palard <julien at palard.fr> wrote:

> Hi Mario,
>
> > It would be helpful, perhaps, to color the box of the illegal code
> another way, or, in the interest of eventual printout, a double-frame box,
> an "ILLEGAL" text block, or some other visual cue.
>
> I like the idea, would you mind opening an issue on bugs.python.org to
> keep track of it? And if you feel trying to implement it, don't hesitate to
> open a PR :)
>
> --
> Julien Palard
> https://mdk.fr
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190529/199bda52/attachment.html>

From report at bugs.python.org  Wed May 29 13:05:32 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 17:05:32 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1559149532.86.0.871362156353.issue33071@roundup.psfhosted.org>


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


New changeset 103b8d9f9179089019ddb363ec0098b63816001b by Miss Islington (bot) (Hai Shi) in branch '2.7':
[2.7] bpo-33071: remove outdated PyPI docs (GH-13087) (GH-13584)
https://github.com/python/cpython/commit/103b8d9f9179089019ddb363ec0098b63816001b


----------

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

From report at bugs.python.org  Wed May 29 13:08:20 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 17:08:20 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1559149700.91.0.491840881101.issue36794@roundup.psfhosted.org>


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


New changeset 34f4f5efea730504216ee19f237734e0bb0104ee by Miss Islington (bot) (Hrvoje Nik?i?) in branch 'master':
bpo-36794: Document that Lock.acquire is fair. (GH-13082)
https://github.com/python/cpython/commit/34f4f5efea730504216ee19f237734e0bb0104ee


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

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

From report at bugs.python.org  Wed May 29 13:11:21 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 29 May 2019 17:11:21 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1559149881.84.0.133214552507.issue36794@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


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

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

From report at bugs.python.org  Wed May 29 13:30:46 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 17:30:46 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1559151046.14.0.246797521659.issue36794@roundup.psfhosted.org>


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


----------
pull_requests: +13551
pull_request: https://github.com/python/cpython/pull/13659

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

From report at bugs.python.org  Wed May 29 14:24:40 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 29 May 2019 18:24:40 +0000
Subject: [docs] [issue36794] asyncio.Lock documentation in Py3.8 lacks parts
 presented in documentation in Py3.6
In-Reply-To: <1556979606.65.0.142990517106.issue36794@roundup.psfhosted.org>
Message-ID: <1559154280.32.0.902739863497.issue36794@roundup.psfhosted.org>


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


New changeset 4e1e887203ef069bf293ecabd945f7567d6a4879 by Miss Islington (bot) in branch '3.7':
bpo-36794: Document that Lock.acquire is fair. (GH-13082)
https://github.com/python/cpython/commit/4e1e887203ef069bf293ecabd945f7567d6a4879


----------

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

From report at bugs.python.org  Wed May 29 20:50:45 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Thu, 30 May 2019 00:50:45 +0000
Subject: [docs] [issue36373] Deprecate explicit loop parameter in all public
 asyncio APIs
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559177445.57.0.636443476814.issue36373@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
keywords: +patch
pull_requests: +13559
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/13670

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

From report at bugs.python.org  Wed May 29 21:43:11 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Thu, 30 May 2019 01:43:11 +0000
Subject: [docs] [issue36373] Deprecate explicit loop parameter in all public
 asyncio APIs
In-Reply-To: <1553025335.55.0.640410639085.issue36373@roundup.psfhosted.org>
Message-ID: <1559180591.34.0.312112162513.issue36373@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
pull_requests: +13560
pull_request: https://github.com/python/cpython/pull/13671

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

From report at bugs.python.org  Wed May 29 21:50:03 2019
From: report at bugs.python.org (=?utf-8?b?6bqm5qCL6ZOW?=)
Date: Thu, 30 May 2019 01:50:03 +0000
Subject: [docs] [issue37094] Provide an example for TestCase.skipTest in
 unittest doc
Message-ID: <1559181003.42.0.162580428843.issue37094@roundup.psfhosted.org>


New submission from ??? <makdon at makdon.me>:

I found that there's an function TestCase.skipTest(reason)[0] supports skipping test in testing, but there's no example for this function in chapter Skipping tests[1] and expected failures

I create PR[2] for updating the example for TestCase.skipTest in unittest doc.
The example is from Lib/unittest/test, the test for unittest.

I am sorry for that i don't know if the issue tracker support markdown link syntax, so i just copy and paste the link below:

[0] https://docs.python.org/3.7/library/unittest.html#unittest.TestCase.skipTest
[1]https://docs.python.org/3.7/library/unittest.html#skipping-tests-and-expected-failures
[2]https://github.com/python/cpython/pull/13645

----------
assignee: docs at python
components: Documentation
messages: 343943
nosy: docs at python, ???
priority: normal
pull_requests: 13561
severity: normal
status: open
title: Provide an example for TestCase.skipTest in unittest doc
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu May 30 13:55:14 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 30 May 2019 17:55:14 +0000
Subject: [docs] [issue30754] textwrap.dedent mishandles empty lines
In-Reply-To: <1498404324.65.0.525714137023.issue30754@psf.upfronthosting.co.za>
Message-ID: <1559238914.13.0.544611656157.issue30754@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

The current behavior is desired.  We just need to document it better in https://docs.python.org/3/library/textwrap.html#textwrap.dedent

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy
nosy: +docs at python, gregory.p.smith
versions: +Python 3.8 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Thu May 30 15:31:56 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 30 May 2019 19:31:56 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1559244716.82.0.532370116389.issue5028@roundup.psfhosted.org>


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


New changeset 1e36f75d634383eb243aa1798c0f2405c9ceb5d4 by Miss Islington (bot) (Andrew Carr) in branch 'master':
bpo-5028: fix doc bug for tokenize (GH-11683)
https://github.com/python/cpython/commit/1e36f75d634383eb243aa1798c0f2405c9ceb5d4


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

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

From report at bugs.python.org  Thu May 30 15:33:23 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 30 May 2019 19:33:23 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1559244803.24.0.585880240774.issue5028@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Thu May 30 15:50:25 2019
From: report at bugs.python.org (Anders Kaseorg)
Date: Thu, 30 May 2019 19:50:25 +0000
Subject: [docs] [issue37103] Undo deprecation of optparse
Message-ID: <1559245825.26.0.384245211115.issue37103@roundup.psfhosted.org>


New submission from Anders Kaseorg <andersk at mit.edu>:

The optparse library is currently marked in the documentation as deprecated in favor of argparse.  However, argparse uses a nonstandard reinterpretation of Unix command line grammars that makes certain arguments impossible to express, and causes scripts to break when ported from optparse to argparse.  See the bug report I filed nine years ago:

https://bugs.python.org/issue9334
argparse does not accept options taking arguments beginning with dash (regression from optparse)

The conclusion of the core developers (e.g. msg309691) seems to have been that although it?s a valid bug, it can?t or won?t be fixed with the current argparse architecture.

I was asked by another core developer to file a bug report for the de-deprecation of optparse (https://discuss.python.org/t/pep-594-removing-dead-batteries-from-the-standard-library/1704/20), so here it is.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 343997
nosy: andersk, docs at python
priority: normal
severity: normal
status: open
title: Undo deprecation of optparse
versions: Python 3.8

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

From report at bugs.python.org  Thu May 30 16:19:45 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 30 May 2019 20:19:45 +0000
Subject: [docs] [issue30969] Docs should say that `x is z or x == z` is used
 for `x in y` in containers that do not implement `__contains__`
In-Reply-To: <1500465353.64.0.619810995706.issue30969@psf.upfronthosting.co.za>
Message-ID: <1559247585.16.0.272576345558.issue30969@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset 2f5b9dcc0a89cbde1499c76df81c36bfd5ef9aa8 by Cheryl Sabella (Antti Haapala) in branch 'master':
bpo-30969: Fix docs about the comparison in absence of __contains__ (GH-2761)
https://github.com/python/cpython/commit/2f5b9dcc0a89cbde1499c76df81c36bfd5ef9aa8


----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Thu May 30 16:20:17 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 30 May 2019 20:20:17 +0000
Subject: [docs] [issue30969] Docs should say that `x is z or x == z` is used
 for `x in y` in containers that do not implement `__contains__`
In-Reply-To: <1500465353.64.0.619810995706.issue30969@psf.upfronthosting.co.za>
Message-ID: <1559247617.63.0.642538028791.issue30969@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Thu May 30 16:23:36 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 30 May 2019 20:23:36 +0000
Subject: [docs] [issue30969] Docs should say that `x is z or x == z` is used
 for `x in y` in containers that do not implement `__contains__`
In-Reply-To: <1500465353.64.0.619810995706.issue30969@psf.upfronthosting.co.za>
Message-ID: <1559247816.95.0.733816839051.issue30969@roundup.psfhosted.org>


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


----------
pull_requests: +13572
pull_request: https://github.com/python/cpython/pull/13684

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

From report at bugs.python.org  Thu May 30 16:41:26 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 30 May 2019 20:41:26 +0000
Subject: [docs] [issue30969] Docs should say that `x is z or x == z` is used
 for `x in y` in containers that do not implement `__contains__`
In-Reply-To: <1500465353.64.0.619810995706.issue30969@psf.upfronthosting.co.za>
Message-ID: <1559248885.97.0.917309543329.issue30969@roundup.psfhosted.org>


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


New changeset e8661c1dabc206bf7fe6e302e38fa426aa734dd0 by Miss Islington (bot) in branch '3.7':
bpo-30969: Fix docs about the comparison in absence of __contains__ (GH-2761)
https://github.com/python/cpython/commit/e8661c1dabc206bf7fe6e302e38fa426aa734dd0


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

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

From report at bugs.python.org  Thu May 30 16:41:50 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 30 May 2019 20:41:50 +0000
Subject: [docs] [issue27605] Inconsistent calls to __eq__ from built-in
 __contains__
In-Reply-To: <1469362395.06.0.246923750082.issue27605@psf.upfronthosting.co.za>
Message-ID: <1559248910.38.0.305076256465.issue27605@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.8, Python 3.9

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

From report at bugs.python.org  Thu May 30 16:43:23 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 30 May 2019 20:43:23 +0000
Subject: [docs] [issue37103] Undo deprecation of optparse
In-Reply-To: <1559245825.26.0.384245211115.issue37103@roundup.psfhosted.org>
Message-ID: <1559249003.83.0.823657417036.issue37103@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu May 30 17:48:48 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Thu, 30 May 2019 21:48:48 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1559252928.62.0.0271220541834.issue5028@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
pull_requests: +13574
pull_request: https://github.com/python/cpython/pull/13686

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

From report at bugs.python.org  Thu May 30 18:03:29 2019
From: report at bugs.python.org (Mario Corchero)
Date: Thu, 30 May 2019 22:03:29 +0000
Subject: [docs] [issue37104] logging.Logger.disabled is not documented
Message-ID: <1559253809.15.0.569168617436.issue37104@roundup.psfhosted.org>


New submission from Mario Corchero <mariocj89 at gmail.com>:

Just realised the "disabled" attribute of the Logger class is not documented in https://docs.python.org/3/library/logging.html#logging.Logger.

Any reason to not have it documented? I'll send a PR otherwise.

This comes as I was trying to point to the docs of the attribute in https://bugs.python.org/issue29143

----------
assignee: docs at python
components: Documentation
messages: 344007
nosy: docs at python, mariocj89
priority: low
severity: normal
status: open
title: logging.Logger.disabled is not documented
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu May 30 18:03:46 2019
From: report at bugs.python.org (Mario Corchero)
Date: Thu, 30 May 2019 22:03:46 +0000
Subject: [docs] [issue37104] logging.Logger.disabled is not documented
In-Reply-To: <1559253809.15.0.569168617436.issue37104@roundup.psfhosted.org>
Message-ID: <1559253826.86.0.00402336646829.issue37104@roundup.psfhosted.org>


Change by Mario Corchero <mariocj89 at gmail.com>:


----------
keywords: +patch
pull_requests: +13575
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/13687

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

From report at bugs.python.org  Thu May 30 18:06:44 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 30 May 2019 22:06:44 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1559254004.7.0.937657994829.issue5028@roundup.psfhosted.org>


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


New changeset 2a58b0636d1f620f8a85a2e4c030cc10551936a5 by Miss Islington (bot) (Anthony Sottile) in branch 'master':
bpo-5028: Fix up rest of documentation for tokenize documenting line (GH-13686)
https://github.com/python/cpython/commit/2a58b0636d1f620f8a85a2e4c030cc10551936a5


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

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

From report at bugs.python.org  Thu May 30 21:40:39 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Fri, 31 May 2019 01:40:39 +0000
Subject: [docs] [issue37105] Add deprecated-remove information on stream doc
Message-ID: <1559266839.05.0.214061892347.issue37105@roundup.psfhosted.org>


New submission from Emmanuel Arias <emmanuelarias30 at gmail.com>:

According to the code on streams.py the functions:
open_connection(), start_server(), open_unix_connection(),
start_unix_server() are deprecated. I inform that on
documentation.

----------
assignee: docs at python
components: Documentation
messages: 344015
nosy: docs at python, eamanu
priority: normal
severity: normal
status: open
title: Add deprecated-remove information on stream doc
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu May 30 21:41:12 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Fri, 31 May 2019 01:41:12 +0000
Subject: [docs] [issue37105] Add deprecated-remove information on stream doc
In-Reply-To: <1559266839.05.0.214061892347.issue37105@roundup.psfhosted.org>
Message-ID: <1559266872.57.0.169019117026.issue37105@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
keywords: +patch
pull_requests: +13578
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/13672

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

From report at bugs.python.org  Fri May 31 00:55:30 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 31 May 2019 04:55:30 +0000
Subject: [docs] [issue37103] Undo deprecation of optparse
In-Reply-To: <1559245825.26.0.384245211115.issue37103@roundup.psfhosted.org>
Message-ID: <1559278530.49.0.479172889665.issue37103@roundup.psfhosted.org>


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

See also issue25521

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

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

From report at bugs.python.org  Fri May 31 04:52:17 2019
From: report at bugs.python.org (Antony Lee)
Date: Fri, 31 May 2019 08:52:17 +0000
Subject: [docs] [issue37109] Inacurrate documentation regarding return type
 of math.factorial
Message-ID: <1559292737.06.0.619691147167.issue37109@roundup.psfhosted.org>


New submission from Antony Lee <anntzer.lee at gmail.com>:

https://docs.python.org/3/library/math.html says

The following functions are provided by this module. Except when explicitly noted otherwise, all return values are floats.

and

math.factorial(x)
Return x factorial. Raises ValueError if x is not integral or is negative.

but math.factorial returns an int (which is perfectly reasonable and just needs to be documented):

In [3]: math.factorial(5)                                                                                                                                                                                                                   
Out[3]: 120

----------
assignee: docs at python
components: Documentation
messages: 344039
nosy: Antony.Lee, docs at python
priority: normal
severity: normal
status: open
title: Inacurrate documentation regarding return type of math.factorial
versions: Python 3.8

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

From report at bugs.python.org  Fri May 31 05:07:25 2019
From: report at bugs.python.org (Christoph Zwerschke)
Date: Fri, 31 May 2019 09:07:25 +0000
Subject: [docs] [issue37110] Clarify hashability of custom class instances
Message-ID: <1559293645.61.0.954260937021.issue37110@roundup.psfhosted.org>


New submission from Christoph Zwerschke <cito at online.de>:

The Python documentation says about hashability in the glossary (https://docs.python.org/3/glossary.html#term-hashable):

"Objects which are instances of user-defined classes are hashable by default."

This is not quite true. Objects of a user-defined class with an __eq__ method are not hashable. Maybe it would be better to make this more explicit:

"Objects which are instances of user_defined classes without custom __eq__ and __hash__ methods are hashable by default."

----------
assignee: docs at python
components: Documentation
messages: 344042
nosy: cito, docs at python
priority: normal
severity: normal
status: open
title: Clarify hashability of custom class instances
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Fri May 31 05:12:33 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 31 May 2019 09:12:33 +0000
Subject: [docs] [issue37104] logging.Logger.disabled is not documented
In-Reply-To: <1559253809.15.0.569168617436.issue37104@roundup.psfhosted.org>
Message-ID: <1559293953.71.0.701492195258.issue37104@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

Thanks for looking at this, Mario, but I'd rather not document this attribute, for the reason stated on the PR when I closed it:

"I'd like to avoid documenting this attribute, as it's really meant for internal use by the configuration machinery. I realise that it's named disabled rather than _disabled, which might indicate that it's public, but it isn't meant to be, and the name can't be changed now for compatibility reasons, in case some code somewhere is relying on it! I don't want someone to ask for "disabled" to be explicitly supported in configurations, for instance - I can currently argue that it's not meant to be public, as it isn't documented."

----------
nosy: +vinay.sajip
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri May 31 05:23:35 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 31 May 2019 09:23:35 +0000
Subject: [docs] [issue37109] Inacurrate documentation regarding return type
 of math.factorial
In-Reply-To: <1559292737.06.0.619691147167.issue37109@roundup.psfhosted.org>
Message-ID: <1559294614.99.0.867079401243.issue37109@roundup.psfhosted.org>


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

Is this same as issue25735 ?

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

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

From report at bugs.python.org  Fri May 31 05:27:15 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 31 May 2019 09:27:15 +0000
Subject: [docs] [issue21314] Document '/' in signatures
In-Reply-To: <1397988439.5.0.703056699862.issue21314@psf.upfronthosting.co.za>
Message-ID: <1559294835.43.0.636160521572.issue21314@roundup.psfhosted.org>


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

Hooray!  Now that PEP570 is implemented in 3.8:

>>> def f(a, /, *, b): return 3
...
>>> f(0, b=2)
3
# other combinations raise

and somewhat documented, ('/' in grammar of '8.6 Function definitions', though not explained, should its status become final and listing moved?

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

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

From report at bugs.python.org  Fri May 31 05:29:34 2019
From: report at bugs.python.org (Antony Lee)
Date: Fri, 31 May 2019 09:29:34 +0000
Subject: [docs] [issue37109] Inacurrate documentation regarding return type
 of math.factorial
In-Reply-To: <1559292737.06.0.619691147167.issue37109@roundup.psfhosted.org>
Message-ID: <1559294974.58.0.635158066796.issue37109@roundup.psfhosted.org>


Antony Lee <anntzer.lee at gmail.com> added the comment:

oops, missed that, thanks for pointing that out.

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

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

From report at bugs.python.org  Fri May 31 05:53:36 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 31 May 2019 09:53:36 +0000
Subject: [docs] [issue37109] Inacurrate documentation regarding return type
 of math.factorial
In-Reply-To: <1559292737.06.0.619691147167.issue37109@roundup.psfhosted.org>
Message-ID: <1559296416.1.0.0912483950679.issue37109@roundup.psfhosted.org>


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


----------
resolution:  -> duplicate
superseder:  -> math.factorial doc should mention integer return type

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

From report at bugs.python.org  Fri May 31 05:57:21 2019
From: report at bugs.python.org (Antony Lee)
Date: Fri, 31 May 2019 09:57:21 +0000
Subject: [docs] [issue37109] Inacurrate documentation regarding return type
 of math.factorial
In-Reply-To: <1559292737.06.0.619691147167.issue37109@roundup.psfhosted.org>
Message-ID: <1559296641.88.0.736823894712.issue37109@roundup.psfhosted.org>


Change by Antony Lee <anntzer.lee at gmail.com>:


----------
nosy:  -Antony.Lee

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

From report at bugs.python.org  Fri May 31 06:00:35 2019
From: report at bugs.python.org (Mario Corchero)
Date: Fri, 31 May 2019 10:00:35 +0000
Subject: [docs] [issue37104] logging.Logger.disabled is not documented
In-Reply-To: <1559253809.15.0.569168617436.issue37104@roundup.psfhosted.org>
Message-ID: <1559296835.23.0.177747176208.issue37104@roundup.psfhosted.org>


Mario Corchero <mariocj89 at gmail.com> added the comment:

Thanks! I was wondering about it but saw no comment about it, issue or anything in the history. At least we have now this issue :).

Would you like that I move this to `_disabled` and have a setter for `disabled` that emits a deprecation warning so we can remove this someday or at least make it more explicit that it should not be used?

----------

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

From report at bugs.python.org  Fri May 31 06:13:28 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 31 May 2019 10:13:28 +0000
Subject: [docs] [issue37104] logging.Logger.disabled is not documented
In-Reply-To: <1559253809.15.0.569168617436.issue37104@roundup.psfhosted.org>
Message-ID: <1559297608.66.0.992892030253.issue37104@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

As it's not documented, people would come across it by browsing the source. I'd just mention in the source (Logger constructor) that it's for internal use, and leave it at that.

----------

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

From report at bugs.python.org  Fri May 31 06:26:25 2019
From: report at bugs.python.org (Mario Corchero)
Date: Fri, 31 May 2019 10:26:25 +0000
Subject: [docs] [issue37104] logging.Logger.disabled is not documented
In-Reply-To: <1559253809.15.0.569168617436.issue37104@roundup.psfhosted.org>
Message-ID: <1559298385.94.0.760382051575.issue37104@roundup.psfhosted.org>


Mario Corchero <mariocj89 at gmail.com> added the comment:

Note that even if not in the standard library I've seen this attributed used and documented quite often.

Example: https://docs.python-guide.org/writing/logging/#or-print

I would really suggest making it private as mentioned before to make sure this does not happen, but if you still prefer just a comment (as in source comment, not even documentation) I'll go with that.

----------

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

From report at bugs.python.org  Fri May 31 06:58:06 2019
From: report at bugs.python.org (Stefan Behnel)
Date: Fri, 31 May 2019 10:58:06 +0000
Subject: [docs] [issue18911] minidom does not encode correctly when calling
 Document.writexml
In-Reply-To: <1378186619.58.0.930376227557.issue18911@psf.upfronthosting.co.za>
Message-ID: <1559300286.03.0.124864502787.issue18911@roundup.psfhosted.org>


Stefan Behnel <stefan_ml at behnel.de> added the comment:

Asking users unconditionally to use the "xmlcharrefreplace" replacement method seems wrong for UTF-8. It should not be necessary.

We should, however, document explicitly that the file will receive text and not bytes, i.e. that users are themselves responsible for opening the output file with the desired encoding. We should also make it clearer that the "encoding" argument to writexml() does not change that.

----------

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

From report at bugs.python.org  Fri May 31 12:16:39 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 31 May 2019 16:16:39 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559319399.32.0.714942556623.issue36896@roundup.psfhosted.org>


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

In msg342227 Pablo Galindo Salgado said "I am +1 to such a sentence, but I think this is a decision that more core devs should agree on."

> "These types are not supposed to be instantiated outside of CPython internals"

At least Petr Vidtorin and I disagree with this part.  As Petr wrote on pydev thread "Expected stability of PyCode_New() and types.CodeType() signatures", there are multiple tools that instantiate code objects, in particular Cython, which is far from being a rogue project.  Python is a 'consenting adults' languages, and we generally do not officially tell people what they are 'supposed' to do or not do.

----------
nosy: +petr.viktorin, terry.reedy

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

From report at bugs.python.org  Fri May 31 12:19:15 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 16:19:15 +0000
Subject: [docs] [issue37094] Provide an example for TestCase.skipTest in
 unittest doc
In-Reply-To: <1559181003.42.0.162580428843.issue37094@roundup.psfhosted.org>
Message-ID: <1559319555.97.0.143128456795.issue37094@roundup.psfhosted.org>


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


New changeset ffed76b6fc4d7dd0244b662d6e5738eb496d9def by Miss Islington (bot) (Makdon) in branch 'master':
bpo-37094: Add example for TestCase.skipTest in unittest doc (GH-13645)
https://github.com/python/cpython/commit/ffed76b6fc4d7dd0244b662d6e5738eb496d9def


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

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

From report at bugs.python.org  Fri May 31 12:19:34 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 16:19:34 +0000
Subject: [docs] [issue37094] Provide an example for TestCase.skipTest in
 unittest doc
In-Reply-To: <1559181003.42.0.162580428843.issue37094@roundup.psfhosted.org>
Message-ID: <1559319574.17.0.777097455911.issue37094@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +13587
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/13701

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

From report at bugs.python.org  Fri May 31 12:31:58 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 16:31:58 +0000
Subject: [docs] [issue37094] Provide an example for TestCase.skipTest in
 unittest doc
In-Reply-To: <1559181003.42.0.162580428843.issue37094@roundup.psfhosted.org>
Message-ID: <1559320318.61.0.536681899396.issue37094@roundup.psfhosted.org>


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


New changeset 8135455c840b9e169a6cd527cb1ee922cafb9109 by Miss Islington (bot) in branch '3.7':
bpo-37094: Add example for TestCase.skipTest in unittest doc (GH-13645)
https://github.com/python/cpython/commit/8135455c840b9e169a6cd527cb1ee922cafb9109


----------

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

From report at bugs.python.org  Fri May 31 12:41:34 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 31 May 2019 16:41:34 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1559320894.7.0.240927181437.issue25735@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset 4612671df2742eade8ecf8003a6ce1247973c135 by Cheryl Sabella (Akshay Sharma) in branch 'master':
bpo-25735: math.factorial doc should mention integer return type (GH-6420)
https://github.com/python/cpython/commit/4612671df2742eade8ecf8003a6ce1247973c135


----------

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

From report at bugs.python.org  Fri May 31 12:43:16 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 16:43:16 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1559320996.96.0.374762177028.issue25735@roundup.psfhosted.org>


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


----------
pull_requests: +13588
pull_request: https://github.com/python/cpython/pull/13702

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

From report at bugs.python.org  Fri May 31 12:44:19 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 31 May 2019 16:44:19 +0000
Subject: [docs] [issue37109] Inacurrate documentation regarding return type
 of math.factorial
In-Reply-To: <1559292737.06.0.619691147167.issue37109@roundup.psfhosted.org>
Message-ID: <1559321059.57.0.94847701362.issue37109@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Thanks for pointing out the other issue.  I've now merged it.

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Fri May 31 12:46:33 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 31 May 2019 16:46:33 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1559321193.43.0.508290301974.issue25735@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@John.Yeung, thank you for the report.  @mine0901, thanks for the initial patch and @akshaysharma, thank you for the PR.

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

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

From report at bugs.python.org  Fri May 31 12:58:30 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 16:58:30 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1559321910.53.0.0551150431978.issue25735@roundup.psfhosted.org>


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


New changeset fc3b8437c86167983cc75e5a9a3ed1dc542a1b79 by Miss Islington (bot) in branch '3.7':
bpo-25735: math.factorial doc should mention integer return type (GH-6420)
https://github.com/python/cpython/commit/fc3b8437c86167983cc75e5a9a3ed1dc542a1b79


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

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

From report at bugs.python.org  Fri May 31 13:38:09 2019
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 31 May 2019 17:38:09 +0000
Subject: [docs] [issue37094] Provide an example for TestCase.skipTest in
 unittest doc
In-Reply-To: <1559181003.42.0.162580428843.issue37094@roundup.psfhosted.org>
Message-ID: <1559324289.74.0.43030014511.issue37094@roundup.psfhosted.org>


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

Thanks for the patch!

----------
nosy: +zach.ware
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7

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

From report at bugs.python.org  Fri May 31 13:43:40 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 31 May 2019 17:43:40 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559324620.65.0.579181055953.issue36896@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Although I completely agree with the decision of figuring out an explicit consensus regarding these APIs, I will explain a bit my +1:

My +1 is not about the usage of PyCode_New, is about the usage of `types.CodeType`. The constructor for the later has never been documented on the Python side, so one could argue that is not a supported feature to manually construct code objects.

The more we expose and call "stable" regarding internals, the less freedom we will have to apply optimizations and add additional data members to internal structures.

With this, I am not saying that we should say that whoever uses this is a "roge" project but marking these APIs as stable will greatly restrict future changes.

----------
nosy: +pablogsal

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

From report at bugs.python.org  Fri May 31 14:12:06 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 31 May 2019 18:12:06 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559326326.56.0.0625010365834.issue36896@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Being said that, I am very happy with the current changes on the PR :)

 Thank you @Terry and @Petr for helping with this!

----------

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

From report at bugs.python.org  Fri May 31 14:44:26 2019
From: report at bugs.python.org (Chirag Garg)
Date: Fri, 31 May 2019 18:44:26 +0000
Subject: [docs] [issue10936] Simple CSS fix for left margin at
 docs.python.org
In-Reply-To: <1295377924.0.0.902429691003.issue10936@psf.upfronthosting.co.za>
Message-ID: <1559328266.12.0.411261895167.issue10936@roundup.psfhosted.org>


Chirag Garg <chrggrg2018 at gmail.com> added the comment:

Yes, it is creating a vision problem as the text is creating a problem. And the CSS script of @cdunn2001 is correct also there is a need to change the navigation bar.

----------
nosy: +codevil_2o

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

From report at bugs.python.org  Fri May 31 14:45:59 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Fri, 31 May 2019 18:45:59 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559328359.14.0.801860063221.issue36896@roundup.psfhosted.org>


Matthias Bussonnier <bussonniermatthias at gmail.com> added the comment:

Victor recently implemented CodeType.replace(); which I believe will cover many of the usecase.

Should I also send a PR that update the DocStrings of (some of) ? these objects? many people don't go and read the html docs...

----------

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

From report at bugs.python.org  Fri May 31 14:52:04 2019
From: report at bugs.python.org (Chirag Garg)
Date: Fri, 31 May 2019 18:52:04 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1559328724.32.0.433132324847.issue36947@roundup.psfhosted.org>


Chirag Garg <chrggrg2018 at gmail.com> added the comment:

It should be written like "In the following example, both MyClass and MySubclass are instances of Meta and the type of MyClass is of metaclass Meta and type of MySubclass is MyClass:"

----------
nosy: +codevil_2o

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

From report at bugs.python.org  Fri May 31 15:47:05 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 31 May 2019 19:47:05 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559332025.58.0.568780477625.issue36896@roundup.psfhosted.org>


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

Pablo, I am all for respectfully preserving implementation freedom where we can.  From idlelib.__init__: [idlelib files other than idle*.*]  "are private implementations.  Their details are subject to change.  See PEP 434 for more.  Import them at your own risk."

Matthias: I don't believe we put version changed notes in docstrings, as they are for the current code.  But if a docstring covers arguments, as usual, then the new one should be added.

----------

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

From report at bugs.python.org  Fri May 31 16:02:15 2019
From: report at bugs.python.org (Matthias Bussonnier)
Date: Fri, 31 May 2019 20:02:15 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559332935.37.0.297975675002.issue36896@roundup.psfhosted.org>


Matthias Bussonnier <bussonniermatthias at gmail.com> added the comment:

>  I don't believe we put version changed notes in docstrings,

Oh no I was thinking a note in the docstring "constructor signature may change between Python versions".

Whether to put changed/addition info in docstrings is another subject and a thing I would be in favor of; but let's not digress and the current issue which is to convey to users the non-stability of interface.

----------

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

From report at bugs.python.org  Fri May 31 16:19:01 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 31 May 2019 20:19:01 +0000
Subject: [docs] [issue15115] Duplicated Content-Transfer-Encoding header
 when applying email.encoders
In-Reply-To: <1340188711.86.0.286169814605.issue15115@psf.upfronthosting.co.za>
Message-ID: <1559333941.44.0.00242264207268.issue15115@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:


New changeset a747c3a5edf21fa5670bc30f5e1d804de89ebf62 by Cheryl Sabella in branch 'master':
bpo-15115: Document deprecation of email.encoders in Python 3 (GH-5354)
https://github.com/python/cpython/commit/a747c3a5edf21fa5670bc30f5e1d804de89ebf62


----------

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

From report at bugs.python.org  Fri May 31 16:20:02 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 20:20:02 +0000
Subject: [docs] [issue15115] Duplicated Content-Transfer-Encoding header
 when applying email.encoders
In-Reply-To: <1340188711.86.0.286169814605.issue15115@psf.upfronthosting.co.za>
Message-ID: <1559334002.41.0.361127236087.issue15115@roundup.psfhosted.org>


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


----------
pull_requests: +13596
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/13709

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

From report at bugs.python.org  Fri May 31 16:20:22 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 31 May 2019 20:20:22 +0000
Subject: [docs] [issue15115] Duplicated Content-Transfer-Encoding header
 when applying email.encoders
In-Reply-To: <1340188711.86.0.286169814605.issue15115@psf.upfronthosting.co.za>
Message-ID: <1559334022.9.0.355524314138.issue15115@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


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

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

From report at bugs.python.org  Fri May 31 16:26:09 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 31 May 2019 20:26:09 +0000
Subject: [docs] [issue15115] Duplicated Content-Transfer-Encoding header
 when applying email.encoders
In-Reply-To: <1340188711.86.0.286169814605.issue15115@psf.upfronthosting.co.za>
Message-ID: <1559334369.91.0.511080310665.issue15115@roundup.psfhosted.org>


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


New changeset 464c1ec65af2c1c1d849d50d9726fa453804e70e by Miss Islington (bot) in branch '3.7':
bpo-15115: Document deprecation of email.encoders in Python 3 (GH-5354)
https://github.com/python/cpython/commit/464c1ec65af2c1c1d849d50d9726fa453804e70e


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

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

From report at bugs.python.org  Fri May 31 16:49:05 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Fri, 31 May 2019 20:49:05 +0000
Subject: [docs] [issue37105] Add deprecated-remove information on stream doc
In-Reply-To: <1559266839.05.0.214061892347.issue37105@roundup.psfhosted.org>
Message-ID: <1559335745.62.0.16035272024.issue37105@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:


New changeset ed9f3562b637a59b9000abbceee5ae369d35444d by Andrew Svetlov (Emmanuel Arias) in branch 'master':
bpo-37105: Add deprecated-remove information on stream doc (#13672)
https://github.com/python/cpython/commit/ed9f3562b637a59b9000abbceee5ae369d35444d


----------
nosy: +asvetlov

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

From report at bugs.python.org  Fri May 31 17:22:42 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 31 May 2019 21:22:42 +0000
Subject: [docs] [issue37073] clarify functions docs in IO modules and Bytes
 Objects
In-Reply-To: <1559027884.63.0.0963085588001.issue37073@roundup.psfhosted.org>
Message-ID: <1559337762.69.0.812588957446.issue37073@roundup.psfhosted.org>


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

Can you prepare a PR?

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

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

From report at bugs.python.org  Fri May 31 17:55:03 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 31 May 2019 21:55:03 +0000
Subject: [docs] [issue37082] Assignment expression symbol (walrus) not in
 built-in help()
In-Reply-To: <1559067983.32.0.880606504508.issue37082@roundup.psfhosted.org>
Message-ID: <1559339703.9.0.0510544498351.issue37082@roundup.psfhosted.org>


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

The augmented assignment symbol, like that for plain assignment, is not, properly speaking, an operator.  But it definitely is a symbol that needs to be documented.

1. Generally update the help symbol list.

2. Document :=, assignment expression, in the regular docs, but I found nothing.

':=' should be on https://docs.python.org/3.8/genindex-Symbols.html just ':(colon)'.

'expression' should be listed under 'assignment on
https://docs.python.org/3.8/genindex-A.html

I think 'assignment' should be listed under 'expression' on
https://docs.python.org/3.8/genindex-E.html

I could not find anything in the expressions chapter.

----------
nosy: +terry.reedy
title: Assignment expression operator (walrus) not in built-in help() -> Assignment expression symbol (walrus) not in built-in help()

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

From report at bugs.python.org  Fri May 31 18:16:38 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 31 May 2019 22:16:38 +0000
Subject: [docs] [issue36896] clarify in types.rst that FunctionTypes & co
 constructors don't have stable signature
In-Reply-To: <1557698610.19.0.556381141599.issue36896@roundup.psfhosted.org>
Message-ID: <1559340998.76.0.824016873332.issue36896@roundup.psfhosted.org>


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

Yes, I think " Not for the faint of heart." could be replaced or augmented by 'api may change'

----------

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

From report at bugs.python.org  Fri May 31 19:00:39 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 31 May 2019 23:00:39 +0000
Subject: [docs] [issue37110] Clarify hashability of custom class instances
In-Reply-To: <1559293645.61.0.954260937021.issue37110@roundup.psfhosted.org>
Message-ID: <1559343639.47.0.973129266.issue37110@roundup.psfhosted.org>


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

The docs look correct to me:

    >>> class A:
            pass

    >>> hash(A())
    274859987

User defined classes are in-fact hashable by default.  Other methods can be defined to change hashability, but they are not the default.

FWIW, it isn't the purpose of the glossary to be a language spec; rather, it is to provide a rough meaning of what the word "hashable" means.  Already, the wording has exceeded its original intent.  The correct place for a more detailed specification in the language reference for object.__hash__():

   https://docs.python.org/3/reference/datamodel.html?highlight=__hash__#object.__hash__

Thank you for the suggestion, but we'll pass on this one.

----------
assignee: docs at python -> rhettinger
nosy: +rhettinger
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri May 31 19:25:28 2019
From: report at bugs.python.org (Christoph Zwerschke)
Date: Fri, 31 May 2019 23:25:28 +0000
Subject: [docs] [issue37110] Clarify hashability of custom class instances
In-Reply-To: <1559293645.61.0.954260937021.issue37110@roundup.psfhosted.org>
Message-ID: <1559345128.31.0.779577271033.issue37110@roundup.psfhosted.org>


Christoph Zwerschke <cito at online.de> added the comment:

My point was that it's not immediately obvious what "by default" means and that hashability is not only affected by the __hash__ method but also by __eq__.

But I agree, you can argue that "by default" already includes not adding any special methods like __eq__ and the glossary should not become too verbose. (I remember these words from Donald Knuth in one of his books: "In the interest of conciseness, you need to indulge in simplifications that are really little lies; these should be overlooked.")

----------

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

From jibarra4 at live.nmhu.edu  Fri May 31 19:00:25 2019
From: jibarra4 at live.nmhu.edu (Ibarra, Jesse)
Date: Fri, 31 May 2019 23:00:25 +0000
Subject: [docs] Embedding Python in Another Application tutorial problem
Message-ID: <SN4PR0201MB35528CAC8A2666ED8B66D826D3190@SN4PR0201MB3552.namprd02.prod.outlook.com>

Hi,
I am working on CentOS7

I am trying the 1.1 Very High Level Embedding

I am using
Python 3.7.3 (default, Mar 27 2019, 22:11:17)
[GCC 7.3.0] :: Anaconda, Inc. on linux


I created a file by pasting the tutorial code into original.c

#define PY_SSIZE_T_CLEAN
#include <Python.h>

int
main(int argc, char *argv[])
{
    wchar_t *program = Py_DecodeLocale(argv[0], NULL);
    if (program == NULL) {
        fprintf(stderr, "Fatal error: cannot decode argv[0]\n");
        exit(1);
    }
    Py_SetProgramName(program);  /* optional but recommended */
    Py_Initialize();
    PyRun_SimpleString("from time import time,ctime\n"
                       "print('Today is', ctime(time()))\n");
    if (Py_FinalizeEx() < 0) {
        exit(120);
    }
    PyMem_RawFree(program);
    return 0;
}

After executing:

gcc -o original original.c

original.c:2:20: fatal error: Python.h: No such file or directory

 #include <Python.h>
                    ^
compilation terminated.

What am I doing wrong? Is the tutorial complete?

Thanks,

Jesse




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