From report at bugs.python.org  Fri Jun  1 03:22:30 2018
From: report at bugs.python.org (Tobias Kunze)
Date: Fri, 01 Jun 2018 07:22:30 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1527837750.87.0.262363346258.issue27902@psf.upfronthosting.co.za>


Change by Tobias Kunze <r at rixx.de>:


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

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

From report at bugs.python.org  Fri Jun  1 12:25:52 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Fri, 01 Jun 2018 16:25:52 +0000
Subject: [docs] [issue33736] Improve the documentation of asyncio stream API
Message-ID: <1527870352.37.0.269611931914.issue33736@psf.upfronthosting.co.za>


Change by Elvis Pranskevichus <elvis at magic.io>:


----------
assignee: docs at python
components: Documentation
nosy: Elvis.Pranskevichus, docs at python
priority: normal
severity: normal
status: open
title: Improve the documentation of asyncio stream API
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jun  1 12:29:56 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Fri, 01 Jun 2018 16:29:56 +0000
Subject: [docs] [issue33736] Improve the documentation of asyncio stream API
Message-ID: <1527870596.0.0.269611931914.issue33736@psf.upfronthosting.co.za>


Change by Elvis Pranskevichus <elvis at magic.io>:


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

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

From report at bugs.python.org  Fri Jun  1 12:52:48 2018
From: report at bugs.python.org (Alexander Belopolsky)
Date: Fri, 01 Jun 2018 16:52:48 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1527871968.33.0.269611931914.issue33649@psf.upfronthosting.co.za>


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


----------
nosy: +belopolsky

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

From report at bugs.python.org  Fri Jun  1 13:05:10 2018
From: report at bugs.python.org (Puneet Singh)
Date: Fri, 01 Jun 2018 17:05:10 +0000
Subject: [docs] [issue33737] Multiprocessing not working
Message-ID: <1527872710.36.0.81473610881.issue33737@psf.upfronthosting.co.za>


New submission from Puneet Singh <duhrasoft1 at gmail.com>:

I have attached a sampl program for my project.can anyone help e to solve this multiprocessing problem.I have applied all the tpes of multiprocessing ( map,map_async, starmap, starmap_async, aplly_async) but the result is same that CPU utilisation is one core instead it had to use all of them.

The picture for cpu utilisation an be found in github account:- 
https://github.com/joddiy/multiprocess/issues/1

----------
components: Library (Lib)
messages: 318433
nosy: Puneet Singh, docs at python
priority: normal
severity: normal
status: open
title: Multiprocessing not working
type: performance
versions: Python 3.5

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

From report at bugs.python.org  Fri Jun  1 14:27:14 2018
From: report at bugs.python.org (Puneet Singh)
Date: Fri, 01 Jun 2018 18:27:14 +0000
Subject: [docs] [issue33737] Multiprocessing not working
In-Reply-To: <1527872710.36.0.81473610881.issue33737@psf.upfronthosting.co.za>
Message-ID: <1527877634.67.0.81473610881.issue33737@psf.upfronthosting.co.za>


Puneet Singh <duhrasoft1 at gmail.com> added the comment:

Can anyone help me in solving this problem ??

----------
Added file: https://bugs.python.org/file47629/Prog.py

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

From report at bugs.python.org  Fri Jun  1 14:33:51 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 01 Jun 2018 18:33:51 +0000
Subject: [docs] [issue33737] Multiprocessing not working
In-Reply-To: <1527872710.36.0.81473610881.issue33737@psf.upfronthosting.co.za>
Message-ID: <1527878031.24.0.81473610881.issue33737@psf.upfronthosting.co.za>


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

Puneet, sorry but this bug tracker is for reporting issues found with the Python language and its implementation, not for help with programming problems.  Please see the Help page on python.org for suggestions on getting help:

https://www.python.org/about/help/

----------
nosy: +ned.deily
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Jun  1 15:49:10 2018
From: report at bugs.python.org (Mayank Singhal)
Date: Fri, 01 Jun 2018 19:49:10 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1527882550.15.0.81473610881.issue31215@psf.upfronthosting.co.za>


Mayank Singhal <17mayanksinghal at gmail.com> added the comment:

Hey, I'll take this up.

----------
nosy: +storymode7

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

From report at bugs.python.org  Sat Jun  2 03:48:26 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 02 Jun 2018 07:48:26 +0000
Subject: [docs] [issue26979] The danger of PyType_FromSpec()
In-Reply-To: <1462731878.82.0.9073654009.issue26979@psf.upfronthosting.co.za>
Message-ID: <1527925706.85.0.584625200856.issue26979@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Sat Jun  2 06:30:09 2018
From: report at bugs.python.org (Christian Tismer)
Date: Sat, 02 Jun 2018 10:30:09 +0000
Subject: [docs] [issue26979] The danger of PyType_FromSpec()
In-Reply-To: <1462731878.82.0.9073654009.issue26979@psf.upfronthosting.co.za>
Message-ID: <1527935409.08.0.592728768989.issue26979@psf.upfronthosting.co.za>


Christian Tismer <tismer at stackless.com> added the comment:

There is another catch that belongs in the same category.

There is line 2841 in typeobject.c

    if (type->tp_dealloc == NULL) {
        /* It's a heap type, so needs the heap types' dealloc.
           subtype_dealloc will call the base type's tp_dealloc, if
           necessary. */
        type->tp_dealloc = subtype_dealloc;
    }

When converting the PySide types, it became a real problem. Types with an
existing tp_dealloc behaved normal, but those with tp_dealloc=NULL
gave segfaults. I ended up supplying a default dummy_dealloc()
that is just there to occupy this slot. Then it worked.


And another source of incompatibility:

PyType_FromSpec() enforces a tp_name field to be dotted, to compute a module
name. Very annoying incompatibility that could be avoided.


A small but remarkable glitch:
Most fields of the PyType_Spec/PyType_Slot combo are copied, but some are not.
So expect funny behaviour when creating types with dynamically generated
specs without strdup. That should IMHO be changed.

----------
nosy: +Christian.Tismer

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

From report at bugs.python.org  Sat Jun  2 07:58:23 2018
From: report at bugs.python.org (Timo Furrer)
Date: Sat, 02 Jun 2018 11:58:23 +0000
Subject: [docs] [issue30974] Update os.samefile docstring to match
 documentation
In-Reply-To: <1500538030.77.0.17785692497.issue30974@psf.upfronthosting.co.za>
Message-ID: <1527940703.64.0.584625200856.issue30974@psf.upfronthosting.co.za>


Change by Timo Furrer <tuxtimo at gmail.com>:


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

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

From report at bugs.python.org  Sat Jun  2 11:02:19 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 02 Jun 2018 15:02:19 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527951738.87.0.592728768989.issue23495@psf.upfronthosting.co.za>


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


New changeset a801cf164be7c62b6a6dba47ff91d6c3edb67729 by Mariatta (Zackery Spytz) in branch 'master':
bpo-23495: Correct the documentation for writerows() of csv Writer objects (GH-6316)
https://github.com/python/cpython/commit/a801cf164be7c62b6a6dba47ff91d6c3edb67729


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

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

From report at bugs.python.org  Sat Jun  2 11:03:54 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 02 Jun 2018 15:03:54 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527951834.29.0.584625200856.issue23495@psf.upfronthosting.co.za>


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


----------
pull_requests: +6969

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

From report at bugs.python.org  Sat Jun  2 11:04:59 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 02 Jun 2018 15:04:59 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527951899.38.0.584625200856.issue23495@psf.upfronthosting.co.za>


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


----------
pull_requests: +6970

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

From report at bugs.python.org  Sat Jun  2 11:05:54 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 02 Jun 2018 15:05:54 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527951954.0.0.584625200856.issue23495@psf.upfronthosting.co.za>


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


----------
pull_requests: +6971

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

From report at bugs.python.org  Sat Jun  2 11:37:31 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 02 Jun 2018 15:37:31 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527953850.98.0.592728768989.issue23495@psf.upfronthosting.co.za>


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


New changeset db3039085845af5d68ab863f03e9684681b1516d by Miss Islington (bot) in branch '3.6':
bpo-23495: Correct the documentation for writerows() of csv Writer objects (GH-6316)
https://github.com/python/cpython/commit/db3039085845af5d68ab863f03e9684681b1516d


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

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

From report at bugs.python.org  Sat Jun  2 11:40:03 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 02 Jun 2018 15:40:03 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527954003.71.0.592728768989.issue23495@psf.upfronthosting.co.za>


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


New changeset 949da9e44b4e0d5b32745b91f9582158442b68d1 by Miss Islington (bot) in branch '3.7':
bpo-23495: Correct the documentation for writerows() of csv Writer objects (GH-6316)
https://github.com/python/cpython/commit/949da9e44b4e0d5b32745b91f9582158442b68d1


----------

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

From report at bugs.python.org  Sat Jun  2 11:41:29 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 02 Jun 2018 15:41:29 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527954089.27.0.592728768989.issue23495@psf.upfronthosting.co.za>


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


New changeset af3685963652721269ca0196f9f7fc08d3e830b7 by Miss Islington (bot) in branch '2.7':
bpo-23495: Correct the documentation for writerows() of csv Writer objects (GH-6316)
https://github.com/python/cpython/commit/af3685963652721269ca0196f9f7fc08d3e830b7


----------

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

From report at bugs.python.org  Sat Jun  2 11:54:24 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 02 Jun 2018 15:54:24 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1527954864.62.0.592728768989.issue23495@psf.upfronthosting.co.za>


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

Thanks all!

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

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

From report at bugs.python.org  Sat Jun  2 13:26:48 2018
From: report at bugs.python.org (Nikhil Patel)
Date: Sat, 02 Jun 2018 17:26:48 +0000
Subject: [docs] [issue25237] Add doc for tkinter commondialog.Dialog and
 subclasses
In-Reply-To: <1443236612.77.0.515516122635.issue25237@psf.upfronthosting.co.za>
Message-ID: <1527960408.69.0.592728768989.issue25237@psf.upfronthosting.co.za>


Nikhil Patel <patenikh2 at gmail.com> added the comment:

PR to add documentation still up-to-date and all checks successful just pending review

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

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

From report at bugs.python.org  Sat Jun  2 15:13:04 2018
From: report at bugs.python.org (Mayank Singhal)
Date: Sat, 02 Jun 2018 19:13:04 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1527966784.04.0.584625200856.issue31215@psf.upfronthosting.co.za>


Change by Mayank Singhal <17mayanksinghal at gmail.com>:


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

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

From report at bugs.python.org  Sat Jun  2 17:10:56 2018
From: report at bugs.python.org (Egor Dranischnikow)
Date: Sat, 02 Jun 2018 21:10:56 +0000
Subject: [docs] [issue33740] PyByteArray_AsString C-API description lacks
 the assurance, that the trailing null-byte is appended.
Message-ID: <1527973856.37.0.592728768989.issue33740@psf.upfronthosting.co.za>


New submission from Egor Dranischnikow <no-one at turm-lahnstein.de>:

The C-API for Python2.7 https://docs.python.org/2/c-api/bytearray.html#c.PyByteArray_AsString

lacks the sentence: "The returned array always has an extra null byte appended." which clarifies, that the returned C-string is null-terminated.

This sentence is a part of Python3-documentation: https://docs.python.org/3/c-api/bytearray.html#c.PyByteArray_AsString

I might be very wrong, but so far I understand the code this is the case for both versions, Python3 and Python2.

Probably parts of this change https://github.com/python/cpython/commit/0a560a11af0ccc816d1172180f44e5afb34ba600 could be integrated in Python2.7

----------
assignee: docs at python
components: Documentation
messages: 318515
nosy: docs at python, realead
priority: normal
severity: normal
status: open
title: PyByteArray_AsString C-API description lacks the assurance, that the trailing null-byte is appended.
versions: Python 2.7

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

From report at bugs.python.org  Sun Jun  3 03:47:13 2018
From: report at bugs.python.org (Farhaan Bukhsh)
Date: Sun, 03 Jun 2018 07:47:13 +0000
Subject: [docs] [issue30516] Documentation for datetime substract operation
 incorrect?
In-Reply-To: <1496179333.45.0.413102703331.issue30516@psf.upfronthosting.co.za>
Message-ID: <1528012033.52.0.584625200856.issue30516@psf.upfronthosting.co.za>


Change by Farhaan Bukhsh <farhaan.bukhsh at gmail.com>:


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

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

From report at bugs.python.org  Sun Jun  3 08:39:02 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 03 Jun 2018 12:39:02 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1528029542.1.0.592728768989.issue17045@psf.upfronthosting.co.za>


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

Do you mind to create a PR Eric?

----------
nosy: +serhiy.storchaka
versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.3, Python 3.4

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

From mi_thom at hotmail.com  Fri Jun  1 21:43:00 2018
From: mi_thom at hotmail.com (Thomas Michiels)
Date: Sat, 2 Jun 2018 01:43:00 +0000
Subject: [docs] sqlite3 issue/bug
Message-ID: <AM0PR02MB3700624370D8B5793951D2918A610@AM0PR02MB3700.eurprd02.prod.outlook.com>

Dear python developpers,

First of all, I wanna say thanks for the awesome language about which i am still learning new stuff each day.
Secondly, i wanne report a bug, I hope this is right adress. It is a bug in the sqlite3 package (using the 2.7.13 version).
Normally a timestamp (using the datetime converter/adapter*) is saved like:
2018-06-02 01:28:56.4610000+00:00
Now in the very rare case the save happens exactly at a round second, it will be saved like this:
2018-06-02 01:28:56+00:00
Without any miliseconds. The adapter/converter for reading in the values will give an error on this on line 71 of the dbapi2.py file
ValueError: invalid literal for int() with base 10: '56+00'

The chances of this error happening are very small, but with very frequent timestamp updates, that chance becomes bigger.
I hope you can confirm this

*connection made with option: detect_types=sqlite3.PARSE_DECLTYPES


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

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

From report at bugs.python.org  Mon Jun  4 00:55:42 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 04 Jun 2018 04:55:42 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528088142.11.0.592728768989.issue33766@psf.upfronthosting.co.za>


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

Good point Ammar.

Seems there is also a missing corner case in the definition of a physical line:

https://docs.python.org/3.8/reference/lexical_analysis.html#physical-lines
"""
A physical line is a sequence of characters terminated by an end-of-line sequence. In source files, any of the standard platform line termination sequences can be used - the Unix form using ASCII LF (linefeed), the Windows form using the ASCII sequence CR LF (return followed by linefeed), or the old Macintosh form using the ASCII CR (return) character. All of these forms can be used equally, regardless of platform.
"""

It misses a case when a physical line is terminated by the end of file.

----------
assignee:  -> docs at python
components: +Documentation -Interpreter Core
nosy: +docs at python, gvanrossum
versions: +Python 2.7 -Python 3.5

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

From report at bugs.python.org  Mon Jun  4 01:01:35 2018
From: report at bugs.python.org (Ammar Askar)
Date: Mon, 04 Jun 2018 05:01:35 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528088495.41.0.592728768989.issue33766@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Relevant bit of the parser that emits a fake newline at the end of the file if not present: https://github.com/python/cpython/blob/master/Parser/tokenizer.c#L1059-L1069

----------

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

From report at bugs.python.org  Mon Jun  4 01:29:33 2018
From: report at bugs.python.org (Isaac Elliott)
Date: Mon, 04 Jun 2018 05:29:33 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528090173.32.0.592728768989.issue33766@psf.upfronthosting.co.za>


Isaac Elliott <isaace71295 at gmail.com> added the comment:

Cool, thanks for the help. Should I submit a PR with the updated documentation?

----------

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

From report at bugs.python.org  Mon Jun  4 01:30:37 2018
From: report at bugs.python.org (Ammar Askar)
Date: Mon, 04 Jun 2018 05:30:37 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528090237.3.0.584625200856.issue33766@psf.upfronthosting.co.za>


Change by Ammar Askar <ammar at ammaraskar.com>:


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

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

From report at bugs.python.org  Mon Jun  4 01:37:06 2018
From: report at bugs.python.org (Ammar Askar)
Date: Mon, 04 Jun 2018 05:37:06 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528090626.68.0.592728768989.issue33766@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Sorry, I was already working on the patch by the time you posted the comment. If we see above, it seems like the tokenize module doesn't correctly mirror the behavior of the C tokenizer. Do you want to try fixing that as a bug? That would involve making a new bpo ticket and submitting a PR there.

----------

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

From report at bugs.python.org  Mon Jun  4 03:29:04 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 04 Jun 2018 07:29:04 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528097344.68.0.592728768989.issue33640@psf.upfronthosting.co.za>


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


New changeset b75ec0856771b51684b08c4e5068fbfad25c5e83 by Victor Stinner (Farhaan Bukhsh) in branch 'master':
bpo-33640, uuid.UUID doc: document endian of bytes parameter (GH-7263)
https://github.com/python/cpython/commit/b75ec0856771b51684b08c4e5068fbfad25c5e83


----------

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

From report at bugs.python.org  Mon Jun  4 03:30:21 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 07:30:21 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528097421.34.0.584625200856.issue33640@psf.upfronthosting.co.za>


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


----------
pull_requests: +7012

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

From report at bugs.python.org  Mon Jun  4 03:31:20 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 07:31:20 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528097480.2.0.584625200856.issue33640@psf.upfronthosting.co.za>


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


----------
pull_requests: +7013

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

From report at bugs.python.org  Mon Jun  4 03:32:26 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 07:32:26 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528097546.28.0.584625200856.issue33640@psf.upfronthosting.co.za>


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


----------
pull_requests: +7014

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

From report at bugs.python.org  Mon Jun  4 06:07:26 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 04 Jun 2018 10:07:26 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528106846.32.0.592728768989.issue27902@psf.upfronthosting.co.za>


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


New changeset f7745e1dcb8e8473cc86112a0213b3f244a07230 by INADA Naoki (Tobias Kunze) in branch 'master':
bpo-27902: Add compatibility note to Profile docs (GH-7295)
https://github.com/python/cpython/commit/f7745e1dcb8e8473cc86112a0213b3f244a07230


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

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

From report at bugs.python.org  Mon Jun  4 06:08:28 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 10:08:28 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528106908.07.0.584625200856.issue27902@psf.upfronthosting.co.za>


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


----------
pull_requests: +7016

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

From report at bugs.python.org  Mon Jun  4 06:09:27 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 10:09:27 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528106967.67.0.584625200856.issue27902@psf.upfronthosting.co.za>


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


----------
pull_requests: +7017

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

From report at bugs.python.org  Mon Jun  4 06:10:26 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 10:10:26 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528107026.7.0.584625200856.issue27902@psf.upfronthosting.co.za>


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


----------
pull_requests: +7018

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

From report at bugs.python.org  Mon Jun  4 11:12:42 2018
From: report at bugs.python.org (Eric Snow)
Date: Mon, 04 Jun 2018 15:12:42 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1528125162.3.0.592728768989.issue17045@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

I'll definitely take a look.  It might not be until Friday though.

----------

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

From report at bugs.python.org  Mon Jun  4 12:18:03 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 04 Jun 2018 16:18:03 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528129083.5.0.592728768989.issue33766@psf.upfronthosting.co.za>


Guido van Rossum <guido at python.org> added the comment:

I am fine with adding this to the docs. But the irony of the case is that the echo command adds a newline, so the original premise (that test.py contains an invalid program) is incorrect. ;-)

----------

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

From report at bugs.python.org  Mon Jun  4 13:17:31 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 17:17:31 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528132651.52.0.592728768989.issue33640@psf.upfronthosting.co.za>


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


New changeset 1cdd0e71ecba53ab60080958c24193c27c3adee2 by Miss Islington (bot) in branch '3.7':
bpo-33640, uuid.UUID doc: document endian of bytes parameter (GH-7263)
https://github.com/python/cpython/commit/1cdd0e71ecba53ab60080958c24193c27c3adee2


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

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

From report at bugs.python.org  Mon Jun  4 13:18:25 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 17:18:25 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528132705.71.0.592728768989.issue33640@psf.upfronthosting.co.za>


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


New changeset 6a43d5f4fb3a83815bf7c2f157773a3b0d8f59b3 by Miss Islington (bot) in branch '3.6':
bpo-33640, uuid.UUID doc: document endian of bytes parameter (GH-7263)
https://github.com/python/cpython/commit/6a43d5f4fb3a83815bf7c2f157773a3b0d8f59b3


----------

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

From report at bugs.python.org  Mon Jun  4 13:24:40 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 17:24:40 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528133080.47.0.592728768989.issue33640@psf.upfronthosting.co.za>


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


New changeset 5f0726a3813dd9873e10690e708f8da9ede9502e by Miss Islington (bot) in branch '2.7':
bpo-33640, uuid.UUID doc: document endian of bytes parameter (GH-7263)
https://github.com/python/cpython/commit/5f0726a3813dd9873e10690e708f8da9ede9502e


----------

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

From report at bugs.python.org  Mon Jun  4 13:25:39 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 17:25:39 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528133139.77.0.592728768989.issue27902@psf.upfronthosting.co.za>


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


New changeset 7548a9327409df787eef5f8c2780b53b5788012f by Miss Islington (bot) in branch '3.7':
bpo-27902: Add compatibility note to Profile docs (GH-7295)
https://github.com/python/cpython/commit/7548a9327409df787eef5f8c2780b53b5788012f


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

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

From report at bugs.python.org  Mon Jun  4 13:29:57 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 17:29:57 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528133397.52.0.592728768989.issue27902@psf.upfronthosting.co.za>


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


New changeset 134bb46db706416d76d03c0af6018372f35be06f by Miss Islington (bot) in branch '2.7':
bpo-27902: Add compatibility note to Profile docs (GH-7295)
https://github.com/python/cpython/commit/134bb46db706416d76d03c0af6018372f35be06f


----------

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

From report at bugs.python.org  Mon Jun  4 13:30:37 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 17:30:37 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528133436.98.0.592728768989.issue27902@psf.upfronthosting.co.za>


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


New changeset 889a1ef6833d47cc732c291852602b5fc8d5fde7 by Miss Islington (bot) in branch '3.6':
bpo-27902: Add compatibility note to Profile docs (GH-7295)
https://github.com/python/cpython/commit/889a1ef6833d47cc732c291852602b5fc8d5fde7


----------

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

From report at bugs.python.org  Mon Jun  4 16:43:33 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 04 Jun 2018 20:43:33 +0000
Subject: [docs] [issue33640] [EASY DOC] uuid: endian of the bytes argument
 is not documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1528145013.43.0.592728768989.issue33640@psf.upfronthosting.co.za>


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

Thank you Farhaan Bukhsh for your documentation enhancement! I applied your change to 2.7, 3.6, 3.7 and master branches.

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

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

From report at bugs.python.org  Mon Jun  4 17:42:47 2018
From: report at bugs.python.org (Julien Palard)
Date: Mon, 04 Jun 2018 21:42:47 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1528148567.02.0.592728768989.issue32523@psf.upfronthosting.co.za>


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

It's from docutils (see details below), it can be fixed in pydoctheme.css by adding something like:


li p {
    margin-bottom: 0;
}

Would look like: https://mdk.fr/list-before.png ? https://mdk.fr/list-after.png is it better? (If it's better I still have to ensure this rule won't break something else in another place.)


For more information I quote here the docstring of `class HTMLTranslator`:

The html4css1 writer has been optimized to produce visually compact
lists (less vertical whitespace).  HTML's mixed content models
allow list items to contain "<li><p>body elements</p></li>" or
"<li>just text</li>" or even "<li>text<p>and body
elements</p>combined</li>", each with different effects.  It would
be best to stick with strict body elements in list items, but they
affect vertical spacing in older browsers (although they really
shouldn't).
The html5_polyglot writer solves this using CSS2.

Here is an outline of the optimization:

- Check for and omit <p> tags in "simple" lists: list items
  contain either a single paragraph, a nested simple list, or a
  paragraph followed by a nested simple list.  This means that
  this list can be compact:

      - Item 1.
      - Item 2.

  But this list cannot be compact:

      - Item 1.

        This second paragraph forces space between list items.

      - Item 2.

- In non-list contexts, omit <p> tags on a paragraph if that
  paragraph is the only child of its parent (footnotes & citations
  are allowed a label first).

- Regardless of the above, in definitions, table cells, field bodies,
  option descriptions, and list items, mark the first child with
  'class="first"' and the last child with 'class="last"'.  The stylesheet
  sets the margins (top & bottom respectively) to 0 for these elements.

----------

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

From report at bugs.python.org  Mon Jun  4 17:53:43 2018
From: report at bugs.python.org (Julien Palard)
Date: Mon, 04 Jun 2018 21:53:43 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1528149223.23.0.592728768989.issue32523@psf.upfronthosting.co.za>


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

An intermediate fix would be to remove only bottom of first paragraphs:

li p.first {
    margin-bottom: 0;
}

It looks like: https://mdk.fr/list-intermediate.png

----------

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

From report at bugs.python.org  Mon Jun  4 17:55:55 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 04 Jun 2018 21:55:55 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1528149355.37.0.592728768989.issue32523@psf.upfronthosting.co.za>


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

Thank you for looking into it!  In the example you chose, I think the first step would be to trim the two two-paragraph news items to be only one paragraph each; in general, news items should only be a few sentences at most.  With that change, I think the choice is pretty clear (to me, at least:): I prefer without the blank lines.  And the issue is that today the changelogs have a "random" mixture of both.  So, if news items followed that rule, would the css change still be necessary?

----------

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

From report at bugs.python.org  Mon Jun  4 18:09:33 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 04 Jun 2018 22:09:33 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528150173.38.0.592728768989.issue33609@psf.upfronthosting.co.za>


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


New changeset f822549653d8d09bffff5b7dcddfdf12679a787c by Ned Deily (INADA Naoki) in branch 'master':
bpo-33609: Document dict insertion order guarantee as of 3.7 (GH-7093)
https://github.com/python/cpython/commit/f822549653d8d09bffff5b7dcddfdf12679a787c


----------

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

From report at bugs.python.org  Mon Jun  4 18:09:40 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 22:09:40 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528150180.93.0.584625200856.issue33609@psf.upfronthosting.co.za>


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


----------
pull_requests: +7033

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

From report at bugs.python.org  Mon Jun  4 18:25:14 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 04 Jun 2018 22:25:14 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528151114.75.0.592728768989.issue33609@psf.upfronthosting.co.za>


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


New changeset 8585ec9b761947aae6be5f653a5b9ddef2801d58 by Miss Islington (bot) in branch '3.7':
bpo-33609: Document dict insertion order guarantee as of 3.7 (GH-7093)
https://github.com/python/cpython/commit/8585ec9b761947aae6be5f653a5b9ddef2801d58


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

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

From report at bugs.python.org  Mon Jun  4 18:27:42 2018
From: report at bugs.python.org (Neil Schemenauer)
Date: Mon, 04 Jun 2018 22:27:42 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528151262.56.0.592728768989.issue33609@psf.upfronthosting.co.za>


Neil Schemenauer <nas-python at arctrix.com> added the comment:

The wording sounds strange to me.  Currently it is:
> Note that updating key doesn't affects the order ...

I would say:
> Note that updating a key does not affect the order ...

----------
nosy: +nascheme

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

From report at bugs.python.org  Mon Jun  4 18:30:54 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 04 Jun 2018 22:30:54 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528151454.81.0.592728768989.issue33609@psf.upfronthosting.co.za>


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

Neil, that looks like a perfect opportunity to use the GitHub web interface to make that edit :)

----------

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

From report at bugs.python.org  Mon Jun  4 20:54:10 2018
From: report at bugs.python.org (Eric Snow)
Date: Tue, 05 Jun 2018 00:54:10 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1528160050.31.0.584625200856.issue17045@psf.upfronthosting.co.za>


Change by Eric Snow <ericsnowcurrently at gmail.com>:


----------
pull_requests: +7038

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

From report at bugs.python.org  Mon Jun  4 20:55:13 2018
From: report at bugs.python.org (Eric Snow)
Date: Tue, 05 Jun 2018 00:55:13 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1528160113.31.0.592728768989.issue17045@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

I found some time to at least get the patch to apply cleanly to master and to make a PR. :)

----------

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

From report at bugs.python.org  Tue Jun  5 01:09:48 2018
From: report at bugs.python.org (Julien Palard)
Date: Tue, 05 Jun 2018 05:09:48 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1528175388.28.0.592728768989.issue32523@psf.upfronthosting.co.za>


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

> So, if news items followed that rule, would the css change still be necessary?

The CSS change would not be necessary, so yes the issue is "Don't mix paragraphs in changelogs".

Maybe we can add an option to blurb merge to only keep the first paragraph, to fix every list in a single shot, then better document the "a single paragraph per news entry"?

Would it be OK to edit old Misc/NEWS.d/ to fix it in the past?

----------

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

From report at bugs.python.org  Tue Jun  5 02:55:04 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 05 Jun 2018 06:55:04 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1528181704.77.0.584625200856.issue27902@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jun  5 04:33:47 2018
From: report at bugs.python.org (Svyatoslav)
Date: Tue, 05 Jun 2018 08:33:47 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
Message-ID: <1528187627.25.0.584625200856.issue33771@psf.upfronthosting.co.za>


Change by Svyatoslav <ab7eb487 at gmail.com>:


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

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

From report at bugs.python.org  Tue Jun  5 04:46:10 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 05 Jun 2018 08:46:10 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
Message-ID: <1528188370.15.0.584625200856.issue33771@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jun  5 07:41:44 2018
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 05 Jun 2018 11:41:44 +0000
Subject: [docs] [issue32392] subprocess.run documentation does not have
 **kwargs
In-Reply-To: <1513802831.78.0.213398074469.issue32392@psf.upfronthosting.co.za>
Message-ID: <1528198904.54.0.592728768989.issue32392@psf.upfronthosting.co.za>


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


New changeset af1ec97a6d1dde68b2dc0ee9b78965eb219061a8 by Berker Peksag (Tobias Kunze) in branch 'master':
bpo-32392: Document env keyword argument of subprocess.run() (GH-7289)
https://github.com/python/cpython/commit/af1ec97a6d1dde68b2dc0ee9b78965eb219061a8


----------

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

From report at bugs.python.org  Tue Jun  5 07:43:02 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 05 Jun 2018 11:43:02 +0000
Subject: [docs] [issue32392] subprocess.run documentation does not have
 **kwargs
In-Reply-To: <1513802831.78.0.213398074469.issue32392@psf.upfronthosting.co.za>
Message-ID: <1528198982.5.0.584625200856.issue32392@psf.upfronthosting.co.za>


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


----------
pull_requests: +7048

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

From report at bugs.python.org  Tue Jun  5 08:03:04 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 05 Jun 2018 12:03:04 +0000
Subject: [docs] [issue32392] subprocess.run documentation does not have
 **kwargs
In-Reply-To: <1513802831.78.0.213398074469.issue32392@psf.upfronthosting.co.za>
Message-ID: <1528200184.81.0.592728768989.issue32392@psf.upfronthosting.co.za>


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


New changeset 23b7ee205270320f836e93e411b28ac995cbabf1 by Miss Islington (bot) in branch '3.7':
bpo-32392: Document env keyword argument of subprocess.run() (GH-7289)
https://github.com/python/cpython/commit/23b7ee205270320f836e93e411b28ac995cbabf1


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

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

From report at bugs.python.org  Tue Jun  5 08:13:48 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 05 Jun 2018 12:13:48 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1528200828.08.0.592728768989.issue17045@psf.upfronthosting.co.za>


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

This isn't directly related to this change, but I wanted to point out #23869 since you seem to understand the topic enough to respond to that ticket.

Thanks!

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Tue Jun  5 08:37:22 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 05 Jun 2018 12:37:22 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
Message-ID: <1528202242.78.0.592728768989.issue33771@psf.upfronthosting.co.za>


New submission from Cheryl Sabella <cheryl.sabella at gmail.com>:

Looks like this was changed in #28240.

@svyatoslav, would you like to make a github pull request for the change?

----------
keywords: +easy
nosy: +cheryl.sabella
stage:  -> needs patch

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

From report at bugs.python.org  Tue Jun  5 08:43:06 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 05 Jun 2018 12:43:06 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
In-Reply-To: <1528202242.78.0.592728768989.issue33771@psf.upfronthosting.co.za>
Message-ID: <1528202586.92.0.592728768989.issue33771@psf.upfronthosting.co.za>


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

I created https://github.com/python/cpython/pull/7419 to update the documentation.

----------

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

From report at bugs.python.org  Tue Jun  5 08:56:01 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 05 Jun 2018 12:56:01 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
In-Reply-To: <1528202242.78.0.592728768989.issue33771@psf.upfronthosting.co.za>
Message-ID: <1528203361.75.0.592728768989.issue33771@psf.upfronthosting.co.za>


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

Thanks, Victor.  Sorry about the noise.

----------

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

From report at bugs.python.org  Tue Jun  5 09:58:35 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 05 Jun 2018 13:58:35 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
In-Reply-To: <1528202242.78.0.592728768989.issue33771@psf.upfronthosting.co.za>
Message-ID: <1528207114.97.0.592728768989.issue33771@psf.upfronthosting.co.za>


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

> Thanks, Victor.  Sorry about the noise.

No worry, it's my fault: I forgot to mention bpo-33771 in my PR.

----------

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

From report at bugs.python.org  Tue Jun  5 10:14:47 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 05 Jun 2018 14:14:47 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528208087.22.0.592728768989.issue31215@psf.upfronthosting.co.za>


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


New changeset 9ef1b0690b90c526798b6b3125b0fa7ae98319a2 by Nick Coghlan (Mayank Singhal) in branch 'master':
bpo-31215: Add version changed notes for OpenSSL 1.1.0 compatibility (GH-7346)
https://github.com/python/cpython/commit/9ef1b0690b90c526798b6b3125b0fa7ae98319a2


----------

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

From report at bugs.python.org  Tue Jun  5 12:58:55 2018
From: report at bugs.python.org (Al-Scandar Solstag)
Date: Tue, 05 Jun 2018 16:58:55 +0000
Subject: [docs] [issue33774] Improve doc of @lru_cache to avoid misuse and
 confusion
Message-ID: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>


New submission from Al-Scandar Solstag <solstag at member.fsf.org>:

Ni!

It is not clear at all in the documentation of @lru_cache that the cache takes into account the exact way the function was called, not the values passed to its arguments, as one could/would expect.

I mean that for function(a, b, c=3) the three calls below are not considered equivalent as far as the cache is concerned:

function(1, 2, 3)
function(1, 2, c=3)
function(1, 2)

I hope this can be clarified in the documentation. I wasted a great deal of time today trying to understand why my calls were not getting cached and only figured it out when I decided to go read @lru_cache's code.

It seems very likely that other people have had the same problem. Or worse, people might be using @lru_cache believing it is working when it isn't.

Cheers!

----------
assignee: docs at python
components: Documentation
messages: 318770
nosy: docs at python, solstag
priority: normal
severity: normal
status: open
title: Improve doc of @lru_cache to avoid misuse and confusion

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

From report at bugs.python.org  Tue Jun  5 13:25:16 2018
From: report at bugs.python.org (R. David Murray)
Date: Tue, 05 Jun 2018 17:25:16 +0000
Subject: [docs] [issue33774] Document that @lru_cache caches based on
 exactly how the function arguments are specified
In-Reply-To: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>
Message-ID: <1528219516.11.0.592728768989.issue33774@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

Agreed that this should be documented.

----------
nosy: +r.david.murray, rhettinger
stage:  -> needs patch
title: Improve doc of @lru_cache to avoid misuse and confusion -> Document that @lru_cache caches based on exactly how the function arguments are specified
versions: +Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Jun  5 14:28:22 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Tue, 05 Jun 2018 18:28:22 +0000
Subject: [docs] [issue33477] Document that compile(code,
 'exec') has different behavior in 3.7+
In-Reply-To: <1526173050.51.0.682650639539.issue33477@psf.upfronthosting.co.za>
Message-ID: <1528223302.65.0.592728768989.issue33477@psf.upfronthosting.co.za>


Matthias Bussonnier <bussonniermatthias at gmail.com> added the comment:

Closing as the ast changes have been reverted.

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

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

From report at bugs.python.org  Tue Jun  5 16:14:49 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 05 Jun 2018 20:14:49 +0000
Subject: [docs] [issue33600] [EASY DOC] Python 2: document that
 platform.linux_distribution() has been removed
In-Reply-To: <1526994321.44.0.682650639539.issue33600@psf.upfronthosting.co.za>
Message-ID: <1528229689.24.0.592728768989.issue33600@psf.upfronthosting.co.za>


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


New changeset 7b9b87e76c44660de8a973c0e0a118f539532496 by Victor Stinner (Timo Furrer) in branch '2.7':
bpo-33600: document that platform.linux_distribution() has been removed (GH-7281)
https://github.com/python/cpython/commit/7b9b87e76c44660de8a973c0e0a118f539532496


----------

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

From report at bugs.python.org  Tue Jun  5 17:55:22 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 05 Jun 2018 21:55:22 +0000
Subject: [docs] [issue33600] [EASY DOC] Python 2: document that
 platform.linux_distribution() has been removed
In-Reply-To: <1526994321.44.0.682650639539.issue33600@psf.upfronthosting.co.za>
Message-ID: <1528235722.94.0.584625200856.issue33600@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jun  5 21:07:13 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 06 Jun 2018 01:07:13 +0000
Subject: [docs] [issue33774] Document that @lru_cache caches based on
 exactly how the function arguments are specified
In-Reply-To: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>
Message-ID: <1528247233.24.0.592728768989.issue33774@psf.upfronthosting.co.za>


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

Sure, I can add a line mentioning that distinct argument patterns may be considered as distinct cache entries even though they otherwise seem to be equivalent calls.  That will just be a general statement though. 
The specific details are implementation dependent, have changed over time, and may change again in the future.

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

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

From report at bugs.python.org  Wed Jun  6 09:48:39 2018
From: report at bugs.python.org (Al-Scandar Solstag)
Date: Wed, 06 Jun 2018 13:48:39 +0000
Subject: [docs] [issue33774] Document that @lru_cache caches based on
 exactly how the function arguments are specified
In-Reply-To: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>
Message-ID: <1528292919.17.0.592728768989.issue33774@psf.upfronthosting.co.za>


Al-Scandar Solstag <solstag at member.fsf.org> added the comment:

Hi Raymond, I think I understand what you mean, and would suggest something along the lines of:

"""
Note that lru_cache only guarantees cache matches on the exact way function arguments are specified, so the following ways of calling 'def f(a, b=7)' are not guaranteed to cache each other: f(1), f(a=1), f(1, 7), f(1, b=7), f(a=1, b=7).
"""

----------

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

From report at bugs.python.org  Thu Jun  7 01:04:07 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 07 Jun 2018 05:04:07 +0000
Subject: [docs] [issue21196] Name mangling example in Python tutorial
In-Reply-To: <1397133080.37.0.870141660622.issue21196@psf.upfronthosting.co.za>
Message-ID: <1528347846.79.0.592728768989.issue21196@psf.upfronthosting.co.za>


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

What should we do with this issue?  Raymond, it sounds like you think the proposed PR should not be merged, is that right?  If so, should the issue and PR be closed?  Other opinions?  I would like to resolve this so we can either merge or close PR 5667.  Thanks!

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

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

From report at bugs.python.org  Thu Jun  7 01:17:27 2018
From: report at bugs.python.org (Tim Peters)
Date: Thu, 07 Jun 2018 05:17:27 +0000
Subject: [docs] [issue21196] Name mangling example in Python tutorial
In-Reply-To: <1397133080.37.0.870141660622.issue21196@psf.upfronthosting.co.za>
Message-ID: <1528348647.82.0.592728768989.issue21196@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

Berker Peksag's change (PR 5667) is very simple and, I think, helpful.

----------
nosy: +tim.peters

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

From agarwalamit272 at gmail.com  Tue Jun  5 03:28:39 2018
From: agarwalamit272 at gmail.com (AMIT AGARWAL)
Date: Tue, 5 Jun 2018 12:58:39 +0530
Subject: [docs] Unable to access the release notes for version 2.7.15
Message-ID: <CAGkhirJYtLK7f7hvpEa=__A2GPr7GKWp7kGc8+Riy6gVxdtyaA@mail.gmail.com>

Hello ,

I am not able to see/download  the release notes for version 2.7.15

Kindly help.

Regards,
Amit Agarwal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180605/ecc23d12/attachment.html>

From staringthestar at gmail.com  Wed Jun  6 03:25:21 2018
From: staringthestar at gmail.com (Staring the Star)
Date: Wed, 6 Jun 2018 16:25:21 +0900
Subject: [docs] About Document Download-Other Languages
Message-ID: <CAFxA6Jjj85cdULuezx19XJ-u4pHCGX7jAtDNN+wHR6qhVJd9mQ@mail.gmail.com>

Dear Python Team

Hello, I'm one of the newbies who has just started (actually, few days ago)
Python.
However, while I tried to download the online document file of Python
3.6.5, I found out that the downloading page only supported English
document download.
Although I CAN read English, it would be a great help if the "download"
supports other languages(French, Japanese, Korean).
Also, could I know who translate this document? My friend, who started
Python with me, is Korean, and he always wants to look at full-translated
document. He even said that rather he could translate the documents than
waiting all day XD

Sorry for my bad English... :(

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

From report at bugs.python.org  Thu Jun  7 12:14:52 2018
From: report at bugs.python.org (Neil Schemenauer)
Date: Thu, 07 Jun 2018 16:14:52 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528388092.07.0.584625200856.issue33609@psf.upfronthosting.co.za>


Change by Neil Schemenauer <nas-python at arctrix.com>:


----------
pull_requests: +7110

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

From report at bugs.python.org  Thu Jun  7 15:01:05 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 07 Jun 2018 19:01:05 +0000
Subject: [docs] [issue32392] subprocess.run documentation does not have
 **kwargs
In-Reply-To: <1513802831.78.0.213398074469.issue32392@psf.upfronthosting.co.za>
Message-ID: <1528398065.23.0.584625200856.issue32392@psf.upfronthosting.co.za>


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


----------
pull_requests: +7114

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

From report at bugs.python.org  Thu Jun  7 15:12:49 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 19:12:49 +0000
Subject: [docs] [issue33798] Fix csv module comment regarding dict insertion
 order
Message-ID: <1528398769.16.0.592728768989.issue33798@psf.upfronthosting.co.za>


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

The csv module says "Python?s dict objects are not ordered". PR fixes this , leaving a comment on the rationale.

----------
assignee: docs at python
components: Documentation
messages: 318961
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Fix csv module comment regarding dict insertion order
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun  7 15:13:10 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 19:13:10 +0000
Subject: [docs] [issue33798] Fix csv module comment regarding dict insertion
 order
In-Reply-To: <1528398769.16.0.592728768989.issue33798@psf.upfronthosting.co.za>
Message-ID: <1528398790.54.0.584625200856.issue33798@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun  7 15:13:50 2018
From: report at bugs.python.org (Jay Crotts)
Date: Thu, 07 Jun 2018 19:13:50 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1528398830.9.0.584625200856.issue33722@psf.upfronthosting.co.za>


Change by Jay Crotts <crotts.jay at gmail.com>:


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

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

From report at bugs.python.org  Thu Jun  7 15:22:37 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 07 Jun 2018 19:22:37 +0000
Subject: [docs] [issue32392] subprocess.run documentation does not have
 **kwargs
In-Reply-To: <1513802831.78.0.213398074469.issue32392@psf.upfronthosting.co.za>
Message-ID: <1528399357.34.0.592728768989.issue32392@psf.upfronthosting.co.za>


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


New changeset 279564431e8e2fa4c20e8850420caea484a5d20b by Berker Peksag in branch '3.6':
[3.6] bpo-32392: Document env keyword argument of subprocess.run() (GH-7289)
https://github.com/python/cpython/commit/279564431e8e2fa4c20e8850420caea484a5d20b


----------

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

From report at bugs.python.org  Thu Jun  7 15:23:19 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 07 Jun 2018 19:23:19 +0000
Subject: [docs] [issue32392] subprocess.run documentation does not have
 **kwargs
In-Reply-To: <1513802831.78.0.213398074469.issue32392@psf.upfronthosting.co.za>
Message-ID: <1528399399.83.0.592728768989.issue32392@psf.upfronthosting.co.za>


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

Thanks!

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

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

From report at bugs.python.org  Thu Jun  7 15:28:00 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 19:28:00 +0000
Subject: [docs] [issue33799] Remove non-ordered dicts comments from FAQ
Message-ID: <1528399680.16.0.592728768989.issue33799@psf.upfronthosting.co.za>


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

Both Design and Programming sections have comments related to the non-ordered dict implementation. PR removes those comments.

----------
assignee: docs at python
components: Documentation
messages: 318964
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Remove non-ordered dicts comments from FAQ
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun  7 15:28:16 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 19:28:16 +0000
Subject: [docs] [issue33799] Remove non-ordered dicts comments from FAQ
In-Reply-To: <1528399680.16.0.592728768989.issue33799@psf.upfronthosting.co.za>
Message-ID: <1528399696.96.0.584625200856.issue33799@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun  7 16:01:29 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 20:01:29 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
Message-ID: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>


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

Default argument of parameter dict_type of ConfigParser/RawConfigParser is shown as "collections.OrderedDict", while it recently migrated to "dict".

PR fixes this, documents the change to dict, and fixes a versionchanged changed directive in "items" with wrong indentation.

----------
assignee: docs at python
components: Documentation
messages: 318968
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Fix default argument for parameter dict_type of ConfigParser/RawConfigParser
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu Jun  7 16:01:46 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 20:01:46 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1528401706.09.0.584625200856.issue33800@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun  7 16:12:56 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 20:12:56 +0000
Subject: [docs] [issue33801] Remove non-ordered dict comment from plistlib
Message-ID: <1528402376.25.0.592728768989.issue33801@psf.upfronthosting.co.za>


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

plistlib documentation says:

"The exact structure of the plist can be recovered by using collections.OrderedDict (although the order of keys shouldn't be important in plist files)"

This is no longer necessary, since dict objects preserve insertion order. PR changes this.

----------
assignee: docs at python
components: Documentation
messages: 318969
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Remove non-ordered dict comment from plistlib
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun  7 16:13:50 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 07 Jun 2018 20:13:50 +0000
Subject: [docs] [issue33801] Remove non-ordered dict comment from plistlib
In-Reply-To: <1528402376.25.0.592728768989.issue33801@psf.upfronthosting.co.za>
Message-ID: <1528402430.8.0.584625200856.issue33801@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun  7 17:46:14 2018
From: report at bugs.python.org (Neil Schemenauer)
Date: Thu, 07 Jun 2018 21:46:14 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528407974.22.0.592728768989.issue33609@psf.upfronthosting.co.za>


Neil Schemenauer <nas-python at arctrix.com> added the comment:


New changeset d3ed67d14ed401dfe2b5d07b6941adc3ecacb268 by Neil Schemenauer in branch 'master':
bpo-33609: small wording fixes to dict ordering docs
https://github.com/python/cpython/commit/d3ed67d14ed401dfe2b5d07b6941adc3ecacb268


----------

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

From report at bugs.python.org  Thu Jun  7 17:47:23 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 07 Jun 2018 21:47:23 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528408043.12.0.584625200856.issue33609@psf.upfronthosting.co.za>


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


----------
pull_requests: +7122

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

From report at bugs.python.org  Thu Jun  7 20:38:25 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 08 Jun 2018 00:38:25 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1528418305.29.0.592728768989.issue33609@psf.upfronthosting.co.za>


Yury Selivanov <yselivanov at gmail.com> added the comment:


New changeset 9b0d4d04a15a97a1055f1b729f14e9257f149fd3 by Yury Selivanov (Miss Islington (bot)) in branch '3.7':
bpo-33609: small wording fixes to dict ordering docs (#7497)
https://github.com/python/cpython/commit/9b0d4d04a15a97a1055f1b729f14e9257f149fd3


----------

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

From report at bugs.python.org  Thu Jun  7 20:51:37 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 08 Jun 2018 00:51:37 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
Message-ID: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>


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

Documentation of io.TextIOBase.read makes it look like the size parameter is required. Attached PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 319003
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Document the default value of the size parameter of io.TextIOBase.read
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun  7 20:51:59 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 08 Jun 2018 00:51:59 +0000
Subject: [docs] [issue33804] Document the default value of the size
 parameter of io.TextIOBase.read
In-Reply-To: <1528419097.71.0.592728768989.issue33804@psf.upfronthosting.co.za>
Message-ID: <1528419119.48.0.584625200856.issue33804@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun  8 02:38:09 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 08 Jun 2018 06:38:09 +0000
Subject: [docs] [issue33799] Remove non-ordered dicts comments from FAQ
In-Reply-To: <1528399680.16.0.592728768989.issue33799@psf.upfronthosting.co.za>
Message-ID: <1528439889.89.0.592728768989.issue33799@psf.upfronthosting.co.za>


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


New changeset 396ecb9c3e7fb150eace7bfc733d5b9d0263d697 by INADA Naoki (Andr?s Delfino) in branch 'master':
bpo-33799: Remove non-ordered dicts comments from FAQ
https://github.com/python/cpython/commit/396ecb9c3e7fb150eace7bfc733d5b9d0263d697


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

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

From report at bugs.python.org  Fri Jun  8 02:39:16 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 06:39:16 +0000
Subject: [docs] [issue33799] Remove non-ordered dicts comments from FAQ
In-Reply-To: <1528399680.16.0.592728768989.issue33799@psf.upfronthosting.co.za>
Message-ID: <1528439956.23.0.584625200856.issue33799@psf.upfronthosting.co.za>


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


----------
pull_requests: +7148

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

From report at bugs.python.org  Fri Jun  8 06:02:12 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 10:02:12 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528452132.55.0.584625200856.issue31215@psf.upfronthosting.co.za>


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


----------
pull_requests: +7154

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

From report at bugs.python.org  Fri Jun  8 06:03:09 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 10:03:09 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528452189.22.0.584625200856.issue31215@psf.upfronthosting.co.za>


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


----------
pull_requests: +7155

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

From report at bugs.python.org  Fri Jun  8 06:22:41 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 10:22:41 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528453361.32.0.592728768989.issue31215@psf.upfronthosting.co.za>


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


New changeset a0accc0f8e747145a3ee36b91338777bc94b3348 by Miss Islington (bot) in branch '3.6':
bpo-31215: Add version changed notes for OpenSSL 1.1.0 compatibility (GH-7346)
https://github.com/python/cpython/commit/a0accc0f8e747145a3ee36b91338777bc94b3348


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

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

From report at bugs.python.org  Fri Jun  8 06:22:43 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 10:22:43 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528453362.95.0.592728768989.issue31215@psf.upfronthosting.co.za>


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


New changeset d16d72f555447fbedacdc01bb14f380afca705ae by Miss Islington (bot) in branch '3.7':
bpo-31215: Add version changed notes for OpenSSL 1.1.0 compatibility (GH-7346)
https://github.com/python/cpython/commit/d16d72f555447fbedacdc01bb14f380afca705ae


----------

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

From report at bugs.python.org  Fri Jun  8 08:50:54 2018
From: report at bugs.python.org (Suriyaa Sundararuban)
Date: Fri, 08 Jun 2018 12:50:54 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
Message-ID: <1528462254.19.0.584625200856.issue33807@psf.upfronthosting.co.za>


Change by Suriyaa Sundararuban <python at suriyaa.tk>:


----------
assignee: docs at python
components: Documentation
nosy: docs at python, suriyaa
priority: normal
severity: normal
status: open
title: CONTRIBUTING.rst: 'Stable buildbots' links with 404 errors
type: behavior

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

From report at bugs.python.org  Fri Jun  8 08:51:15 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 08 Jun 2018 12:51:15 +0000
Subject: [docs] [issue33798] Fix csv module comment regarding dict insertion
 order
In-Reply-To: <1528398769.16.0.592728768989.issue33798@psf.upfronthosting.co.za>
Message-ID: <1528462275.81.0.592728768989.issue33798@psf.upfronthosting.co.za>


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


New changeset 6860629d87d0f6728ff7430453d4900b695adf7b by INADA Naoki (Andr?s Delfino) in branch 'master':
bpo-33798: Update csv document about dict order (GH-7490)
https://github.com/python/cpython/commit/6860629d87d0f6728ff7430453d4900b695adf7b


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

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

From report at bugs.python.org  Fri Jun  8 08:52:23 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 12:52:23 +0000
Subject: [docs] [issue33798] Fix csv module comment regarding dict insertion
 order
In-Reply-To: <1528398769.16.0.592728768989.issue33798@psf.upfronthosting.co.za>
Message-ID: <1528462343.31.0.584625200856.issue33798@psf.upfronthosting.co.za>


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


----------
pull_requests: +7170

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

From report at bugs.python.org  Fri Jun  8 08:52:39 2018
From: report at bugs.python.org (Suriyaa Sundararuban)
Date: Fri, 08 Jun 2018 12:52:39 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
Message-ID: <1528462359.08.0.592728768989.issue33807@psf.upfronthosting.co.za>


New submission from Suriyaa Sundararuban <python at suriyaa.tk>:

I'm working on this issue.

----------

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

From report at bugs.python.org  Fri Jun  8 09:04:46 2018
From: report at bugs.python.org (Suriyaa Sundararuban)
Date: Fri, 08 Jun 2018 13:04:46 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
In-Reply-To: <1528462359.08.0.592728768989.issue33807@psf.upfronthosting.co.za>
Message-ID: <1528463086.34.0.584625200856.issue33807@psf.upfronthosting.co.za>


Change by Suriyaa Sundararuban <python at suriyaa.tk>:


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

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

From report at bugs.python.org  Fri Jun  8 09:33:42 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 13:33:42 +0000
Subject: [docs] [issue33798] Fix csv module comment regarding dict insertion
 order
In-Reply-To: <1528398769.16.0.592728768989.issue33798@psf.upfronthosting.co.za>
Message-ID: <1528464822.74.0.592728768989.issue33798@psf.upfronthosting.co.za>


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


New changeset 9f56a93e8986e06ac61a7356082fe8be285f26a4 by Miss Islington (bot) in branch '3.7':
bpo-33798: Update csv document about dict order (GH-7490)
https://github.com/python/cpython/commit/9f56a93e8986e06ac61a7356082fe8be285f26a4


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

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

From report at bugs.python.org  Fri Jun  8 09:38:04 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 08 Jun 2018 13:38:04 +0000
Subject: [docs] [issue33798] Fix csv module comment regarding dict insertion
 order
In-Reply-To: <1528398769.16.0.592728768989.issue33798@psf.upfronthosting.co.za>
Message-ID: <1528465084.35.0.584625200856.issue33798@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun  8 10:00:56 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 08 Jun 2018 14:00:56 +0000
Subject: [docs] [issue33745] 3.7.0b5 changes the line number of empty
 functions with docstrings
In-Reply-To: <1528024309.59.0.592728768989.issue33745@psf.upfronthosting.co.za>
Message-ID: <1528466456.6.0.592728768989.issue33745@psf.upfronthosting.co.za>


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

The rationale for documenting it in the porting section is that even though this isn't a guaranteed stable interface, the output *does* potentially affect development tools like Ned's coverage.py, as well as other implementations attempting to adhere closely to CPython's behaviour for any given version.

(Although it doesn't usually help *Ned* much, since he's often the one letting us know that we inadvertently changed some details of the code generator's output...)

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

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

From report at bugs.python.org  Fri Jun  8 11:36:04 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 08 Jun 2018 15:36:04 +0000
Subject: [docs] [issue33736] Improve the documentation of asyncio stream API
Message-ID: <1528472164.69.0.592728768989.issue33736@psf.upfronthosting.co.za>


New submission from Yury Selivanov <yselivanov at gmail.com>:


New changeset c0d062f523b16331444ff910e4596ee5608c8170 by Yury Selivanov (Elvis Pranskevichus) in branch 'master':
bpo-33736: Improve the documentation of asyncio stream APIs (GH-7326)
https://github.com/python/cpython/commit/c0d062f523b16331444ff910e4596ee5608c8170


----------
nosy: +yselivanov

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

From report at bugs.python.org  Fri Jun  8 11:37:15 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 15:37:15 +0000
Subject: [docs] [issue33736] Improve the documentation of asyncio stream API
In-Reply-To: <1528472164.69.0.592728768989.issue33736@psf.upfronthosting.co.za>
Message-ID: <1528472235.12.0.584625200856.issue33736@psf.upfronthosting.co.za>


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


----------
pull_requests: +7174

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

From report at bugs.python.org  Fri Jun  8 11:41:02 2018
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 08 Jun 2018 15:41:02 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
In-Reply-To: <1528462359.08.0.592728768989.issue33807@psf.upfronthosting.co.za>
Message-ID: <1528472462.06.0.592728768989.issue33807@psf.upfronthosting.co.za>


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


New changeset 9e6685ea7b749ee34466e71b22d99e5112d71a95 by Zachary Ware (Suriyaa ???) in branch 'master':
bpo-33807: Add Python 3.7 buildbot link to '.github/CONTRIBUTING.rst' (GH-7532)
https://github.com/python/cpython/commit/9e6685ea7b749ee34466e71b22d99e5112d71a95


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

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

From report at bugs.python.org  Fri Jun  8 11:42:06 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 15:42:06 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
In-Reply-To: <1528462359.08.0.592728768989.issue33807@psf.upfronthosting.co.za>
Message-ID: <1528472526.09.0.584625200856.issue33807@psf.upfronthosting.co.za>


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


----------
pull_requests: +7175

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

From report at bugs.python.org  Fri Jun  8 11:42:43 2018
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 08 Jun 2018 15:42:43 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
In-Reply-To: <1528462359.08.0.592728768989.issue33807@psf.upfronthosting.co.za>
Message-ID: <1528472563.63.0.592728768989.issue33807@psf.upfronthosting.co.za>


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

I fixed the issue by reenabling redirects in the buildbot.python.org Apache config, and Suriyaa fixed the lack of a 3.7 link with PR7532.

Thanks for the report and PR!

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

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

From report at bugs.python.org  Fri Jun  8 11:54:34 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 15:54:34 +0000
Subject: [docs] [issue33736] Improve the documentation of asyncio stream API
In-Reply-To: <1528472164.69.0.592728768989.issue33736@psf.upfronthosting.co.za>
Message-ID: <1528473274.33.0.592728768989.issue33736@psf.upfronthosting.co.za>


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


New changeset f4dcf49159e404273f426bccf8d0d71a4c3274e6 by Miss Islington (bot) in branch '3.7':
bpo-33736: Improve the documentation of asyncio stream APIs (GH-7326)
https://github.com/python/cpython/commit/f4dcf49159e404273f426bccf8d0d71a4c3274e6


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

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

From report at bugs.python.org  Fri Jun  8 12:05:09 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 16:05:09 +0000
Subject: [docs] [issue33807] CONTRIBUTING.rst: 'Stable buildbots' links with
 404 errors
In-Reply-To: <1528462359.08.0.592728768989.issue33807@psf.upfronthosting.co.za>
Message-ID: <1528473908.99.0.592728768989.issue33807@psf.upfronthosting.co.za>


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


New changeset 552c1bc94887a5e897c398725776ac1ef3d21c6a by Miss Islington (bot) in branch '3.7':
bpo-33807: Add Python 3.7 buildbot link to '.github/CONTRIBUTING.rst' (GH-7532)
https://github.com/python/cpython/commit/552c1bc94887a5e897c398725776ac1ef3d21c6a


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

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

From report at bugs.python.org  Fri Jun  8 14:30:44 2018
From: report at bugs.python.org (Mayank Singhal)
Date: Fri, 08 Jun 2018 18:30:44 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528482644.98.0.584625200856.issue31215@psf.upfronthosting.co.za>


Change by Mayank Singhal <17mayanksinghal at gmail.com>:


----------
pull_requests: +7176

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

From report at bugs.python.org  Fri Jun  8 14:39:34 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 08 Jun 2018 18:39:34 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528483173.94.0.592728768989.issue33766@psf.upfronthosting.co.za>


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

A few years ago, there was a particular case in which compile failed without a trailing newline.  We fixed it so that it would work anyway.
Unless we are willing for a conforming Python interpreter to fail
>>> exec('print("hello")')
hello

The Reference Manual should be clear that EOF and EOS (end-of-string) is treated as NEWLINE.

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

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

From report at bugs.python.org  Fri Jun  8 14:43:24 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 18:43:24 +0000
Subject: [docs] [issue33799] Remove non-ordered dicts comments from FAQ
In-Reply-To: <1528399680.16.0.592728768989.issue33799@psf.upfronthosting.co.za>
Message-ID: <1528483404.55.0.592728768989.issue33799@psf.upfronthosting.co.za>


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


New changeset 5c7f22c2a339f23f8a236540d0ebed955637095b by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-33799: Remove non-ordered dicts comments from FAQ (GH-7520)
https://github.com/python/cpython/commit/5c7f22c2a339f23f8a236540d0ebed955637095b


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

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

From report at bugs.python.org  Fri Jun  8 14:59:43 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 08 Jun 2018 18:59:43 +0000
Subject: [docs] [issue33771] Module: timeit. According to documentation
 default_repeat should have the value 3. Has 5.
In-Reply-To: <1528202242.78.0.592728768989.issue33771@psf.upfronthosting.co.za>
Message-ID: <1528484383.59.0.592728768989.issue33771@psf.upfronthosting.co.za>


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

This is a duplicate in that the 3 => 5 change was incorporated into PR 7419 for #28240.

----------
nosy: +terry.reedy
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> Enhance the timeit module: display average +- std dev instead of minimum

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

From report at bugs.python.org  Fri Jun  8 15:19:24 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 19:19:24 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1528485563.96.0.592728768989.issue33800@psf.upfronthosting.co.za>


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


New changeset 3b0b90c8c3b8161f0ae9005b83b9b6449d4a8476 by Ned Deily (Andr?s Delfino) in branch 'master':
bpo-33800: Fix default argument for parameter dict_type of ConfigParser/RawConfigParser (GH-7494)
https://github.com/python/cpython/commit/3b0b90c8c3b8161f0ae9005b83b9b6449d4a8476


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

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

From report at bugs.python.org  Fri Jun  8 15:20:46 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 19:20:46 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1528485646.29.0.584625200856.issue33800@psf.upfronthosting.co.za>


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


----------
pull_requests: +7177

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

From report at bugs.python.org  Fri Jun  8 15:26:09 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 19:26:09 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1528485969.93.0.592728768989.issue33800@psf.upfronthosting.co.za>


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


New changeset dc20d9d1026282a2879992f4cef517a270c8a467 by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-33800: Fix default argument for parameter dict_type of ConfigParser/RawConfigParser (GH-7494) (GH-7542)
https://github.com/python/cpython/commit/dc20d9d1026282a2879992f4cef517a270c8a467


----------

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

From report at bugs.python.org  Fri Jun  8 15:26:43 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 19:26:43 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1528486003.13.0.592728768989.issue33800@psf.upfronthosting.co.za>


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

Thanks, Andr?s!

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

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

From report at bugs.python.org  Fri Jun  8 15:47:47 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 19:47:47 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1528487267.51.0.592728768989.issue33082@psf.upfronthosting.co.za>


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

These doc changes have been languishing.  We have a difference of opinion about adding a callback example.  I don't have a strong feeling one way or the other.  Davin or anyone else, what say you?

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

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

From report at bugs.python.org  Fri Jun  8 16:55:37 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 08 Jun 2018 20:55:37 +0000
Subject: [docs] [issue33799] Remove non-ordered dicts comments from FAQ
In-Reply-To: <1528399680.16.0.592728768989.issue33799@psf.upfronthosting.co.za>
Message-ID: <1528491337.99.0.584625200856.issue33799@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino 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/issue33799>
_______________________________________

From report at bugs.python.org  Fri Jun  8 17:51:28 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 21:51:28 +0000
Subject: [docs] [issue33801] Remove non-ordered dict comment from plistlib
In-Reply-To: <1528402376.25.0.592728768989.issue33801@psf.upfronthosting.co.za>
Message-ID: <1528494688.31.0.592728768989.issue33801@psf.upfronthosting.co.za>


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


New changeset 1cbdb2208aa309cf288ee0b53f0ecd85279bb934 by Ned Deily (Andr?s Delfino) in branch 'master':
bpo-33801: Remove non-ordered dict comment from plistlib doc (GH-7495)
https://github.com/python/cpython/commit/1cbdb2208aa309cf288ee0b53f0ecd85279bb934


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

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

From report at bugs.python.org  Fri Jun  8 17:52:38 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 08 Jun 2018 21:52:38 +0000
Subject: [docs] [issue33801] Remove non-ordered dict comment from plistlib
In-Reply-To: <1528402376.25.0.592728768989.issue33801@psf.upfronthosting.co.za>
Message-ID: <1528494758.92.0.584625200856.issue33801@psf.upfronthosting.co.za>


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


----------
pull_requests: +7179

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

From report at bugs.python.org  Fri Jun  8 17:57:51 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 21:57:51 +0000
Subject: [docs] [issue33801] Remove non-ordered dict comment from plistlib
In-Reply-To: <1528402376.25.0.592728768989.issue33801@psf.upfronthosting.co.za>
Message-ID: <1528495071.12.0.592728768989.issue33801@psf.upfronthosting.co.za>


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


New changeset 416fbe41b783d5686b9cb7ff7f8af94b41dc16b8 by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-33801: Remove non-ordered dict comment from plistlib doc (GH-7495) (GH-7546)
https://github.com/python/cpython/commit/416fbe41b783d5686b9cb7ff7f8af94b41dc16b8


----------

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

From report at bugs.python.org  Fri Jun  8 17:58:42 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 08 Jun 2018 21:58:42 +0000
Subject: [docs] [issue33801] Remove non-ordered dict comment from plistlib
In-Reply-To: <1528402376.25.0.592728768989.issue33801@psf.upfronthosting.co.za>
Message-ID: <1528495122.01.0.592728768989.issue33801@psf.upfronthosting.co.za>


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

Thanks for the PR!

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

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

From report at bugs.python.org  Fri Jun  8 21:29:20 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 09 Jun 2018 01:29:20 +0000
Subject: [docs] [issue31215] Add version changed notes for OpenSSL 1.1.0
 compatibility
In-Reply-To: <1502860659.7.0.930691554308.issue31215@psf.upfronthosting.co.za>
Message-ID: <1528507760.44.0.592728768989.issue31215@psf.upfronthosting.co.za>


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

Merged for 2.7 in https://github.com/python/cpython/commit/458ed1b237150f5c59b6ab3e1a5241a672ac8cbd

Thank you for the PRs, Mayank!

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

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

From report at bugs.python.org  Sat Jun  9 10:03:22 2018
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 09 Jun 2018 14:03:22 +0000
Subject: [docs] [issue31711] ssl.SSLSocket.send(b"") fails
In-Reply-To: <1507282980.19.0.213398074469.issue31711@psf.upfronthosting.co.za>
Message-ID: <1528553002.52.0.584625200856.issue31711@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun  9 12:50:20 2018
From: report at bugs.python.org (Dan Snider)
Date: Sat, 09 Jun 2018 16:50:20 +0000
Subject: [docs] [issue33814] exec() maybe has a memory leak
Message-ID: <1528563020.57.0.592728768989.issue33814@psf.upfronthosting.co.za>


New submission from Dan Snider <mr.assume.away at gmail.com>:

Sort of because I'm really not sure if it's working as intended or not. When I found this out today, I noticed that the documentation of `exec` has been updated since the last time I saw it, which is good, but it still leaves much to be desired. Specifically, I don't feel it does enough to explain the supposed justification for `exec`'s ability to very easily trigger a catastrophic memory leak someone unfamiliar with the code they're working on may never have the patience (if not time) to track down.. 

An illustration:

    import itertools
    import sys
    import weakref
    
    def noleak():
        
        def outer():
            from itertools import repeat as reeeee
            def f():
                return reeeee(1, 1)
            return f
        
        f = outer()
        c = sys.getrefcount(f)
        return c, weakref.ref(f), sys.getrefcount(itertools.repeat)

    def leaks():
        ns = {}
        co =  ('from itertools import repeat as reeeee\n'
               'def f(): return reeeee(1, 1)')
        pre = sys.getrefcount(ns)
        exec(co, ns)
        pos = sys.getrefcount(ns)
        return (pre, pos), weakref.ref(ns['f']), sys.getrefcount(itertools.repeat)

    for i in range(10):
        leaks()
    for i in range(10):
        noleak()

Perhaps I'm wrong in thinking that this is behaving as intended and it actually is a bug. Starting from builtin_exec_impl I got as far as _PyFrame_New_NoTrack before I threw up my hands and decided this is something for someone else. 

If `exec` with only a `globals` argument is indeed working as intended, I still think it's ridiculous that every item added to that dict has an "extra", non-obvious reference count that is impossible to vanquish of from within Python. I intuited leaving `locals` blank will do what usually happens when functions take optional arguments, and *usually* that is *not* the triggering of a "hidden" memory leak.


Perhaps the only solution here is to deprecate `exec` accepting `globals` and `locals` as optional arguments.

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 319157
nosy: bup, docs at python
priority: normal
severity: normal
status: open
title: exec() maybe has a memory leak
versions: Python 3.6, Python 3.7

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

From report at bugs.python.org  Sat Jun  9 13:44:32 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 09 Jun 2018 17:44:32 +0000
Subject: [docs] [issue33814] exec() maybe has a memory leak
In-Reply-To: <1528563020.57.0.592728768989.issue33814@psf.upfronthosting.co.za>
Message-ID: <1528566272.36.0.592728768989.issue33814@psf.upfronthosting.co.za>


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

It would be helpful if you could show what output you see, and how it differs from what you expect.

I think you're just seeing reference cycles or some other delayed garbage collection. If you put in a gc.collect() in your loops to force a collection, you'll see the reference numbers drop back.

There's no way we would deprecate globals and locals params to exec().

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

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

From report at bugs.python.org  Sat Jun  9 13:59:20 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 09 Jun 2018 17:59:20 +0000
Subject: [docs] [issue33816] New metaclass example for Data Model topic
Message-ID: <1528567160.68.0.592728768989.issue33816@psf.upfronthosting.co.za>


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

Since Python 3.6, when PEP 520 was accepted, class attribute definition order is preserved. That alone is sufficient to replace the example, but then 3.7 came with guaranteed dictionary insertion order. The metaclass example uses OrderedDict, what may cause confusing to new programmers, since it is not needed.

I'm creating this issue in case someone who actually has used metaclasses can come up with an example, but I'll try to find/think of an example myself.

----------
assignee: docs at python
components: Documentation
messages: 319166
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: New metaclass example for Data Model topic
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Jun  9 14:00:40 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 09 Jun 2018 18:00:40 +0000
Subject: [docs] [issue33816] New metaclass example for Data Model topic
In-Reply-To: <1528567160.68.0.592728768989.issue33816@psf.upfronthosting.co.za>
Message-ID: <1528567240.07.0.592728768989.issue33816@psf.upfronthosting.co.za>


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

I'm talking about the example in Data Model, 3.3.3.6.

----------

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

From report at bugs.python.org  Sat Jun  9 15:54:22 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 09 Jun 2018 19:54:22 +0000
Subject: [docs] [issue33816] New metaclass example for Data Model topic
In-Reply-To: <1528567160.68.0.592728768989.issue33816@psf.upfronthosting.co.za>
Message-ID: <1528574062.29.0.592728768989.issue33816@psf.upfronthosting.co.za>


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

Probably, the entire section with the OrderedClass example should be removed.  Once class dicts became ordered by default, the __prepare__ attribute lost its principal motivating use case.

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

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

From report at bugs.python.org  Sat Jun  9 16:01:51 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 09 Jun 2018 20:01:51 +0000
Subject: [docs] [issue33816] New metaclass example for Data Model topic
In-Reply-To: <1528567160.68.0.592728768989.issue33816@psf.upfronthosting.co.za>
Message-ID: <1528574511.66.0.592728768989.issue33816@psf.upfronthosting.co.za>


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

To what section are you refering by "the entire section"?

On a side note: I'll make a PR to remove the example. IMHO, there should be an example to give some idea of what a metaclass can do, but the current example is no longer useful and it's confusing because of how dicts now work.

----------

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

From report at bugs.python.org  Sat Jun  9 16:06:49 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 09 Jun 2018 20:06:49 +0000
Subject: [docs] [issue33816] New metaclass example for Data Model topic
In-Reply-To: <1528567160.68.0.592728768989.issue33816@psf.upfronthosting.co.za>
Message-ID: <1528574809.26.0.584625200856.issue33816@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun  9 19:49:42 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 09 Jun 2018 23:49:42 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528588182.54.0.592728768989.issue33766@psf.upfronthosting.co.za>


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


New changeset 0aa17ee6a76df0946d42e7657a501f1862065a22 by Terry Jan Reedy (Ammar Askar) in branch 'master':
bpo-33766: Document that end of file or string is a newline (GH-7383)
https://github.com/python/cpython/commit/0aa17ee6a76df0946d42e7657a501f1862065a22


----------

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

From report at bugs.python.org  Sat Jun  9 19:50:58 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 09 Jun 2018 23:50:58 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528588258.5.0.584625200856.issue33766@psf.upfronthosting.co.za>


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


----------
pull_requests: +7199

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

From report at bugs.python.org  Sat Jun  9 19:52:50 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 09 Jun 2018 23:52:50 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528588370.36.0.584625200856.issue33766@psf.upfronthosting.co.za>


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


----------
pull_requests: +7200

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

From report at bugs.python.org  Sat Jun  9 19:55:28 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 09 Jun 2018 23:55:28 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528588528.56.0.584625200856.issue33766@psf.upfronthosting.co.za>


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


----------
pull_requests: +7201

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

From report at bugs.python.org  Sat Jun  9 19:55:29 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 09 Jun 2018 23:55:29 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528588529.05.0.592728768989.issue33766@psf.upfronthosting.co.za>


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


New changeset f01b951a0e70f36ca2a3caa043f89a5277bb0bb0 by Miss Islington (bot) in branch '2.7':
bpo-33766: Document that end of file or string is a newline (GH-7383)
https://github.com/python/cpython/commit/f01b951a0e70f36ca2a3caa043f89a5277bb0bb0


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

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

From report at bugs.python.org  Sat Jun  9 20:07:37 2018
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 10 Jun 2018 00:07:37 +0000
Subject: [docs] [issue33814] exec() maybe has a memory leak
In-Reply-To: <1528563020.57.0.592728768989.issue33814@psf.upfronthosting.co.za>
Message-ID: <1528589256.91.0.592728768989.issue33814@psf.upfronthosting.co.za>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Perhaps a little less self-righteous anger and a little more detail on this alleged bug would be appropriate.

Quote: 
I still think it's ridiculous that every item added to that dict has an "extra", non-obvious reference count that is impossible to vanquish of from within Python.

Have you demonstrated that this is the case? How do you know that is what is happening?

Quote:
I intuited leaving `locals` blank will do what usually happens when functions take optional arguments, and *usually* that is *not* the triggering of a "hidden" memory leak.

Have you demonstrated a memory leak? What is your intuition for what leaving locals blank should do? Did you try running the code without leaving locals blank?

Quote: 
the supposed justification for `exec`'s ability to very easily trigger a catastrophic memory leak

I wouldn't call your example code "very easily", nor do I know what "supposed justification" you are referring to. I read the docs for exec here

https://docs.python.org/3/library/functions.html#exec

and I see nothing justifying memory leaks or even mentioning them. Are you reading some other documentation?

Is this the shortest, simplest demonstration of the leak you can come up with? What output do you get and what output did you expect?

If it necessary for repeat to be imported under the name "reeeee" over and over again? What do weakrefs have to do with this?

You call this a "catastrophic" memory leak, I don't know whether this is mere hyperbole or something that will lock up or crash my computer when I run it.

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

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

From report at bugs.python.org  Sat Jun  9 20:25:05 2018
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 10 Jun 2018 00:25:05 +0000
Subject: [docs] [issue33814] exec() maybe has a memory leak
In-Reply-To: <1528563020.57.0.592728768989.issue33814@psf.upfronthosting.co.za>
Message-ID: <1528590302.99.0.592728768989.issue33814@psf.upfronthosting.co.za>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

I decided to risk this "catastrophic" leak, and ran this:

py> x = leaks()
py> x
((2, 3), <weakref at 0xb7a1998c; to 'function' at 0xb789826c (f)>, 24)
py> import gc
py> gc.collect()
22
py> x
((2, 3), <weakref at 0xb7a1998c; dead>, 24)


so I think Eric is correct, it is just a garbage collection issue. Possibly a bug, possibly normal behaviour. I don't think it is a documentation bug, if it is a bug at all it might be a garbage collection bug.

But I really don't know, because I don't understand what Dan thinks is the memory leak here or why it happens. I *think* Dan might be referring to the fact that each time you call leaks(), there's one extra reference to itertools.repeat.

Dan, if you can confirm that's the leak you are referring to, we would have a better chance of deciding whether it is a bug and if so if it is specific to exec.

----------

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

From report at bugs.python.org  Sat Jun  9 20:28:18 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 10 Jun 2018 00:28:18 +0000
Subject: [docs] [issue33766] Grammar Incongruence
In-Reply-To: <1528085120.11.0.592728768989.issue33766@psf.upfronthosting.co.za>
Message-ID: <1528590498.54.0.584625200856.issue33766@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun  9 20:46:08 2018
From: report at bugs.python.org (Tim Peters)
Date: Sun, 10 Jun 2018 00:46:08 +0000
Subject: [docs] [issue33814] exec() maybe has a memory leak
In-Reply-To: <1528563020.57.0.592728768989.issue33814@psf.upfronthosting.co.za>
Message-ID: <1528591568.82.0.592728768989.issue33814@psf.upfronthosting.co.za>


Tim Peters <tim at python.org> added the comment:

Dan, your bug report is pretty much incoherent ;-)  This standard Stack Overflow advice applies here too:

https://stackoverflow.com/help/mcve

Guessing your complaint is that:

    sys.getrefcount(itertools.repeat)

keeps increasing by 1 across calls to `leaks()`, then as Eric said it will drop back to its original value after a `gc.collect()` call.

Steven, best I can tell weakrefs have nothing to do with this.  The refcount on itertools.repeat increases if

    weakref.ref(ns['f']), 

is deleted.

It's a simple reference cycle.  That is

    ns['f'].__globals__ is ns

is True, so `ns` can't be collected via reference counting, and so `ns` also holds a reference to the irrelevantly renamed `itertools.repeat` too until cyclic gc can detect the trash cycle.

Dan, if that's _not_ what you're complaining about, please follow the advice at the top and add a focused, minimal example of what you are talking about.  In the meantime, I'm closing this as not-a-bug.

----------
nosy: +tim.peters
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Jun 10 04:03:42 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sun, 10 Jun 2018 08:03:42 +0000
Subject: [docs] [issue32400] inspect.isdatadescriptor  false negative
In-Reply-To: <1513882624.99.0.213398074469.issue32400@psf.upfronthosting.co.za>
Message-ID: <1528617822.34.0.592728768989.issue32400@psf.upfronthosting.co.za>


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

@Serhiy Storchaka
This issue can be closed due to PR 1959

----------
keywords: +patch
nosy: +corona10, serhiy.storchaka
pull_requests: +7206
stage:  -> patch review

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

From report at bugs.python.org  Sun Jun 10 04:03:55 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sun, 10 Jun 2018 08:03:55 +0000
Subject: [docs] [issue32400] inspect.isdatadescriptor  false negative
In-Reply-To: <1513882624.99.0.213398074469.issue32400@psf.upfronthosting.co.za>
Message-ID: <1528617835.21.0.584625200856.issue32400@psf.upfronthosting.co.za>


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


----------
pull_requests:  -7206

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

From report at bugs.python.org  Sun Jun 10 07:24:32 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 10 Jun 2018 11:24:32 +0000
Subject: [docs] [issue32400] inspect.isdatadescriptor  false negative
In-Reply-To: <1513882624.99.0.213398074469.issue32400@psf.upfronthosting.co.za>
Message-ID: <1528629872.09.0.584625200856.issue32400@psf.upfronthosting.co.za>


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


----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> Contradiction in definition of "data descriptor" between (dotted lookup behavior/datamodel documentation) and (inspect lib/descriptor how-to)

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

From report at bugs.python.org  Sun Jun 10 09:13:06 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 10 Jun 2018 13:13:06 +0000
Subject: [docs] [issue33819] Mention "ordered mapping" instead of "ordered
 dictionary" in email module
Message-ID: <1528636386.67.0.592728768989.issue33819@psf.upfronthosting.co.za>


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

IMHO, we should replace the "ordered dictionary" with "ordered mapping" now that regular dictionaries are ordered.

I'm proposing "ordered mapping" instead of "dictionary" because there's no actual dictionary behind; it's just a "conceptual model".

PR changes this.

----------
assignee: docs at python
components: Documentation
messages: 319218
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Mention "ordered mapping" instead of "ordered dictionary" in email module
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 10 09:14:30 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 10 Jun 2018 13:14:30 +0000
Subject: [docs] [issue33819] Mention "ordered mapping" instead of "ordered
 dictionary" in email module
In-Reply-To: <1528636386.67.0.592728768989.issue33819@psf.upfronthosting.co.za>
Message-ID: <1528636470.04.0.584625200856.issue33819@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 10 09:15:22 2018
From: report at bugs.python.org (Tal Einat)
Date: Sun, 10 Jun 2018 13:15:22 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1528636522.88.0.584625200856.issue33573@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 10 09:17:23 2018
From: report at bugs.python.org (Tal Einat)
Date: Sun, 10 Jun 2018 13:17:23 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1528636643.22.0.592728768989.issue33573@psf.upfronthosting.co.za>


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

PR ready for review.

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

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

From report at bugs.python.org  Sun Jun 10 21:52:46 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 11 Jun 2018 01:52:46 +0000
Subject: [docs] [issue33825] Change mentions of "magic" attributes to
 "special"
Message-ID: <1528681966.39.0.592728768989.issue33825@psf.upfronthosting.co.za>


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

PR makes all documentation use the same term.

----------
assignee: docs at python
components: Documentation
messages: 319263
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Change mentions of "magic" attributes to "special"
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 10 21:53:13 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 11 Jun 2018 01:53:13 +0000
Subject: [docs] [issue33825] Change mentions of "magic" attributes to
 "special"
In-Reply-To: <1528681966.39.0.592728768989.issue33825@psf.upfronthosting.co.za>
Message-ID: <1528681993.31.0.584625200856.issue33825@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 10 22:35:07 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 02:35:07 +0000
Subject: [docs] [issue33745] 3.7.0b5 changes the line number of empty
 functions with docstrings
In-Reply-To: <1528024309.59.0.592728768989.issue33745@psf.upfronthosting.co.za>
Message-ID: <1528684507.1.0.584625200856.issue33745@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 10 22:41:17 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 02:41:17 +0000
Subject: [docs] [issue33745] 3.7.0b5 changes the line number of empty
 functions with docstrings
In-Reply-To: <1528024309.59.0.592728768989.issue33745@psf.upfronthosting.co.za>
Message-ID: <1528684877.04.0.592728768989.issue33745@psf.upfronthosting.co.za>


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


New changeset 12c6cdf4d16078aa09de32a39193c8161177b39d by Ned Deily in branch 'master':
bpo-33745: Add What's New for empty function docstring change. (GH-7611)
https://github.com/python/cpython/commit/12c6cdf4d16078aa09de32a39193c8161177b39d


----------

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

From report at bugs.python.org  Sun Jun 10 22:42:24 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 11 Jun 2018 02:42:24 +0000
Subject: [docs] [issue33745] 3.7.0b5 changes the line number of empty
 functions with docstrings
In-Reply-To: <1528024309.59.0.592728768989.issue33745@psf.upfronthosting.co.za>
Message-ID: <1528684944.41.0.584625200856.issue33745@psf.upfronthosting.co.za>


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


----------
pull_requests: +7237

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

From report at bugs.python.org  Sun Jun 10 23:00:19 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 11 Jun 2018 03:00:19 +0000
Subject: [docs] [issue33745] 3.7.0b5 changes the line number of empty
 functions with docstrings
In-Reply-To: <1528024309.59.0.592728768989.issue33745@psf.upfronthosting.co.za>
Message-ID: <1528686019.44.0.592728768989.issue33745@psf.upfronthosting.co.za>


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


New changeset 14a190c88273fb22d9439bbed394f19f21e8a0f9 by Miss Islington (bot) in branch '3.7':
bpo-33745: Add What's New for empty function docstring change. (GH-7611)
https://github.com/python/cpython/commit/14a190c88273fb22d9439bbed394f19f21e8a0f9


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

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

From report at bugs.python.org  Sun Jun 10 23:02:20 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 03:02:20 +0000
Subject: [docs] [issue33745] 3.7.0b5 changes the line number of empty
 functions with docstrings
In-Reply-To: <1528024309.59.0.592728768989.issue33745@psf.upfronthosting.co.za>
Message-ID: <1528686140.87.0.592728768989.issue33745@psf.upfronthosting.co.za>


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

The 3.7 What's New has been updated as Nick suggested.  Thanks, Nick, and thanks, Ned, for bringing it up!

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

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

From report at bugs.python.org  Mon Jun 11 00:04:00 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 11 Jun 2018 04:04:00 +0000
Subject: [docs] [issue33825] Change mentions of "magic" attributes to
 "special"
In-Reply-To: <1528681966.39.0.592728768989.issue33825@psf.upfronthosting.co.za>
Message-ID: <1528689840.74.0.592728768989.issue33825@psf.upfronthosting.co.za>


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

Both terms are in common use.  There is no need to elide the word "special".

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

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

From report at bugs.python.org  Mon Jun 11 03:41:50 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 11 Jun 2018 07:41:50 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1528702910.66.0.584625200856.issue24356@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Jun 11 04:33:19 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 11 Jun 2018 08:33:19 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
Message-ID: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>


New submission from Xiang Zhang <angwerzx at 126.com>:

I propose to add versionchanged note about auto-numbering feature of string.Formatter, introduced in #13598. It's quite confusing which version could I use the feature reading the doc. Also it's better to note in 2.7 the feature is not available.

Currently the doc gives me the feeling string.Formatter and str.format share the same feature and the auto-numbering feature is available in 2.7 and >3.1.

----------
assignee: docs at python
components: Documentation
messages: 319284
nosy: docs at python, eric.smith, xiang.zhang
priority: normal
severity: normal
stage: needs patch
status: open
title: Add versionchanged notes for string.Formatter
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Jun 11 06:45:03 2018
From: report at bugs.python.org (Aifu LIU)
Date: Mon, 11 Jun 2018 10:45:03 +0000
Subject: [docs] [issue33830] example output error
Message-ID: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>


New submission from Aifu LIU <laf163 at gmail.com>:

The output of this line:
    print r2.status, r2.reason
should same as:
    print r1.status, r1.reason

from https://docs.python.org/2.7/library/httplib.html

>>> import httplib
>>> conn = httplib.HTTPSConnection("www.python.org")
>>> conn.request("GET", "/")
>>> r1 = conn.getresponse()
>>> print r1.status, r1.reason
200 OK
>>> data1 = r1.read()
>>> conn.request("GET", "/")
>>> r2 = conn.getresponse()
>>> print r2.status, r2.reason
404 Not Found
>>> data2 = r2.read()
>>> conn.close()

----------
assignee: docs at python
components: Documentation
messages: 319290
nosy: Aifu LIU, docs at python
priority: normal
severity: normal
status: open
title: example output error
versions: Python 2.7

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

From report at bugs.python.org  Mon Jun 11 07:28:07 2018
From: report at bugs.python.org (Martin Panter)
Date: Mon, 11 Jun 2018 11:28:07 +0000
Subject: [docs] [issue33830] example output error
In-Reply-To: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>
Message-ID: <1528716487.9.0.592728768989.issue33830@psf.upfronthosting.co.za>


Martin Panter <vadmium+py at gmail.com> added the comment:

Looks like poor application of a Python 3 patch in Issue 24118. The second request was meant to be for /parrot.spam.

----------
nosy: +benjamin.peterson, martin.panter

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

From report at bugs.python.org  Mon Jun 11 07:31:10 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 11 Jun 2018 11:31:10 +0000
Subject: [docs] [issue33825] Change mentions of "magic" attributes to
 "special"
In-Reply-To: <1528681966.39.0.592728768989.issue33825@psf.upfronthosting.co.za>
Message-ID: <1528716670.42.0.592728768989.issue33825@psf.upfronthosting.co.za>


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

ok :)

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

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

From report at bugs.python.org  Mon Jun 11 07:56:31 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 11 Jun 2018 11:56:31 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
Message-ID: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>


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

PR adds "magic method" to the glossary, and adds a mention in Data Model 3.3. Special method names.

----------
assignee: docs at python
components: Documentation
messages: 319300
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Make "magic methods" a little more discoverable in the docs
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Jun 11 07:57:36 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 11 Jun 2018 11:57:36 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1528718256.08.0.584625200856.issue33832@psf.upfronthosting.co.za>


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


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

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

From silverparasol at hotmail.com  Sat Jun  9 23:06:11 2018
From: silverparasol at hotmail.com (Witthawat P.)
Date: Sun, 10 Jun 2018 03:06:11 +0000
Subject: [docs] Bug in functools.reduce
Message-ID: <SN2PR17MB0784B6754E9576A67C4C71A0AA790@SN2PR17MB0784.namprd17.prod.outlook.com>

Hi,

I have found bug in functools.reduce (Python V 3.6.5). The function ignores the value of initializer, if initializer is zero.

Below is the example code

import functools as f

ar = [2, 5, 4, 1, 3]
out = f.reduce(lambda prev, curr: prev < curr and prev or curr, ar, 0)
print(out)
>>  Expected: 0
>>  Actual: 1

out2 = f.reduce(lambda prev, curr: prev < curr and prev or curr, ar, -1)
print(out2)
>> Expected: -1
>> Actual: -1



Best Regards,
Witthawat P.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180610/1eab404d/attachment-0001.html>

From report at bugs.python.org  Mon Jun 11 09:13:21 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 11 Jun 2018 13:13:21 +0000
Subject: [docs] [issue17286] Make subprocess handling text output with
 universal_newlines more obious
In-Reply-To: <1361708455.88.0.426093416103.issue17286@psf.upfronthosting.co.za>
Message-ID: <1528722801.17.0.584625200856.issue17286@psf.upfronthosting.co.za>


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


----------
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> subprocess.run should alias universal_newlines to text

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

From report at bugs.python.org  Mon Jun 11 11:59:35 2018
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 11 Jun 2018 15:59:35 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
Message-ID: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>


New submission from Zachary Ware <zachary.ware at gmail.com>:

In https://docs.python.org/3/faq/programming.html#why-are-default-values-shared-between-objects there is an example showing memoization using `def expensive(arg1, arg2, _cache={}):`.  We should change the signature in that example to make `_cache` a keyword-only parameter and possibly adjust the comment to note that that's been done to prevent accidental calls with three positional arguments.



Note to existing contributors: if this wouldn't be within your first couple of patches, please leave this for a new contributor to find.  Thanks!

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 319310
nosy: docs at python, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: [Good first-time issue] Recommend keyword-only param for memoization in FAQ
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Jun 11 15:59:28 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 19:59:28 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does nto emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528747168.8.0.584625200856.issue33582@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Jun 11 16:08:19 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 20:08:19 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does nto emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528747699.04.0.592728768989.issue33582@psf.upfronthosting.co.za>


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


New changeset 46c5cd0f6e22bdfbdd3f0b18f1d01eda754e7e11 by Ned Deily (Matthias Bussonnier) in branch 'master':
bpo-33582: Emit deprecation warning for `formatargspec` (GH-6994)
https://github.com/python/cpython/commit/46c5cd0f6e22bdfbdd3f0b18f1d01eda754e7e11


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

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

From report at bugs.python.org  Mon Jun 11 16:09:54 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 11 Jun 2018 20:09:54 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does nto emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528747794.44.0.584625200856.issue33582@psf.upfronthosting.co.za>


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


----------
pull_requests: +7264

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

From report at bugs.python.org  Mon Jun 11 16:44:18 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 11 Jun 2018 20:44:18 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does nto emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528749858.73.0.592728768989.issue33582@psf.upfronthosting.co.za>


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


New changeset 60b8274fec3ff029591d8718650223c5ce78a05c by Miss Islington (bot) in branch '3.7':
bpo-33582: Emit deprecation warning for `formatargspec` (GH-6994)
https://github.com/python/cpython/commit/60b8274fec3ff029591d8718650223c5ce78a05c


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

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

From report at bugs.python.org  Mon Jun 11 16:47:04 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 20:47:04 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does nto emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528750024.56.0.592728768989.issue33582@psf.upfronthosting.co.za>


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

Thanks for the PR, Matthias, and thanks for shepherding this, Tal.  Merged for 3.7.0rc1 (I don't think it is appropriate to backport to earlier releases.)

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

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

From songofacandy at gmail.com  Mon Jun 11 18:18:00 2018
From: songofacandy at gmail.com (INADA Naoki)
Date: Tue, 12 Jun 2018 07:18:00 +0900
Subject: [docs] Bug in functools.reduce
In-Reply-To: <SN2PR17MB0784B6754E9576A67C4C71A0AA790@SN2PR17MB0784.namprd17.prod.outlook.com>
References: <SN2PR17MB0784B6754E9576A67C4C71A0AA790@SN2PR17MB0784.namprd17.prod.outlook.com>
Message-ID: <CAEfz+TzW7ahQDBP_g=NPYvgGCQ=+LMfp8Aace4TkxjstdD5oog@mail.gmail.com>

It's not a bug.

Since 0 is falsy value, `0 or 2` is 2, not 0.
You need to use `prev if prev < curr else curr` instead of `cond and A or
B` hack.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180612/d3f064e0/attachment.html>

From report at bugs.python.org  Mon Jun 11 18:59:48 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 22:59:48 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528757988.34.0.592728768989.issue31432@psf.upfronthosting.co.za>


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


New changeset ef24b6c54d40e7820456873a6eab6ef57d2bd0db by Ned Deily (Christian Heimes) in branch 'master':
bpo-31432: Clarify ssl CERT_NONE/OPTIONAL/REQUIRED docs. (GH-3530)
https://github.com/python/cpython/commit/ef24b6c54d40e7820456873a6eab6ef57d2bd0db


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

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

From report at bugs.python.org  Mon Jun 11 19:00:09 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 11 Jun 2018 23:00:09 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528758009.9.0.584625200856.issue31432@psf.upfronthosting.co.za>


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


----------
pull_requests: +7268

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

From report at bugs.python.org  Mon Jun 11 19:20:27 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Jun 2018 23:20:27 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528759227.06.0.592728768989.issue31432@psf.upfronthosting.co.za>


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


New changeset a5db479ac4cdcc0d94ec1d7a594720a651d90433 by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-31432: Clarify ssl CERT_NONE/OPTIONAL/REQUIRED docs. (GH-3530) (GH-7649)
https://github.com/python/cpython/commit/a5db479ac4cdcc0d94ec1d7a594720a651d90433


----------

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

From report at bugs.python.org  Mon Jun 11 20:08:29 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 00:08:29 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528762109.47.0.584625200856.issue31432@psf.upfronthosting.co.za>


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


----------
pull_requests: +7269

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

From report at bugs.python.org  Mon Jun 11 20:26:36 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 00:26:36 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528763194.97.0.592728768989.issue31432@psf.upfronthosting.co.za>


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


New changeset 4531ec74c4a9c8e15ee2bdec11b12796ce000f6f by Ned Deily in branch 'master':
bpo-31432: Revert unrelated code changes to _ssl.c and test_ssl (GH-7650)
https://github.com/python/cpython/commit/4531ec74c4a9c8e15ee2bdec11b12796ce000f6f


----------

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

From report at bugs.python.org  Mon Jun 11 20:27:47 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 12 Jun 2018 00:27:47 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528763267.48.0.584625200856.issue31432@psf.upfronthosting.co.za>


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


----------
pull_requests: +7270

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

From report at bugs.python.org  Mon Jun 11 20:58:12 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 00:58:12 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528765092.74.0.592728768989.issue31432@psf.upfronthosting.co.za>


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


New changeset 42198571c586e0dc56836b79329f94952b1975bb by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-31432: Revert unrelated code changes to _ssl.c and test_ssl (GH-7650) (GH-7651)
https://github.com/python/cpython/commit/42198571c586e0dc56836b79329f94952b1975bb


----------

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

From report at bugs.python.org  Mon Jun 11 21:15:09 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 01:15:09 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528766109.13.0.584625200856.issue31432@psf.upfronthosting.co.za>


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


----------
pull_requests: +7271

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

From report at bugs.python.org  Mon Jun 11 21:45:03 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 01:45:03 +0000
Subject: [docs] [issue31432] Documention for CERT_OPTIONAL is misleading
In-Reply-To: <1505232519.67.0.963615295738.issue31432@psf.upfronthosting.co.za>
Message-ID: <1528767903.6.0.592728768989.issue31432@psf.upfronthosting.co.za>


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


New changeset e25757408dc22561af9f9589c2c7e2a2fbb66ee4 by Ned Deily in branch '3.6':
bpo-31432: Clarify ssl CERT_NONE/OPTIONAL/REQUIRED docs. (GH-3530) (GH-7652)
https://github.com/python/cpython/commit/e25757408dc22561af9f9589c2c7e2a2fbb66ee4


----------

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

From report at bugs.python.org  Mon Jun 11 22:37:42 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Tue, 12 Jun 2018 02:37:42 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does not emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528771062.37.0.584625200856.issue33582@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
nosy: +ZackerySpytz
title: formatargspec deprecated but does nto emit DeprecationWarning. -> formatargspec deprecated but does not emit DeprecationWarning.

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

From report at bugs.python.org  Mon Jun 11 22:40:59 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Tue, 12 Jun 2018 02:40:59 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does not emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528771259.25.0.584625200856.issue33582@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
pull_requests: +7272

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

From report at bugs.python.org  Mon Jun 11 23:16:21 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 03:16:21 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does not emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528773381.13.0.592728768989.issue33582@psf.upfronthosting.co.za>


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


New changeset 41254ebd5e4f40a2e095d8aaea60bf3973de4647 by Ned Deily (Zackery Spytz) in branch 'master':
bpo-33582: Remove duplicate space in inspect.formatargspec() deprecation warning (GH-7655)
https://github.com/python/cpython/commit/41254ebd5e4f40a2e095d8aaea60bf3973de4647


----------

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

From report at bugs.python.org  Mon Jun 11 23:17:35 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 12 Jun 2018 03:17:35 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does not emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528773455.96.0.584625200856.issue33582@psf.upfronthosting.co.za>


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


----------
pull_requests: +7274

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

From report at bugs.python.org  Tue Jun 12 00:25:35 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 12 Jun 2018 04:25:35 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does not emit
 DeprecationWarning.
In-Reply-To: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>
Message-ID: <1528777535.86.0.475983251502.issue33582@psf.upfronthosting.co.za>


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


New changeset 8379b70be2c0a9e3f11cdb694a8faaf5763f99ed by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-33582: Remove duplicate space in inspect.formatargspec() deprecation warning (GH-7655) (GH-7657)
https://github.com/python/cpython/commit/8379b70be2c0a9e3f11cdb694a8faaf5763f99ed


----------

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

From report at bugs.python.org  Tue Jun 12 04:20:27 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 12 Jun 2018 08:20:27 +0000
Subject: [docs] [issue33819] Mention "ordered mapping" instead of "ordered
 dictionary" in email module
In-Reply-To: <1528636386.67.0.592728768989.issue33819@psf.upfronthosting.co.za>
Message-ID: <1528791627.68.0.475983251502.issue33819@psf.upfronthosting.co.za>


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

I think "dictionary" means just "dict-like", and it doesn't implies "ordered".  Glossary doesn't say "dictionary" is ordered too.

So "regular dictionary is ordered now" is not enough reason to stop using "ordered dictionary".

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

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

From report at bugs.python.org  Tue Jun 12 08:21:27 2018
From: report at bugs.python.org (R. David Murray)
Date: Tue, 12 Jun 2018 12:21:27 +0000
Subject: [docs] [issue33819] Mention "ordered mapping" instead of "ordered
 dictionary" in email module
In-Reply-To: <1528636386.67.0.592728768989.issue33819@psf.upfronthosting.co.za>
Message-ID: <1528806086.97.0.475983251502.issue33819@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

Message/EmailMessage are intentionally mimicing the full dictionary API, not just the Mapping API (with a couple exceptions and several extensions).  But it is important to mention that it is ordered, both for the reason INADA stgtes, and because the text goes on to discuss the handling of duplicate headers and what happens when you add and delete headers.  While this turns out to be almost the same as the rules used by a standard python dictionary, that is partially a coincidence....other ordering rules could have been chosen.

----------
nosy: +r.david.murray
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Jun 12 11:13:06 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Tue, 12 Jun 2018 15:13:06 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528816386.14.0.597367554133.issue33828@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jun 12 14:44:14 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 12 Jun 2018 18:44:14 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
Message-ID: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>


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

Currently, the index only refers to decorators for the @ symbol. PR adds entry for the matrix multiplication operator.

----------
assignee: docs at python
components: Documentation
messages: 319398
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc: Add '@' operator entry to index
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Jun 12 14:44:53 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 12 Jun 2018 18:44:53 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1528829093.55.0.121749146738.issue33847@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jun 12 21:42:46 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 13 Jun 2018 01:42:46 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528854166.92.0.947875510639.issue33828@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset b9d8ad5130e0f77be28a3dec6d468e6470835573 by Xiang Zhang in branch 'master':
bpo-33828: Add missing versionchanged note for string.Formatter. (GH-7668)
https://github.com/python/cpython/commit/b9d8ad5130e0f77be28a3dec6d468e6470835573


----------

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

From report at bugs.python.org  Tue Jun 12 21:43:20 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 01:43:20 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528854200.78.0.121749146738.issue33828@psf.upfronthosting.co.za>


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


----------
pull_requests: +7286

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

From report at bugs.python.org  Tue Jun 12 21:43:57 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 01:43:57 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528854237.28.0.121749146738.issue33828@psf.upfronthosting.co.za>


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


----------
pull_requests: +7287

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

From report at bugs.python.org  Tue Jun 12 22:04:12 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 13 Jun 2018 02:04:12 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528855452.73.0.121749146738.issue33828@psf.upfronthosting.co.za>


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


----------
pull_requests: +7288

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

From report at bugs.python.org  Tue Jun 12 22:10:54 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 02:10:54 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528855854.06.0.947875510639.issue33828@psf.upfronthosting.co.za>


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


New changeset 29fdea5ec2054f18e68733ec83edbd0b855fd8bb by Miss Islington (bot) in branch '3.7':
bpo-33828: Add missing versionchanged note for string.Formatter. (GH-7668)
https://github.com/python/cpython/commit/29fdea5ec2054f18e68733ec83edbd0b855fd8bb


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

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

From report at bugs.python.org  Tue Jun 12 22:11:27 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 02:11:27 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528855887.65.0.947875510639.issue33828@psf.upfronthosting.co.za>


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


New changeset 439a9b69985bd4757de1504d19b040f78e384ca4 by Miss Islington (bot) in branch '3.6':
bpo-33828: Add missing versionchanged note for string.Formatter. (GH-7668)
https://github.com/python/cpython/commit/439a9b69985bd4757de1504d19b040f78e384ca4


----------

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

From report at bugs.python.org  Tue Jun 12 22:38:04 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 13 Jun 2018 02:38:04 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528857484.63.0.947875510639.issue33828@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset fc8ea20c6f8571de96791bc5f7f2d693406024c7 by Xiang Zhang in branch '2.7':
[2.7] bpo-33828: Clarify auto-numbering is not available to string.Formatter. (GH-7668) (GH-7676)
https://github.com/python/cpython/commit/fc8ea20c6f8571de96791bc5f7f2d693406024c7


----------

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

From report at bugs.python.org  Tue Jun 12 22:40:48 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 13 Jun 2018 02:40:48 +0000
Subject: [docs] [issue33828] Add versionchanged notes for string.Formatter
In-Reply-To: <1528705999.65.0.592728768989.issue33828@psf.upfronthosting.co.za>
Message-ID: <1528857648.38.0.947875510639.issue33828@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:

Thanks for the review, Eric. :-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> enhancement
versions: +Python 2.7

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

From report at bugs.python.org  Wed Jun 13 01:54:47 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Wed, 13 Jun 2018 05:54:47 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528869287.53.0.121749146738.issue31378@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


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

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

From report at bugs.python.org  Wed Jun 13 01:56:28 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Wed, 13 Jun 2018 05:56:28 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528869388.32.0.121749146738.issue31378@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
nosy: +ZackerySpytz
versions: +Python 3.8

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

From report at bugs.python.org  Wed Jun 13 05:02:07 2018
From: report at bugs.python.org (Jason)
Date: Wed, 13 Jun 2018 09:02:07 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1528880526.99.0.947875510639.issue33836@psf.upfronthosting.co.za>


Jason <jatkinsee3 at gmail.com> added the comment:

Hey Zach,

Can I get this one? I haven't contributed anything yet.


Cheers,
Jason

----------
nosy: +codecamelot

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

From report at bugs.python.org  Wed Jun 13 05:09:40 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 13 Jun 2018 09:09:40 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528880980.77.0.947875510639.issue31378@psf.upfronthosting.co.za>


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


New changeset 71ede00f140fa6b67a8ac17df68b80079efa8dc2 by Berker Peksag (Zackery Spytz) in branch 'master':
bpo-31378: Document sqlite3.OperationalError exception (GH-7677)
https://github.com/python/cpython/commit/71ede00f140fa6b67a8ac17df68b80079efa8dc2


----------

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

From report at bugs.python.org  Wed Jun 13 05:10:05 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 09:10:05 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528881005.94.0.121749146738.issue31378@psf.upfronthosting.co.za>


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


----------
pull_requests: +7290

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

From report at bugs.python.org  Wed Jun 13 05:10:42 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 09:10:42 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528881042.67.0.121749146738.issue31378@psf.upfronthosting.co.za>


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


----------
pull_requests: +7291

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

From report at bugs.python.org  Wed Jun 13 05:28:51 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 09:28:51 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528882131.4.0.947875510639.issue31378@psf.upfronthosting.co.za>


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


New changeset eea4f149717cc83038641ca53f6f74be785de6f1 by Miss Islington (bot) in branch '3.7':
bpo-31378: Document sqlite3.OperationalError exception (GH-7677)
https://github.com/python/cpython/commit/eea4f149717cc83038641ca53f6f74be785de6f1


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

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

From report at bugs.python.org  Wed Jun 13 05:30:11 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 13 Jun 2018 09:30:11 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528882211.8.0.947875510639.issue31378@psf.upfronthosting.co.za>


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


New changeset 961332dfd3dbff4c63ed4d9f8b5de937aa63475b by Miss Islington (bot) in branch '3.6':
bpo-31378: Document sqlite3.OperationalError exception (GH-7677)
https://github.com/python/cpython/commit/961332dfd3dbff4c63ed4d9f8b5de937aa63475b


----------

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

From report at bugs.python.org  Wed Jun 13 05:30:47 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 13 Jun 2018 09:30:47 +0000
Subject: [docs] [issue31378] Missing documentation for
 sqlite3.OperationalError
In-Reply-To: <1504772099.62.0.812032551606.issue31378@psf.upfronthosting.co.za>
Message-ID: <1528882247.08.0.121749146738.issue31378@psf.upfronthosting.co.za>


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/issue31378>
_______________________________________

From report at bugs.python.org  Wed Jun 13 06:11:45 2018
From: report at bugs.python.org (Damon Atkins)
Date: Wed, 13 Jun 2018 10:11:45 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1528884705.65.0.947875510639.issue15533@psf.upfronthosting.co.za>


Damon Atkins <damon.atkins at gmail.com> added the comment:

I see from this. That this is still an issue
https://github.com/python/cpython/blob/master/Lib/subprocess.py#L1146

Is it not a solution to
save current directory location
chdir(cwd) before calling  _winapi.CreateProcess()
restore the original directory.

This will result in the cwd being searched for the executable, which most people would expect to happen.  It seems CreateProcess does not change to cwd until after the file is checked for existence or loaded.

----------
nosy: +Damon Atkins

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

From report at bugs.python.org  Wed Jun 13 06:14:19 2018
From: report at bugs.python.org (Damon Atkins)
Date: Wed, 13 Jun 2018 10:14:19 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1528884858.99.0.947875510639.issue15533@psf.upfronthosting.co.za>


Damon Atkins <damon.atkins at gmail.com> added the comment:

See also https://bugs.python.org/msg262399

----------

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

From report at bugs.python.org  Wed Jun 13 09:12:22 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 13 Jun 2018 13:12:22 +0000
Subject: [docs] [issue33852] doc Remove parentheses from
Message-ID: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>


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

I think the idea of having "list" inside parentheses is to document that in case of sequences, only "one-expression" expression lists are legal.

That being said, IMHO, explaining that in actual prose would be better, but removing the parentheses (taking into account that there's a description of what the expected evaluation of sequences subscription expression lists is) is enough, plus, it's the production list term's name.

If a prose is considered better, it could read:

"If the primary is a sequence, the expression list must be formed by only one expression, and it must evaluate to an integer or a slice (as discussed in the following section)."

Couldn't find the original author. It was committed before the move to mercurial, and I don't know if there's a subversion repo still available to see historical changes.

----------
assignee: docs at python
components: Documentation
messages: 319460
nosy: adelfino, docs at python
priority: normal
pull_requests: 7295
severity: normal
status: open
title: doc Remove parentheses from
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Wed Jun 13 09:14:33 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 13 Jun 2018 13:14:33 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1528895673.68.0.121749146738.issue33852@psf.upfronthosting.co.za>


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


----------
title: doc Remove parentheses from -> doc Remove parentheses from sequence subscription description

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

From report at bugs.python.org  Wed Jun 13 09:19:51 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 13 Jun 2018 13:19:51 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1528895991.41.0.947875510639.issue33852@psf.upfronthosting.co.za>


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

This wording was introduced in 3a0ad6089bccf0b167fe8ebd2457fedec8f851a3.

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

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

From report at bugs.python.org  Wed Jun 13 09:30:13 2018
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 13 Jun 2018 13:30:13 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1528896613.01.0.947875510639.issue33836@psf.upfronthosting.co.za>


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

Certainly!  Have a look at the devguide to get started.

----------

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

From report at bugs.python.org  Wed Jun 13 09:45:01 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 13 Jun 2018 13:45:01 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1528897501.24.0.947875510639.issue33852@psf.upfronthosting.co.za>


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

Thanks, Serhiy! Didn't know I should trace the LaTeX version.

Guido, I'm adding you because it seems you authored or at least agreed on the current wording. Do you believe this proposal for improvement makes sense?

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

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

From report at bugs.python.org  Wed Jun 13 10:08:31 2018
From: report at bugs.python.org (Jan Lachnitt)
Date: Wed, 13 Jun 2018 14:08:31 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1528898911.22.0.947875510639.issue15533@psf.upfronthosting.co.za>


Jan Lachnitt <pepalogik at seznam.cz> added the comment:

@eryksun: Sorry for my late reply, apparently I did not have time to reply in 2017. I see your point, but still I think that Python is conceptually multi-platform, so its behavior on Linux and Windows should be as much consistent as possible.

I am not the one to decide which one of the two possible behaviors shall be the correct one. The current documentation <https://docs.python.org/3/library/subprocess.html#subprocess.Popen> describes the behavior on Linux: "In particular, the function looks for executable (or for the first item in args) relative to cwd if the executable path is a relative path." If this is chosen as the correct behavior, then the behavior on Windows is incorrect.

@Damon Atkins: Thank you for reminding this issue, but I suspect your proposed solution of being thread-unsafe. I propose another solution: On Windows, Python should resolve the executable path itself (taking cwd and env into account) and then pass the absolute path to CreateProcess().

----------

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

From report at bugs.python.org  Wed Jun 13 11:33:43 2018
From: report at bugs.python.org (Eric Snow)
Date: Wed, 13 Jun 2018 15:33:43 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1528904023.27.0.947875510639.issue17045@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

@Cheryl, thanks for pointing that out.  I'll take a look.

----------

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

From report at bugs.python.org  Wed Jun 13 20:02:05 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 14 Jun 2018 00:02:05 +0000
Subject: [docs] [issue33726] Add short descriptions to PEP references in
 seealso
In-Reply-To: <1527822205.22.0.682650639539.issue33726@psf.upfronthosting.co.za>
Message-ID: <1528934525.18.0.947875510639.issue33726@psf.upfronthosting.co.za>


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

My personal opinion is that the PEP title should suffice and that a person can click the link for more detail.

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

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

From report at bugs.python.org  Wed Jun 13 23:01:29 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 03:01:29 +0000
Subject: [docs] [issue33726] Add short descriptions to PEP references in
 seealso
In-Reply-To: <1527822205.22.0.682650639539.issue33726@psf.upfronthosting.co.za>
Message-ID: <1528945289.28.0.947875510639.issue33726@psf.upfronthosting.co.za>


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

Yeah, I think you are right. The motivation for this PR was to not have two PEPs references in the same line, because, IMHO, it looks somewhat weird. Now, they look like:

"See also: PEP 3115 - Metaclasses in Python 3 PEP 3129 - Class Decorators"

Would a change to make it look like:

"""
See also:

PEP 3115 - Metaclasses in Python 3
PEP 3129 - Class Decorators
"""

be accepted?

----------

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

From report at bugs.python.org  Wed Jun 13 23:12:52 2018
From: report at bugs.python.org (Noah Haasis)
Date: Thu, 14 Jun 2018 03:12:52 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1528945972.88.0.121749146738.issue33836@psf.upfronthosting.co.za>


Change by Noah Haasis <haasis_noah at yahoo.de>:


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

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

From report at bugs.python.org  Wed Jun 13 23:33:29 2018
From: report at bugs.python.org (Damon Atkins)
Date: Thu, 14 Jun 2018 03:33:29 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1528947209.48.0.947875510639.issue15533@psf.upfronthosting.co.za>


Damon Atkins <damon.atkins at gmail.com> added the comment:

>From https://msdn.microsoft.com/en-us/library/windows/desktop/ms682425.aspx

Note Python is using CreateProcess(), consider using CreateProcessW()

The Unicode version of this function, CreateProcessW, can modify the contents of this string. Therefore, this parameter cannot be a pointer to read-only memory (such as a const variable or a literal string). If this parameter is a constant string, the function may cause an access violation.

----------

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

From report at bugs.python.org  Wed Jun 13 23:50:38 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 03:50:38 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
Message-ID: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>


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

Add PEP 461 title to Built-in Types seealso.

----------
assignee: docs at python
components: Documentation
messages: 319493
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add PEP title in seealso of Built-in Types
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Wed Jun 13 23:51:39 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 03:51:39 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1528948299.74.0.121749146738.issue33854@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun 14 07:39:18 2018
From: report at bugs.python.org (aruseni)
Date: Thu, 14 Jun 2018 11:39:18 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
Message-ID: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>


New submission from aruseni <aruseni.magiku at gmail.com>:

https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods

> locks created using the fork context cannot be passed to a processes started using the spawn or forkserver start methods

----------
assignee: docs at python
components: Documentation
messages: 319509
nosy: aruseni, docs at python
priority: normal
severity: normal
status: open
title: A typo in multiprocessing documentation
versions: Python 3.6

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

From ahmadsugandi06 at gmail.com  Tue Jun 12 17:28:45 2018
From: ahmadsugandi06 at gmail.com (Ahmad Sugandi)
Date: Wed, 13 Jun 2018 04:28:45 +0700
Subject: [docs] Can't download documentation
Message-ID: <CAMM-cU5Z9nNTqev-4nZGqQw7rGdWHBO8jodqFu3GM_mTzUhM5g@mail.gmail.com>

Why i cant download documentation from mobile... ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180613/9f2749d7/attachment.html>

From arifugurel at gmail.com  Tue Jun 12 06:12:22 2018
From: arifugurel at gmail.com (Arif Ugurel)
Date: Tue, 12 Jun 2018 13:12:22 +0300
Subject: [docs] Python Doc Download Problem
Message-ID: <CAD6GQOakd+9iyhYeaTwgfD19Ldt0gXjBrO4jdtOJZ=HCUa0BUw@mail.gmail.com>

Hi there,

I'm trying to download Python 3.x documentation using below link:

https://docs.python.org/3/archives/python-3.6.6rc1-docs-pdf-letter.zip

It gives "404 Not Found" error. I tried other versions of the docs (A4
size, html, plain), but all links are dead.

Thanks for your works,

Best Regards,

-- 
M.Arif UGUREL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180612/d54aa72b/attachment.html>

From dakotacars2018 at gmail.com  Tue Jun 12 15:38:08 2018
From: dakotacars2018 at gmail.com (Diego diaz)
Date: Tue, 12 Jun 2018 20:38:08 +0100
Subject: [docs] =?utf-8?q?My_py_exe_won=E2=80=99t_open?=
Message-ID: <CAOnVt_HtN=saj53DtKaJwT_Utkz3QGOY2KV0Y4E9Uz4=JSAxhg@mail.gmail.com>

Hello I created a program but when I made it an exe  file and go to the
build folder and try to open it it opens but closes immediately. I created
another program to see if it was because my code was wrong but in this one
all I did was

print(?Hello?)
Input()

But it stil closes when I try to open it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180612/58738b38/attachment.html>

From eefvandongen at gmail.com  Tue Jun 12 11:14:30 2018
From: eefvandongen at gmail.com (Eef van Dongen)
Date: Tue, 12 Jun 2018 17:14:30 +0200
Subject: [docs] Documentation download not found
Message-ID: <CALLKFdNSyhAYJK_i3SxVKij5j4bLwe4Xp=4LigdXA4ds0mM0eQ@mail.gmail.com>

Dear Sir or Madam,

I am trying to download python documentation for offline use.
I tested all links at https://docs.python.org/3/download.html but all of
them said '404 not found'.

Am I at the wrong location to download the documentation or is there
another problem?

Kind regards,
Eef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180612/957f75a4/attachment.html>

From phanindra.kundula at gmail.com  Tue Jun 12 09:19:51 2018
From: phanindra.kundula at gmail.com (Phani babu)
Date: Tue, 12 Jun 2018 18:49:51 +0530
Subject: [docs] Python Documentation
Message-ID: <CA+Tk2m-zzAEqQDeU9zS0uzzXfmdjZOZYu-YHkjFoRWcxk5ZW1Q@mail.gmail.com>

Hi,
    how can i download the Python 3.6 documentation.

Regards,
Phanindra k
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180612/bee59ad4/attachment.html>

From report at bugs.python.org  Thu Jun 14 08:09:39 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 14 Jun 2018 12:09:39 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
Message-ID: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>


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

I have found some typos in docs folder using aspell. I have fixed them. The changes are as below : 

Doc/library/codecs.rst - cypher - cipher
Doc/library/email.rst - Protcol - Protocol
Doc/library/importlib.rst - abstact - abstract
Doc/library/xmlrpc.client.rst - unmarsalling - unmarshalling
Doc/license.rst - aheared to - adhered to
Doc/using/cmdline.rst - descibed - described
Doc/whatsnew/3.3.rst - accumlated - accumulated
Doc/whatsnew/3.6.rst - Lollilop - Lollipop
Doc/whatsnew/3.7.rst - direcory - directory

Find typos - 

find . -iname '*rst' | xargs -I{} sh -c "aspell --master=en_US --extra-dicts=en_GB --ignore 3 list < {}" | sort | uniq > typos.txt

Ignore case

tr '[:upper:]' '[:lower:]' < typos.txt | sort | uniq | less

This requires manually looking at output of less and then making changes.

----------
assignee: docs at python
components: Documentation
messages: 319510
nosy: docs at python, xtreak
priority: normal
severity: normal
status: open
title: Spelling mistakes found using aspell
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu Jun 14 08:12:54 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 14 Jun 2018 12:12:54 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1528978374.45.0.121749146738.issue33859@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun 14 09:58:05 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 14 Jun 2018 13:58:05 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1528984685.59.0.947875510639.issue33858@psf.upfronthosting.co.za>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Could you make a PR correcting this bug? If you cannot I can do it instead. :)

----------
nosy: +pablogsal

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

From report at bugs.python.org  Thu Jun 14 10:11:01 2018
From: report at bugs.python.org (aruseni)
Date: Thu, 14 Jun 2018 14:11:01 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1528985461.83.0.947875510639.issue33858@psf.upfronthosting.co.za>


aruseni <aruseni.magiku at gmail.com> added the comment:

I just took a look at the most recent version of this file, and found out that this has already been fixed.

https://github.com/python/cpython/blob/master/Doc/library/multiprocessing.rst

----------

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

From report at bugs.python.org  Thu Jun 14 10:55:32 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 14 Jun 2018 14:55:32 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1528988132.79.0.121749146738.issue15533@psf.upfronthosting.co.za>


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


----------
nosy: +gregory.p.smith
versions: +Python 3.8 -Python 3.5

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

From report at bugs.python.org  Thu Jun 14 11:25:56 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 15:25:56 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
Message-ID: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

IMHO, using "ordered dictionaries" references is somewhat confusing now that dictionaries preserve insertion order.

PR changes this references to "OrderedDict object".

----------
assignee: docs at python
components: Documentation
messages: 319523
nosy: adelfino, docs at python
priority: normal
pull_requests: 7308
severity: normal
status: open
title: doc Avoid "ordered dictionary" references now that dictionaries are ordered
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun 14 11:48:44 2018
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 14 Jun 2018 15:48:44 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1528991324.47.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

"ordered dictionary" means "dict-like object which preserves insertion order".  Both of dict and OrderedDict is "ordered dictionary".

If we change it to OrderedDict, it make harder to change return type from OrderedDict to normal dict.

Do you propose we should never change return type?

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

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

From report at bugs.python.org  Thu Jun 14 11:56:43 2018
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 14 Jun 2018 15:56:43 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1528991803.82.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

Sometime, we chose weak name like "file-like" or "dictionary" over "io.TextIOWrapper" or "dict", to avoid making future improvements harder.

If there are no strong reason to specify concrete type, let's keep using weak name.

In case of enum members, I want to change it to regular dict in Python 3.8, but I'm not sure yet.

----------

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

From report at bugs.python.org  Thu Jun 14 11:57:46 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 14 Jun 2018 15:57:46 +0000
Subject: [docs] [issue33830] Error in the output of one example in the
 httplib docs
In-Reply-To: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>
Message-ID: <1528991866.66.0.121749146738.issue33830@psf.upfronthosting.co.za>


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


----------
title: example output error -> Error in the output of one example in the httplib docs

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

From report at bugs.python.org  Thu Jun 14 13:14:41 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 14 Jun 2018 17:14:41 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1528996481.19.0.947875510639.issue15533@psf.upfronthosting.co.za>


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

Thanks for pointing me at this issue Ned.  It sounds like there is a behavior difference between Windows and POSIX systems related to the current directory and/or which process environment is used by the system call that launches the new process to find the executable.

It seems to have existed "forever" in subprocess module API terms, so I don't know if we should reconcile the corner cases when cwd and/or env are supplied to a single cross platform behavior as that could break existing code.  Such a behavior change _could_ be made but be 3.8 specific.  BUT:  If we did that, it becomes a challenge for people writing code that needs to work on multiple Python versions.  Popen growing yet another bool flag parameter to choose the new behavior is possible, but quite ugly (and unusable on multi-python version code).

I think we should start out by living with the difference - document these platform specific corner case behaviors to minimize surprise.

If we want to provide a way for people to have the same behavior on both, we should document a recommended way to do that.  I believe that entails telling people get an absolute path to their executable themselves before launching the subprocess as that should work the same no matter the cwd or environment?

----------

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

From report at bugs.python.org  Thu Jun 14 13:28:53 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 17:28:53 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1528997333.17.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

Please note that DictReader already mentions "OrderedDict" as a type it returns now. I do see the issue you raise though and I'm not proposing to guarantee that type for next versions.

I see the benefits of using weak names, but "dictionary" alone doesn't seem like a good weak name to me, as it's the common name of an actual type. "ordered dictionary" is the common name of a type, too, which makes the "dictionary" in that phrase less of a weak name. Bacause of this, I don't think we are using weak names in the cases the PR changes.

A dict-like object must preserve insertion order as that's what dict does; specifying it could make people think dicts aren't ordered. I understand a dict-like object as if it were a dict subclass, that is, following the full dict API.

As to what the changes could look like with these things in mind... It's difficult to say without knowing which API are we actually telling people to rely on now: dict, dict-like, OrderedDict, OrderedDict-like?

----------

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

From report at bugs.python.org  Thu Jun 14 13:37:32 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 17:37:32 +0000
Subject: [docs] [issue33862] doc Fix Enum __members__ type
Message-ID: <1528997852.32.0.947875510639.issue33862@psf.upfronthosting.co.za>


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

Documentation says __members__ attribute returns an "ordered dictionary" but it returns a mappingproxy instead.

PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 319532
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Fix Enum __members__ type
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun 14 13:57:40 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 17:57:40 +0000
Subject: [docs] [issue33862] doc Fix Enum __members__ type
In-Reply-To: <1528997852.32.0.947875510639.issue33862@psf.upfronthosting.co.za>
Message-ID: <1528999060.12.0.121749146738.issue33862@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jun 14 14:16:47 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 14 Jun 2018 18:16:47 +0000
Subject: [docs] [issue33862] doc Fix Enum __members__ type
In-Reply-To: <1528997852.32.0.947875510639.issue33862@psf.upfronthosting.co.za>
Message-ID: <1529000207.39.0.947875510639.issue33862@psf.upfronthosting.co.za>


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

Is not returning a mappingproxy an implementation detail? The important thing is that the result is a mapping of names to members, and that it is ordered.

----------
nosy: +barry, eli.bendersky, ethan.furman, serhiy.storchaka

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

From report at bugs.python.org  Thu Jun 14 14:48:42 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 18:48:42 +0000
Subject: [docs] [issue33862] doc Fix Enum __members__ type
In-Reply-To: <1528997852.32.0.947875510639.issue33862@psf.upfronthosting.co.za>
Message-ID: <1529002121.99.0.947875510639.issue33862@psf.upfronthosting.co.za>


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

I can't really say if it the return of __members__ is an implementation detail as there's no mention of that in the doc, but from reading the doc I think it's reasonable to think this is allowed:

import enum

class Colors(enum.Enum):
    RED = enum.auto()
    BLUE = enum.auto()

Colors.__members__['GREEN'] = enum.auto()

And the traceback:

Traceback (most recent call last):
  File "<pyshell#8>", line 1, in <module>
    Colors.__members__['GREEN'] = enum.auto()
TypeError: 'mappingproxy' object does not support item assignment

is somewhat confusing, as the documentation says an "ordered dictionary" is to be returned, and the traceback talks about a mapping proxy.

----------

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

From report at bugs.python.org  Thu Jun 14 15:55:45 2018
From: report at bugs.python.org (Ethan Furman)
Date: Thu, 14 Jun 2018 19:55:45 +0000
Subject: [docs] [issue33862] doc Fix Enum __members__ type
In-Reply-To: <1528997852.32.0.947875510639.issue33862@psf.upfronthosting.co.za>
Message-ID: <1529006145.87.0.947875510639.issue33862@psf.upfronthosting.co.za>


Ethan Furman <ethan at stoneleaf.us> added the comment:

Serhiy is correct.  The exact return type only needs to be ordered, and have appropriate dictionary methods such as `keys()`, `values()`, and `items()`.

The reason a mappingproxy was chosen is exactly because what you just tried is illegal and/or confusing:

- illegal because an Enum cannot be modified that way
- confusing because the dictionary returned is only a copy of the Enum class' __dict__, and successful attempts to modify it would not change the Enum class.

It is an implementation detail because the exact type of dictionary returned could change in the future.

----------
assignee: docs at python -> ethan.furman
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Jun 14 17:43:36 2018
From: report at bugs.python.org (Jason Fried)
Date: Thu, 14 Jun 2018 21:43:36 +0000
Subject: [docs] [issue33864] collections.abc.ByteString does not register
 memoryview
Message-ID: <1529012616.87.0.947875510639.issue33864@psf.upfronthosting.co.za>


New submission from Jason Fried <me at jasonfried.info>:

Looking at the typing Module docs in the section for ByteString

This type represents the types bytes, bytearray, and memoryview.

But collections.abc.ByteString does not have memoryview registered.

Is it because memoryview doesn't support .index()?

----------
assignee: docs at python
components: Documentation
messages: 319557
nosy: docs at python, fried, lukasz.langa
priority: normal
severity: normal
status: open
title: collections.abc.ByteString does not register memoryview
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jun 14 17:46:45 2018
From: report at bugs.python.org (Eric Snow)
Date: Thu, 14 Jun 2018 21:46:45 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1529012805.18.0.947875510639.issue17045@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:


New changeset 9e7c92193cc98fd3c2d4751c87851460a33b9118 by Eric Snow in branch 'master':
bpo-17045:  Improve C-API doc for PyTypeObject. (gh-7413)
https://github.com/python/cpython/commit/9e7c92193cc98fd3c2d4751c87851460a33b9118


----------

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

From report at bugs.python.org  Thu Jun 14 17:47:01 2018
From: report at bugs.python.org (Eric Snow)
Date: Thu, 14 Jun 2018 21:47:01 +0000
Subject: [docs] [issue17045] Improve C-API doc for PyTypeObject
In-Reply-To: <1359245485.06.0.557532055897.issue17045@psf.upfronthosting.co.za>
Message-ID: <1529012821.0.0.121749146738.issue17045@psf.upfronthosting.co.za>


Change by Eric Snow <ericsnowcurrently at gmail.com>:


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

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

From report at bugs.python.org  Thu Jun 14 18:52:28 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 14 Jun 2018 22:52:28 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1529016748.83.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

I believe the discussion in #33863 is relevant. Depending on what the API the user can rely on, perhaps "an ordered mapping" fits here too.

----------

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

From report at bugs.python.org  Thu Jun 14 22:39:13 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 15 Jun 2018 02:39:13 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1529030353.65.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

> Please note that DictReader already mentions "OrderedDict" as a type it returns now.

OK, but PR-7535 changes enum too.

> but "dictionary" alone doesn't seem like a good weak name to me, as it's the common name of an actual type.

As I commented in #33863, "dictionary" is really common weak name defined in glossary.  dict ? dictionary

----------

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

From report at bugs.python.org  Thu Jun 14 22:52:05 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 02:52:05 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1529031125.78.0.947875510639.issue33860@psf.upfronthosting.co.za>


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

Perhaps we can continue the discussion on #33863 as there are more argumnets there, from all points of view, and when a decision is taken there, we can apply it here too.

----------

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

From report at bugs.python.org  Fri Jun 15 02:55:10 2018
From: report at bugs.python.org (Ethan Furman)
Date: Fri, 15 Jun 2018 06:55:10 +0000
Subject: [docs] [issue33860] doc Avoid "ordered dictionary" references now
 that dictionaries are ordered
In-Reply-To: <1528989956.26.0.947875510639.issue33860@psf.upfronthosting.co.za>
Message-ID: <1529045710.05.0.947875510639.issue33860@psf.upfronthosting.co.za>


Ethan Furman <ethan at stoneleaf.us> added the comment:

As I said on the PR:

This feels like an unnecessary change. The phrase "ordered dictionary" does not always refer to an 'OrderedDict`, and there is more than one way to order a dictionary besides insertion order.

As a side note: it's generally better to have different pull requests for different modules.

----------
nosy: +ethan.furman
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Jun 15 04:02:27 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Fri, 15 Jun 2018 08:02:27 +0000
Subject: [docs] [issue33032] Mention implicit cache in struct.Struct docs
In-Reply-To: <1520551378.96.0.467229070634.issue33032@psf.upfronthosting.co.za>
Message-ID: <1529049747.54.0.121749146738.issue33032@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


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

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

From report at bugs.python.org  Fri Jun 15 04:03:42 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Fri, 15 Jun 2018 08:03:42 +0000
Subject: [docs] [issue33032] Mention implicit cache in struct.Struct docs
In-Reply-To: <1520551378.96.0.467229070634.issue33032@psf.upfronthosting.co.za>
Message-ID: <1529049822.86.0.121749146738.issue33032@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
nosy: +ZackerySpytz

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

From report at bugs.python.org  Fri Jun 15 07:05:09 2018
From: report at bugs.python.org (Josh Rosenberg)
Date: Fri, 15 Jun 2018 11:05:09 +0000
Subject: [docs] [issue33864] collections.abc.ByteString does not register
 memoryview
In-Reply-To: <1529012616.87.0.947875510639.issue33864@psf.upfronthosting.co.za>
Message-ID: <1529060709.26.0.947875510639.issue33864@psf.upfronthosting.co.za>


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

memoryview isn't just for bytes strings though; the format can make it a sequence of many types of different widths, meanings, etc. Calling it a BytesString would be misleading in many cases.

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

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

From report at bugs.python.org  Fri Jun 15 10:43:21 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 14:43:21 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
Message-ID: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>


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

PR adds entries for these three terms and a link to the list definition.

----------
assignee: docs at python
components: Documentation
messages: 319619
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add set, frozen set, and tuple entries to Glossary
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jun 15 10:44:51 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 14:44:51 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529073891.1.0.121749146738.issue33869@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 13:50:07 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 17:50:07 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529085007.28.0.947875510639.issue33832@psf.upfronthosting.co.za>


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

It is unclear what problem this issue is meant to serve.  If the reference manual uses 'magic method', I think it should be changed.  Special method names are obvious by their form and need not and should not be labelled.  I think doc policy issues should be discussed on pydev or python-ideas lists.

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

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

From report at bugs.python.org  Fri Jun 15 14:08:18 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 18:08:18 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529086098.2.0.947875510639.issue33847@psf.upfronthosting.co.za>


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

This is definitely an oversight to be corrected.  Index entries for the other binary arithmetic operators point to the table at
https://docs.python.org/3/library/stdtypes.html#numeric-types-int-float-complex
But @ is not in that table since number @ number is meaningless and invalid.  So I agree that the best location is the sentence in
https://docs.python.org/3/reference/expressions.html#binary-arithmetic-operations.

----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy

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

From report at bugs.python.org  Fri Jun 15 14:12:57 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 18:12:57 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529086377.31.0.579493977442.issue33832@psf.upfronthosting.co.za>


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

The original intention of the PR, as shown in this issue, was to add "magic method" in the Glossary as a synonym for "special method", and add "magic method" in Data model (so that people reading Data Model would understand what a "magic method" is).

Then I was requested some changes, and stated I wasn't sure about them.

I don't believe special methods should be explicitly declared in each mention.

The "problem" this PR intended to "solve" was to let people know what a "magic method" is, because as I see it, it has become pretty standard to use "special method" with no indication that it is a synonym of "magic method".

----------

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

From report at bugs.python.org  Fri Jun 15 14:13:26 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 18:13:26 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529086406.12.0.579493977442.issue33832@psf.upfronthosting.co.za>


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

I'll update the PR so that it shows what the original intention was.

----------

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

From report at bugs.python.org  Fri Jun 15 14:24:30 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 18:24:30 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529087070.42.0.69318462047.issue33852@psf.upfronthosting.co.za>


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


New changeset 4fddd4e4069aad9efad999d8d9ce3cd9fb523a5c by Terry Jan Reedy (Andr?s Delfino) in branch 'master':
bpo-33852: Remove misplaced parentheses around 'list'. (GH-7672)
https://github.com/python/cpython/commit/4fddd4e4069aad9efad999d8d9ce3cd9fb523a5c


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

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

From report at bugs.python.org  Fri Jun 15 14:25:44 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 18:25:44 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529087144.58.0.0826556172391.issue33852@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 14:27:38 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 18:27:38 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529087258.1.0.902498594338.issue33852@psf.upfronthosting.co.za>


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


----------
pull_requests: +7329

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

From report at bugs.python.org  Fri Jun 15 14:28:17 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 15 Jun 2018 18:28:17 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529087297.48.0.56676864532.issue33832@psf.upfronthosting.co.za>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Just for clarification. My question in the PR was:

>I think these are not the only occurrences of method referring to a 
>magic method. A quick grep reveals that there are more places where the 
>construction the __something__ method happens. Should we change these 
> too to __something__ special method?

This is because I was not sure if the intention of the PR was changing these everywhere or not. Sorry
if that was interpreted as a change request. :S

----------
nosy: +pablogsal

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

From report at bugs.python.org  Fri Jun 15 14:30:51 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 15 Jun 2018 18:30:51 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529087451.16.0.902498594338.issue33832@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 14:34:17 2018
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 15 Jun 2018 18:34:17 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529087657.48.0.56676864532.issue33832@psf.upfronthosting.co.za>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

A quick grep on the 3.7 branch indicates that the standard documentation includes each of the terms "magic method" and "special method" about the same number of times.  (I didn't check for instances that wrapped lines.)

Perhaps we should decide on just one of these terms and fix references that use the other.  I agree this can be a source of confusion, but having two terms for the same concept is a bug.

I don't think we need to change references to "the __something__ method", because those are specific.  We only need to decide on and consistently use the categorical term for these methods when referring to the entire category.

----------
nosy: +fdrake -pablogsal, rhettinger

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

From report at bugs.python.org  Fri Jun 15 14:40:40 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 18:40:40 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529088040.35.0.56676864532.issue33832@psf.upfronthosting.co.za>


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

Terry:
I have updated the PR with the original intention. You'll see it is much simpler.

Pablo:
Don't worry! I take it as a mistake of my own.

Fred:
I believe synonyms aren't the best things to have, but, if used consistently, they don't pose a real problem. Plus, they are so common, that most probably "magic" will reappear.

----------

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

From report at bugs.python.org  Fri Jun 15 14:43:48 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 18:43:48 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529088228.27.0.56676864532.issue33832@psf.upfronthosting.co.za>


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

For context, I opened this issue after Raymond's reasoning in #33825 (which I agreed with).

----------

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

From report at bugs.python.org  Fri Jun 15 14:45:42 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 18:45:42 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529088342.89.0.56676864532.issue33852@psf.upfronthosting.co.za>


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


New changeset 0113391e3f3db0fea6a9545310dc06aa5ea41461 by Miss Islington (bot) in branch '3.7':
bpo-33852: Remove misplaced parentheses around 'list'. (GH-7672)
https://github.com/python/cpython/commit/0113391e3f3db0fea6a9545310dc06aa5ea41461


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

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

From report at bugs.python.org  Fri Jun 15 14:46:11 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 18:46:11 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529088371.72.0.56676864532.issue33832@psf.upfronthosting.co.za>


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

Sorry, for some reason the PR doesn't show the intended changes. I'm working on fixing it.

----------

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

From report at bugs.python.org  Fri Jun 15 14:48:24 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 18:48:24 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529088504.74.0.56676864532.issue33852@psf.upfronthosting.co.za>


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


New changeset eb4989970ce639845ca17e9a040f55fe704b862e by Miss Islington (bot) in branch '3.6':
bpo-33852: Remove misplaced parentheses around 'list'. (GH-7672)
https://github.com/python/cpython/commit/eb4989970ce639845ca17e9a040f55fe704b862e


----------

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

From report at bugs.python.org  Fri Jun 15 14:49:43 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 18:49:43 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529088583.29.0.902498594338.issue33852@psf.upfronthosting.co.za>


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


----------
pull_requests: +7331

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

From report at bugs.python.org  Fri Jun 15 15:11:48 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 19:11:48 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529089908.11.0.56676864532.issue33832@psf.upfronthosting.co.za>


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

Fred, did you intend to delete people from nosy?

----------

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

From report at bugs.python.org  Fri Jun 15 15:23:02 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 19:23:02 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529090582.89.0.56676864532.issue33847@psf.upfronthosting.co.za>


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


New changeset 695118600fecaa7b95634e168ad7cbbc561fd1ec by Terry Jan Reedy (Andr?s Delfino) in branch 'master':
bpo-33847: Add '@' operator entry to index (GH-7669)
https://github.com/python/cpython/commit/695118600fecaa7b95634e168ad7cbbc561fd1ec


----------

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

From report at bugs.python.org  Fri Jun 15 15:23:40 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 19:23:40 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529090620.12.0.56676864532.issue33852@psf.upfronthosting.co.za>


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


New changeset 184e8ed1eeda3ba869755ff37374dd86f332f30d by Terry Jan Reedy (Andr?s Delfino) in branch '2.7':
[2.7] bpo-33852: Remove misplaced parentheses around 'list'. (GH-7672) (#7716)
https://github.com/python/cpython/commit/184e8ed1eeda3ba869755ff37374dd86f332f30d


----------

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

From report at bugs.python.org  Fri Jun 15 15:24:19 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 19:24:19 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529090659.61.0.902498594338.issue33847@psf.upfronthosting.co.za>


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


----------
pull_requests: +7332

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

From report at bugs.python.org  Fri Jun 15 15:25:01 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 19:25:01 +0000
Subject: [docs] [issue33852] doc Remove parentheses from sequence
 subscription description
In-Reply-To: <1528895542.1.0.947875510639.issue33852@psf.upfronthosting.co.za>
Message-ID: <1529090701.23.0.56676864532.issue33852@psf.upfronthosting.co.za>


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

Guido approved the change on the PR.

----------
assignee: docs at python -> terry.reedy
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Jun 15 15:25:14 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 19:25:14 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529090714.29.0.902498594338.issue33847@psf.upfronthosting.co.za>


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


----------
pull_requests: +7333

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

From report at bugs.python.org  Fri Jun 15 15:30:56 2018
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 15 Jun 2018 19:30:56 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529091056.36.0.56676864532.issue33832@psf.upfronthosting.co.za>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

Indeed, I did not.  Fixed now.  I hope.

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

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

From report at bugs.python.org  Fri Jun 15 15:34:34 2018
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 15 Jun 2018 19:34:34 +0000
Subject: [docs] [issue33832] Make "magic methods" a little more discoverable
 in the docs
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529091274.75.0.902498594338.issue33832@psf.upfronthosting.co.za>


Change by Fred L. Drake, Jr. <fdrake at gmail.com>:


----------
nosy: +pablogsal

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

From report at bugs.python.org  Fri Jun 15 15:42:29 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 19:42:29 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1529091749.23.0.56676864532.issue33854@psf.upfronthosting.co.za>


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


New changeset a9d0b34a5c5d4fdc12bba4f9c1e314e6e132cc65 by Terry Jan Reedy (Andr?s Delfino) in branch 'master':
bpo-33854: Add PEP 461 title to 'See also' note (GH-7688)
https://github.com/python/cpython/commit/a9d0b34a5c5d4fdc12bba4f9c1e314e6e132cc65


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

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

From report at bugs.python.org  Fri Jun 15 15:42:33 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 19:42:33 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529091753.27.0.56676864532.issue33847@psf.upfronthosting.co.za>


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


New changeset c05c0e045ccf6e065c59c193195dc0e9b7242dd4 by Miss Islington (bot) in branch '3.7':
bpo-33847: Add '@' operator entry to index (GH-7669)
https://github.com/python/cpython/commit/c05c0e045ccf6e065c59c193195dc0e9b7242dd4


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

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

From report at bugs.python.org  Fri Jun 15 15:43:40 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 19:43:40 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1529091820.31.0.902498594338.issue33854@psf.upfronthosting.co.za>


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


----------
pull_requests: +7334

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

From report at bugs.python.org  Fri Jun 15 15:44:30 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 19:44:30 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1529091870.29.0.902498594338.issue33854@psf.upfronthosting.co.za>


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


----------
pull_requests: +7335

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

From report at bugs.python.org  Fri Jun 15 15:45:22 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 15 Jun 2018 19:45:22 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529091922.43.0.56676864532.issue33847@psf.upfronthosting.co.za>


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


New changeset cd9ede6b20948af51f9a27b64bd0dfd8909c24f1 by Miss Islington (bot) in branch '3.6':
bpo-33847: Add '@' operator entry to index (GH-7669)
https://github.com/python/cpython/commit/cd9ede6b20948af51f9a27b64bd0dfd8909c24f1


----------

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

From report at bugs.python.org  Fri Jun 15 15:55:39 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 19:55:39 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1529092539.19.0.56676864532.issue33858@psf.upfronthosting.co.za>


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

Doc fixes are routinely backported, when valid, at least within 3.x.  If this was not, I could either be intention or accident.  If the change in master was with a github PR, maybe someone just forgot the backport label.

Is the change in 3.7?  Can either of you find the commit that made the change?

----------
nosy: +davin, pitrou, terry.reedy

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

From report at bugs.python.org  Fri Jun 15 16:04:27 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 15 Jun 2018 20:04:27 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1529093067.48.0.56676864532.issue33858@psf.upfronthosting.co.za>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

It seems that it was this commit:

https://github.com/python/cpython/commit/5619ab2db3a6c62ffaa55e8826cf67b7459fc484

----------

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

From report at bugs.python.org  Fri Jun 15 16:09:08 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 15 Jun 2018 20:09:08 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1529093348.77.0.56676864532.issue33858@psf.upfronthosting.co.za>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

And this PR:

https://github.com/python/cpython/pull/698

----------

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

From report at bugs.python.org  Fri Jun 15 16:12:05 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 20:12:05 +0000
Subject: [docs] [issue33847] doc: Add '@' operator entry to index
In-Reply-To: <1528829054.17.0.947875510639.issue33847@psf.upfronthosting.co.za>
Message-ID: <1529093525.48.0.902498594338.issue33847@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 16:14:34 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 20:14:34 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1529093674.65.0.56676864532.issue33854@psf.upfronthosting.co.za>


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


New changeset ce1bda774ee28fcdc8966e4158ed42b1246a29d0 by Terry Jan Reedy (Miss Islington (bot)) in branch '3.7':
bpo-33854: Add PEP 461 title to 'See also' note (GH-7688) (#7719)
https://github.com/python/cpython/commit/ce1bda774ee28fcdc8966e4158ed42b1246a29d0


----------

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

From report at bugs.python.org  Fri Jun 15 16:14:56 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 20:14:56 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1529093696.2.0.56676864532.issue33854@psf.upfronthosting.co.za>


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


New changeset ae4b2af42ce908cd3872dd4442c9805beb725167 by Terry Jan Reedy (Miss Islington (bot)) in branch '3.6':
bpo-33854: Add PEP 461 title to 'See also' note (GH-7688) (GH-7720)
https://github.com/python/cpython/commit/ae4b2af42ce908cd3872dd4442c9805beb725167


----------

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

From report at bugs.python.org  Fri Jun 15 16:15:39 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 15 Jun 2018 20:15:39 +0000
Subject: [docs] [issue33854] doc Add PEP title in seealso of Built-in Types
In-Reply-To: <1528948238.24.0.947875510639.issue33854@psf.upfronthosting.co.za>
Message-ID: <1529093739.62.0.902498594338.issue33854@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> terry.reedy
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Jun 15 16:28:48 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 15 Jun 2018 20:28:48 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1529094528.19.0.56676864532.issue33858@psf.upfronthosting.co.za>


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

Ok, I've backported to 3.6 in https://github.com/python/cpython/pull/7721

----------
components: +Library (Lib)
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type:  -> behavior

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

From report at bugs.python.org  Fri Jun 15 17:19:58 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 15 Jun 2018 21:19:58 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529097598.63.0.56676864532.issue33869@psf.upfronthosting.co.za>


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

This probably shouldn't be done.  It is not the goal of the glossary to define all built-in types.  We have other sections of the documentation for that purpose.  Also, there is no demonstrated need.

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

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

From report at bugs.python.org  Fri Jun 15 17:38:37 2018
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 15 Jun 2018 21:38:37 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529098717.95.0.902498594338.issue33869@psf.upfronthosting.co.za>


Change by Fred L. Drake, Jr. <fdrake at gmail.com>:


----------
nosy: +fdrake

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

From report at bugs.python.org  Fri Jun 15 17:40:47 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 21:40:47 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529098847.78.0.56676864532.issue33869@psf.upfronthosting.co.za>


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

I thought since dictionary and list is there, tuple/set/frozenset should be, too. But I think you are right.

I'd keep the link to the list definition, though. I didn't add a link to the dictionary definition as "dictionary" seems to be a very open term.

----------

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

From report at bugs.python.org  Fri Jun 15 17:54:35 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 21:54:35 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
Message-ID: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>


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

Glossary talks about list access complexity, but the actual list definition doesn't. I think glossary entries should have more information than actual definitions.

PR adds list access complexity to list definition.

----------
assignee: docs at python
components: Documentation
messages: 319678
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add list access time to list definition
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jun 15 17:59:12 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 15 Jun 2018 21:59:12 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529099952.7.0.902498594338.issue33872@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 23:15:10 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 03:15:10 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
Message-ID: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>


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

IMHO, mentioning MicroPython is a plus because it's a mature project with a focus not covered by any of the other mentioned implementations.

PR adds the mention.

----------
assignee: docs at python
components: Documentation
messages: 319700
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Mention the MicroPython implementation in Introduction
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jun 15 23:17:39 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 03:17:39 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529119059.48.0.902498594338.issue33876@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 23:29:14 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 16 Jun 2018 03:29:14 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1529119754.33.0.56676864532.issue33836@psf.upfronthosting.co.za>


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


New changeset 2707e41a5c7ede30349cc7dbd66f8be564965d7c by Mariatta (Noah Haasis) in branch 'master':
bpo-33836: Recommend keyword-only param for memoization in FAQ (GH-7687)
https://github.com/python/cpython/commit/2707e41a5c7ede30349cc7dbd66f8be564965d7c


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

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

From report at bugs.python.org  Fri Jun 15 23:30:29 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:30:29 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1529119829.4.0.902498594338.issue33836@psf.upfronthosting.co.za>


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


----------
pull_requests: +7350

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

From report at bugs.python.org  Fri Jun 15 23:31:20 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:31:20 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1529119880.49.0.902498594338.issue33836@psf.upfronthosting.co.za>


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


----------
pull_requests: +7351

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

From report at bugs.python.org  Fri Jun 15 23:33:50 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 03:33:50 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
Message-ID: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>


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

Reference 9.1. says: "Under Unix, a complete program can be passed to the interpreter in three forms...".

This also applies to Windows. PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 319703
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Mention Windows along UNIX for script running instructions
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jun 15 23:34:23 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 16 Jun 2018 03:34:23 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1529120063.87.0.56676864532.issue33836@psf.upfronthosting.co.za>


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

Thanks!

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

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

From report at bugs.python.org  Fri Jun 15 23:36:36 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 03:36:36 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529120196.1.0.902498594338.issue33877@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jun 15 23:45:09 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 16 Jun 2018 03:45:09 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529120709.82.0.56676864532.issue33876@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

A reasonable suggestion. Let's make sure that we mention CircuitPython as well.

----------
nosy: +willingc

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

From report at bugs.python.org  Fri Jun 15 23:46:32 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:46:32 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1529120792.94.0.56676864532.issue33836@psf.upfronthosting.co.za>


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


New changeset 5a0bf74d4ec11a246b401896cbfb2e840c13da40 by Miss Islington (bot) in branch '3.7':
bpo-33836: Recommend keyword-only param for memoization in FAQ (GH-7687)
https://github.com/python/cpython/commit/5a0bf74d4ec11a246b401896cbfb2e840c13da40


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

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

From report at bugs.python.org  Fri Jun 15 23:46:41 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 16 Jun 2018 03:46:41 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
Message-ID: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>


New submission from Mariatta Wijaya <mariatta.wijaya at gmail.com>:


New changeset 68680035143a3a6398faa88f067f244c74691d19 by Mariatta (Andr?s Delfino) in branch 'master':
bpo-33571: Improve the glossary description for '...' prompt (GH-6971)
https://github.com/python/cpython/commit/68680035143a3a6398faa88f067f244c74691d19


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

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

From report at bugs.python.org  Fri Jun 15 23:47:09 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 16 Jun 2018 03:47:09 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529120829.37.0.56676864532.issue33571@psf.upfronthosting.co.za>


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

Thanks!

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

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

From report at bugs.python.org  Fri Jun 15 23:47:53 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:47:53 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529120873.42.0.902498594338.issue33571@psf.upfronthosting.co.za>


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


----------
pull_requests: +7353

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

From report at bugs.python.org  Fri Jun 15 23:48:50 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:48:50 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529120930.13.0.902498594338.issue33571@psf.upfronthosting.co.za>


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


----------
pull_requests: +7354

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

From report at bugs.python.org  Fri Jun 15 23:49:47 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:49:47 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529120987.32.0.902498594338.issue33571@psf.upfronthosting.co.za>


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


----------
pull_requests: +7355

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

From report at bugs.python.org  Fri Jun 15 23:50:30 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:50:30 +0000
Subject: [docs] [issue33836] [Good first-time issue] Recommend keyword-only
 param for memoization in FAQ
In-Reply-To: <1528732775.39.0.592728768989.issue33836@psf.upfronthosting.co.za>
Message-ID: <1529121030.45.0.56676864532.issue33836@psf.upfronthosting.co.za>


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


New changeset 2636833e8e9cb16ba3ae7bf776bbfc91f176367c by Miss Islington (bot) in branch '3.6':
bpo-33836: Recommend keyword-only param for memoization in FAQ (GH-7687)
https://github.com/python/cpython/commit/2636833e8e9cb16ba3ae7bf776bbfc91f176367c


----------

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

From report at bugs.python.org  Fri Jun 15 23:58:17 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 03:58:17 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529121497.43.0.56676864532.issue33571@psf.upfronthosting.co.za>


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


New changeset 80c51c4737c6bb51dd76d2ab6c5f7ea75bf118f2 by Miss Islington (bot) in branch '2.7':
bpo-33571: Improve the glossary description for '...' prompt (GH-6971)
https://github.com/python/cpython/commit/80c51c4737c6bb51dd76d2ab6c5f7ea75bf118f2


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

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

From report at bugs.python.org  Sat Jun 16 00:03:22 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 04:03:22 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529121802.42.0.56676864532.issue33571@psf.upfronthosting.co.za>


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


New changeset 380a2b09e8c78b1222f9295e82e7ef34a0e70d99 by Miss Islington (bot) in branch '3.7':
bpo-33571: Improve the glossary description for '...' prompt (GH-6971)
https://github.com/python/cpython/commit/380a2b09e8c78b1222f9295e82e7ef34a0e70d99


----------

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

From report at bugs.python.org  Sat Jun 16 00:08:24 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 04:08:24 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
In-Reply-To: <1529120801.36.0.56676864532.issue33571@psf.upfronthosting.co.za>
Message-ID: <1529122104.62.0.56676864532.issue33571@psf.upfronthosting.co.za>


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


New changeset 8e6428f21699e15b5d96f949db221f20d8466b4b by Miss Islington (bot) in branch '3.6':
bpo-33571: Improve the glossary description for '...' prompt (GH-6971)
https://github.com/python/cpython/commit/8e6428f21699e15b5d96f949db221f20d8466b4b


----------

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

From report at bugs.python.org  Sat Jun 16 01:08:34 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 16 Jun 2018 05:08:34 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529125714.14.0.56676864532.issue33859@psf.upfronthosting.co.za>


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


New changeset c151f7846d6d900c22edaaa77f5f7771b529099e by Serhiy Storchaka (Xtreak) in branch 'master':
bpo-33859: Fix spelling mistakes in docs. (GH-7691)
https://github.com/python/cpython/commit/c151f7846d6d900c22edaaa77f5f7771b529099e


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

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

From report at bugs.python.org  Sat Jun 16 01:09:46 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 05:09:46 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529125786.92.0.902498594338.issue33859@psf.upfronthosting.co.za>


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


----------
pull_requests: +7356

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

From report at bugs.python.org  Sat Jun 16 01:26:41 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 16 Jun 2018 05:26:41 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529126801.8.0.56676864532.issue33859@psf.upfronthosting.co.za>


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


New changeset 416e488415cacec98778da11da401c1b94d92c10 by Miss Islington (bot) in branch '3.7':
bpo-33859: Fix spelling mistakes in docs. (GH-7691)
https://github.com/python/cpython/commit/416e488415cacec98778da11da401c1b94d92c10


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

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

From report at bugs.python.org  Sat Jun 16 01:52:13 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 16 Jun 2018 05:52:13 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529128333.73.0.902498594338.issue33859@psf.upfronthosting.co.za>


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


----------
pull_requests: +7358

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

From report at bugs.python.org  Sat Jun 16 02:33:22 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 16 Jun 2018 06:33:22 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529130801.98.0.56676864532.issue33859@psf.upfronthosting.co.za>


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


New changeset c5ff553ae717c33f86d4fa984ee92de71c467f2a by Serhiy Storchaka (Xtreak) in branch '3.6':
[3.6] bpo-33859: Fix spelling mistakes in docs. (GH-7691). (GH-7750)
https://github.com/python/cpython/commit/c5ff553ae717c33f86d4fa984ee92de71c467f2a


----------

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

From report at bugs.python.org  Sat Jun 16 02:42:59 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 16 Jun 2018 06:42:59 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529131379.35.0.56676864532.issue33859@psf.upfronthosting.co.za>


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

Thanks for finding these mistakes :-)

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

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

From report at bugs.python.org  Sat Jun 16 03:06:20 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 16 Jun 2018 07:06:20 +0000
Subject: [docs] [issue33859] Spelling mistakes found using aspell
In-Reply-To: <1528978179.87.0.947875510639.issue33859@psf.upfronthosting.co.za>
Message-ID: <1529132780.78.0.56676864532.issue33859@psf.upfronthosting.co.za>


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

Thanks much @rhettinger and the team for all the work on documentation. This is my first patch and I am pretty amazed at the smooth experience for a beginner like me with GitHub and helpful bots. I hope to contribute more.

Just wanted to leave a note that this was inspired by the Rust book's work where they have a CI running with aspell to make sure that there are no spelling mistakes in the book. It would require a personal dictionary where all the valid words have to be added. I think given the rate of documentation changes that go into the repository having a personal dictionary will result in merge conflicts and not a feasible option but I just want to put this idea here. The initial work requires me to a manual scan of 10k words and hence I might have missed some words or assumed some spellings as correct. I think this can be used for code comments as well but would require even more attention since the dictionary file will be large.

Reference : https://github.com/rust-lang/book/blob/a5c9f1f9fbcda0a6e16ea80e64452b33006f4127/ci/spellcheck.sh#L56

Command to generate a personal file : 

cd Docs && find . -iname '*rst' | xargs -I{} sh -c "aspell --master=en_US --extra-dicts=en_GB --ignore 3 list < {}" | sort | uniq > typos.txt

typos.txt : https://gist.github.com/tirkarthi/d49ac3fdce93c1e3ab4b85b5e1c82b49

Thanks again :)

----------

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

From report at bugs.python.org  Sat Jun 16 03:26:50 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 16 Jun 2018 07:26:50 +0000
Subject: [docs] [issue33864] collections.abc.ByteString does not register
 memoryview
In-Reply-To: <1529012616.87.0.947875510639.issue33864@psf.upfronthosting.co.za>
Message-ID: <1529134010.13.0.56676864532.issue33864@psf.upfronthosting.co.za>


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

The docs should be made more precise.  Perhaps, "This type represents the types bytes, bytearray, and memoryview of byte sequences"?

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

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

From report at bugs.python.org  Sat Jun 16 03:40:29 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 16 Jun 2018 07:40:29 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529134829.57.0.56676864532.issue33876@psf.upfronthosting.co.za>


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

IIRC, Guido recognized only PyPy, Jython, and IronPython as alternate conforming implementations.   A number of other projects were python-like but were also going off in their own directions not subject to his pronouncements.

MicroPython is a pretty cool project but I don't think that its goal is for most code written for CPython would run on MicroPython or vice-versa.

That said, somewhere in the docs (a FAQ entry) there should be a list some of pythonesque implementation like MicroPython, CircuitPython, CPython, VPython, etc.

IMO, the Language Reference is the wrong place.  That document (which used to be subtitled "for language lawyers only") is intended to be the most precise and offical specification of the Python language.  It doesn't make sense to reference implementations that don't follow the specification.

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

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

From report at bugs.python.org  Sat Jun 16 03:43:13 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 16 Jun 2018 07:43:13 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529134993.65.0.56676864532.issue33876@psf.upfronthosting.co.za>


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

Addenda:  Somewhere in the annals of our history this was discussed before (perhaps dating back to Stackless Python).

----------

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

From report at bugs.python.org  Sat Jun 16 08:32:11 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 16 Jun 2018 12:32:11 +0000
Subject: [docs] [issue33830] Error in the output of one example in the
 httplib docs
In-Reply-To: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>
Message-ID: <1529152331.14.0.902498594338.issue33830@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun 16 09:01:46 2018
From: report at bugs.python.org (Julien Palard)
Date: Sat, 16 Jun 2018 13:01:46 +0000
Subject: [docs] [issue33878] Doc: Assignment statement to tuple or list:
 case missing.
Message-ID: <1529154106.75.0.56676864532.issue33878@psf.upfronthosting.co.za>


New submission from Julien Palard <julien+python at palard.fr>:

In [1] I read:

> If the target list is a comma-separated list of targets, or a single target in square brackets

This come from https://bugs.python.org/issue23275 (patch is [2]).

I suspect there's a missing case "list of targets in square brackets" (and to be pedantic "list of targets in parenthesis").

The specialized documentation about single-valued targets in sequence-like construction come from this difference:

    >>> (a) = 42
    >>> a
    42

    >>> [a] = [42]
    >>> a
    42


which is correctly described the line before:

> If the target list is a single target in parentheses: The object is assigned to that target.

So the correct way to state it may be:

> Else the object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets.

The `Else`, coupled with the existing "Assignment of an object to a target list, optionally enclosed in parentheses or square brackets" covers properly the cases:

- Multiple target separated by comas (already covered)
- Multiple target enclosed by parenthesis and brackets (not covered)
- Single target enclosed by angle brackets (already covered)


[1]: https://docs.python.org/3.7/reference/simple_stmts.html#assignment-statements
[2]: https://bugs.python.org/file42878/issue23275_v4.diff

----------
assignee: docs at python
components: Documentation
messages: 319735
nosy: docs at python, martin.panter, mdk
priority: normal
severity: normal
status: open
title: Doc: Assignment statement to tuple or list: case missing.
type: enhancement

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

From report at bugs.python.org  Sat Jun 16 09:32:49 2018
From: report at bugs.python.org (Martin Panter)
Date: Sat, 16 Jun 2018 13:32:49 +0000
Subject: [docs] [issue33878] Doc: Assignment statement to tuple or list:
 case missing.
In-Reply-To: <1529154106.75.0.56676864532.issue33878@psf.upfronthosting.co.za>
Message-ID: <1529155969.73.0.56676864532.issue33878@psf.upfronthosting.co.za>


Martin Panter <vadmium+py at gmail.com> added the comment:

I think I intended the third option to include all comma-separated lists, including:

a, b, c = x  # No brackets
(a, b, c) = x  # Round brackets
[a, b, c] = x  # Square brackets
a, = x  # Single target with comma

Perhaps something like this would be clearer:

* If the target list is
    * a comma-separated list of targets, with or without brackets, or
    * a single target with a trailing comma, with or without brackets, or
    * a single target in square brackets,
  the object must be . . .

The empty target list case could also be merged. Then the only differentiation is between a single target (no comma, optional round brackets) and iterable unpacking.

----------

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

From report at bugs.python.org  Sat Jun 16 09:36:04 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 13:36:04 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529156164.24.0.56676864532.issue33876@psf.upfronthosting.co.za>


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

Sorry, I didn't knew that :) I'll update the PR adding an entry in the FAQ.

With "CPython" in "pythonesque implementation like MicroPython, CircuitPython, CPython" did you mean Cython?

----------

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

From report at bugs.python.org  Sat Jun 16 10:24:37 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 16 Jun 2018 14:24:37 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529159077.76.0.56676864532.issue33876@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

Thanks Raymond :-)

The FAQ seems like a good place to share. Cython would be a nice addition and perhaps IPython too.

----------

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

From report at bugs.python.org  Sat Jun 16 10:34:45 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 16 Jun 2018 14:34:45 +0000
Subject: [docs] [issue22571] Remove import * recommendations and examples in
 doc?
In-Reply-To: <1412627004.13.0.564055290321.issue22571@psf.upfronthosting.co.za>
Message-ID: <1529159685.22.0.56676864532.issue22571@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

Hi @terry.reedy @rhettinger,

I'm triaging the 'turtle' open issues. I'm wondering if we can close this issue with a resolution of "Remind". If there are '*' imports that folks feel strongly about changing, then those could be opened now or in the future as a new, more narrowly scoped issue(s) with cleared next actions for contributors.

----------
nosy: +willingc

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

From report at bugs.python.org  Sat Jun 16 10:52:59 2018
From: report at bugs.python.org (Julien Palard)
Date: Sat, 16 Jun 2018 14:52:59 +0000
Subject: [docs] [issue33878] Doc: Assignment statement to tuple or list:
 case missing.
In-Reply-To: <1529154106.75.0.56676864532.issue33878@psf.upfronthosting.co.za>
Message-ID: <1529160779.7.0.56676864532.issue33878@psf.upfronthosting.co.za>


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

Agree, the empty list could be merged, the only special-case is the "single item in parenthesis", as always.

I'm still exploring the path to simplicity over explicitly listing everything (but in the reference, explicitly listing could be what we need):

    Assignment of an object to a target list, optionally enclosed in parentheses or square brackets, is recursively defined as follows.

        If the target list is a single target in parentheses: The object is assigned to that target.
        Else the object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets.

What do you think? Should we go full-explicit, with trailing comas and everything?

----------

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

From report at bugs.python.org  Sat Jun 16 11:00:18 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 16 Jun 2018 15:00:18 +0000
Subject: [docs] [issue33830] Error in the output of one example in the
 httplib docs
In-Reply-To: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>
Message-ID: <1529161218.53.0.56676864532.issue33830@psf.upfronthosting.co.za>


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

I was making a patch for this and both Python 2.7 and Python 3.6 returned "404 OK" for the example instead of "404 Not Found". I think the end-point is misleading and it's better to use httpbin.org for this. 

cpython git:(master)   ./python
Python 3.8.0a0 (heads/master:c151f78, Jun 16 2018, 14:50:28)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import http.client
>>> conn = http.client.HTTPSConnection("www.python.org")
>>> conn.request("GET", "/")
>>> r1 = conn.getresponse()
>>> print(r1.status, r1.reason)
200 OK
>>> data1 = r1.read()
>>> conn.request("GET", "/parrot.spam")
>>> r2 = conn.getresponse()
>>> print(r2.status, r2.reason)
404 OK
>>> data2 = r2.read()
>>> conn.close()
>>> conn = http.client.HTTPSConnection("httpbin.org")
>>> conn.request("GET", "/status/404")
>>> r2 = conn.getresponse()
>>> print(r2.status, r2.reason)
404 NOT FOUND


?  ~ python2.7
Python 2.7.14 (default, Mar 12 2018, 13:54:56)
[GCC 4.2.1 Compatible Apple LLVM 7.0.2 (clang-700.1.81)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import httplib
>>> conn = httplib.HTTPSConnection("www.python.org")
>>> conn.request("GET", "/")
>>> r1 = conn.getresponse()
>>> print r1.status, r1.reason
200 OK
>>> data1 = r1.read()
>>> conn.request("GET", "/parrot.spam")
>>> r2 = conn.getresponse()
>>> print r2.status, r2.reason
404 OK
>>>

----------

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

From report at bugs.python.org  Sat Jun 16 11:37:41 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 16 Jun 2018 15:37:41 +0000
Subject: [docs] [issue27461] Optimize PNGs
In-Reply-To: <1467894574.39.0.144098385194.issue27461@psf.upfronthosting.co.za>
Message-ID: <1529163461.58.0.902498594338.issue27461@psf.upfronthosting.co.za>


Change by Carol Willing <willingc at gmail.com>:


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

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

From report at bugs.python.org  Sat Jun 16 11:54:54 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 16 Jun 2018 15:54:54 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529164494.57.0.902498594338.issue33877@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun 16 11:55:33 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 16 Jun 2018 15:55:33 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529164533.47.0.902498594338.issue33877@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun 16 12:10:31 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 16:10:31 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529165431.57.0.56676864532.issue33876@psf.upfronthosting.co.za>


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

What do you think about also mentioning Skulpt and Brython? On one hand, they -like MicroPython/CirtcuitPython- cover a focus no other implementation does (and a special one: client side Web scripting); but on the other hand, we shouldn't make space for everybody to add her/his pythonesque implementation.

----------

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

From report at bugs.python.org  Sat Jun 16 12:16:52 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 16 Jun 2018 16:16:52 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529165812.55.0.56676864532.issue33876@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

I think your suggestion for Brython and Skulpt is excellent. I believe that it's important to point out that Python can be used client-side, and both your suggestions have been around for a while, are stable, and often used in large courses such as OpenEdX.

----------

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

From report at bugs.python.org  Sat Jun 16 12:47:27 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 16 Jun 2018 16:47:27 +0000
Subject: [docs] [issue22571] Remove import * recommendations and examples in
 doc?
In-Reply-To: <1412627004.13.0.564055290321.issue22571@psf.upfronthosting.co.za>
Message-ID: <1529167647.54.0.56676864532.issue22571@psf.upfronthosting.co.za>


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

I am going to accept Raymond's rejection of a general change.  I will reconsider the tkinter doc should I ever work on it.

For IDLE code, I have settled on 'from tkinter import Tk, Text, ..., perhaps followed by 'from tkinter.ttk import Scrollbar, ...'.  But having alternate sources for many modules is a special case.  Listing each object is a bit more effort*, but I like knowing what is imported, from where after reading the module header. (* With complete tests, NameErrors quickly expose omissions.)

Carol, thank you for bumping this issue.

----------
resolution:  -> rejected
stage: needs patch -> resolved
status: open -> closed
type:  -> enhancement

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

From report at bugs.python.org  Sat Jun 16 14:36:51 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 16 Jun 2018 18:36:51 +0000
Subject: [docs] [issue24978] Contributing to Documentation. Translation to
 Russian.
In-Reply-To: <1441109047.57.0.29993860249.issue24978@psf.upfronthosting.co.za>
Message-ID: <1529174211.18.0.56676864532.issue24978@psf.upfronthosting.co.za>


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

There are now several official translations: see current doc pages, the bottom of https://devguide.python.org/experts/, and https://www.python.org/dev/peps/pep-0545/.  According to the pep, discussion is on doc-sig.  https://mail.python.org/mailman/listinfo/doc-sig

'third party' is not quite right, but there is no 'separate repository and issues tracker' selection.

Carol, perhaps devguide 7. Documenting Python should have a short new section 7.6 Translations with at least the above info, better formatted.

----------
nosy: +terry.reedy, willingc
resolution:  -> third party
stage:  -> resolved
status: open -> closed
title: Contributing to Python 2x and 3x Documentation. Translation to Russian. -> Contributing to Documentation. Translation to Russian.

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

From report at bugs.python.org  Sat Jun 16 16:14:29 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 16 Jun 2018 20:14:29 +0000
Subject: [docs] [issue29560] Tkinter and turtle graphics fill differs
 between Windows and *nix
In-Reply-To: <1487100128.83.0.366459584593.issue29560@psf.upfronthosting.co.za>
Message-ID: <1529180069.11.0.56676864532.issue29560@psf.upfronthosting.co.za>


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

Behavior has not changed.  It is a legitimate doc issue for both tkinter and turtle.

The turtle intro, https://docs.python.org/3/library/turtle.html#introduction, currently 24.1.1. says nothing about the sidebar and image.  I think there should be a short paragraph added, which includes "The image was drawn on Linux.  On Windows, the star will be filled in solid." 

The filling doc, https://docs.python.org/3/library/turtle.html#filling, should also have a note.

If you do a PR, I will review.

The tkinter docs should be handled separately.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
title: Turtle graphics fill behavior differs between versions -> Tkinter and turtle graphics fill differs between Windows and *nix
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Sat Jun 16 19:49:13 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 23:49:13 +0000
Subject: [docs] [issue33882] doc Mention breakpoint() in debugger-related FAQ
Message-ID: <1529192953.25.0.56676864532.issue33882@psf.upfronthosting.co.za>


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

IMHO, it's a good opportunity to advertise the convenience of breakpoint().

PR adds a mention.

----------
assignee: docs at python
components: Documentation
messages: 319796
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Mention breakpoint() in debugger-related FAQ
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Jun 16 19:52:00 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 16 Jun 2018 23:52:00 +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: <1529193120.37.0.902498594338.issue33882@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun 16 19:52:17 2018
From: report at bugs.python.org (Martin Panter)
Date: Sat, 16 Jun 2018 23:52:17 +0000
Subject: [docs] [issue33878] Doc: Assignment statement to tuple or list:
 case missing.
In-Reply-To: <1529154106.75.0.56676864532.issue33878@psf.upfronthosting.co.za>
Message-ID: <1529193137.14.0.56676864532.issue33878@psf.upfronthosting.co.za>


Martin Panter <vadmium+py at gmail.com> added the comment:

I think it is okay to leave out the options for the unpacking case. But I think it is worth clarifying that the single-target case also applies without parentheses, but that it doesn?t apply if there is a trailing comma. So:

???
If the target list is a single target with no trailing comma, optionally in parentheses, the object is assigned to that target.

Else the object must be an iterable . . .
???

----------

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

From report at bugs.python.org  Sat Jun 16 20:52:16 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 00:52:16 +0000
Subject: [docs] [issue33883] doc Mention mypy, pytype and PyAnnotate in FAQ
Message-ID: <1529196736.16.0.56676864532.issue33883@psf.upfronthosting.co.za>


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

As far as I know, mypy and pytype are more advanced that any of the other tools mentioned in the FAQ for static analysis, however we are not touching them.

PR adds mentions.

----------
assignee: docs at python
components: Documentation
messages: 319798
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Mention mypy, pytype and PyAnnotate in FAQ
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Jun 16 20:53:45 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 00:53:45 +0000
Subject: [docs] [issue33883] doc Mention mypy, pytype and PyAnnotate in FAQ
In-Reply-To: <1529196736.16.0.56676864532.issue33883@psf.upfronthosting.co.za>
Message-ID: <1529196825.38.0.902498594338.issue33883@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jun 16 22:10:54 2018
From: report at bugs.python.org (Ammar Askar)
Date: Sun, 17 Jun 2018 02:10:54 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529201454.2.0.56676864532.issue33872@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

I don't think this should be documented at all, not in the glossary, nor the stdtypes section. A quick search through of the glossary and stdtypes indicates that the glossary entry of list is the only place where a time complexity is documented.

The problem with documenting this is that the underlying complexity is an implementation detail, by saying its always O(1), alternative implementations like PyPy etc cannot freely implement lists in whatever way they wish.

----------
nosy: +ammar2

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

From report at bugs.python.org  Sat Jun 16 22:14:28 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 02:14:28 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529201668.65.0.56676864532.issue33872@psf.upfronthosting.co.za>


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

If O(1) time complexity for element access is not a requirement (which it seems it's not), I agree that this PR as it is should be closed, and the Glossary entry should have this detail removed.

In that case, can I edit the PR or should I open a new one?

----------

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

From report at bugs.python.org  Sat Jun 16 22:16:12 2018
From: report at bugs.python.org (Ammar Askar)
Date: Sun, 17 Jun 2018 02:16:12 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529201772.24.0.56676864532.issue33872@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

I'd say edit the PR and the bug tracker issue to reflect the change. Though you might want to wait for the opinion of a core dev or someone with more documentation experience than me.

----------

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

From report at bugs.python.org  Sun Jun 17 01:44:46 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 17 Jun 2018 05:44:46 +0000
Subject: [docs] [issue33095] Cross-reference isolated mode from relevant
 locations
In-Reply-To: <1521352636.34.0.467229070634.issue33095@psf.upfronthosting.co.za>
Message-ID: <1529214286.39.0.56676864532.issue33095@psf.upfronthosting.co.za>


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

There are four parts where I could see sys.path manipulation being mentioned while running scripts : 

-c option (https://docs.python.org/3/using/cmdline.html#cmdoption-c)
-m option (https://docs.python.org/3/using/cmdline.html#cmdoption-m)
-  (input option) 
<script> (running as script)

For some reason I am not able to hyperlink to - and <script> parts since they are not a command line option but a method to execute code. I could sys.path references in windows (https://docs.python.org/3/using/windows.html#finding-modules) where `._pth` file is mentioned to completely override sys.path. 

I am new to adding documentation so add in if it needs a simple reference or explain the option which I feel redundant and useful at the same time kind of missing the point of cross-referencing. I am attaching a patch for `-m` and <script> option. Feel free to add comments and if I am missing something.

Thanks

----------
keywords: +patch
nosy: +xtreak
Added file: https://bugs.python.org/file47644/33095.patch

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

From report at bugs.python.org  Sun Jun 17 03:11:41 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 17 Jun 2018 07:11:41 +0000
Subject: [docs] [issue33586] 2.7.15 missing release notes on download page
In-Reply-To: <1526833708.19.0.682650639539.issue33586@psf.upfronthosting.co.za>
Message-ID: <1529219501.84.0.56676864532.issue33586@psf.upfronthosting.co.za>


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

This is tracked at https://github.com/python/pythondotorg/issues/1252

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

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

From report at bugs.python.org  Sun Jun 17 04:09:36 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 17 Jun 2018 08:09:36 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529222976.45.0.56676864532.issue33872@psf.upfronthosting.co.za>


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

List is documented in ?sequence? section and O(1) index access is typical for sequences.  At least, every builtin types have it.
So adding such note only to list seems a bit curious to me.

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

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

From report at bugs.python.org  Sun Jun 17 06:47:16 2018
From: report at bugs.python.org (Julien Palard)
Date: Sun, 17 Jun 2018 10:47:16 +0000
Subject: [docs] [issue33878] Doc: Assignment statement to tuple or list:
 case missing.
In-Reply-To: <1529154106.75.0.56676864532.issue33878@psf.upfronthosting.co.za>
Message-ID: <1529232436.97.0.902498594338.issue33878@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 07:40:55 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 17 Jun 2018 11:40:55 +0000
Subject: [docs] [issue33095] Cross-reference isolated mode from relevant
 locations
In-Reply-To: <1521352636.34.0.467229070634.issue33095@psf.upfronthosting.co.za>
Message-ID: <1529235655.5.0.56676864532.issue33095@psf.upfronthosting.co.za>


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

xtreak: if you're familiar with GitHub workflows, then we now accept docs and code updates as GitHub PRs: https://devguide.python.org/pullrequest/

The parts about running the tests aren't exactly relevant here, what's more relevant is building the documentation: https://devguide.python.org/documenting/#building-the-documentation

In relation to your draft patch, I think that's a good starting point, but for -c and -m, it's the current directory that gets omitted, rather than "the script's directory" (that isn't well defined when anything other than a path is passed in).

For making "-" and "<script>" hyperlinkable, you'll need to add a label definition to the Sphinx source code immediately before those description sections. I'd suggest ".. _cmdarg-dash:" and ".. _cmdarg-script:" so the resulting anchors look similar to the option ones, without being the same.

----------

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

From report at bugs.python.org  Sun Jun 17 09:34:18 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 13:34:18 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529242458.6.0.56676864532.issue33872@psf.upfronthosting.co.za>


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

INADA, I believe that piece of information is on the Glossary just to make the difference with a "linked list", but in that case, it should be in the list definition too, as it's fair to think people can learn what a list is by reading its definition first, instead of the Glossary entry.

I believe Ammar's reasoning is right, though. If the time complexity of the task is not required, then we should remove those mentions.

Benjamin, I'm adding you as you introduced the change. Perhaps you can bring some light? Even if 10 years have passed? :P

----------
nosy: +benjamin.peterson

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

From report at bugs.python.org  Sun Jun 17 09:42:56 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 17 Jun 2018 13:42:56 +0000
Subject: [docs] [issue33095] Cross-reference isolated mode from relevant
 locations
In-Reply-To: <1521352636.34.0.467229070634.issue33095@psf.upfronthosting.co.za>
Message-ID: <1529242976.85.0.902498594338.issue33095@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 10:54:03 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 17 Jun 2018 14:54:03 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529247243.74.0.56676864532.issue33872@psf.upfronthosting.co.za>


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

In case of "difference with linked-list", I don't want to make list definition longer and longer for readers only small part of people.  I think that's why difference with "linked-list" is documented only in glossary.

By adding all information for non-zero group of people, resulting document will be very long, redundant, and suitable for no one.

We should effort to make document "necessary and sufficient" state.

---

In case of time complexity, I agree it's useful for users.  Not only for list, but also for all basic operation of basic types, too.

But at my understanding, we don't have formal spec for time complexity of stdtypes.  We use consensus instead.

I think we can say random access is O(1) for bytes, bytearray, tuple, list, and range (except time for building large numeric value).

On the other hand, I'm not sure about str.  Other Python implementation will want to use UTF-8 based implementation of str.

----------

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

From report at bugs.python.org  Sun Jun 17 11:57:01 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 15:57:01 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529251021.03.0.56676864532.issue33872@psf.upfronthosting.co.za>


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

IMHO, if we deem it useful for users not to expect the time complexity of a linked list for list elements access to the extent of adding a comment in the glossary, there's no reason it isn't useful to someone who is reading the actual list definition. Moreover, I don't see the reason why someone would read the list glossary entry after reading the list definition.

I believe glossary entries should be a (rather small) subset of the topics they touch.

All of this, of course, if Ammar is not right about list not requiring O(1) time complexity.

Please note that, while interesting, I'm not proposing to document the time complexity in list definition per se, but only because it's already documented in the glossary.

----------

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

From report at bugs.python.org  Sun Jun 17 12:57:13 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sun, 17 Jun 2018 16:57:13 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529251021.03.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <CAEfz+Tyc4N+GKY0gGjhj+h1piPX8_aHUPGFKt8sKPDzfpQJ0jQ@mail.gmail.com>


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

Andr?s Delfino <report at bugs.python.org>:

>
> Andr?s Delfino <adelfino at gmail.com> added the comment:
>
> IMHO, if we deem it useful for users not to expect the time complexity of
> a linked list for list elements access to the extent of adding a comment in
> the glossary, there's no reason it isn't useful to someone who is reading
> the actual list definition.

I didn't deny "it is useful to someone."

I just worry about adding many random notes "useful to someone" in document
"everyone" reads.  It's worse than nothing.

When writing document for wide readers, adding such "useful to someone"
note is bad idea.
We should focus on "important to everyone" or "critical for someone".

Moreover, I don't see the reason why someone would read the list glossary
> entry after reading the list definition.
>

That's why "useful to only someone" information can be noted on glossary,
but no on main document.

I believe glossary entries should be a (rather small) subset of the topics
> they touch.
>

I don't think so. Glossary is the best place to document "no definition,
but used conventionally" word which is not defined in other document

Current glossary has random tips and notes like this.  They don't bother
readers of main document.

I don't think "document in glossary" is not enough reason to add it on main
definition, because it may lead bad S/N ratio.

Of course, if it's very common pitfall for many people, it's worth enough
to note in the definition.

But IList in C# is sequence and LinkedList doesn't implement it. If many
people feel the word "list" implies "linked list", why they choose the name
"IList"?  That's why I think the note is only for someone, not for
 most readers.

So I'm -0.5 on adding it in list definition, and +0 on removing it from
glossary.

----------

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

From report at bugs.python.org  Sun Jun 17 13:21:31 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 17:21:31 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
Message-ID: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>


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

The reporthook of urllib.request.urlretrieve is treated as a function hook, while the right term is "callable".

PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 319822
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Replace "hook function" with "callable" in urllib.request.urlretrieve
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 17 13:22:16 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 17:22:16 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529256136.9.0.902498594338.issue33885@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 14:05:50 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 18:05:50 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
Message-ID: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>


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

IHMO, having all questions put together is really useful.

----------
assignee: docs at python
components: Documentation
messages: 319824
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add TOC in Design and History FAQ
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 17 14:06:54 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 18:06:54 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529258814.85.0.902498594338.issue33887@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 14:13:18 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 18:13:18 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
Message-ID: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>


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

The FAQ talks about list and dictionary implementation details using "Python". I believe this should be changed to CPython.

----------
assignee: docs at python
components: Documentation
messages: 319825
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Use CPython instead of Python when talking about implementation details
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 17 14:15:21 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 18:15:21 +0000
Subject: [docs] [issue33888] Use CPython instead of Python when talking
 about implementation details
In-Reply-To: <1529259198.28.0.56676864532.issue33888@psf.upfronthosting.co.za>
Message-ID: <1529259321.1.0.902498594338.issue33888@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 15:32:50 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 19:32:50 +0000
Subject: [docs] [issue33889] doc Mention Python on-line shell in Tutorial
Message-ID: <1529263970.37.0.56676864532.issue33889@psf.upfronthosting.co.za>


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

If having a link to that specific console is not deemed appropriate, perhaps we can point to PythonAnywhere.

IMHO, it's good to let users know that they can try Python right away without needing to install.

----------
assignee: docs at python
components: Documentation
messages: 319829
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Mention Python on-line shell in Tutorial
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 17 15:34:02 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 19:34:02 +0000
Subject: [docs] [issue33889] doc Mention Python on-line shell in Tutorial
In-Reply-To: <1529263970.37.0.56676864532.issue33889@psf.upfronthosting.co.za>
Message-ID: <1529264042.72.0.902498594338.issue33889@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 17:54:21 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 17 Jun 2018 21:54:21 +0000
Subject: [docs] [issue33889] doc Mention Python on-line shell in Tutorial
In-Reply-To: <1529263970.37.0.56676864532.issue33889@psf.upfronthosting.co.za>
Message-ID: <1529272461.75.0.56676864532.issue33889@psf.upfronthosting.co.za>


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

Thanks, but I just don't think this is needed but adding complexity.

----------
nosy: +Mariatta
resolution:  -> remind
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Jun 17 18:14:59 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 17 Jun 2018 22:14:59 +0000
Subject: [docs] [issue33889] doc Mention Python on-line shell in Tutorial
In-Reply-To: <1529263970.37.0.56676864532.issue33889@psf.upfronthosting.co.za>
Message-ID: <1529273699.74.0.902498594338.issue33889@psf.upfronthosting.co.za>


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


----------
resolution: remind -> rejected

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

From report at bugs.python.org  Sun Jun 17 18:23:29 2018
From: report at bugs.python.org (Patrick Lehmann)
Date: Sun, 17 Jun 2018 22:23:29 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529274208.95.0.56676864532.issue28710@psf.upfronthosting.co.za>


Patrick Lehmann <Patrick.Lehmann at tu-dresden.de> added the comment:

Any progress on that issue?

1.5 years passed by and it should be possible to fix the Python documentation in that time, right?

----------

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

From report at bugs.python.org  Sun Jun 17 19:04:29 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 17 Jun 2018 23:04:29 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529276669.59.0.56676864532.issue33876@psf.upfronthosting.co.za>


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

I have updated the PR with a FAQ that mentions all implementations mentioned here, except Cython and Stackless Python.

I added RapydScript as it's used by VPython for Web visualization, in the category of client-side scripting pythonesque languages/implementations.

I didn't add Cython because it's not clear to me if it's useful for creating extension modules in a pythonesque language, or if it's also useful by it's own.

I didn't add Stackless Python because it doesn't fit with the "problem domain specific" category I've chosen for the FAQ.

I'm pretty sure this will need a few iterations, but at least we have an starting point :)

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

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

From report at bugs.python.org  Sun Jun 17 19:53:09 2018
From: report at bugs.python.org (R. David Murray)
Date: Sun, 17 Jun 2018 23:53:09 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529279589.2.0.56676864532.issue28710@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

Thanks for coming back to this.

We're accepting PRs via github now, so the next step now would be to make it into a PR.  

Sometimes things just get forgotten and you have to nudge them to get them moving (see the devguide for guidelines about when it is appropriate to nudge an issue).

----------

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

From report at bugs.python.org  Sun Jun 17 20:34:00 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 18 Jun 2018 00:34:00 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529282040.12.0.56676864532.issue28710@psf.upfronthosting.co.za>


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

I agree with David about replacing `x' with 'x' instead of ``x``, so please make this change.  Do you know what ``x.y = v'' is supposed to mean?

David, do you want one PR with 139+ changes, or should we start with fewer?  Patrick, are these usages scattered over numerous files or concentrated in a few?

----------

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

From report at bugs.python.org  Sun Jun 17 20:41:34 2018
From: report at bugs.python.org (Patrick Lehmann)
Date: Mon, 18 Jun 2018 00:41:34 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529282494.43.0.56676864532.issue28710@psf.upfronthosting.co.za>


Patrick Lehmann <Patrick.Lehmann at tu-dresden.de> added the comment:

Against what branch should I create the PR?

I was a huge number of changes.
I think I'll create multiple PRs to ease the review.

----------

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

From report at bugs.python.org  Sun Jun 17 20:44:00 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 00:44:00 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
Message-ID: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>


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

PR adds some "or she/her".

----------
assignee: docs at python
components: Documentation
messages: 319840
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add a couple of "or she/her"
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jun 17 20:47:08 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 00:47:08 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529282828.7.0.902498594338.issue33892@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jun 17 20:53:10 2018
From: report at bugs.python.org (Emanuel Barry)
Date: Mon, 18 Jun 2018 00:53:10 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529283190.4.0.56676864532.issue33892@psf.upfronthosting.co.za>


Emanuel Barry <barry at dadadata.net> added the comment:

Nice initiative! I like the idea of moving towards more inclusive documentation; as an addition, I would recommend using they/them/their instead - it's less clumsy to read (also, singular they is perfectly valid English) and includes everyone, even those who may not use either he/him or she/her pronouns :)

All in all, great initiative, I encourage you to keep going in that direction!

----------
nosy: +ebarry

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

From report at bugs.python.org  Sun Jun 17 20:55:10 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 00:55:10 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529283310.2.0.56676864532.issue33892@psf.upfronthosting.co.za>


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

Yeap, Ammar just told me the same suggestion on GitHub :)

PR will be a little more ambitious now, as I'm replacing all he/him/she/her mentions.

----------

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

From report at bugs.python.org  Sun Jun 17 21:08:31 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 18 Jun 2018 01:08:31 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529284110.96.0.56676864532.issue28710@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

master, and maybe backport from there, unless the PR never touches master.

I wonder if we should bring this up on pydev.  Without discussion and agreement, someone might object just because there are so many changes.  Or someone might say that they want the 'illegal' markup kept.

I see that the one docstring you linked to, 
https://github.com/python/cpython/blob/master/Lib/configparser.py?ts=2#L26
had 9 occurences, 1 for each parameter.

I never see any warnings.  It must be that our build system somewhere discards them.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Sun Jun 17 21:39:28 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 18 Jun 2018 01:39:28 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529285968.34.0.56676864532.issue28710@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

This should probably be discussed on python-dev.  In particular, changing from single backticks to double backticks is something that makes Sphinx happy but will uglify the docstrings for all other ways of viewing the docs.

Also, note that most of our docs aren't autogenerated from the docstrings so we've never had any particular need to impose Sphinx markup requirements for docstrings.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Sun Jun 17 21:45:52 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 18 Jun 2018 01:45:52 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529286352.31.0.56676864532.issue28710@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

In my last comment above, I forgot that this issue is about *docstrings*.  We do not officially process docstrings with Sphinx, so there are no warnings to be suppressed.

PEP 8, which covers style for the stdlib, refers to https://www.python.org/dev/peps/pep-0257/
Neither says anything about markup and last I remember, there should not be any for the stdlib. Pep-0257 gives this example:

def complex(real=0.0, imag=0.0):
    """Form a complex number.

    Keyword arguments:
    real -- the real part (default 0.0)
    imag -- the imaginary part (default 0.0)
    """
Here, parameter names are indicated by the formatting, not by markup.  If `' is used in such lists, it should just be deleted.  I believe 'name' is sometimes used in running text.

The help() function prints a docstring as is.

----------
nosy:  -rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Sun Jun 17 21:52:45 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 18 Jun 2018 01:52:45 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529286765.07.0.902498594338.issue28710@psf.upfronthosting.co.za>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
title: Sphinx incompatible markup in the standard library -> Sphinx incompatible markup in the standard library docstrings

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Sun Jun 17 22:16:09 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 18 Jun 2018 02:16:09 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529288169.0.0.56676864532.issue33869@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

Andr?s, you seems making pull request to document at very high pace.

First of all, thank you for trying improving document.

But some of your pull request seems very little benefit for most readers.  Your motivation seems consistency than real people.

In PEP 8, "A Foolish Consistency is the Hobgoblin of Little Minds" is top of the rules.  I think it is same to documentation.

Random many small changes to document will consume core-dev's time and reduce translation coverage.

Please stop thinking like "Because X is ~, Y should be ~".
Instead, please think about helping real world people.

Regards,

----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33869>
_______________________________________

From report at bugs.python.org  Sun Jun 17 22:16:10 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 18 Jun 2018 02:16:10 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529288170.29.0.56676864532.issue33887@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Please don't fill-up the tracker with dozens of micro-PRs for tiny documentation changes of dubious benefit or occasional detriment.  On the balance, it isn't helpful to have a newcomer second-guess every little writing decision that has been made.  Ideally, we should focus on issues that are known to actually be confusing real users.  Also, it would be ideal to spend time learning the existing documentation norms.  

The little micro-edits each take time to discuss, review and apply or reject.  This eats into the small bits of spare time that the reviewers have and takes them away from other issues.

Perhaps you could channel your enthusiasm into reviewing other doc patches or open bugs.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sun Jun 17 22:36:54 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 02:36:54 +0000
Subject: [docs] [issue33869] doc Add set, frozen set,
 and tuple entries to Glossary
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529289414.7.0.56676864532.issue33869@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

Sorry, INADA, you are right.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33869>
_______________________________________

From report at bugs.python.org  Sun Jun 17 22:37:15 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 02:37:15 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529289435.26.0.56676864532.issue33887@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

Sorry, Raymond, you are right.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Mon Jun 18 00:34:33 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 18 Jun 2018 04:34:33 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529296473.05.0.56676864532.issue33892@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:


New changeset 5092439c2cb32112a5869b138011d38491db90a9 by INADA Naoki (Andr?s Delfino) in branch 'master':
bpo-33892: Doc: Use gender neutral words (GH-7770)
https://github.com/python/cpython/commit/5092439c2cb32112a5869b138011d38491db90a9


----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 00:34:52 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 18 Jun 2018 04:34:52 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529296492.56.0.902498594338.issue33892@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7379

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 00:35:40 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 18 Jun 2018 04:35:40 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529296540.94.0.902498594338.issue33892@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7380

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 00:49:46 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 18 Jun 2018 04:49:46 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529297386.33.0.56676864532.issue33892@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 5f165851b9b6ae6e75b01d68f9a40ed95def4c9f by Miss Islington (bot) in branch '3.7':
bpo-33892: Doc: Use gender neutral words (GH-7770)
https://github.com/python/cpython/commit/5f165851b9b6ae6e75b01d68f9a40ed95def4c9f


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 00:54:53 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 18 Jun 2018 04:54:53 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529297693.78.0.56676864532.issue33892@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f14e8eaaa52f799958e77b426283df0f69a81725 by Miss Islington (bot) in branch '3.6':
bpo-33892: Doc: Use gender neutral words (GH-7770)
https://github.com/python/cpython/commit/f14e8eaaa52f799958e77b426283df0f69a81725


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 00:56:07 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 18 Jun 2018 04:56:07 +0000
Subject: [docs] [issue33892] doc Add a couple of "or she/her"
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529297767.86.0.56676864532.issue33892@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

Andr?s, would you create PR for 2.7?
It can't be backported automatically.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 03:48:28 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 18 Jun 2018 07:48:28 +0000
Subject: [docs] [issue33876] doc Mention the MicroPython implementation in
 Introduction
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529308108.02.0.56676864532.issue33876@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

> I didn't add Cython because it's not clear to me if it's useful for creating extension modules in a pythonesque language, or if it's also useful by it's own.

Cython only makes extensions for CPython, and uses CPython's runtime. But it does have its own syntax, which is quite useful in the number-crunching domain.

I think it should be left out, but then, so should VPython which seems like it's a module usable by either the CPython or RapydScript interpreters.

----------
nosy: +petr.viktorin

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33876>
_______________________________________

From report at bugs.python.org  Mon Jun 18 04:57:54 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 18 Jun 2018 08:57:54 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529312274.16.0.56676864532.issue33894@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:

"If tempdir is unset or None" means "If tempdir has not been assigned to, or if it has been assigned the value None". "Unset" doesn't mean "delete from the module".

I agree the documentation wording could be improved.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, eric.smith
type: crash -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Mon Jun 18 06:35:27 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 10:35:27 +0000
Subject: [docs] [issue33892] doc Use gender neutral words
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529318127.87.0.56676864532.issue33892@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

Yes, of course!

----------
title: doc Add a couple of "or she/her" -> doc Use gender neutral words

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 07:19:02 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 11:19:02 +0000
Subject: [docs] [issue33892] doc Use gender neutral words
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529320742.15.0.902498594338.issue33892@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
pull_requests: +7383

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 07:32:53 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 11:32:53 +0000
Subject: [docs] [issue33876] doc Mention relevant pythonesque implementations
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529321573.47.0.902498594338.issue33876@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
title: doc Mention the MicroPython implementation in Introduction -> doc Mention relevant pythonesque implementations

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33876>
_______________________________________

From report at bugs.python.org  Mon Jun 18 07:34:12 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 11:34:12 +0000
Subject: [docs] [issue33832] doc Add "magic method" entry to Glossary
In-Reply-To: <1528718191.62.0.592728768989.issue33832@psf.upfronthosting.co.za>
Message-ID: <1529321652.34.0.902498594338.issue33832@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
title: Make "magic methods" a little more discoverable in the docs -> doc Add "magic method" entry to Glossary

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33832>
_______________________________________

From report at bugs.python.org  Mon Jun 18 09:32:33 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 13:32:33 +0000
Subject: [docs] [issue15474] Differentiate decorator and decorator factory
 in docs
In-Reply-To: <1343416207.69.0.71696747041.issue15474@psf.upfronthosting.co.za>
Message-ID: <1529328753.66.0.56676864532.issue15474@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

If deemed appropriate, I can take the task of writing a HOWTO for decorators/decorators factories.

----------
nosy: +adelfino

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15474>
_______________________________________

From report at bugs.python.org  Mon Jun 18 09:46:07 2018
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Mon, 18 Jun 2018 13:46:07 +0000
Subject: [docs] [issue15474] Differentiate decorator and decorator factory
 in docs
In-Reply-To: <1343416207.69.0.71696747041.issue15474@psf.upfronthosting.co.za>
Message-ID: <1529329567.32.0.56676864532.issue15474@psf.upfronthosting.co.za>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

I like ?ric's terminology; giving a concrete name to the concept makes it a lot easier to grasp, and this doesn't require inventing any new component terms.

Andr?s, if you'd like to tackle this, that's great!  I'd be happy to for you to bounce drafts through me if you like.

----------
nosy: +fdrake

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15474>
_______________________________________

From report at bugs.python.org  Mon Jun 18 10:16:06 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 18 Jun 2018 14:16:06 +0000
Subject: [docs] [issue15474] Differentiate decorator and decorator factory
 in docs
In-Reply-To: <1343416207.69.0.71696747041.issue15474@psf.upfronthosting.co.za>
Message-ID: <1529331366.87.0.56676864532.issue15474@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

Alright! :D Yes, your help will definitely come in handy, thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15474>
_______________________________________

From report at bugs.python.org  Mon Jun 18 11:34:01 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 18 Jun 2018 15:34:01 +0000
Subject: [docs] [issue33892] doc Use gender neutral words
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529336041.23.0.56676864532.issue33892@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:


New changeset 60c888d0eb673272920fa3b33f6e5b176d217dc9 by INADA Naoki (Andr?s Delfino) in branch '2.7':
bpo-33892: Doc: Use gender neutral words (GH-7770)
https://github.com/python/cpython/commit/60c888d0eb673272920fa3b33f6e5b176d217dc9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 11:34:25 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 18 Jun 2018 15:34:25 +0000
Subject: [docs] [issue33892] doc Use gender neutral words
In-Reply-To: <1529282640.33.0.56676864532.issue33892@psf.upfronthosting.co.za>
Message-ID: <1529336065.57.0.56676864532.issue33892@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

thanks

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33892>
_______________________________________

From report at bugs.python.org  Mon Jun 18 11:37:01 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 18 Jun 2018 15:37:01 +0000
Subject: [docs] [issue33830] Error in the output of one example in the
 httplib docs
In-Reply-To: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>
Message-ID: <1529336221.28.0.902498594338.issue33830@psf.upfronthosting.co.za>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
keywords: +patch
pull_requests: +7386
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33830>
_______________________________________

From report at bugs.python.org  Mon Jun 18 11:39:04 2018
From: report at bugs.python.org (R. David Murray)
Date: Mon, 18 Jun 2018 15:39:04 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529336344.37.0.56676864532.issue28710@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

Right, my opinion is that we shouldn't be putting markup in docstrings.  They are (from our point of view) pure text.

I don't know if discussion on python-dev is warranted, it seems like a fairly uncontroversial change, since it brings the docstrings in question into compliance with our general practice in the majority of the stdlib.  Unless my impression about that is wrong :)

I don't have an opinion on multiple versus single PR for this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 11:55:05 2018
From: report at bugs.python.org (R. David Murray)
Date: Mon, 18 Jun 2018 15:55:05 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529337305.64.0.56676864532.issue28710@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

By the way, in case anyone is curious, I'm pretty sure that markup is left over from the days when tex/latex was what docs were *written* in.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 12:00:06 2018
From: report at bugs.python.org (Philip Rowlands)
Date: Mon, 18 Jun 2018 16:00:06 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529337605.98.0.56676864532.issue33894@psf.upfronthosting.co.za>


Philip Rowlands <pythonbugs at dimebar.com> added the comment:

How about

- If tempdir is unset or None at any call to
+ If tempdir is None (the default) at any call to

This avoids headaches over the meaning of "unset", and accurately reflects the code at:
https://github.com/python/cpython/blob/3.6/Lib/tempfile.py#L289

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Mon Jun 18 12:30:00 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 18 Jun 2018 16:30:00 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529339399.99.0.56676864532.issue28710@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What is the problem? Docstrings are not written in the reStructuredText format in general. If Sphinx complains about docstrings in the stlib, don't run Sphinx for the stdlib files or report a Sphinx bug. Even if remove all `x', docstrings still will not be valid reStructuredText. For example the last three lines will be joined in a single paragraph for the docstring in msg319848.

`name' does not have special meaning in (La)TeX. AFAIK `name' is common writing of quotes in English texts. It predates reStructuredText and was widely used in Usenet and mailing lists (as two spaces after sentence-ending punctuation, double hyphen for a dash, _n_a_m_e_ to simulate underscoring, etc). It is just a part of old computer-typing culture (or may be even pre-computer).

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 12:38:34 2018
From: report at bugs.python.org (R. David Murray)
Date: Mon, 18 Jun 2018 16:38:34 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529339914.45.0.56676864532.issue28710@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

No, it is (somewhat) unique to tex.  If you write `word' tex would turn that into a pair of opposing quotes in the typeset document, as opposed to 'word' (the convention in regular text/emails/posts/etc) where you'd just see ascii quotes.  tex would render 'word' as a closing quote both before and after word, which looks weird in typeset text.

There's no bug here; as you say we aren't interested in making the docstrings parseable as restructured text (at least, I'm not).  For me, this is about getting rid of the now-odd-looking tex leftovers and making the ascii styling consistent with the bulk of our docstrings.

It's not a big deal, though.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 13:28:07 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 18 Jun 2018 17:28:07 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529342887.55.0.56676864532.issue28710@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

> AFAIK `name' is common writing of quotes in English texts

I don't remember ever seeing it before.  It looks like a typo to me, and I am sure it will to most readers.  I think it should be corrected as if it were a typo.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 14:05:56 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 18 Jun 2018 18:05:56 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1529339914.45.0.56676864532.issue28710@psf.upfronthosting.co.za>
Message-ID: <7f7125d3-c046-625f-894d-ca610f7cbd78@gmail.com>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Oh, you are right. I didn't write much English TeX, and used other types 
of quotes.

I'm sure that I seen `such quotation' in non-TeX files, but maybe my 
memory fools me. In any case using this writing here is likely an 
artifact of copying from a TeX documentation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 14:18:39 2018
From: report at bugs.python.org (Patrick Lehmann)
Date: Mon, 18 Jun 2018 18:18:39 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529345919.26.0.56676864532.issue28710@psf.upfronthosting.co.za>


Patrick Lehmann <Patrick.Lehmann at tu-dresden.de> added the comment:

Having single quotes in docstrings is also ok for Sphinx documentation.

Btw. ReStructured text (docutils) was invented to document Python sources, why is it not used by Python?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 15:37:03 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 18 Jun 2018 19:37:03 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529350623.24.0.56676864532.issue28710@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

RestructuredText, DocUtils, and Sphinx were developed independently, by people other than the pydev/cpython group.  (The proposal to include DocUtils in the stdlib was rejected.)  We converted to .rst for the Python documentation sources files about a decade ago.  Sphinx turns them into the .html files you can see online.  RestructuredText markup can now also be used in PEP, news/changelog, and What's New sources.  These are things that most people only view online or in other processed forms, not in source form.

On the other hand, stdlib docstrings are mostly viewed unprocessed in .py sources or as output from help() in text consoles or text widgets.  So markup in stdlib docstrings would impact everyone, not just core developers.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 16:31:52 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 18 Jun 2018 20:31:52 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529353912.61.0.56676864532.issue28710@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Marking this as closed.  Though well-intentioned, the suggestion is predicated on a misperception of the role of Sphinx for CPython and existing PEP recommendations on docstring practices.

----------
nosy: +rhettinger
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 16:37:45 2018
From: report at bugs.python.org (R. David Murray)
Date: Mon, 18 Jun 2018 20:37:45 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529354265.07.0.56676864532.issue28710@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

I would still like to see the legacy tex markup removed from the docstrings, so I think closing this issue is not appropriate, but it's not a big enough deal that I'll push for it if Raymond wants to keep it closed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 17:04:13 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 18 Jun 2018 21:04:13 +0000
Subject: [docs] [issue28710] Sphinx incompatible markup in the standard
 library docstrings
In-Reply-To: <1479257982.94.0.253343336813.issue28710@psf.upfronthosting.co.za>
Message-ID: <1529355853.58.0.56676864532.issue28710@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I agree with David.  I would like the ugly markup changed independent of how Sphinx treats it.  I was thinking of changing the title to "Change obsolete tex markup in stdlib docstrings".  The intent of `word' was for people to see balanced quotes, which in ascii text means 'word'.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28710>
_______________________________________

From report at bugs.python.org  Mon Jun 18 19:57:26 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 18 Jun 2018 23:57:26 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529366246.19.0.56676864532.issue33894@psf.upfronthosting.co.za>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

What about:

"If tempdir is unset or None (the default value has not been modified) ..." 

?

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Mon Jun 18 20:38:43 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 19 Jun 2018 00:38:43 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529368723.45.0.56676864532.issue33894@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:

I like philiprowlands' version:

- If tempdir is unset or None at any call to
+ If tempdir is None (the default) at any call to

Care to produce a PR?

----------
versions: +Python 2.7, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Mon Jun 18 23:35:38 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Tue, 19 Jun 2018 03:35:38 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529379338.49.0.56676864532.issue33872@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:

I concur with INADA. I don't prefer to add such implementation choice in definition. As for glossary, it may be unnecessary either but since it's already there, I don't think it needs to be removed.

----------
nosy: +xiang.zhang

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33872>
_______________________________________

From report at bugs.python.org  Tue Jun 19 03:29:42 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 19 Jun 2018 07:29:42 +0000
Subject: [docs] [issue33872] doc Add list access time to list definition
In-Reply-To: <1529099675.69.0.56676864532.issue33872@psf.upfronthosting.co.za>
Message-ID: <1529393382.1.0.56676864532.issue33872@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

-1 We've historically chosen to not include such implementation specific details and it seems to have not been a problem for users.  The glossary in particular is no place to talk about such specifics.

----------
nosy: +rhettinger, tim.peters
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed
versions:  -Python 2.7, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33872>
_______________________________________

From report at bugs.python.org  Tue Jun 19 03:34:32 2018
From: report at bugs.python.org (aruseni)
Date: Tue, 19 Jun 2018 07:34:32 +0000
Subject: [docs] [issue33858] A typo in multiprocessing documentation
In-Reply-To: <1528976358.35.0.947875510639.issue33858@psf.upfronthosting.co.za>
Message-ID: <1529393672.72.0.56676864532.issue33858@psf.upfronthosting.co.za>


aruseni <aruseni.magiku at gmail.com> added the comment:

Thanks all!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33858>
_______________________________________

From report at bugs.python.org  Wed Jun 20 04:23:24 2018
From: report at bugs.python.org (Eric Wieser)
Date: Wed, 20 Jun 2018 08:23:24 +0000
Subject: [docs] [issue33909] PyObject_CallFinalizerFromDealloc is not
 referenced in any documentation
Message-ID: <1529483004.36.0.56676864532.issue33909@psf.upfronthosting.co.za>


New submission from Eric Wieser <wieser.eric+pybug at gmail.com>:

PEP 442 states that:

> Two new C API functions are provided to ease calling of tp_finalize, especially from custom deallocators.

But it does not give the names of these functions, nor do any python docs I can discover.

>From grepping for tp_finalize, it seems the functions in question are:

- PyObject_CallFinalizerFromDealloc 
- PyObject_CallFinalizer

It would be great if these could be documented, and perhaps even an example given of when it's appropriate to call each one.

----------
assignee: docs at python
components: Documentation
messages: 320036
nosy: Eric.Wieser, docs at python
priority: normal
severity: normal
status: open
title: PyObject_CallFinalizerFromDealloc is not referenced in any documentation
versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33909>
_______________________________________

From report at bugs.python.org  Wed Jun 20 12:47:14 2018
From: report at bugs.python.org (Jan Lachnitt)
Date: Wed, 20 Jun 2018 16:47:14 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1529513234.55.0.56676864532.issue15533@psf.upfronthosting.co.za>


Jan Lachnitt <pepalogik at seznam.cz> added the comment:

Nobody responds yet, so I will.

I think that the basic proposal was made by Chris Jerdonek in msg171692 already on 2012-10-01: First document both behaviors and then discuss the possible harmonization. I think the proposal was good and further discussion has confirmed this.

Chris Jerdonek, to whom this issue is assigned, last commented it on 2012-12-18. Shouldn't the issue be assigned to somebody else?

By the way, the related env issue is #8557.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15533>
_______________________________________

From report at bugs.python.org  Wed Jun 20 12:53:27 2018
From: report at bugs.python.org (Jan Lachnitt)
Date: Wed, 20 Jun 2018 16:53:27 +0000
Subject: [docs] [issue8557] subprocess PATH semantics and portability
In-Reply-To: <1272451494.53.0.273790888777.issue8557@psf.upfronthosting.co.za>
Message-ID: <1529513607.76.0.56676864532.issue8557@psf.upfronthosting.co.za>


Jan Lachnitt <pepalogik at seznam.cz> added the comment:

A related issue exists with cwd: #15533.

----------
nosy: +pepalogik

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8557>
_______________________________________

From report at bugs.python.org  Wed Jun 20 16:07:40 2018
From: report at bugs.python.org (Srinivas Reddy T)
Date: Wed, 20 Jun 2018 20:07:40 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529525260.9.0.902498594338.issue33894@psf.upfronthosting.co.za>


Change by Srinivas  Reddy T <thatiparthysreenivas at gmail.com>:


----------
keywords: +patch
pull_requests: +7437
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Wed Jun 20 16:29:48 2018
From: report at bugs.python.org (Chris Jerdonek)
Date: Wed, 20 Jun 2018 20:29:48 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1529526588.15.0.902498594338.issue15533@psf.upfronthosting.co.za>


Change by Chris Jerdonek <chris.jerdonek at gmail.com>:


----------
assignee: chris.jerdonek -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15533>
_______________________________________

From report at bugs.python.org  Wed Jun 20 18:54:25 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 20 Jun 2018 22:54:25 +0000
Subject: [docs] [issue15533] subprocess.Popen(cwd) documentation: Posix vs
 Windows
In-Reply-To: <1343886272.5.0.825552125397.issue15533@psf.upfronthosting.co.za>
Message-ID: <1529535265.67.0.902498594338.issue15533@psf.upfronthosting.co.za>


Change by Gregory P. Smith <greg at krypto.org>:


----------
assignee:  -> gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15533>
_______________________________________

From report at bugs.python.org  Wed Jun 20 18:56:36 2018
From: report at bugs.python.org (John Hagen)
Date: Wed, 20 Jun 2018 22:56:36 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
Message-ID: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>


New submission from John Hagen <johnthagen at gmail.com>:

The socket documentation (https://docs.python.org/3/library/socket.html#socket-families) does not list '' as a way to bind to all interfaces for the AF_INET/AF_INET6 address family.

This is answered on SO here: https://stackoverflow.com/a/8034146 but it took me a while to find it. Ideally if this was mentioned in the docs, that would be great.

----------
assignee: docs at python
components: Documentation
messages: 320125
nosy: John Hagen, docs at python
priority: normal
severity: normal
status: open
title: Explain that '' can be used to bind to all interfaces for the AF_INET address family in the docs
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Wed Jun 20 22:33:23 2018
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 21 Jun 2018 02:33:23 +0000
Subject: [docs] [issue33909] PyObject_CallFinalizerFromDealloc is not
 referenced in any documentation
In-Reply-To: <1529483004.36.0.56676864532.issue33909@psf.upfronthosting.co.za>
Message-ID: <1529548403.54.0.56676864532.issue33909@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

I think I can describe what two function does/for.
But I'm not good English writer.  Would you write document instead?

---

"Finalizer" is __del__ in Python and tp_finalize in C.

Calling finalizer requires some tricks, including avoiding call twice.
That is what PyObject_CallFinalizer() does.  Use it instead of call `type->tp_finalize(obj)` directly.

But finalizer is called from destructor (tp_dealloc) usually, and calling finalizer from destructor need more hack (e.g. temporary increment refcount).  This is what PyObject_CallFinalizerFromDealloc does.

Generally speaking, this API is used only when you want to use both of custom tp_dealloc and tp_finalize.  This is very rare because you can write cleanup code in tp_dealloc and skip using tp_finalize.

When you need really need both of tp_dealloc and tp_finalize, note that:

* Finalizer may resurrect the object.
* When the type is subclassed from Python, tp_finalize is called automatically.  You must not call PyObject_CallFinalizerFromDealloc then.

This is tp_dealloc of Future object in asyncio.  This object uses both of tp_dealloc and tp_finalize for compatibility with Future object implemented in pure Python.  This covers many edge cases of tp_dealloc.

```
static void
FutureObj_dealloc(PyObject *self)
{
    FutureObj *fut = (FutureObj *)self;

    if (Future_CheckExact(fut)) {
        /* When fut is subclass of Future, finalizer is called from
         * subtype_dealloc.
         */
        if (PyObject_CallFinalizerFromDealloc(self) < 0) {
            // resurrected.
            return;
        }
    }

    // Weakref callback and finalizer of other objects may start GC.
    // So you need to untrack this object from GC before calling PyObject_ClearWeakRefs()
    // or any Py_DECREF()s
    // Otherwise, GC will cause segfault because refcount of this object is 0.
    PyObject_GC_UnTrack(self);

    // Handle weakrefs
    if (fut->fut_weakreflist != NULL) {
        PyObject_ClearWeakRefs(self);
    }

    // Reuse tp_clear() for clearing all members.
    (void)FutureObj_clear(fut);

    // Free this object at last.
    Py_TYPE(fut)->tp_free(fut);
}
```

----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33909>
_______________________________________

From report at bugs.python.org  Wed Jun 20 23:33:31 2018
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 21 Jun 2018 03:33:31 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1529552010.92.0.56676864532.issue32500@psf.upfronthosting.co.za>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

I don't believe this. Are you seriously saying that it is ok to tell the user "object of type 'dict' has no len()" when of course it does? Please change the error message so it does not so blatantly lie. Yes, I understand the underlying issue, but the common user doesn't need to understand it, and they shouldn't be lied to.

----------
nosy: +veky

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Thu Jun 21 03:56:15 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 21 Jun 2018 07:56:15 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529567775.83.0.902498594338.issue33894@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7451

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Thu Jun 21 03:57:56 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 21 Jun 2018 07:57:56 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529567876.04.0.902498594338.issue33894@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7452

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Thu Jun 21 04:05:10 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 21 Jun 2018 08:05:10 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529568310.28.0.56676864532.issue33894@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:


New changeset b225cb770fb17596298f5a05c41a7c90c470c4f8 by Eric V. Smith (Miss Islington (bot)) in branch '3.6':
bpo-33894: Clarified the tempfile.tempdir documentation (GH-7829) (GH-7842)
https://github.com/python/cpython/commit/b225cb770fb17596298f5a05c41a7c90c470c4f8


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Thu Jun 21 07:01:12 2018
From: report at bugs.python.org (Ammar Askar)
Date: Thu, 21 Jun 2018 11:01:12 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1529578872.15.0.56676864532.issue33921@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

It's kinda mentioned:

"For IPv4 addresses, two special forms are accepted instead of a host address: the empty string represents INADDR_ANY"

Though it could be more explicit on what means since binding to all interfaces is a common use case.

----------
nosy: +ammar2

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Thu Jun 21 07:15:46 2018
From: report at bugs.python.org (John Hagen)
Date: Thu, 21 Jun 2018 11:15:46 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1529579746.02.0.56676864532.issue33921@psf.upfronthosting.co.za>


John Hagen <johnthagen at gmail.com> added the comment:

@ammar2

I see that now. Yeah it's further down in the docs and doesn't actually call out '' like is done for AF_CAN:

A tuple (interface, ) is used for the AF_CAN address family, where interface is a string representing a network interface name like 'can0'. The network interface name '' can be used to receive packets from all network interfaces of this family.

Ideally I think putting something in this section would be helpful:

A pair (host, port) is used for the AF_INET address family, where host is a string representing either a hostname in Internet domain notation like 'daring.cwi.nl' or an IPv4 address like '100.50.200.5', and port is an integer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:08:48 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 21 Jun 2018 13:08:48 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
Message-ID: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>


New submission from STINNER Victor <vstinner at redhat.com>:

It would help to document that calling Py_Initialize() twice in Python 3.7 now triggers a fatal error, whereas previous the second call did nothing. Document it at:
https://docs.python.org/dev/whatsnew/3.7.html#changes-in-the-c-api

... Or should it be considered as a regression?

--

My colleague Miro Hron?ok reported a Python crash (SIGABRT) when running https://github.com/konlpy/konlpy test suite on Python 3.7:

"Fatal Python error: _Py_InitializeCore: main interpreter already initialized"

konlpy uses the JPype project, the bug is in JPype initialization function (it's a C extension):

* https://github.com/originell/jpype/issues/331
* https://github.com/originell/jpype/pull/332

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 320175
nosy: docs at python, eric.snow, ncoghlan, ned.deily, vstinner
priority: normal
severity: normal
status: open
title: Calling Py_Initialize() twice now triggers a fatal error (Python 3.7)
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:19:41 2018
From: report at bugs.python.org (R. David Murray)
Date: Thu, 21 Jun 2018 13:19:41 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1529587181.57.0.56676864532.issue32500@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

IIUC that error message came from pypy, not CPython.  If you have a reproducer for CPython, you can open a new issue with a request to fix the error message.

----------
nosy: +r.david.murray

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:26:24 2018
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 21 Jun 2018 13:26:24 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1529587584.81.0.56676864532.issue32500@psf.upfronthosting.co.za>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

Sure, here it is: https://bugs.python.org/issue33933

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:30:53 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 21 Jun 2018 13:30:53 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529587853.58.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

I set the priority to release blocker to make sure that someone looks at this issue, even if I'm not sure that it's a huge regression.

----------
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:31:43 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 21 Jun 2018 13:31:43 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529587903.98.0.902498594338.issue33932@psf.upfronthosting.co.za>


Change by STINNER Victor <vstinner at redhat.com>:


----------
keywords: +patch
pull_requests: +7455
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:35:14 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 21 Jun 2018 13:35:14 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529588114.65.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

The behaviour changed has been introduced by bpo-22257:

commit 1abcf6700b4da6207fe859de40c6c1bada6b4fec
Author: Eric Snow <ericsnowcurrently at gmail.com>
Date:   Tue May 23 21:46:51 2017 -0700

    bpo-22257: Private C-API for core runtime initialization (PEP 432). (#1772)
    
    (patch by Nick Coghlan)

Simplified change:

-    if (initialized)
-        return;
-    initialized = 1;

+    if (_Py_Initialized) {
+        Py_FatalError("Py_InitializeCore: main interpreter already initialized");
+    }

----------
components: +Interpreter Core -Documentation

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:40:20 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 21 Jun 2018 13:40:20 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529588420.09.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

Attached PR 7845 restores the Python 3.6 behaviour: calling Py_Initialize() twice does nothing.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 21 09:41:11 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 21 Jun 2018 13:41:11 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529588471.83.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

Note: the doc doesn't say that the function must only be called once, nor document the (current) new Python 3.7 restriction (must only be called once):
https://docs.python.org/dev/c-api/init.html#c.Py_Initialize

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 21 10:24:22 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 21 Jun 2018 14:24:22 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1529591062.36.0.902498594338.issue32500@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +7456

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Thu Jun 21 10:30:09 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 21 Jun 2018 14:30:09 +0000
Subject: [docs] [issue32500] PySequence_Length() raises TypeError on dict
 type
In-Reply-To: <1515199107.36.0.467229070634.issue32500@psf.upfronthosting.co.za>
Message-ID: <1529591409.67.0.56676864532.issue32500@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I agree that error messages sometimes is misleading if use the C API.

PR 7846 fixes this, although I'm not sure this is the best wording.

----------
assignee: docs at python -> serhiy.storchaka
components: +Interpreter Core
resolution: fixed -> 
stage: resolved -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32500>
_______________________________________

From report at bugs.python.org  Thu Jun 21 18:56:48 2018
From: report at bugs.python.org (Lew Kurtz)
Date: Thu, 21 Jun 2018 22:56:48 +0000
Subject: [docs] [issue33460] ... used to indicate many different things in
 chapter 3, some are confusing
In-Reply-To: <1525995197.73.0.682650639539.issue33460@psf.upfronthosting.co.za>
Message-ID: <1529621808.97.0.902498594338.issue33460@psf.upfronthosting.co.za>


Change by Lew Kurtz <lew.kurtz at icloud.com>:


----------
keywords: +patch
pull_requests: +7462
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33460>
_______________________________________

From report at bugs.python.org  Thu Jun 21 23:01:00 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 22 Jun 2018 03:01:00 +0000
Subject: [docs] [issue33876] doc Mention relevant pythonesque implementations
In-Reply-To: <1529118910.74.0.56676864532.issue33876@psf.upfronthosting.co.za>
Message-ID: <1529636459.99.0.56676864532.issue33876@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks for the PR, and thanks everyone for the feedback.

But I don't think we should be the one maintaining a list of all available alternative Python implementation out there.

There is already a good list: https://wiki.python.org/moin/PythonImplementations which is the top result when people search for "Python implementation".

I'm inclined to close this issue.

----------
nosy: +Mariatta
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33876>
_______________________________________

From report at bugs.python.org  Fri Jun 22 05:00:38 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Fri, 22 Jun 2018 09:00:38 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529658037.91.0.56676864532.issue33932@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:

> Note: the doc doesn't say that the function must only be called once, nor document the (current) new Python 3.7 restriction (must only be called once):

But the doc says:

  This is a no-op when called for a second time (without calling Py_FinalizeEx() first).

no-op means it could be called twice?

----------
nosy: +xiang.zhang

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 07:13:28 2018
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 22 Jun 2018 11:13:28 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529666008.48.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

"no-op means it could be called twice" oops right :-) So it's a regression. Would you mind to review my PR 7845, Xiang?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 07:26:55 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 22 Jun 2018 11:26:55 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529666815.13.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

While I agree the documentation issue means that this should be made to work again for Python 3.7.1, I'd like for Python 3.7 to at least deprecate calling Py_Initialize twice without an intervening Py_Finalize.

Otherwise the public multi-phase interpreter initialization API is going to have to cope with somebody starting the initialization process, and then calling a full Py_Initialize to finish it (instead of the new "complete initialization" API, whatever we end up calling that), and I'd prefer to keep the permitted state transitions more linear than that.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 07:41:27 2018
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 22 Jun 2018 11:41:27 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529667687.14.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

> While I agree the documentation issue means that this should be made to work again for Python 3.7.1, I'd like for Python 3.7 to at least deprecate calling Py_Initialize twice without an intervening Py_Finalize.

In term of timeline, I would prefer to fix the regression right now, and then see how to deprecate calling the function later :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 08:01:06 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 22 Jun 2018 12:01:06 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529668866.61.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Aye, I'm fine with deferring the programmatic deprecation for now - it's mainly the docs I'd like to see changed at the same time as the regression is fixed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 11:45:56 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 22 Jun 2018 15:45:56 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
Message-ID: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

IMHO, the logging.basicConfig documentation could have some useful references for filemodes, time.strftime, printf-formatting, and logging level.

PR adds them.

----------
assignee: docs at python
components: Documentation
messages: 320242
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add references to logging.basicConfig
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Fri Jun 22 11:47:49 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 22 Jun 2018 15:47:49 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529682469.62.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7468
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Fri Jun 22 13:14:54 2018
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 22 Jun 2018 17:14:54 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529687694.35.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:


New changeset 209abf746985526bce255e2fba97d3246924885d by Victor Stinner in branch 'master':
bpo-33932: Calling Py_Initialize() twice does nothing (GH-7845)
https://github.com/python/cpython/commit/209abf746985526bce255e2fba97d3246924885d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 13:16:19 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 17:16:19 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529687779.67.0.902498594338.issue33932@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7469

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 13:33:51 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 17:33:51 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529688831.16.0.56676864532.issue33932@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3747dd16d5d2af3499f586386e49740a0454cf44 by Miss Islington (bot) in branch '3.7':
bpo-33932: Calling Py_Initialize() twice does nothing (GH-7845)
https://github.com/python/cpython/commit/3747dd16d5d2af3499f586386e49740a0454cf44


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 15:12:47 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 22 Jun 2018 19:12:47 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1529694767.63.0.56676864532.issue33932@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

Since the undocumented change in behavior from 3.6 to 3.7 appears to be causing some downstream regressions at this late stage, I think Victor's change should be cherry-picked for 3.7.0 final.

Nick or Eric, if you merge a 3.7 doc change, I'll cherry-pick that as well.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 22 15:18:45 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 22 Jun 2018 19:18:45 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529695125.9.0.902498594338.issue33885@psf.upfronthosting.co.za>


Change by Ned Deily <nad at python.org>:


----------
nosy: +orsenthil

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Fri Jun 22 15:33:59 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 22 Jun 2018 19:33:59 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1529696039.31.0.56676864532.issue33921@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

John, since you raised the issue, would you like to provide a doc PR?

----------
keywords: +easy
nosy: +ned.deily
stage:  -> needs patch
versions:  -Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Fri Jun 22 16:08:48 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 22 Jun 2018 20:08:48 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529698128.19.0.56676864532.issue33877@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

The paragraph reads:

Under Unix, a complete program can be passed to the interpreter in three forms: with the -c string command line option, as a file passed as the first command line argument, or as standard input. If the file or standard input is a tty device, the interpreter enters interactive mode; otherwise, it executes the file as a complete program.

This is slightly confusing because a complete programs cannot be passed all at once if the file (regular or stdin) is interactive.

Not being a Windows expert, I was curious whether the standard input part is true for Win 10.  Indeed, both "python con:" and "python <con:" (as well as just "python") start Python in interactive mode, which both "python file" and "python < file" executes the file.

Ned, is the statement untrue for MacOS, or does 'Unix' always include Macs?  In other words, should we add 'Windows' or delete 'Unix'?

----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 16:23:37 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 22 Jun 2018 20:23:37 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529699016.98.0.56676864532.issue33885@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I am not even sure what a 'hook function' is supposed to mean.  A beginner might think it means something other than any old callable.  Unless Sentil or someone objects within a week, I would merge this.  Ping me if nothing happens.

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Fri Jun 22 16:25:24 2018
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 22 Jun 2018 20:25:24 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529699124.93.0.56676864532.issue33885@psf.upfronthosting.co.za>


Senthil Kumaran <senthil at uthcode.com> added the comment:

@Terry, the change in terminology looks good to me.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Fri Jun 22 16:51:54 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 22 Jun 2018 20:51:54 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529700714.59.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by Ned Deily <nad at python.org>:


----------
nosy: +vinay.sajip

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Fri Jun 22 16:55:34 2018
From: report at bugs.python.org (Philip Rowlands)
Date: Fri, 22 Jun 2018 20:55:34 +0000
Subject: [docs] [issue33894] tempfile.tempdir cannot be unset
In-Reply-To: <1529307283.94.0.56676864532.issue33894@psf.upfronthosting.co.za>
Message-ID: <1529700934.65.0.56676864532.issue33894@psf.upfronthosting.co.za>


Philip Rowlands <pythonbugs at dimebar.com> added the comment:

Thanks for the edit. I did try a PR but was defeated by build/doc tool's recent version requirements (and didn't want to send untested changes, however minor).

The reason for getting rid of "unset" is the confusion of "state", i.e. it has never been assigned to, or "action", i.e. the user is unsetting it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33894>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:08:27 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 22 Jun 2018 21:08:27 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529701707.72.0.56676864532.issue33877@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

The statement is true for macOS (note macOS is the correct current styling per Apple); in general, macOS is a UNIX platform as far as Python is concerned.  So, yes, it appears the documentation there could be simplified by eliminating the platform distinction.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:10:26 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 22 Jun 2018 21:10:26 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529701826.33.0.56676864532.issue33885@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset c45cb479074b5d25f0d382d3109f527520a9f03c by Terry Jan Reedy (Andr?s Delfino) in branch '3.6':
bpo-33885: Replace "hook function" with "callable" (GH-7765)
https://github.com/python/cpython/commit/c45cb479074b5d25f0d382d3109f527520a9f03c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:11:46 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 21:11:46 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529701906.0.0.902498594338.issue33885@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7471

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:16:51 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 22 Jun 2018 21:16:51 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529702211.35.0.56676864532.issue33877@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Thanks.  I did that and will merge when possible.

----------
assignee: docs at python -> terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:30:47 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 21:30:47 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529703047.45.0.56676864532.issue33885@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e4db73058b6c31f71c64d0f87a10547f3cf72f20 by Miss Islington (bot) in branch '3.7':
bpo-33885: Replace "hook function" with "callable" (GH-7765)
https://github.com/python/cpython/commit/e4db73058b6c31f71c64d0f87a10547f3cf72f20


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:31:05 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 22 Jun 2018 21:31:05 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529703065.75.0.56676864532.issue33877@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset c9d43c702a53804c23ecb22a0dbf6a47c804d2b1 by Terry Jan Reedy (Andr?s Delfino) in branch 'master':
bpo-33877: Remove UNIX qualification for running complete programs (GH-7744)
https://github.com/python/cpython/commit/c9d43c702a53804c23ecb22a0dbf6a47c804d2b1


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:32:18 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 21:32:18 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529703138.6.0.902498594338.issue33877@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7472

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:34:13 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 21:34:13 +0000
Subject: [docs] [issue33877] doc Mention Windows along UNIX for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529703253.88.0.902498594338.issue33877@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7473

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:42:54 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 22 Jun 2018 21:42:54 +0000
Subject: [docs] [issue33877] Doc: Delete UNIX qualification for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529703774.23.0.902498594338.issue33877@psf.upfronthosting.co.za>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
title: doc Mention Windows along UNIX for script running instructions -> Doc: Delete UNIX qualification for script running instructions

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:51:10 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 21:51:10 +0000
Subject: [docs] [issue33877] Doc: Delete UNIX qualification for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529704270.32.0.56676864532.issue33877@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f47d8983fe35239cccf4e623e4ad70c9e0f636f9 by Miss Islington (bot) in branch '3.7':
bpo-33877: Remove UNIX qualification for running complete programs (GH-7744)
https://github.com/python/cpython/commit/f47d8983fe35239cccf4e623e4ad70c9e0f636f9


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 17:54:29 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 22 Jun 2018 21:54:29 +0000
Subject: [docs] [issue33877] Doc: Delete UNIX qualification for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529704469.11.0.56676864532.issue33877@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 688325ed1a4d549f03d886507c265093aa3b2cab by Miss Islington (bot) in branch '3.6':
bpo-33877: Remove UNIX qualification for running complete programs (GH-7744)
https://github.com/python/cpython/commit/688325ed1a4d549f03d886507c265093aa3b2cab


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 22:28:11 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 23 Jun 2018 02:28:11 +0000
Subject: [docs] [issue33877] Doc: Delete UNIX qualification for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529720891.79.0.902498594338.issue33877@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
pull_requests: +7476

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Fri Jun 22 22:37:20 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 23 Jun 2018 02:37:20 +0000
Subject: [docs] [issue33877] Doc: Delete UNIX qualification for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529721440.24.0.56676864532.issue33877@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset 1c9a72cc99d4f76a18755d7227bd1c375e44b4ad by Terry Jan Reedy (Andr?s Delfino) in branch '2.7':
[2.7] bpo-33877: Remove UNIX qualification for running complete programs (GH-7744)
https://github.com/python/cpython/commit/1c9a72cc99d4f76a18755d7227bd1c375e44b4ad


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Sat Jun 23 10:54:23 2018
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 23 Jun 2018 14:54:23 +0000
Subject: [docs] [issue33921] Explain that '' can be used to bind to all
 interfaces for the AF_INET address family in the docs
In-Reply-To: <1529535395.97.0.56676864532.issue33921@psf.upfronthosting.co.za>
Message-ID: <1529765663.42.0.902498594338.issue33921@psf.upfronthosting.co.za>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +7484
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33921>
_______________________________________

From report at bugs.python.org  Sat Jun 23 12:52:55 2018
From: report at bugs.python.org (Mikhail)
Date: Sat, 23 Jun 2018 16:52:55 +0000
Subject: [docs] [issue33948] doc truncated lines in PDF
Message-ID: <1529772775.32.0.56676864532.issue33948@psf.upfronthosting.co.za>


New submission from Mikhail <mikhail.domanov at gmail.com>:

Hello, Python Team,

In reference.pdf I came across truncated lines in Python syntax that are not wrapped and carried forward to the next line, but instead run across the right margin.

Examples
"2.3 Identifiers and keywords" line contains "id_start ::= <all characters in general categories"

"8.8.1 Coroutine function definition" line contains "async_funcdef ::= [decorators] "async" "def" funcname "(" [parameter_list] ")" ["->" expression"

It would be VERY convenient to fix this for printing.

Thank you

----------
assignee: docs at python
components: Documentation
messages: 320313
nosy: Mikhail_D, docs at python
priority: normal
severity: normal
status: open
title: doc truncated lines in PDF
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33948>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:27:18 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 23 Jun 2018 18:27:18 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529778438.53.0.56676864532.issue33887@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset 38cf49bf695903ac7a8516bca6bbb6b32d935bb5 by Mariatta (Andr?s Delfino) in branch 'master':
bpo-33887: Add TOC to Design and History FAQ(GH-7766)
https://github.com/python/cpython/commit/38cf49bf695903ac7a8516bca6bbb6b32d935bb5


----------
nosy: +Mariatta

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:28:36 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 23 Jun 2018 18:28:36 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529778516.78.0.902498594338.issue33887@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7486

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:29:27 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 23 Jun 2018 18:29:27 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529778567.98.0.902498594338.issue33887@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7487

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:30:27 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 23 Jun 2018 18:30:27 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529778627.09.0.902498594338.issue33887@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7488

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:31:31 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 23 Jun 2018 18:31:31 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529778691.89.0.56676864532.issue33887@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks for the PR!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:33:12 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 23 Jun 2018 18:33:12 +0000
Subject: [docs] [issue33948] doc truncated lines in PDF
In-Reply-To: <1529772775.32.0.56676864532.issue33948@psf.upfronthosting.co.za>
Message-ID: <1529778792.34.0.56676864532.issue33948@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

Can you say from which URL you downloaded the PDF (assuming you didn't build it yourself)?

----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33948>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:33:46 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 23 Jun 2018 18:33:46 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529778826.1.0.56676864532.issue33887@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3e3157bd55f197ab36b280b26aea8dcd04e37fcf by Miss Islington (bot) in branch '2.7':
bpo-33887: Add TOC to Design and History FAQ(GH-7766)
https://github.com/python/cpython/commit/3e3157bd55f197ab36b280b26aea8dcd04e37fcf


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:43:45 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 23 Jun 2018 18:43:45 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529779425.81.0.56676864532.issue33887@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 070c91e46579429f7af7599af6d9e67a8dc5be50 by Miss Islington (bot) in branch '3.7':
bpo-33887: Add TOC to Design and History FAQ(GH-7766)
https://github.com/python/cpython/commit/070c91e46579429f7af7599af6d9e67a8dc5be50


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 14:48:30 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 23 Jun 2018 18:48:30 +0000
Subject: [docs] [issue33887] doc Add TOC in Design and History FAQ
In-Reply-To: <1529258750.3.0.56676864532.issue33887@psf.upfronthosting.co.za>
Message-ID: <1529779710.52.0.56676864532.issue33887@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a845b7ab3e8ba1c20ef4c3ee23ebf50df7e7c4c6 by Miss Islington (bot) in branch '3.6':
bpo-33887: Add TOC to Design and History FAQ(GH-7766)
https://github.com/python/cpython/commit/a845b7ab3e8ba1c20ef4c3ee23ebf50df7e7c4c6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33887>
_______________________________________

From report at bugs.python.org  Sat Jun 23 19:12:46 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 23 Jun 2018 23:12:46 +0000
Subject: [docs] [issue33948] doc truncated lines in PDF
In-Reply-To: <1529772775.32.0.56676864532.issue33948@psf.upfronthosting.co.za>
Message-ID: <1529795566.28.0.902498594338.issue33948@psf.upfronthosting.co.za>


Change by Ned Deily <nad at python.org>:


----------
nosy: +mdk

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33948>
_______________________________________

From report at bugs.python.org  Sat Jun 23 21:28:39 2018
From: report at bugs.python.org (Mikhail)
Date: Sun, 24 Jun 2018 01:28:39 +0000
Subject: [docs] [issue33948] doc truncated lines in PDF
In-Reply-To: <1529772775.32.0.56676864532.issue33948@psf.upfronthosting.co.za>
Message-ID: <1529803719.27.0.56676864532.issue33948@psf.upfronthosting.co.za>


Mikhail <mikhail.domanov at gmail.com> added the comment:

This file was taken from

https://docs.python.org/3.7/archives/python-3.7.0rc1-docs-pdf-a4.zip

Hashes 

CRC32: 327CF408
MD5: 7EBEB565C1EA7E52F366B5C734500FAC
SHA-1: 09727C07C45965E4E43664B727E7CAECC4F3CD89
SHA-256: 3EB1E769F3A1F17922B3BC99AE5C316209E74B7CB6CBE4B4769D55D859AC5BC8
SHA-512: EB60766B2C594BD86CF2C038147AF50462DFC379F7DA88C0A89F8791ED0332F67986DA6D328549B463E6CD5A0630F1ECDC140E6DE2C769EE20799C03384F0A2C
SHA3-256: 136575BABCC4B666E39AEBD9E96D09684EE677EDC01825C4D891E141D43CC252

Thank you

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33948>
_______________________________________

From report at bugs.python.org  Sat Jun 23 21:58:00 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 24 Jun 2018 01:58:00 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529805480.03.0.902498594338.issue33885@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
pull_requests: +7494

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Sat Jun 23 22:19:02 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 24 Jun 2018 02:19:02 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529806742.27.0.902498594338.issue33885@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
pull_requests: +7495

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Sat Jun 23 22:23:53 2018
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 24 Jun 2018 02:23:53 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529807033.16.0.56676864532.issue33885@psf.upfronthosting.co.za>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 0ba9a0b7d19da8b4bd3c13b358d3fd2a5ad16f09 by Senthil Kumaran (Andr?s Delfino) in branch 'master':
[master] bpo-33885: Replace "hook function" with "callable" (GH-7765) (#7886)
https://github.com/python/cpython/commit/0ba9a0b7d19da8b4bd3c13b358d3fd2a5ad16f09


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Sat Jun 23 22:34:50 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 24 Jun 2018 02:34:50 +0000
Subject: [docs] [issue33885] doc Replace "hook function" with "callable" in
 urllib.request.urlretrieve
In-Reply-To: <1529256091.43.0.56676864532.issue33885@psf.upfronthosting.co.za>
Message-ID: <1529807690.67.0.56676864532.issue33885@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

The bots occasionally miss.
PR 7885 was indeed merged even though the message has not appeared.
https://github.com/python/cpython/commit/2c11e23a5a686edc69bcbb4c65f500d50d992bb3
PR 7886 was merged as the message says, even though the status was not changed.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33885>
_______________________________________

From report at bugs.python.org  Sat Jun 23 23:29:06 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 24 Jun 2018 03:29:06 +0000
Subject: [docs] [issue33934] locale.getlocale() seems wrong when the locale
 is yet unset (python3 on linux)
In-Reply-To: <1529596837.65.0.56676864532.issue33934@psf.upfronthosting.co.za>
Message-ID: <1529810946.57.0.56676864532.issue33934@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

This statement is no longer correct: "when python starts, it runs using the C locale, on any platform (Windows, Linux, BSD), any python version (2, 3...), until locale.setlocale() is used to set another locale."

The Python 3 text model doesn't work properly in the legacy C locale due to the assumption of ASCII as the preferred text encoding, so we run setlocale(LC_ALL, "") early in the startup sequence in order to switch to something more sensible. In Python 3.7+, we're even more opinionated about that, and explicitly coerce the C locale to a UTF-8 based one if there's one available.

If our docs are still saying otherwise anywhere, then our docs are outdated, and need to be fixed.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33934>
_______________________________________

From report at bugs.python.org  Sun Jun 24 02:24:57 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 24 Jun 2018 06:24:57 +0000
Subject: [docs] [issue33774] Document that @lru_cache caches based on
 exactly how the function arguments are specified
In-Reply-To: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>
Message-ID: <1529821497.2.0.56676864532.issue33774@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I propose this, "Distinct argument patterns may be considered to be distinct calls with distinct results even if the underlying function sees them as equivalent calls."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33774>
_______________________________________

From report at bugs.python.org  Sun Jun 24 02:59:04 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 24 Jun 2018 06:59:04 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1529823544.12.0.56676864532.issue32554@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> Maybe deprecate using a hash?

Any deprecation will likely break some existing code, but it would be nice to restrict inputs types to int, float, bytes, bytearray, or str.  Then we could remove all reference to hashing.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32554>
_______________________________________

From report at bugs.python.org  Sun Jun 24 03:08:15 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 24 Jun 2018 07:08:15 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1529824095.91.0.56676864532.issue32554@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

This is what I meant. Emit a deprecation warning for input types other than explicitly supported types (but I didn't think about float), and raise an error in future.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32554>
_______________________________________

From report at bugs.python.org  Sun Jun 24 03:13:56 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 24 Jun 2018 07:13:56 +0000
Subject: [docs] [issue32142] heapq.heappop - documentation misleading or
 doesn't work
In-Reply-To: <1511712348.11.0.213398074469.issue32142@psf.upfronthosting.co.za>
Message-ID: <1529824436.15.0.56676864532.issue32142@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

We could apply David Murray's suggested wording but I don't think it would actually help anyone.  There are worked out examples from basic to advanced and a detailed section on the theory as well.

ISTM, that prior to reading the docs, the OP likely already had an incorrect mental model that caused the misreading of "maintaining" as "restoring".

For the most part, these docs have stood the test of time.  I don't see any StackOverflow questions about this either.  I recommend marking this as closed (the OP seems to now have a clear understanding of this so there isn't an open problem to be resolved).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32142>
_______________________________________

From report at bugs.python.org  Sun Jun 24 15:44:55 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 24 Jun 2018 19:44:55 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1529869495.86.0.56676864532.issue32554@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I'm thinking of something like this:

$ git diff
diff --git a/Lib/random.py b/Lib/random.py
index 1e0dcc87ed..f479e66ada 100644
--- a/Lib/random.py
+++ b/Lib/random.py
@@ -136,12 +136,17 @@ class Random(_random.Random):
             x ^= len(a)
             a = -2 if x == -1 else x

-        if version == 2 and isinstance(a, (str, bytes, bytearray)):
+        elif version == 2 and isinstance(a, (str, bytes, bytearray)):
             if isinstance(a, str):
                 a = a.encode()
             a += _sha512(a).digest()
             a = int.from_bytes(a, 'big')

+        elif not isinstance(a, (type(None), int, float, str, bytes, bytearray)):
+            _warn('Seeding based on hashing is deprecated.\n'
+                  'The only supported seed types are None, int, float, '
+                  'str, bytes, and bytearray.', DeprecationWarning, 2)
+
         super().seed(a)
         self.gauss_next = None

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32554>
_______________________________________

From report at bugs.python.org  Sun Jun 24 22:36:12 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 02:36:12 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
Message-ID: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

Doc says:

Note that str.upper().isupper() might be False if s...

Should say:

Note that s.upper().isupper() might be False if s...

PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 320395
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Fix typo in str.upper() documentation
type: enhancement
versions: Python 2.7, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Sun Jun 24 22:38:02 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 02:38:02 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529894282.59.0.902498594338.issue33952@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7504
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 00:39:42 2018
From: report at bugs.python.org (Nicolas Hainaux)
Date: Mon, 25 Jun 2018 04:39:42 +0000
Subject: [docs] [issue33934] locale.getlocale() seems wrong when the locale
 is yet unset (python3 on linux)
In-Reply-To: <1529596837.65.0.56676864532.issue33934@psf.upfronthosting.co.za>
Message-ID: <1529901582.88.0.56676864532.issue33934@psf.upfronthosting.co.za>


Nicolas Hainaux <nh.techn at gmail.com> added the comment:

I understand that the statement "when python starts, it runs using the C locale..." should not be correct anymore (and the doc should then be updated), but in fact this statement is still true on the systems I tested; only, the output of locale.getlocale() at start is in contradiction with the locale really set in fact.

It looks like the setting done by setlocale(LC_ALL, "") at an early stage is lost at some point (only locale.getlocale() seems to "remember" it).

For instance, my box locale is 'fr_FR.UTF-8', so the decimal point is a comma, but when starting python 3.7:


>>> import locale
>>> locale.str(2.4)
'2.4'                     # Wrong: if the locale in use is 'fr_FR.UTF-8', then '2,4' is expected instead
>>> locale.getlocale()
('fr_FR', 'UTF-8')
>>> locale.localeconv()
{'int_curr_symbol': '', 'currency_symbol': '', 'mon_decimal_point': '', 'mon_thousands_sep': '', 'mon_grouping': [], 'positive_sign': '', 'negative_sign': '', 'int_frac_digits': 127, 'frac_digits': 127, 'p_cs_precedes': 127, 'p_sep_by_space': 127, 'n_cs_precedes': 127, 'n_sep_by_space': 127, 'p_sign_posn': 127, 'n_sign_posn': 127, 'decimal_point': '.', 'thousands_sep': '', 'grouping': []}
>>>


Note that the output of localeconv() does match C locale, not 'fr_FR.UTF-8'.

Compare this with the outputs of locale.str() and locale.localeconv() when the locale is explicitly set at start:


>>> import locale
>>> locale.setlocale(locale.LC_ALL, '')
'LC_CTYPE=fr_FR.utf8;LC_NUMERIC=fr_FR.UTF-8;LC_TIME=fr_FR.UTF-8;LC_COLLATE=fr_FR.utf8;LC_MONETARY=fr_FR.UTF-8;LC_MESSAGES=fr_FR.utf8;LC_PAPER=fr_FR.UTF-8;LC_NAME=fr_FR.UTF-8;LC_ADDRESS=fr_FR.UTF-8;LC_TELEPHONE=fr_FR.UTF-8;LC_MEASUREMENT=fr_FR.UTF-8;LC_IDENTIFICATION=fr_FR.UTF-8'
>>> locale.str(2.4)
'2,4'                       # Correct!
>>> locale.localeconv()     # Output of localeconv() does match 'fr_FR.UTF-8' locale
{'int_curr_symbol': 'EUR ', 'currency_symbol': '?', 'mon_decimal_point': ',', 'mon_thousands_sep': '\u202f', 'mon_grouping': [3, 0], 'positive_sign': '', 'negative_sign': '-', 'int_frac_digits': 2, 'frac_digits': 2, 'p_cs_precedes': 0, 'p_sep_by_space': 1, 'n_cs_precedes': 0, 'n_sep_by_space': 1, 'p_sign_posn': 1, 'n_sign_posn': 1, 'decimal_point': ',', 'thousands_sep': '\u202f', 'grouping': [3, 0]}
>>>


Maybe the title of this issue should be turned to "at start, the C locale is in use in spite of locale.getlocale()'s output (python3 on linux)"?




As to the behaviour on Windows, I guess this is another topic (locales belonging to another world on Windows)... but it may be interesting to note that it complies with the current documentation: at start python 3.6 also uses the C locale, and the output of locale.getlocale() is consistent with that. Here is a test on Windows 10:

Python 3.6.3 (v3.6.3:2c5fed8, Oct  3 2017, 18:11:49) [MSC v.1900 64 bit (AMD64)] on win32

>>> import locale
>>> locale.getlocale()
(None, None)
>>> locale.localeconv()
{'decimal_point': '.', 'thousands_sep': '', 'grouping': [], 'int_curr_symbol': '', 'currency_symbol': '', 'mon_decimal_point': '', 'mon_thousands_sep': '', 'mon_grouping': [], 'positive_sign': '', 'negative_sign': '', 'int_frac_digits': 127, 'frac_digits': 127, 'p_cs_precedes': 127, 'p_sep_by_space': 127, 'n_cs_precedes': 127, 'n_sep_by_space': 127, 'p_sign_posn': 127, 'n_sign_posn': 127}
>>> locale.str(2.4)
'2.4'
>>> locale.getdefaultlocale()
('fr_FR', 'cp1252')

----------
components: +Library (Lib) -Documentation

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33934>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:06:14 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:06:14 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529906774.84.0.56676864532.issue33943@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset a8ddf85a84364d2c660e6670a7e06621993d1fdc by Tal Einat (Andr?s Delfino) in branch 'master':
bpo-33943: Add references in the docs for logging.basicConfig (GH-7858)
https://github.com/python/cpython/commit/a8ddf85a84364d2c660e6670a7e06621993d1fdc


----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:14:58 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:14:58 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529907298.11.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by Tal Einat <taleinat at gmail.com>:


----------
versions: +Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:17:50 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 25 Jun 2018 06:17:50 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529907470.78.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7505

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:19:49 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 25 Jun 2018 06:19:49 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529907589.04.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7506

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:26:01 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:26:01 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529907961.05.0.56676864532.issue33943@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 66d77d8af8f7c3ebd604ad1e802b8e5006d79d8f by Tal Einat (Miss Islington (bot)) in branch '3.7':
bpo-33943: Add references in the docs for logging.basicConfig (GH-7858) (GH-7900)
https://github.com/python/cpython/commit/66d77d8af8f7c3ebd604ad1e802b8e5006d79d8f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:30:24 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:30:24 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529908224.97.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests: +7507

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:31:26 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:31:26 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529908286.7.0.56676864532.issue33943@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 73848e028de58e7fb2b38bddb1638ca2323561a9 by Tal Einat (Miss Islington (bot)) in branch '3.6':
bpo-33943: Add references in the docs for logging.basicConfig (GH-7858) (GH-7899)
https://github.com/python/cpython/commit/73848e028de58e7fb2b38bddb1638ca2323561a9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:47:48 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:47:48 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529909268.08.0.902498594338.issue33943@psf.upfronthosting.co.za>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests: +7508

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 02:52:38 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 06:52:38 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529909558.6.0.56676864532.issue33943@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset aa770b7096c004abdf3c27bc361d6b60a4b668af by Tal Einat in branch '2.7':
[2.7] bpo-33943: Add references in the docs for logging.basicConfig (GH-7858) (GH-7902)
https://github.com/python/cpython/commit/aa770b7096c004abdf3c27bc361d6b60a4b668af


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 03:59:11 2018
From: report at bugs.python.org (Serge Matveenko)
Date: Mon, 25 Jun 2018 07:59:11 +0000
Subject: [docs] [issue33953] The DEFAULT_ENTROPY variable used to store the
 current default random bytes value should be documented for `secrets`
 module
Message-ID: <1529913551.53.0.56676864532.issue33953@psf.upfronthosting.co.za>


New submission from Serge Matveenko <serge at matveenko.ru>:

There is the corresponding section on the topic here https://github.com/python/cpython/blob/3.6/Doc/library/secrets.rst#how-many-bytes-should-tokens-use

The current value of 32 bytes is mentioned there correctly.

Unfortunately, there is no way to know which constant in the `secrets` stores this value.

It is easy to imagine a use case to use say `DEFAULT_ENTROPY * 4` in the code and stay updated with the default entropy being increased over time.

Thus, it looks reasonable to document the `secrets.DEFAULT_ENTROPY` constant in the module docs.

----------
assignee: docs at python
components: Documentation
messages: 320402
nosy: docs at python, lig
priority: normal
severity: normal
status: open
title: The DEFAULT_ENTROPY variable used to store the current default random bytes value should be documented for `secrets` module
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33953>
_______________________________________

From report at bugs.python.org  Mon Jun 25 04:25:45 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 25 Jun 2018 08:25:45 +0000
Subject: [docs] [issue33934] locale.getlocale() seems wrong when the locale
 is yet unset (python3 on linux)
In-Reply-To: <1529596837.65.0.56676864532.issue33934@psf.upfronthosting.co.za>
Message-ID: <1529915145.94.0.56676864532.issue33934@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

When testing this issue, I found a bug in Python :-(

I opened bpo-33954: float.__format__('n') fails with _PyUnicode_CheckConsistency assertion error.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33934>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:34:33 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:34:33 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529922873.65.0.56676864532.issue33952@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 4a6e746079441d18c30e3c4d014f106faaf7792f by Tal Einat (Andr?s Delfino) in branch 'master':
bpo-33952: Fix typo in str.upper() documentation (GH-7898)
https://github.com/python/cpython/commit/4a6e746079441d18c30e3c4d014f106faaf7792f


----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:35:40 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 25 Jun 2018 10:35:40 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529922940.97.0.902498594338.issue33952@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7509

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:36:04 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:36:04 +0000
Subject: [docs] [issue33943] doc Add references to logging.basicConfig
In-Reply-To: <1529682356.57.0.56676864532.issue33943@psf.upfronthosting.co.za>
Message-ID: <1529922964.44.0.56676864532.issue33943@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

Thanks for the PR, Andr?s! Merged and backported.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33943>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:37:32 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 25 Jun 2018 10:37:32 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529923052.98.0.902498594338.issue33952@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7510

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:41:45 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:41:45 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529923305.12.0.902498594338.issue33952@psf.upfronthosting.co.za>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests: +7511

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:42:22 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:42:22 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529923342.95.0.56676864532.issue33952@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 80f1a908a87e55c318776fb8e6f8c21d8a8664ef by Tal Einat (Miss Islington (bot)) in branch '3.7':
bpo-33952: Fix typo in str.upper() documentation (GH-7898) (GH-7903)
https://github.com/python/cpython/commit/80f1a908a87e55c318776fb8e6f8c21d8a8664ef


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:44:19 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:44:19 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529923459.01.0.56676864532.issue33952@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset ac5a6e35ef4a73846136804fff924760ec67ebbd by Tal Einat (Miss Islington (bot)) in branch '3.6':
bpo-33952: Fix typo in str.upper() documentation (GH-7898) (GH-7904)
https://github.com/python/cpython/commit/ac5a6e35ef4a73846136804fff924760ec67ebbd


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:47:26 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:47:26 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529923646.47.0.56676864532.issue33952@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 78209734a0ecd1567f819d95314b1c7c9b26f48a by Tal Einat in branch '2.7':
[2.7] bpo-33952: Fix typo in str.upper() documentation (GH-7898) (GH-7905)
https://github.com/python/cpython/commit/78209734a0ecd1567f819d95314b1c7c9b26f48a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:48:36 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 10:48:36 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529923716.23.0.56676864532.issue33952@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:

Thanks for the PR, Andr?s! Merged and backported.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 06:50:11 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 25 Jun 2018 10:50:11 +0000
Subject: [docs] [issue33934] locale.getlocale() seems wrong when the locale
 is yet unset (python3 on linux)
In-Reply-To: <1529596837.65.0.56676864532.issue33934@psf.upfronthosting.co.za>
Message-ID: <1529923811.85.0.56676864532.issue33934@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Ah, part of the confusion is that I misremembered the command we run implicitly during startup - it's only `setlocale(LC_CTYPE, "")`, not `setlocale(LC_ALL, "")`.

However, the default category for `locale.getlocale()` is `LC_CTYPE`, so it reports the text encoding locale configured during startup, not the C level default.

The difference on Windows is expected - the startup code that implicitly runs `setlocale(LC_CTYPE, "")` doesn't get compiled in there.

So I think we have a few different potential ways of viewing this bug report:

1. As a docs issue, where we advise users to run `locale.getlocale(locale.LC_MESSAGES)` to find out whether or not a specific locale really has been configured (vs the interpreter's default text encoding change that runs implicitly on startup)
2. As a defaults change for 3.8+, where we switch `locale.getlocale()` over to checking `locale.LC_MESSAGES` instead of `locale.LC_CTYPES`, since the interpreter always sets the latter on startup, so it doesn't convey much useful information.
3. As (1) for maintenance releases, and as (2) for 3.8+

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33934>
_______________________________________

From report at bugs.python.org  Mon Jun 25 07:04:04 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 11:04:04 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1529924644.51.0.56676864532.issue33573@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset fdd6e0bf18517c3dc5e24c48fbfe890229fad1b5 by Tal Einat in branch 'master':
bpo-33573: docs to suggest median() alternatives for non-numeric data (GH-7587)
https://github.com/python/cpython/commit/fdd6e0bf18517c3dc5e24c48fbfe890229fad1b5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33573>
_______________________________________

From report at bugs.python.org  Mon Jun 25 07:05:19 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 25 Jun 2018 11:05:19 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1529924719.58.0.902498594338.issue33573@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7512

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33573>
_______________________________________

From report at bugs.python.org  Mon Jun 25 07:06:13 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 25 Jun 2018 11:06:13 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1529924773.8.0.902498594338.issue33573@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7513

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33573>
_______________________________________

From report at bugs.python.org  Mon Jun 25 07:18:56 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 11:18:56 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1529925536.81.0.56676864532.issue33573@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 150cd3cb272021e9a2d865dd28486b00199fe77d by Tal Einat (Miss Islington (bot)) in branch '3.7':
[3.7] bpo-33573: docs to suggest median() alternatives for non-numeric data (GH-7587) (GH-7906)
https://github.com/python/cpython/commit/150cd3cb272021e9a2d865dd28486b00199fe77d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33573>
_______________________________________

From report at bugs.python.org  Mon Jun 25 07:27:04 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 11:27:04 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1529926023.98.0.56676864532.issue33573@psf.upfronthosting.co.za>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 8fd8cfa369fe4b6d6ac430cd28ead32717df7bee by Tal Einat (Miss Islington (bot)) in branch '3.6':
[3.6] bpo-33573: docs to suggest median() alternatives for non-numeric data (GH-7587) (GH-7907)
https://github.com/python/cpython/commit/8fd8cfa369fe4b6d6ac430cd28ead32717df7bee


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33573>
_______________________________________

From report at bugs.python.org  Mon Jun 25 07:27:42 2018
From: report at bugs.python.org (Tal Einat)
Date: Mon, 25 Jun 2018 11:27:42 +0000
Subject: [docs] [issue33573] statistics.median does not work with ordinal
 scale, add doc
In-Reply-To: <1526671785.76.0.682650639539.issue33573@psf.upfronthosting.co.za>
Message-ID: <1529926062.46.0.902498594338.issue33573@psf.upfronthosting.co.za>


Change by Tal Einat <taleinat at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33573>
_______________________________________

From report at bugs.python.org  Mon Jun 25 09:28:07 2018
From: report at bugs.python.org (Al-Scandar Solstag)
Date: Mon, 25 Jun 2018 13:28:07 +0000
Subject: [docs] [issue33774] Document that @lru_cache caches based on
 exactly how the function arguments are specified
In-Reply-To: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>
Message-ID: <1529933287.47.0.56676864532.issue33774@psf.upfronthosting.co.za>


Al-Scandar Solstag <solstag at member.fsf.org> added the comment:

Speaking frankly, I might not have grasped what might happen by reading your line. I think having at least a minimal example is crucial. Perhaps:

"Distinct argument patterns, such as `f(1)` and `f(first_arg=1)`, may not cache for each other even if the underlying function sees them as equivalent calls."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33774>
_______________________________________

From report at bugs.python.org  Mon Jun 25 13:06:31 2018
From: report at bugs.python.org (Srinivas Reddy T)
Date: Mon, 25 Jun 2018 17:06:31 +0000
Subject: [docs] [issue33774] Document that @lru_cache caches based on
 exactly how the function arguments are specified
In-Reply-To: <1528217935.32.0.592728768989.issue33774@psf.upfronthosting.co.za>
Message-ID: <1529946391.43.0.56676864532.issue33774@psf.upfronthosting.co.za>


Srinivas  Reddy T <thatiparthysreenivas at gmail.com> added the comment:

Hi Raymond,
           I find your statement hard to understand.I agree with Solstag, it is always helpful to have an example.

+1 for solstag wording.

----------
nosy: +thatiparthy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33774>
_______________________________________

From report at bugs.python.org  Mon Jun 25 14:36:53 2018
From: report at bugs.python.org (Srinivas Reddy T)
Date: Mon, 25 Jun 2018 18:36:53 +0000
Subject: [docs] [issue33957] use correct term than generic wording
Message-ID: <1529951813.18.0.56676864532.issue33957@psf.upfronthosting.co.za>


New submission from Srinivas  Reddy T <thatiparthysreenivas at gmail.com>:

I think it is better to use "Big-O notation" than a generic wording "computer science notation". I understand  the use of latter, but i guess it helps the programmer since it makes him/her to google it or ask some one if he/she didn't know it yet.

----------
assignee: docs at python
components: Documentation
messages: 320433
nosy: docs at python, thatiparthy
priority: normal
pull_requests: 7515
severity: normal
status: open
title: use correct term than generic wording
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33957>
_______________________________________

From report at bugs.python.org  Mon Jun 25 14:52:04 2018
From: report at bugs.python.org (Srinivas Reddy T)
Date: Mon, 25 Jun 2018 18:52:04 +0000
Subject: [docs] [issue33957] use standard term than generic wording
In-Reply-To: <1529951813.18.0.56676864532.issue33957@psf.upfronthosting.co.za>
Message-ID: <1529952724.22.0.902498594338.issue33957@psf.upfronthosting.co.za>


Change by Srinivas  Reddy T <thatiparthysreenivas at gmail.com>:


----------
title: use correct term than generic wording -> use standard term than generic wording

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33957>
_______________________________________

From report at bugs.python.org  Mon Jun 25 15:32:55 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 19:32:55 +0000
Subject: [docs] [issue33877] Doc: Delete UNIX qualification for script
 running instructions
In-Reply-To: <1529120030.12.0.56676864532.issue33877@psf.upfronthosting.co.za>
Message-ID: <1529955175.92.0.902498594338.issue33877@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33877>
_______________________________________

From report at bugs.python.org  Mon Jun 25 15:33:18 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 19:33:18 +0000
Subject: [docs] [issue33952] doc Fix typo in str.upper() documentation
In-Reply-To: <1529894172.0.0.56676864532.issue33952@psf.upfronthosting.co.za>
Message-ID: <1529955198.98.0.902498594338.issue33952@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33952>
_______________________________________

From report at bugs.python.org  Mon Jun 25 15:33:45 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 19:33:45 +0000
Subject: [docs] [issue33869] doc Add link to list definition in Glossary
 list entry
In-Reply-To: <1529073801.77.0.947875510639.issue33869@psf.upfronthosting.co.za>
Message-ID: <1529955225.58.0.902498594338.issue33869@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
title: doc Add set, frozen set, and tuple entries to Glossary -> doc Add link to list definition in Glossary list entry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33869>
_______________________________________

From report at bugs.python.org  Mon Jun 25 15:55:15 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 19:55:15 +0000
Subject: [docs] [issue33883] doc Mention mypy, pyrex,
 pytype and PyAnnotate in FAQ
In-Reply-To: <1529196736.16.0.56676864532.issue33883@psf.upfronthosting.co.za>
Message-ID: <1529956515.55.0.56676864532.issue33883@psf.upfronthosting.co.za>


Andr?s Delfino <adelfino at gmail.com> added the comment:

I'm adding Pyre to the list of type checkers. I have also simplified the proposed text.

----------
title: doc Mention mypy, pytype and PyAnnotate in FAQ -> doc Mention mypy, pyrex, pytype and PyAnnotate in FAQ

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33883>
_______________________________________

From report at bugs.python.org  Mon Jun 25 15:56:29 2018
From: report at bugs.python.org (Philip Kendall)
Date: Mon, 25 Jun 2018 19:56:29 +0000
Subject: [docs] [issue33958] Unused variable in pur embedding example
Message-ID: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>


New submission from Philip Kendall <jorallan at gmail.com>:

Line 6 of the "Pure Embedding" example at https://docs.python.org/3/extending/embedding.html#pure-embedding :

PyObject *pName, *pModule, *pDict, *pFunc;

contains the pDict variable which is not used anywhere else in the code, giving a compiler warning. Simple fix: just remove pDict from the list of variables.

I can make a PR if you need one.

----------
assignee: docs at python
components: Documentation
messages: 320436
nosy: Philip Kendall, docs at python
priority: normal
severity: normal
status: open
title: Unused variable in pur embedding example
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Mon Jun 25 16:20:02 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 20:20:02 +0000
Subject: [docs] [issue33959] doc Remove time complexity mention from list
 Glossary entry
Message-ID: <1529958002.86.0.56676864532.issue33959@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

Per Raymond's comment in msg319931 I believe time complexity for list items access should be removed from the Glossary.

----------
assignee: docs at python
components: Documentation
messages: 320437
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Remove time complexity mention from list Glossary entry
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33959>
_______________________________________

From report at bugs.python.org  Mon Jun 25 16:21:28 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 25 Jun 2018 20:21:28 +0000
Subject: [docs] [issue33959] doc Remove time complexity mention from list
 Glossary entry
In-Reply-To: <1529958002.86.0.56676864532.issue33959@psf.upfronthosting.co.za>
Message-ID: <1529958088.23.0.902498594338.issue33959@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7516
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33959>
_______________________________________

From report at bugs.python.org  Mon Jun 25 17:13:39 2018
From: report at bugs.python.org (Emily Morehouse)
Date: Mon, 25 Jun 2018 21:13:39 +0000
Subject: [docs] [issue33958] Unused variable in pur embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1529961219.57.0.56676864532.issue33958@psf.upfronthosting.co.za>


Emily Morehouse <emily at cuttlesoft.com> added the comment:

Thanks, Philip! If you're interested in submitting a PR, please do! If not, just comment back so someone else can pick it up.

----------
nosy: +emilyemorehouse
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Mon Jun 25 17:54:55 2018
From: report at bugs.python.org (Chris Cogdon)
Date: Mon, 25 Jun 2018 21:54:55 +0000
Subject: [docs] [issue33961] Inconsistency in exceptions for
 dataclasses.dataclass documentation
Message-ID: <1529963695.74.0.56676864532.issue33961@psf.upfronthosting.co.za>


New submission from Chris Cogdon <chris at cogdon.org>:

The documentation for dataclasses.dataclass includes this text:

"If any of the added methods already exist on the class, a TypeError will be raised."

However, the documentation for various options has ONE case of TypeError, some cases of ValueError and other cases of "does nothing".

I'll attempt a fix and create a PR for this.

----------
assignee: docs at python
components: Documentation
messages: 320444
nosy: chriscog, docs at python
priority: normal
severity: normal
status: open
title: Inconsistency in exceptions for dataclasses.dataclass documentation
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33961>
_______________________________________

From report at bugs.python.org  Mon Jun 25 18:11:29 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 25 Jun 2018 22:11:29 +0000
Subject: [docs] [issue33961] Inconsistency in exceptions for
 dataclasses.dataclass documentation
In-Reply-To: <1529963695.74.0.56676864532.issue33961@psf.upfronthosting.co.za>
Message-ID: <1529964689.8.0.902498594338.issue33961@psf.upfronthosting.co.za>


Change by Eric V. Smith <eric at trueblade.com>:


----------
nosy: +eric.smith
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33961>
_______________________________________

From report at bugs.python.org  Mon Jun 25 18:49:42 2018
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Jun 2018 22:49:42 +0000
Subject: [docs] [issue33961] Inconsistency in exceptions for
 dataclasses.dataclass documentation
In-Reply-To: <1529963695.74.0.56676864532.issue33961@psf.upfronthosting.co.za>
Message-ID: <1529966982.81.0.902498594338.issue33961@psf.upfronthosting.co.za>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +7521
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33961>
_______________________________________

From report at bugs.python.org  Mon Jun 25 18:54:10 2018
From: report at bugs.python.org (Chris Cogdon)
Date: Mon, 25 Jun 2018 22:54:10 +0000
Subject: [docs] [issue33961] Inconsistency in exceptions for
 dataclasses.dataclass documentation
In-Reply-To: <1529963695.74.0.56676864532.issue33961@psf.upfronthosting.co.za>
Message-ID: <1529967250.8.0.56676864532.issue33961@psf.upfronthosting.co.za>


Chris Cogdon <chris at cogdon.org> added the comment:

Also, one occurrence of s/:/;/

This is my First PR! I've read the contribution docs, but am very open to correction.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33961>
_______________________________________

From report at bugs.python.org  Mon Jun 25 18:55:38 2018
From: report at bugs.python.org (Chris Cogdon)
Date: Mon, 25 Jun 2018 22:55:38 +0000
Subject: [docs] [issue33961] Inconsistency in exceptions for
 dataclasses.dataclass documentation
In-Reply-To: <1529963695.74.0.56676864532.issue33961@psf.upfronthosting.co.za>
Message-ID: <1529967338.05.0.56676864532.issue33961@psf.upfronthosting.co.za>


Chris Cogdon <chris at cogdon.org> added the comment:

CLA signed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33961>
_______________________________________

From report at bugs.python.org  Mon Jun 25 23:05:22 2018
From: report at bugs.python.org (ppperry)
Date: Tue, 26 Jun 2018 03:05:22 +0000
Subject: [docs] [issue33460] "..." is used to confusingly indicate many
 different things in chapter 3
In-Reply-To: <1525995197.73.0.682650639539.issue33460@psf.upfronthosting.co.za>
Message-ID: <1529982322.39.0.902498594338.issue33460@psf.upfronthosting.co.za>


Change by ppperry <mapreader at olum.org>:


----------
title: ... used to indicate many different things in chapter 3, some are confusing -> "..." is used to confusingly indicate many different things in chapter 3

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33460>
_______________________________________

From report at bugs.python.org  Tue Jun 26 00:51:38 2018
From: report at bugs.python.org (Srinivas Reddy T)
Date: Tue, 26 Jun 2018 04:51:38 +0000
Subject: [docs] [issue33958] Unused variable in pur embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1529988698.9.0.902498594338.issue33958@psf.upfronthosting.co.za>


Change by Srinivas  Reddy T <thatiparthysreenivas at gmail.com>:


----------
keywords: +patch
pull_requests: +7535
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Tue Jun 26 04:16:55 2018
From: report at bugs.python.org (Philip Kendall)
Date: Tue, 26 Jun 2018 08:16:55 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530001015.42.0.56676864532.issue33958@psf.upfronthosting.co.za>


Philip Kendall <jorallan at gmail.com> added the comment:

Thanks thatiparthy :-)

----------
title: Unused variable in pur embedding example -> Unused variable in pure embedding example

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Tue Jun 26 04:28:34 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 26 Jun 2018 08:28:34 +0000
Subject: [docs] [issue33957] use standard term than generic wording
In-Reply-To: <1529951813.18.0.56676864532.issue33957@psf.upfronthosting.co.za>
Message-ID: <1530001714.51.0.902498594338.issue33957@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
keywords: +patch
pull_requests: +7537
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33957>
_______________________________________

From report at bugs.python.org  Tue Jun 26 04:32:46 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 26 Jun 2018 08:32:46 +0000
Subject: [docs] [issue33957] use standard term than generic wording
In-Reply-To: <1529951813.18.0.56676864532.issue33957@psf.upfronthosting.co.za>
Message-ID: <1530001966.02.0.902498594338.issue33957@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy 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/issue33957>
_______________________________________

From report at bugs.python.org  Tue Jun 26 04:47:20 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 26 Jun 2018 08:47:20 +0000
Subject: [docs] [issue33957] use standard term than generic wording
In-Reply-To: <1529951813.18.0.56676864532.issue33957@psf.upfronthosting.co.za>
Message-ID: <1530002840.39.0.56676864532.issue33957@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 829b7669f070a6228bba5c7a10a05b12891a95fd by Miss Islington (bot) in branch '3.7':
bpo-33957: Doc: Use better wording (GH-7912)
https://github.com/python/cpython/commit/829b7669f070a6228bba5c7a10a05b12891a95fd


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33957>
_______________________________________

From report at bugs.python.org  Tue Jun 26 08:25:30 2018
From: report at bugs.python.org (James Stevens)
Date: Tue, 26 Jun 2018 12:25:30 +0000
Subject: [docs] [issue33970] bugs.python.org silently refuses registrations
Message-ID: <1530015930.72.0.56676864532.issue33970@psf.upfronthosting.co.za>


New submission from James Stevens <james.stevens at jrcs.co.uk>:

bugs.python.org silently refuses registration if the user's "homepage" does not match some undisclosed URL validation test.

The fact of the validation failure of the "homepage" is not disclosed at any time, including both the initial registration and at activation time.

This appears to have been a "known" issue for at least a year, but is still not fixed.

http://psf.upfronthosting.co.za/roundup/meta/issue591

----------
assignee: docs at python
components: Documentation
messages: 320488
nosy: docs at python, james_r_c_stevens
priority: normal
severity: normal
status: open
title: bugs.python.org silently refuses registrations
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33970>
_______________________________________

From report at bugs.python.org  Tue Jun 26 08:39:47 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 26 Jun 2018 12:39:47 +0000
Subject: [docs] [issue33970] bugs.python.org silently refuses registrations
In-Reply-To: <1530015930.72.0.56676864532.issue33970@psf.upfronthosting.co.za>
Message-ID: <1530016787.66.0.56676864532.issue33970@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks for the report.
As you have found out, the issue tracker for the bug tracker itself is not here.

It seems to be a problem in upstream roundup.

If you can help with fixing this issue, please see the discussion in 
http://psf.upfronthosting.co.za/roundup/meta/issue591
as well as http://issues.roundup-tracker.org/issue2550920

You can also read https://wiki.python.org/moin/TrackerDevelopment about development of the bug tracker itself.

----------
assignee: docs at python -> 
components:  -Documentation
nosy: +Mariatta
resolution:  -> third party
stage:  -> resolved
status: open -> closed
versions:  -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33970>
_______________________________________

From report at bugs.python.org  Tue Jun 26 09:35:56 2018
From: report at bugs.python.org (James Stevens)
Date: Tue, 26 Jun 2018 13:35:56 +0000
Subject: [docs] [issue33971] os.mknod is subject to "umask"
Message-ID: <1530020156.39.0.56676864532.issue33971@psf.upfronthosting.co.za>


New submission from James Stevens <james.stevens at jrcs.co.uk>:

As per the underlying "libc" call, the node created with "mknod" is subjected to the user's current umask setting.

This is not made clear in the Python documentation, but the "libc" documentation makes this clear (see attached).

----------
assignee: docs at python
components: Documentation
files: Selection_2018-06-26_003.png
messages: 320490
nosy: docs at python, james_r_c_stevens
priority: normal
severity: normal
status: open
title: os.mknod is subject to "umask"
versions: Python 3.6
Added file: https://bugs.python.org/file47653/Selection_2018-06-26_003.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33971>
_______________________________________

From report at bugs.python.org  Tue Jun 26 18:26:33 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 26 Jun 2018 22:26:33 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1530051993.82.0.902498594338.issue5978@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7548
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Tue Jun 26 18:28:28 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 26 Jun 2018 22:28:28 +0000
Subject: [docs] [issue5978] cProfile and profile don't work with pygtk/pyqt
 and sys.exit(0)
In-Reply-To: <1241895448.39.0.497331485225.issue5978@psf.upfronthosting.co.za>
Message-ID: <1530052108.41.0.902498594338.issue5978@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
nosy: +adelfino
versions: +Python 2.7, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue5978>
_______________________________________

From report at bugs.python.org  Wed Jun 27 05:36:18 2018
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 27 Jun 2018 09:36:18 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530092178.7.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

Another example of project affected by this regression: fontforge
https://bugzilla.redhat.com/show_bug.cgi?id=1595421

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Wed Jun 27 09:40:31 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 27 Jun 2018 13:40:31 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530106831.97.0.902498594338.issue33932@psf.upfronthosting.co.za>


Change by Nick Coghlan <ncoghlan at gmail.com>:


----------
pull_requests: +7574

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Wed Jun 27 09:52:30 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 27 Jun 2018 13:52:30 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530107550.76.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

https://github.com/python/cpython/pull/7967 amends the docs and adds the deprecation notices, but after taking another look at the way Victor's patch works, I'm thinking we may not need them: the *new* initialization API remains strict about the required state machine transitions, which means that calling `Py_Initialize` when only the core has been initialized will fail at the _Py_InitializeCore step (as that complains if the core has already been initialized).

Similarly, calling _Py_InitializeCore after Py_Initialize still fails, as the *only* case that becomes a no-op is specifically Py_InitializeEx, *after* the interpreter is fully initialized.

Given that, I think we can just keep Victor's compatibility fix indefinitely, and only have the new incremental initialization APIs be strict about the expected transitions through the state machine.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Wed Jun 27 09:55:18 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 27 Jun 2018 13:55:18 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530107718.54.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

I went ahead and closed my PR, as I'm now happy that keeping this behaviour isn't going to block anything we want to do for PEP 432.

If we change our minds and decide we want to deprecate the current behaviour after all, then we can start that deprecation process in Python 3.8.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Wed Jun 27 10:22:58 2018
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 27 Jun 2018 14:22:58 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530109378.44.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

Please keep it open until 3.7.0 is released.

----------
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Wed Jun 27 18:34:51 2018
From: report at bugs.python.org (Ned Deily)
Date: Wed, 27 Jun 2018 22:34:51 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530138890.99.0.665841612001.issue33932@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:


New changeset b940921a67fa33e8c8812aa3b7746161c2552c1d by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-33932: Calling Py_Initialize() twice does nothing (GH-7845)
https://github.com/python/cpython/commit/b940921a67fa33e8c8812aa3b7746161c2552c1d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Wed Jun 27 18:46:14 2018
From: report at bugs.python.org (Bumsik Kim)
Date: Wed, 27 Jun 2018 22:46:14 +0000
Subject: [docs] [issue33986] Typo: BaseSubprocessTransport ->
 SubprocessTransport
Message-ID: <1530139574.74.0.56676864532.issue33986@psf.upfronthosting.co.za>


New submission from Bumsik Kim <kbumsik at gmail.com>:

https://docs.python.org/3/library/asyncio-protocol.html#basesubprocesstransport

I belive the doc has a wrong name "basesubprocesstransport" and it should be "Subprocesstransport".

You can see this in the source code: https://github.com/python/cpython/blob/3.6/Lib/asyncio/transports.py

----------
assignee: docs at python
components: Documentation
messages: 320638
nosy: docs at python, kbumsik
priority: normal
severity: normal
status: open
title: Typo: BaseSubprocessTransport -> SubprocessTransport
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33986>
_______________________________________

From report at bugs.python.org  Wed Jun 27 18:47:17 2018
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 27 Jun 2018 22:47:17 +0000
Subject: [docs] [issue33986] asyncio: Typo in documentation:
 BaseSubprocessTransport -> SubprocessTransport
In-Reply-To: <1530139574.74.0.56676864532.issue33986@psf.upfronthosting.co.za>
Message-ID: <1530139637.04.0.902498594338.issue33986@psf.upfronthosting.co.za>


Change by STINNER Victor <vstinner at redhat.com>:


----------
components: +asyncio -Documentation
nosy: +asvetlov, yselivanov
title: Typo: BaseSubprocessTransport -> SubprocessTransport -> asyncio: Typo in documentation: BaseSubprocessTransport -> SubprocessTransport

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33986>
_______________________________________

From report at bugs.python.org  Wed Jun 27 21:29:46 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 28 Jun 2018 01:29:46 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530149386.7.0.56676864532.issue33932@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

Fixed in 3.7.0.  Thanks, everyone!

----------
priority: release blocker -> 
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 28 00:12:11 2018
From: report at bugs.python.org (Bumsik Kim)
Date: Thu, 28 Jun 2018 04:12:11 +0000
Subject: [docs] [issue33986] asyncio: Typo in documentation:
 BaseSubprocessTransport -> SubprocessTransport
In-Reply-To: <1530139574.74.0.56676864532.issue33986@psf.upfronthosting.co.za>
Message-ID: <1530159131.16.0.902498594338.issue33986@psf.upfronthosting.co.za>


Change by Bumsik Kim <kbumsik at gmail.com>:


----------
keywords: +patch
pull_requests: +7592
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33986>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:24:39 2018
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 28 Jun 2018 06:24:39 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530167079.24.0.902498594338.issue33958@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
versions: +Python 2.7, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:25:47 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 06:25:47 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530167147.33.0.902498594338.issue33958@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7593

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:26:31 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 06:26:31 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530167191.23.0.902498594338.issue33958@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7594

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:27:32 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 06:27:32 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530167252.07.0.902498594338.issue33958@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7595

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:31:48 2018
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 28 Jun 2018 06:31:48 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530167508.31.0.56676864532.issue33958@psf.upfronthosting.co.za>


INADA Naoki <songofacandy at gmail.com> added the comment:

thanks

----------
nosy: +inada.naoki
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:37:21 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 06:37:21 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530167841.78.0.56676864532.issue33958@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset bcb1ac82656fac22b12df387a5c6f4b10b7eefef by Miss Islington (bot) in branch '2.7':
bpo-33958: Doc: Remove unused variable in example (GH-7927)
https://github.com/python/cpython/commit/bcb1ac82656fac22b12df387a5c6f4b10b7eefef


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:41:31 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 06:41:31 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530168091.48.0.56676864532.issue33958@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 702d43cab6ae05751b357dd2e7b7fac1a594113a by Miss Islington (bot) in branch '3.7':
bpo-33958: Doc: Remove unused variable in example (GH-7927)
https://github.com/python/cpython/commit/702d43cab6ae05751b357dd2e7b7fac1a594113a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 02:45:31 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 06:45:31 +0000
Subject: [docs] [issue33958] Unused variable in pure embedding example
In-Reply-To: <1529956589.29.0.56676864532.issue33958@psf.upfronthosting.co.za>
Message-ID: <1530168331.18.0.56676864532.issue33958@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ff41cc7dee7fb2ab2ac39915a7ec6eb8808e6a1c by Miss Islington (bot) in branch '3.6':
bpo-33958: Doc: Remove unused variable in example (GH-7927)
https://github.com/python/cpython/commit/ff41cc7dee7fb2ab2ac39915a7ec6eb8808e6a1c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33958>
_______________________________________

From report at bugs.python.org  Thu Jun 28 08:42:02 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 28 Jun 2018 12:42:02 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530189722.91.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

I reopen the issue because fontforge still fails on Python 3.7.0 final. fontforge calls Py_Initialize() and then calls Py_Main() which fails with an assertion: https://bugzilla.redhat.com/show_bug.cgi?id=1595421

The same code works well on Python 3.6, so should we define this issue as a regression?

Call stack:

* Py_Main()
* pymain_main()
* _Py_InitializeCore() which fails

The problem is that the first call of Py_Initialize() sets a first configuration, but then Py_Main() sets a different configuration.

Is it correct to call Py_Initialize() before Py_Main()?

----------
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 28 08:49:55 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 28 Jun 2018 12:49:55 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530190195.52.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

I looked quickly at _Py_InitializeCore() and I'm not sure that it's designed to replace an existing configuration.

Example:

int Py_HashRandomizationFlag = 0; /* for -R and PYTHONHASHSEED */

(...)

    if (!core_config->use_hash_seed || core_config->hash_seed) {
        /* Random or non-zero hash seed */
        Py_HashRandomizationFlag = 1;
    }

If Py_Initialize() sets Py_HashRandomizationFlag to 1, but Py_Main() doesn't use an hash seed, Py_HashRandomizationFlag value remains 1 which is wrong.

pymain_read_conf() fills _PyCoreConfig from global configuration flags, but then global configuration flags are supposed to be set from the global configuration flags.

So maybe for this specific case, _Py_InitializeCore() should always set Py_HashRandomizationFlag. But it was just one example to show that right now, _Py_InitializeCore() doesn't seem to support to be called twice with two different configurations.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 28 08:51:42 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 28 Jun 2018 12:51:42 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530190302.73.0.56676864532.issue33932@psf.upfronthosting.co.za>


STINNER Victor <vstinner at redhat.com> added the comment:

Ok, now with my regression hat.

In Python 3.6, Py_Main() calls Py_Initialize(). If Py_Initialize() is called twice, the second call does nothing. So it's fine to call Py_Main() after Py_Initialize() in Python 3.6.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 28 09:17:49 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 28 Jun 2018 13:17:49 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530191869.68.0.902498594338.issue33932@psf.upfronthosting.co.za>


Change by Miro Hron?ok <miro at hroncok.cz>:


----------
nosy: +hroncok

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Thu Jun 28 11:47:17 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Thu, 28 Jun 2018 15:47:17 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1530200837.76.0.902498594338.issue32996@psf.upfronthosting.co.za>


Change by Elvis Pranskevichus <elvis at magic.io>:


----------
pull_requests: +7599

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Jun 28 11:57:40 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Thu, 28 Jun 2018 15:57:40 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1530201460.03.0.56676864532.issue32996@psf.upfronthosting.co.za>


Yury Selivanov <yselivanov at gmail.com> added the comment:


New changeset 4d26c8a177d8ada440b3cfdfb1d0423ab5ca81a7 by Yury Selivanov (Elvis Pranskevichus) in branch 'master':
bpo-32996: Enhancements to What's New based on feedback (GH-7988)
https://github.com/python/cpython/commit/4d26c8a177d8ada440b3cfdfb1d0423ab5ca81a7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Jun 28 11:58:56 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 15:58:56 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1530201536.74.0.902498594338.issue32996@psf.upfronthosting.co.za>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +7600

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Jun 28 12:14:56 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 28 Jun 2018 16:14:56 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1530202495.85.0.56676864532.issue32996@psf.upfronthosting.co.za>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 48dc7527e32512a27a58107477926719ea4c589b by Miss Islington (bot) in branch '3.7':
bpo-32996: Enhancements to What's New based on feedback (GH-7988)
https://github.com/python/cpython/commit/48dc7527e32512a27a58107477926719ea4c589b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Fri Jun 29 01:32:26 2018
From: report at bugs.python.org (Alan Huang)
Date: Fri, 29 Jun 2018 05:32:26 +0000
Subject: [docs] [issue33995] test_min_max_version in test_ssl.py fails when
 Python is built against LibreSSL;
 {min,max}imum_version behavior differs from OpenSSL
Message-ID: <1530250345.83.0.56676864532.issue33995@psf.upfronthosting.co.za>


New submission from Alan Huang <Alan.Huang at utdallas.edu>:

LibreSSL's implementation of the function used to get the minimum and maximum SSL versions supported differs from OpenSSL's.

In short, the issue is in the implementations of `SSL_CTX_new` - OpenSSL initializes variables `ret->{min,max}_proto_version` to 0, while LibreSSL initializes corresponding variables to those of the `SSL_METHOD` given.

As such, when Python is built with LibreSSL, the default values for an instance of ssl.SSLContext are, in the case of ssl.SSLContext(), ctx.minimum_version = <TLSVersion.TLSv1: 769>; ctx.maximum_version = <TLSVersion.TLSv1_2: 771>.
This is NOT what test_ssl.py expects; it expects OpenSSL's behavior of initializing the version variables to zero, which _ssl.c then translates to PY_PROTO_{MIN,MAX}IMUM_SUPPORTED -> ssl.TLSVersion.{MIN,MAX}IMUM_SUPPORTED.

Additionally, LibreSSL, when `SSL_CTX_set_{min,max}_proto_version` is called with `version` equal to zero, explicitly sets the minimum / maximum values equal to the minimum / maximum values for the `SSL_METHOD` it was called with (namely, 769/770/771, in the case of `TLS_method()`), not the minimum / maximum values supported by the library.

I have sent an email to the LibreSSL mailing list asking for clarification on this point, namely, if this is intended behavior. If it is, there are two ways that come to mind to work around this behavior. Both ways would only be necessary if `IS_LIBRESSL`.

1. Skip `test_min_max_version`.
2. Instead of testing that ctx is equal *to* the extremes after it's been set to one of the extremes, test that it's equal to the actual constants.
   There are two ways this could be accomplished as well:
      a. Use PY_PROTO_{MIN,MAX}IMUM_AVAILABLE, defined in _ssl.c (this may require the addition of another call to `PyModule_AddIntConstant` to provide access to the constant from _ssl). The downside to this approach is that it assumes that `TLS_method()`, or whatever `SSL_METHOD` test_ssl.py uses has lower and upper bounds equal to PY_PROTO_{MIN,MAX}IMUM_AVAILABLE, which may not always be the case.
      b. Access and store the values for ctx.{min,max}imum_value on creation, then reference them after setting.
   Either of these approaches would likely also have the benefit of removing the need for `self.assertIn(ctx.minimum_version, {ssl.TLSVersion.TLSv1_2, ssl.TLSVersion.TLSv1_3})`.

The test that failed was:
======================================================================
FAIL: test_min_max_version (test.test_ssl.ContextTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/alan/src/cpython/Lib/test/test_ssl.py", line 1066, in test_min_max_version
    ctx.minimum_version, ssl.TLSVersion.MINIMUM_SUPPORTED
AssertionError: <TLSVersion.TLSv1: 769> != <TLSVersion.MINIMUM_SUPPORTED: -2>

Addendum:
I found the documentation for ssl.TLSVersion.{MAX,MIN}IMUM_SUPPORTED confusing at first - it took me quite a while to realize what the purpose of the constants were; I would have expected them to contain the maximum and minimum protocol versions supported by the library; I see why it was phrased that way, after having boned up on ssl.py, _ssl.c, and OpenSSL/LibreSSL, but think it could could be made clearer.

----------
assignee: docs at python
components: Documentation, SSL, Tests
messages: 320703
nosy: Alan.Huang, alex, christian.heimes, docs at python, dstufft, janssen
priority: normal
severity: normal
status: open
title: test_min_max_version in test_ssl.py fails when Python is built against LibreSSL; {min,max}imum_version behavior differs from OpenSSL
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33995>
_______________________________________

From report at bugs.python.org  Fri Jun 29 06:23:44 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 29 Jun 2018 10:23:44 +0000
Subject: [docs] [issue33959] doc Remove time complexity mention from list
 Glossary entry
In-Reply-To: <1529958002.86.0.56676864532.issue33959@psf.upfronthosting.co.za>
Message-ID: <1530267824.87.0.902498594338.issue33959@psf.upfronthosting.co.za>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
assignee: docs at python -> rhettinger
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33959>
_______________________________________

From report at bugs.python.org  Fri Jun 29 11:48:53 2018
From: report at bugs.python.org (Geoffrey Sneddon)
Date: Fri, 29 Jun 2018 15:48:53 +0000
Subject: [docs] [issue34000] Document when compile returns a code object v.
 AST
Message-ID: <1530287332.99.0.56676864532.issue34000@psf.upfronthosting.co.za>


New submission from Geoffrey Sneddon <geoffers+pythonbugs at gmail.com>:

The compile built-in documentation says:

> Compile the source into a code or AST object.

It doesn't however go on to say when it returns each!

It does however note:

> If you want to parse Python code into its AST representation, see ast.parse().

So compile can compile the source into an AST object, but if I want to parse Python code into an AST I should use ast.parse?

As far as I can tell, this goes back to Python 2.5: https://docs.python.org/2/whatsnew/2.5.html#build-and-c-api-changes

>From the What's New page:

> It?s possible for Python code to obtain AST objects by using the compile() built-in and specifying _ast.PyCF_ONLY_AST as the value of the flags parameter

So that would seem to be the case when compile returns an AST!

Interestingly, the implementation of ast.parse *literally just calls compile* (https://github.com/python/cpython/blob/58ed7307ea0b5c5aa052291ebc3030f314f938d8/Lib/ast.py#L30-L35).

Note, however, this means a further part of the compile documentation is wrong:

> The optional arguments flags and dont_inherit control which future statements (see PEP 236) affect the compilation of source.

flags is therefore something more general than just controlling which future statements affect the source, given it also controls the output type of the function.

In short, we should:

 * document the flags argument can take _ast.PyCF_ONLY_AST *or* change the documentation to say it returns a code object (and not an AST object)

----------
assignee: docs at python
components: Documentation
messages: 320721
nosy: docs at python, gsnedders
priority: normal
severity: normal
status: open
title: Document when compile returns a code object v. AST
versions: Python 2.7, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34000>
_______________________________________

From report at bugs.python.org  Fri Jun 29 14:12:17 2018
From: report at bugs.python.org (Eric Snow)
Date: Fri, 29 Jun 2018 18:12:17 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530295937.61.0.56676864532.issue33932@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

> I looked quickly at _Py_InitializeCore() and I'm not sure
> that it's designed to replace an existing configuration.
> ...
> So maybe for this specific case, _Py_InitializeCore() should
> always set Py_HashRandomizationFlag.

+1

At the same time, the use of Py_*Flag variables is a little unclear in the PEP 432 world.  Under the PEP I'd expect code in CPython to use the core config from the current PyInterpreterState (or even _PyRuntimeState), rather than the global flag variables.  So presumably (the PEP doesn't talk about it) the intent of keeping them is to help folks that currently make use of the flags.  However, they shouldn't be modifying them after initialization, and under PEP 432 they don't need to set them beforehand (they set values on the config), right?

Part of the problem here is that Py_Main() results in all the flag variables getting set (before runtime initialization).  However, with the current PEP 432 [internal] implementation those variables are (mostly) never getting set, right?  Shouldn't we set all of them, but only at the end of _Py_InitializeCore() (for the sake of extensions/embedders that use them)?  In that case we'd need to replace our internal use of Py_HashRandomizationFlag with field on the config struct on _PyRuntimeState.

> But it was just one example to show that right now,
> _Py_InitializeCore() doesn't seem to support to be called
> twice with two different configurations.

Are there other things (than how we set that flag) that break in that case?  Regardless, what would ensure that it works properly?

----------
nosy: +emilyemorehouse

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Fri Jun 29 21:30:27 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 30 Jun 2018 01:30:27 +0000
Subject: [docs] [issue33959] doc Remove time complexity mention from list
 Glossary entry
In-Reply-To: <1529958002.86.0.56676864532.issue33959@psf.upfronthosting.co.za>
Message-ID: <1530322227.24.0.56676864532.issue33959@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Let's leave this as-is.

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33959>
_______________________________________

From report at bugs.python.org  Sat Jun 30 02:40:07 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 30 Jun 2018 06:40:07 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530340807.29.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Victor, could you file a separate issue for Py_Main(). It's a different problem, since Py_Main() is an entry point for an *application that embeds Python*. It's not a CPython API in the tradition sense.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Sat Jun 30 03:01:22 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 30 Jun 2018 07:01:22 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530342082.67.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

I filed https://bugs.python.org/issue34008 to cover the fact that "Py_Initialize(); Py_Main();" doesn't work in 3.7.0 whereas it used to sort of work (by only partially applying the settings read from the CLI and environment by the Py_Main() call).

Since "Py_Initialize(); Py_Initialize();" *does* work in 3.7.0, closing this one again.

----------
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Sat Jun 30 03:17:14 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 30 Jun 2018 07:17:14 +0000
Subject: [docs] [issue33932] Calling Py_Initialize() twice now triggers a
 fatal error (Python 3.7)
In-Reply-To: <1529586528.15.0.56676864532.issue33932@psf.upfronthosting.co.za>
Message-ID: <1530343034.83.0.56676864532.issue33932@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Answering Eric's question about the flag variables though:

* pymain_get_global_config copies the global variable flags to their respective struct entries
* pymain_set_global_config copies the various struct entries to their respective global variable flags

One of the first things that Py_Main() does in 3.7 is to:

- read the global variable flags into the relevant structs
- update the structs based on the CLI options
- write the struct values back to the global flags

This mostly fakes the 3.6-and-earlier behaviour of using the global variables directly.

For anything listed in https://docs.python.org/3/c-api/init.html#global-configuration-variables, we also mostly left any code reading the global variable directly alone, since they're considered a public API for embedding applications to dynamically adjust behaviour and we don't have a good way of deprecating using them for that purpose :(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33932>
_______________________________________

From report at bugs.python.org  Sat Jun 30 13:31:44 2018
From: report at bugs.python.org (Julian Berman)
Date: Sat, 30 Jun 2018 17:31:44 +0000
Subject: [docs] [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1530379904.23.0.56676864532.issue17894@psf.upfronthosting.co.za>


Julian Berman <Julian+Python.org at GrayVines.com> added the comment:

This seems very very slightly overly conversational (specifically the "That's all there is to it" sentence), but overall like a pretty decent improvement here.

Personally I'd axe that sentence but then seems like this should be merged as-is and any further improvements could always pile on after given how long this has sat.

----------
nosy: +Julian

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17894>
_______________________________________

From report at bugs.python.org  Sat Jun 30 21:34:22 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 01 Jul 2018 01:34:22 +0000
Subject: [docs] [issue34015] doc Add link to Descriptor HowTo Guide in Data
 Model
Message-ID: <1530408862.0.0.56676864532.issue34015@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

IMHO, it would be useful to make the Descriptor HowTo Guide more discoverable. As far as I can see, we are not linking to it from anywhere except the HOWTO index. Section 3.3.2.2., "Implementing Descriptors", in "Data Model" seems to be the most appropriate place.

----------
assignee: docs at python
components: Documentation
messages: 320821
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Add link to Descriptor HowTo Guide in Data Model
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34015>
_______________________________________

From report at bugs.python.org  Sat Jun 30 21:35:37 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sun, 01 Jul 2018 01:35:37 +0000
Subject: [docs] [issue34015] doc Add link to Descriptor HowTo Guide in Data
 Model
In-Reply-To: <1530408862.0.0.56676864532.issue34015@psf.upfronthosting.co.za>
Message-ID: <1530408937.77.0.902498594338.issue34015@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +7647
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34015>
_______________________________________

From metaprgmr at yahoo.com  Fri Jun 15 11:50:48 2018
From: metaprgmr at yahoo.com (James Huang)
Date: Fri, 15 Jun 2018 15:50:48 -0000
Subject: [docs] https://docs.python.org/fr/3/download.html all links 404
 <eom>
References: <1748091789.933346.1529076622815.ref@mail.yahoo.com>
Message-ID: <1748091789.933346.1529076622815@mail.yahoo.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180615/f3cf1311/attachment-0001.html>

From kung.te at gmail.com  Mon Jun 18 15:04:28 2018
From: kung.te at gmail.com (Kung Te Yang)
Date: Mon, 18 Jun 2018 19:04:28 -0000
Subject: [docs] Python Documentation EPUB
Message-ID: <CANa7eXqKPmkLtmf5EsL7H4j6GcZv_8G2Y6isfN7S5gWPTYCmiQ@mail.gmail.com>

Hi,

I'm trying to upload the Python 3.6.6rc1 documentation epub to my
Google Books but it is not compatible to epub 2.0 or 3.0.
Is possible convert it to one of those format?

Best regards,
--
Kung Te Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180618/ddd680d3/attachment-0001.html>

From wec3217 at gmail.com  Tue Jun 19 13:00:00 2018
From: wec3217 at gmail.com (Weihe Chen)
Date: Tue, 19 Jun 2018 17:00:00 -0000
Subject: [docs] configparser example typo
Message-ID: <CABwE9+QjzGNc_D6Du=9FJM8qqKmJo613K0SKDKe9PTcDX6A_bA@mail.gmail.com>

To whom it may concern,

In the page https://docs.python.org/3/library/configparser.html, under
14.2.1 Quick Start, example 2 with code:

>>> import configparser>>> config = configparser.ConfigParser()>>> config['DEFAULT'] = {'ServerAliveInterval': '45',...                      'Compression': 'yes',...                      'CompressionLevel': '9'}>>> config['bitbucket.org'] = {}>>> config['bitbucket.org']['User'] = 'hg'>>> config['topsecret.server.com'] = {}>>> topsecret = config['topsecret.server.com']>>> topsecret['Port'] = '50022'     # mutates the parser>>> topsecret['ForwardX11'] = 'no'  # same here>>> config['DEFAULT']['ForwardX11'] = 'yes'>>> with open('example.ini', 'w') as configfile:...   config.write(configfile)...

 Shouldn't the last line be configfile.write(config) ?

Weihe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180619/ac6ec3ee/attachment-0001.html>

From 353536233 at qq.com  Sat Jun 23 05:40:02 2018
From: 353536233 at qq.com (=?utf-8?B?5pa55bel?=)
Date: Sat, 23 Jun 2018 09:40:02 -0000
Subject: [docs] documentation bug: window htmlhelp display text
Message-ID: <tencent_0688FEF7720DBE4F83DFDCA60441B0721109@qq.com>

in chm version of docs, there are many display errors, shown in picture attached.
may be html encoding problem?
docs.python.org online documentation has no such problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180623/3b22d523/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pydoc_bug_365.png
Type: application/octet-stream
Size: 56295 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180623/3b22d523/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pydoc_bug_366rc1.png
Type: application/octet-stream
Size: 60511 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180623/3b22d523/attachment-0003.obj>

From ahiraldo41 at gmail.com  Sun Jun 24 15:08:10 2018
From: ahiraldo41 at gmail.com (Angel Hiraldo)
Date: Sun, 24 Jun 2018 19:08:10 -0000
Subject: [docs] (no subject)
Message-ID: <BLUPR0401MB1635C7CF07EC529A61630E47A74B0@BLUPR0401MB1635.namprd04.prod.outlook.com>

theres a bug in 3.7 that makes asyncio.create_subprocess_exec crash the project


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180624/d93e9b67/attachment.html>

From EdgerLA at corning.com  Fri Jun 22 14:46:02 2018
From: EdgerLA at corning.com (Edger, Lisa A)
Date: Fri, 22 Jun 2018 18:46:02 -0000
Subject: [docs] can python be used by a commercial company on their servers?
Message-ID: <8F7B6D7D7F2A4D43BFF6ADF60408AD07A0CD5FDC@KMCI0XMB2004.na.corning.com>

Please let me know. I can find a way to contact anyone on this??

Lisa Edger, CSAM
Certified Software Asset Manager
License Management & Software Compliance

Corning Incorporated
SP-ZV-01-F3L
21 Lynn Morse Dr.
Painted Post, NY 14870

t (607)974-9114
m (607)684-8190
edgerla at corning.com<mailto:briggsaa at corning.com>

Reach Software Management on Blue Line<https://www.yammer.com/corning.com/#/threads/inGroup?type=in_group&feedId=11917664&view=unviewed>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180622/a69cf58a/attachment.html>

From johnnylutz at gmail.com  Wed Jun 27 19:41:11 2018
From: johnnylutz at gmail.com (John Talent)
Date: Wed, 27 Jun 2018 19:41:11 -0400
Subject: [docs] ingx
Message-ID: <CAKaiSK9vTNhDFyemJVL50v2SCOfsf4z4QLtK8rNhyP=owawLMA@mail.gmail.com>

You're using ingx, how quaint.

Your 3.x documentation is not downloadable. La di da.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180627/05006b6a/attachment.html>

From khatri.mann at gmail.com  Tue Jun 19 15:22:12 2018
From: khatri.mann at gmail.com (Mann Khatri)
Date: Tue, 19 Jun 2018 19:22:12 -0000
Subject: [docs] Bug
Message-ID: <CAKOJaZFgbh_p3t2zNFPuU+3Exm0TNZe43+xt1OT4yYUW2Y+GVg@mail.gmail.com>

I don't know whether it should really be called as "bug"

*What I found*

>> import numpy as pandas
>>

It works....

Suggestion:
We can use dictionary of installed libraries on a system and can loop over
it to find whether post 'as' string is already installed library or not
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180619/8fbb7dbe/attachment.html>