From report at bugs.python.org  Tue May  1 06:02:28 2018
From: report at bugs.python.org (Julien Palard)
Date: Tue, 01 May 2018 10:02:28 +0000
Subject: [docs] [issue20709] os.utime(path_to_directory): wrong
 documentation for Windows.
In-Reply-To: <1392937056.04.0.541478480244.issue20709@psf.upfronthosting.co.za>
Message-ID: <1525168948.57.0.682650639539.issue20709@psf.upfronthosting.co.za>


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


New changeset 7508a54c77e85235e07e344cf9440e5b4695e9cc by Julien Palard (St?phane Wirtel) in branch 'master':
bpo-20709: os.utime(path_to_directory): wrong documentation for Windows. (GH-5469)
https://github.com/python/cpython/commit/7508a54c77e85235e07e344cf9440e5b4695e9cc


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

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

From vladimir.guillochet at gmx.fr  Tue May  1 09:54:50 2018
From: vladimir.guillochet at gmx.fr (Vladimir Guillochet gmx)
Date: Tue, 1 May 2018 15:54:50 +0200
Subject: [docs] Impossible de telecharger la documentation
Message-ID: <a2c3dbe1-207c-0d01-015b-00591dbab7e3@gmx.fr>

Bonjour,


Le lien de t?l?chargement de la documentation python ne fonctionne pas.


Pouvez vous y rem?dier ?


Cordialement,


From report at bugs.python.org  Wed May  2 10:03:26 2018
From: report at bugs.python.org (Ben FrantzDale)
Date: Wed, 02 May 2018 14:03:26 +0000
Subject: [docs] [issue33275] glob.glob should explicitly note that results
 aren't sorted
In-Reply-To: <1523644726.46.0.682650639539.issue33275@psf.upfronthosting.co.za>
Message-ID: <1525269806.39.0.682650639539.issue33275@psf.upfronthosting.co.za>


Ben FrantzDale <ben at formlabs.com> added the comment:

I looked into it a bit more. With python 2.7 on macOS High Sierra on APFS (Encrypted) with a FAT32 thumb drive... I have a directory that glob.glob('/Volumes/thumb/tmp/*') shows as sorted. I cp -r that to /tmp with bash. glob.glob('/tmp/tmp/*') is now not sorted. and cp -r /tmp/tmp /Volumes/thumb/tmp1. Then glob.glob('/Volumes/thumb/tmp/*') shows a different order, but if I cp -r /Volumes/thumb/tmp/ /Volumes/thumb/tmp2 then glob.glob('/Volumes/thumb/tmp2/*') is sorted by file name just like glob.glob('/Volumes/thumb/tmp/*'). I'm not sue what that's saying other than that glob.glob can return things out of order on FAT32. It appears that glob.glob's ordering agrees with that of ls -f ("unsorted").

----------

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

From report at bugs.python.org  Wed May  2 14:10:08 2018
From: report at bugs.python.org (Eryk Sun)
Date: Wed, 02 May 2018 18:10:08 +0000
Subject: [docs] [issue33275] glob.glob should explicitly note that results
 aren't sorted
In-Reply-To: <1523644726.46.0.682650639539.issue33275@psf.upfronthosting.co.za>
Message-ID: <1525284608.17.0.682650639539.issue33275@psf.upfronthosting.co.za>


Eryk Sun <eryksun at gmail.com> added the comment:

FAT inserts a new file entry in a directory at the first available position. (If it's a long filename, this could be up to 21 contiguous dirents for a combined long/short dirent set.) This means a directory listing is usually in the same order that files were added. One caveat is that dirents for deleted files may be reused once there are no more unused entries available in a cluster. (I'd expect this depends on the implementation. Also, this is less likely with a long filename, since it needs a large-enough contiguous block of dirents.) Given a volume with a 4 KiB cluster size, sans overhead there are 127 32-byte dirents in a cluster.

I used to have an MP3 player that used FAT32 and only played files in directory order, so I had to resort directories on disk after adding files. In Ubuntu Linux, I see there's a "fatsort" package that implements this. There's probably a build available for MacOS.

----------

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

From report at bugs.python.org  Thu May  3 06:30:05 2018
From: report at bugs.python.org (weapon)
Date: Thu, 03 May 2018 10:30:05 +0000
Subject: [docs] [issue33417] Isinstance() behavior is not consistent with
 the document
Message-ID: <1525343405.44.0.682650639539.issue33417@psf.upfronthosting.co.za>


New submission from weapon <hongweichen8888 at sina.com>:

In the PEP 3119(https://www.python.org/dev/peps/pep-3119/),it introduce about Customizing instance and subclass checks.

>The primary mechanism proposed here is to allow overloading the built-in functions isinstance() and issubclass(). The overloading works as follows: The call isinstance(x, C) first checks whether C.__instancecheck__ exists, and if so, calls C.__instancecheck__(x) instead of its normal implementation.


but my code doesn't works.
```
class Sizeable(object):
    def __instancecheck__(cls, instance):
        print("__instancecheck__ call")
        return hasattr(instance, "__len__")

class B(object):
    pass

b = B()
print(isinstance(b, Sizeable)) # output:False
```
The __instancecheck__ function  is not called. In PyObject_IsInstance,when isinstance(x, C) the following three conditions are reached, __instancecheck__ will take effect:
1. x can not be directly instantiated by C;

2. The C class specifies the metaclass;

3. The __instancecheck__ in the specified metaclass class is defined.

This code can work:
```
class MetaSizeable(type):
    def __instancecheck__(cls, instance):
        print("__instancecheck__ call")
        return hasattr(instance, "__len__")

class Sizeable(metaclass=MetaSizeable):
    pass

class B(object):
    pass

b = B()
print(isinstance(b, Sizeable))  # output: False
print(isinstance([], Sizeable)) # output: True
```

So,the problem is that the document does not conform to the reality.Can it be guaranteed that __instancecheck__  is always called?

If yes: PyObject_IsInstance should be tweaked.
If no:  document should be tweaked.

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 316118
nosy: docs at python, hongweipeng
priority: normal
severity: normal
status: open
title: Isinstance() behavior is not consistent with the document
type: behavior
versions: Python 3.7

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

From vaos.mobile at gmail.com  Wed May  2 13:49:49 2018
From: vaos.mobile at gmail.com (Christopher Schmitt)
Date: Wed, 02 May 2018 17:49:49 +0000
Subject: [docs] Missing change documentation
Message-ID: <CAAJQNd_nKLL5eWt4K3Lk1=Ccg01YRz=GtQdagWVj97FB0ywuVQ@mail.gmail.com>

Hello,

Just found a missing "changed in version" text....

while the "os" lib has a "Changed in version 3.6: Accepts a path-like
object." Text.
This is totally missing in the shutil lib. (okay you could use the argument
that shutil is using os lib and links to it but in the first moment it
totally confused me why my script wasn't working on 3.5)

Greetings,
Christopher Schmitt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180502/c6d8909c/attachment.html>

From report at bugs.python.org  Thu May  3 08:11:41 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 03 May 2018 12:11:41 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1525349501.77.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Guido, now that we are working on this, perhaps you can list what other terms related to type hints/annotations you were thinking for addition.

----------

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

From report at bugs.python.org  Thu May  3 10:16:13 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 03 May 2018 14:16:13 +0000
Subject: [docs] [issue20722] newline is (partially) independent of universal
 newlines; needs to be made more clear in docs
In-Reply-To: <1392989047.5.0.441949548663.issue20722@psf.upfronthosting.co.za>
Message-ID: <1525356973.05.0.262363346258.issue20722@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.8 -Python 3.4

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

From report at bugs.python.org  Thu May  3 16:20:09 2018
From: report at bugs.python.org (Dmitry Alimov)
Date: Thu, 03 May 2018 20:20:09 +0000
Subject: [docs] [issue32625] Update the dis module documentation to reflect
 switch to wordcode
In-Reply-To: <1516642902.05.0.467229070634.issue32625@psf.upfronthosting.co.za>
Message-ID: <1525378809.33.0.682650639539.issue32625@psf.upfronthosting.co.za>


Dmitry Alimov <dvalimov at gmail.com> added the comment:

The documentation for EXTENDED_ARG opcode should also be updated for Python versions 3.6, 3.7, 3.8.

----------
nosy: +delimitry
versions: +Python 3.6, Python 3.8

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

From report at bugs.python.org  Thu May  3 18:55:08 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 03 May 2018 22:55:08 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1525349501.77.0.682650639539.issue32769@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJKhjZ6B_xLexGszDi-xGCeUas39BfSqVtKL_20zyUd8ww@mail.gmail.com>


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

Perhaps you can start with the more important terms from PEP 484 (and
perhaps also PEP 483, and then PEP 526 and PEP 544). E.g. start with terms
from the ToC of those PEPs.

----------

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

From report at bugs.python.org  Thu May  3 19:33:14 2018
From: report at bugs.python.org (Travis DePrato)
Date: Thu, 03 May 2018 23:33:14 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
Message-ID: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>


New submission from Travis DePrato <travigd at umich.edu>:

The documentation for the typing module makes no mention of AsyncContextManager, which is defined in Lib/typing.py as

    AsyncContextManager = _alias(contextlib.AbstractAsyncContextManager, T_co)

as of >= Python 3.8; before 3.8, no such AbstractAsyncContextManager class exists.

----------
assignee: docs at python
components: Documentation
messages: 316145
nosy: Travis DePrato, docs at python, eric.araujo, ezio.melotti, willingc
priority: normal
severity: normal
status: open
title: Missing documentation for typing.AsyncContextManager
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/issue33421>
_______________________________________

From report at bugs.python.org  Thu May  3 19:33:40 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 03 May 2018 23:33:40 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1525390419.96.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Great, I'll look into them.

It will take me some time to make a list of the new terms and write proper descriptions. Perhaps we could deliver the updates to the glossary by waves so people can make benefit of it? As in multiple PR being merged while retaining this issue open until all required terms are added.

----------

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

From report at bugs.python.org  Thu May  3 19:34:24 2018
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 03 May 2018 23:34:24 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
In-Reply-To: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>
Message-ID: <1525390464.24.0.262363346258.issue33421@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu May  3 19:35:16 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 03 May 2018 23:35:16 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1525390419.96.0.682650639539.issue32769@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJLBUhEkOREfm1idZ+fvWqJyJfYt9otXAeaKDnp2SERwBA@mail.gmail.com>


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

I'm okay with multiple PRs, but do beware that each PR requires a core dev
to open a browser window etc., so try to group them a bit. But no need to
wait for the perfect list!

----------

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

From report at bugs.python.org  Fri May  4 08:32:07 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 04 May 2018 12:32:07 +0000
Subject: [docs] [issue26256] Fast decimalisation and conversion to other
 bases
In-Reply-To: <1454322513.41.0.794136944555.issue26256@psf.upfronthosting.co.za>
Message-ID: <1525437127.64.0.682650639539.issue26256@psf.upfronthosting.co.za>


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

ping

----------

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

From report at bugs.python.org  Fri May  4 14:39:06 2018
From: report at bugs.python.org (Michael Klatt)
Date: Fri, 04 May 2018 18:39:06 +0000
Subject: [docs] [issue33426] Behavior of os.path.join does not match
 documentation
Message-ID: <1525459146.45.0.682650639539.issue33426@psf.upfronthosting.co.za>


New submission from Michael Klatt <michael.d.klatt at gmail.com>:

The behavior of os.path.join() regarding path separators does not match the documentation. This affects Python 3.6, and goes back to at least Python 2.7.

>From the documenation: 

"The return value is the concatenation of path and any members of *paths with exactly one directory separator (os.sep) following each non-empty part except the last, meaning that the result will only end in a separator if the last part is empty."

To me, this means that join will remove extraneous separators from the path, and that the only way to produce a trailing separator is to use join "" as the final path segment.

I expect `os.path.join("/abc//", "def/")` to produce the string "/abc/def" based on the documentation, but what it actually produces is "abc//def/".

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 316184
nosy: Michael Klatt, docs at python
priority: normal
severity: normal
status: open
title: Behavior of os.path.join does not match documentation
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri May  4 17:42:39 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 May 2018 21:42:39 +0000
Subject: [docs] [issue33417] Isinstance() behavior is not consistent with
 the document
In-Reply-To: <1525343405.44.0.682650639539.issue33417@psf.upfronthosting.co.za>
Message-ID: <1525470158.97.0.682650639539.issue33417@psf.upfronthosting.co.za>


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

https://docs.python.org/3/reference/datamodel.html#customizing-instance-and-subclass-checks
says
"Note that these methods are looked up on the type (metaclass) of a class. They cannot be defined as class methods in the actual class. This is consistent with the lookup of special methods that are called on instances, only in this case the instance is itself a class."

IE, your first example is documented as wrong.  Your second example, which works, follows the example in
https://docs.python.org/3/reference/datamodel.html#customizing-instance-and-subclass-checks

----------
nosy: +terry.reedy
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
versions: +Python 3.8

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

From report at bugs.python.org  Fri May  4 23:03:55 2018
From: report at bugs.python.org (MATSUURA, yosuke)
Date: Sat, 05 May 2018 03:03:55 +0000
Subject: [docs] [issue33427] Dead link in "The Python Standard Library" page
Message-ID: <1525489435.58.0.682650639539.issue33427@psf.upfronthosting.co.za>


New submission from MATSUURA, yosuke <howl at rampage.red>:

"The Python Standard Library" page (https://docs.python.org/3.6/library/index.html#the-python-standard-library) has a link to "Python Package Index" in the fourth paragraph
 but it linked to 404 URI(https://pypi.org/pypi/).
That link should be changed to a new URI(https://pypi.org/).

---
Fourth paragraph
"In addition to the standard library, there is a growing collection of several thousand components (from individual programs and modules to packages and entire application development frameworks), available from the ""Python Package Index""(This link is broken)."

----------
assignee: docs at python
components: Documentation
messages: 316193
nosy: docs at python, lighthawk
priority: normal
severity: normal
status: open
title: Dead link in "The Python Standard Library" page
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Sat May  5 00:12:33 2018
From: report at bugs.python.org (SilentGhost)
Date: Sat, 05 May 2018 04:12:33 +0000
Subject: [docs] [issue33426] Behavior of os.path.join does not match
 documentation
In-Reply-To: <1525459146.45.0.682650639539.issue33426@psf.upfronthosting.co.za>
Message-ID: <1525493553.6.0.682650639539.issue33426@psf.upfronthosting.co.za>


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

your example actually produces '/abc//def/'.

However, I'm not sure where do you get the idea that it should clean up internal directory separators or do anything at all with the strings in paths. To me it reads like it's concatenating arguments skipping over the empty ones unless it's also the last one. 

In any case, what would you propose to fix the language to describe the behaviour more clear?

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

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

From report at bugs.python.org  Sat May  5 00:21:48 2018
From: report at bugs.python.org (SilentGhost)
Date: Sat, 05 May 2018 04:21:48 +0000
Subject: [docs] [issue33427] Dead link in "The Python Standard Library" page
In-Reply-To: <1525489435.58.0.682650639539.issue33427@psf.upfronthosting.co.za>
Message-ID: <1525494108.89.0.682650639539.issue33427@psf.upfronthosting.co.za>


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

The language of that paragraph could be updated as well.

----------
nosy: +SilentGhost
stage:  -> needs patch
versions: +Python 2.7, Python 3.4, Python 3.5, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May  5 04:54:12 2018
From: report at bugs.python.org (Daniel Chimeno)
Date: Sat, 05 May 2018 08:54:12 +0000
Subject: [docs] [issue33430] Import secrets module in secrets examples
Message-ID: <1525510452.55.0.682650639539.issue33430@psf.upfronthosting.co.za>


New submission from Daniel Chimeno <daniel at chimeno.me>:

In the secrets module documentation, the examples in `15.3.4. Recipes and best practices` need change things, I think this examples must run after a copy & paste into user terminal.

Options for first example:
1:
````
import string
from secrets import choice
alphabet = string.ascii_letters + string.digits
password = ''.join(choice(alphabet) for i in range(8))
````

2:
```
import string
import secrets
alphabet = string.ascii_letters + string.digits
password = ''.join(secrets.choice(alphabet) for i in range(8))
````

I've looked in the devguide, but I haven't found what's the standard approach here.

First issue here, be nice :)

----------
assignee: docs at python
components: Documentation
messages: 316200
nosy: dchimeno, docs at python
priority: normal
severity: normal
status: open
title: Import secrets module in secrets examples
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May  5 05:04:19 2018
From: report at bugs.python.org (Daniel Chimeno)
Date: Sat, 05 May 2018 09:04:19 +0000
Subject: [docs] [issue33430] Import secrets module in secrets examples
In-Reply-To: <1525510452.55.0.682650639539.issue33430@psf.upfronthosting.co.za>
Message-ID: <1525511058.99.0.682650639539.issue33430@psf.upfronthosting.co.za>


Daniel Chimeno <daniel at chimeno.me> added the comment:

Relevant link: https://docs.python.org/3.7/library/secrets.html#recipes-and-best-practices

----------

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

From report at bugs.python.org  Sat May  5 05:14:29 2018
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 05 May 2018 09:14:29 +0000
Subject: [docs] [issue33430] Import secrets module in secrets examples
In-Reply-To: <1525510452.55.0.682650639539.issue33430@psf.upfronthosting.co.za>
Message-ID: <1525511669.86.0.682650639539.issue33430@psf.upfronthosting.co.za>


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

I've always expected that documentation for a module can assume that the module itself, and/or the function being described, has been imported.

On the other hand, I have no objection to making this explicit, especially in the recipes section where it might not be as clear which functions come from the module and which are builtins.

I'm inclined to go for your 2nd option, import the module and use a full-qualified name:

password = ''.join(secrets.choice(alphabet) for i in range(8))

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

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

From report at bugs.python.org  Sat May  5 05:43:10 2018
From: report at bugs.python.org (Daniel Chimeno)
Date: Sat, 05 May 2018 09:43:10 +0000
Subject: [docs] [issue33430] Import secrets module in secrets examples
In-Reply-To: <1525510452.55.0.682650639539.issue33430@psf.upfronthosting.co.za>
Message-ID: <1525513390.06.0.262363346258.issue33430@psf.upfronthosting.co.za>


Change by Daniel Chimeno <daniel at chimeno.me>:


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

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

From report at bugs.python.org  Sat May  5 06:06:00 2018
From: report at bugs.python.org (lvhuiyang)
Date: Sat, 05 May 2018 10:06:00 +0000
Subject: [docs] [issue33431] Change description about doc in programming,
 faq.
Message-ID: <1525514760.56.0.262363346258.issue33431@psf.upfronthosting.co.za>


Change by lvhuiyang <ilvhuiyang at gmail.com>:


----------
assignee: docs at python
components: Documentation
nosy: docs at python, lvhuiyang
priority: normal
severity: normal
status: open
title: Change description about doc in programming, faq.
type: performance
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May  5 06:13:53 2018
From: report at bugs.python.org (lvhuiyang)
Date: Sat, 05 May 2018 10:13:53 +0000
Subject: [docs] [issue33431] Change description about doc in programming,
 faq.
Message-ID: <1525515233.14.0.262363346258.issue33431@psf.upfronthosting.co.za>


Change by lvhuiyang <ilvhuiyang at gmail.com>:


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

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

From report at bugs.python.org  Sat May  5 07:09:51 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 May 2018 11:09:51 +0000
Subject: [docs] [issue32362] multiprocessing.connection.Connection
 misdocumented as multiprocessing.Connection
In-Reply-To: <1513592247.3.0.213398074469.issue32362@psf.upfronthosting.co.za>
Message-ID: <1525518591.32.0.682650639539.issue32362@psf.upfronthosting.co.za>


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


New changeset 4a1bc26832048325aecc01a4783a4984496d52d2 by Serhiy Storchaka (Bo Bayles) in branch '2.7':
[2.7] bpo-32362: Fix references to non-existent multiprocessing.Connection() (GH-6223) (GH-6646)
https://github.com/python/cpython/commit/4a1bc26832048325aecc01a4783a4984496d52d2


----------

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

From report at bugs.python.org  Sat May  5 09:21:58 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 May 2018 13:21:58 +0000
Subject: [docs] [issue32362] multiprocessing.connection.Connection
 misdocumented as multiprocessing.Connection
In-Reply-To: <1513592247.3.0.213398074469.issue32362@psf.upfronthosting.co.za>
Message-ID: <1525526518.13.0.262363346258.issue32362@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May  5 12:46:01 2018
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 05 May 2018 16:46:01 +0000
Subject: [docs] [issue33427] Dead link in "The Python Standard Library" page
In-Reply-To: <1525489435.58.0.682650639539.issue33427@psf.upfronthosting.co.za>
Message-ID: <1525538761.08.0.262363346258.issue33427@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May  5 19:58:11 2018
From: report at bugs.python.org (Michael Klatt)
Date: Sat, 05 May 2018 23:58:11 +0000
Subject: [docs] [issue33426] Behavior of os.path.join does not match
 documentation
In-Reply-To: <1525459146.45.0.682650639539.issue33426@psf.upfronthosting.co.za>
Message-ID: <1525564690.94.0.682650639539.issue33426@psf.upfronthosting.co.za>


Michael Klatt <michael.d.klatt at gmail.com> added the comment:

For me, the ambiguity is due to the phrases "exactly one directory separator" and "the only way to produce a trailing separator".

I would suggest:

"The return value is the concatenation of path and any members of *paths so that there is a directory separator (os.sep) following each part except the last. An empty part is ignored unless it is the last part, in which case the result will end in a separator."

Or:

"The return value is the concatenation of path and any members of *paths such that there is guaranteed to be a directory separator (os.sep) following each part except the last. An empty part is ignored unless it is the last part, in which case the result will end in a separator."

----------

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

From report at bugs.python.org  Mon May  7 09:06:02 2018
From: report at bugs.python.org (Pete Moore)
Date: Mon, 07 May 2018 13:06:02 +0000
Subject: [docs] [issue33442] Python 3 doc sidebar dosnt follow page
 scrolling like 2.7 doc sidebar.
Message-ID: <1525698362.62.0.682650639539.issue33442@psf.upfronthosting.co.za>


New submission from Pete Moore <1petemoore at gmail.com>:

the 3.x docs sidebar at location https://docs.python.org/3.6/library/logging.html does not follow the user's scrolling movements like the 2.7 docs sidebar at location https://docs.python.org/2.7/library/logging.html

----------
assignee: docs at python
components: Documentation
messages: 316269
nosy: docs at python, pete312
priority: normal
severity: normal
status: open
title: Python 3 doc sidebar dosnt follow page scrolling like 2.7 doc sidebar.
type: behavior
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/issue33442>
_______________________________________

From report at bugs.python.org  Mon May  7 09:29:16 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 May 2018 13:29:16 +0000
Subject: [docs] [issue33216] Wrong order of stack for CALL_FUNCTION_VAR and
 CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1525699756.8.0.262363346258.issue33216@psf.upfronthosting.co.za>


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


----------
priority: normal -> release blocker

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

From mrmlionel at gmail.com  Thu May  3 09:50:24 2018
From: mrmlionel at gmail.com (lionel Meloiq)
Date: Thu, 3 May 2018 09:50:24 -0400
Subject: [docs] Your bind is invalid
Message-ID: <A01E2415-A3C4-4EFA-9AFB-0FB6B128DEC0@gmail.com>

Hello

I can ?t download the bind to download the doc in my computer 
							in a intempt of a answer

From mtemelkov at gmail.com  Fri May  4 08:47:07 2018
From: mtemelkov at gmail.com (Mihail Temelkov)
Date: Fri, 04 May 2018 12:47:07 +0000
Subject: [docs] frozenset.copy() does not create a copy
Message-ID: <CAGJMoU=NJnM2bZ+pBdcRvZo7mEN_EzvYHGRZTgxQ59zYqEfiwg@mail.gmail.com>

Tried it in Python 2.7 and found that it just creates an alias to the
original set.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180504/66a2aa1f/attachment.html>

From yupeng0921 at gmail.com  Mon May  7 20:28:59 2018
From: yupeng0921 at gmail.com (peng yu)
Date: Mon, 7 May 2018 17:28:59 -0700
Subject: [docs] add explain about where to set use_builtin_types when use
 customTransport
Message-ID: <CAG3TDc2w-EHASH8A9XHkEcAJQqx7ocQK64cZXGSHiJLnPZ_C7w@mail.gmail.com>

I'm using xmlrpc, and I'm using a custom Transport, follow the
"21.26.8. Example of Client Usage" section of below document:
https://docs.python.org/3/library/xmlrpc.client.html
I found if I use a custom transport, set use_builtin_types parameter
to xmlrpc.client.ServerProxy will have no effect. After read the
source code, I found if I use a custom transport, I should set the
use_builtin_types parameter in the transport. I think it is better to
describe this behavior in the document.

best regards.

From songofacandy at gmail.com  Tue May  8 04:28:12 2018
From: songofacandy at gmail.com (INADA Naoki)
Date: Tue, 08 May 2018 08:28:12 +0000
Subject: [docs] frozenset.copy() does not create a copy
In-Reply-To: <CAGJMoU=NJnM2bZ+pBdcRvZo7mEN_EzvYHGRZTgxQ59zYqEfiwg@mail.gmail.com>
References: <CAGJMoU=NJnM2bZ+pBdcRvZo7mEN_EzvYHGRZTgxQ59zYqEfiwg@mail.gmail.com>
Message-ID: <CAEfz+TxQgE5zfSf7S_BO4Z47PEUMd+PVxyALNCWdi_zro=NUhg@mail.gmail.com>

On Tue, May 8, 2018 at 5:20 PM Mihail Temelkov <mtemelkov at gmail.com> wrote:

> Tried it in Python 2.7 and found that it just creates an alias to the
original set.

In Python, copy() or similar methods may return itself for immutable types.
It's widely used optimization.

>>> t=(1,2)
>>> t1=(1,2)
>>> t2=t1[:]
>>> t1 is t2
True

And it is implementation (CPython) specific optimization; other
implementation
may return new instance.
You shouldn't rely on undocumented behavior.

Regards,
-- 
INADA Naoki  <songofacandy at gmail.com>

From report at bugs.python.org  Wed May  9 03:13:07 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 07:13:07 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525849987.34.0.682650639539.issue13525@psf.upfronthosting.co.za>


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

Error message was fixed. In all supported versions it is:

$ ./python cp_1252broken.py
  File "cp_1252broken.py", line 1
SyntaxError: encoding problem: cp-1252

But the tutorial still contains non-working example. This is an easy issue, but it was open for long time.

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

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

From report at bugs.python.org  Wed May  9 03:14:08 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 07:14:08 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525850048.93.0.262363346258.issue13525@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May  9 04:09:25 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 08:09:25 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1525853365.91.0.262363346258.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +6428

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

From report at bugs.python.org  Wed May  9 04:10:58 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 08:10:58 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525853458.21.0.682650639539.issue13525@psf.upfronthosting.co.za>


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


New changeset ddb6215a55b0218b621d5cb755e9dfac8dab231a by Serhiy Storchaka in branch 'master':
bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)
https://github.com/python/cpython/commit/ddb6215a55b0218b621d5cb755e9dfac8dab231a


----------

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

From report at bugs.python.org  Wed May  9 04:11:14 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 May 2018 08:11:14 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525853474.96.0.262363346258.issue13525@psf.upfronthosting.co.za>


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


----------
pull_requests: +6429

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

From report at bugs.python.org  Wed May  9 04:12:08 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 May 2018 08:12:08 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525853528.74.0.262363346258.issue13525@psf.upfronthosting.co.za>


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


----------
pull_requests: +6430

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

From report at bugs.python.org  Wed May  9 04:19:12 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 08:19:12 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525853953.0.0.262363346258.issue13525@psf.upfronthosting.co.za>


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


----------
pull_requests: +6431

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

From report at bugs.python.org  Wed May  9 04:40:47 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 08:40:47 +0000
Subject: [docs] [issue6673] Uncaught comprehension SyntaxError eats up all
 memory
In-Reply-To: <1249826985.41.0.2934011008.issue6673@psf.upfronthosting.co.za>
Message-ID: <1525855247.65.0.682650639539.issue6673@psf.upfronthosting.co.za>


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

"yield" in comprehensions is deprecated in 3.7:

../issue6673.py:22: DeprecationWarning: 'yield' inside list comprehension
  target.send([ (yield) for i in range(chunk_size) ])

and an error in 3.8:

  File "../issue6673.py", line 22
    target.send([ (yield) for i in range(chunk_size) ])
                 ^
SyntaxError: 'yield' inside list comprehension

----------
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> yield expression inside generator expression does nothing

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

From report at bugs.python.org  Wed May  9 04:54:41 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 May 2018 08:54:41 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525856081.19.0.682650639539.issue13525@psf.upfronthosting.co.za>


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


New changeset 8ffff34ea12ca6478d73a337ce52f33660f6f174 by Miss Islington (bot) in branch '3.7':
bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)
https://github.com/python/cpython/commit/8ffff34ea12ca6478d73a337ce52f33660f6f174


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

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

From report at bugs.python.org  Wed May  9 05:00:24 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 May 2018 09:00:24 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525856424.1.0.682650639539.issue13525@psf.upfronthosting.co.za>


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


New changeset fa40fc0593012893e447875632e9ed3df277561f by Miss Islington (bot) in branch '3.6':
bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738)
https://github.com/python/cpython/commit/fa40fc0593012893e447875632e9ed3df277561f


----------

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

From report at bugs.python.org  Wed May  9 05:33:07 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 09:33:07 +0000
Subject: [docs] [issue32288] Inconsistent behavior with slice assignment?
In-Reply-To: <1513079903.38.0.213398074469.issue32288@psf.upfronthosting.co.za>
Message-ID: <1525858386.96.0.682650639539.issue32288@psf.upfronthosting.co.za>


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

So this issue can be closed now?

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

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

From report at bugs.python.org  Wed May  9 05:35:38 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 09:35:38 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525858538.16.0.682650639539.issue13525@psf.upfronthosting.co.za>


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


New changeset d7e783b17feaedbe0f5b30467cb7f43cefadf904 by Serhiy Storchaka in branch '2.7':
[2.7] bpo-13525: Fix incorrect encoding name in the tutorial example. (GH-6738). (GH-6744)
https://github.com/python/cpython/commit/d7e783b17feaedbe0f5b30467cb7f43cefadf904


----------

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

From report at bugs.python.org  Wed May  9 05:36:35 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 May 2018 09:36:35 +0000
Subject: [docs] [issue13525] Tutorial: Example of Source Code Encoding
 triggers error
In-Reply-To: <1322918242.84.0.309365391343.issue13525@psf.upfronthosting.co.za>
Message-ID: <1525858595.04.0.262363346258.issue13525@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May  9 13:38:58 2018
From: report at bugs.python.org (Francois Labelle)
Date: Wed, 09 May 2018 17:38:58 +0000
Subject: [docs] [issue33449] Documentation for email.charset confusing about
 the location of constants
Message-ID: <1525887538.2.0.682650639539.issue33449@psf.upfronthosting.co.za>


New submission from Francois Labelle <quantum.omega at gmail.com>:

When mentioning the constants contained in the module email.charset, the documentation prefixes them with "Charset", for example: Charset.QP, Charset.BASE64, Charset.SHORTEST. This suggests that the constants can be found on the class "Charset" (uppercase first letter) in the module, while they are in fact contained in the the "charset" (lowercase first letter) module itself.

This is probably a left-over from when the module was called email.Charset (in 2.2 I believe). Under Python 2.7, while the documentation uses the same nomenclature, at least the module is also importable under the name email.Charset so it makes more sense.

----------
assignee: docs at python
components: Documentation
messages: 316327
nosy: Francois Labelle, docs at python
priority: normal
severity: normal
status: open
title: Documentation for email.charset confusing about the location of constants
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu May 10 01:16:28 2018
From: report at bugs.python.org (Massimiliano Culpo)
Date: Thu, 10 May 2018 05:16:28 +0000
Subject: [docs] [issue32288] Inconsistent behavior with slice assignment?
In-Reply-To: <1525858386.96.0.682650639539.issue32288@psf.upfronthosting.co.za>
Message-ID: <CAFY5BQU9SmS=+03wVgwpq5Fy+mauQYbzcgqN8Xr++FoQH_EZZw@mail.gmail.com>


Massimiliano Culpo <massimiliano.culpo at googlemail.com> added the comment:

Hi Serhiy,

I briefly checked out Python 3.7.0b3, and saw no changes with respect to:

   - Documenting what is the exact meaning of "extended slice" (but that
   now is also tracked by issue 32289)
   - Improving the docstring of list.insert (to say that [1, 2, 3,
   4].insert(-101, 0) is allowed?)
   - Fixing the inconsistent behavior for slices with step == -1

If I missed anything, please let me know. Otherwise, from my side, I think
it only depends on whether you want to track these issues (or even if you
consider any of the above an issue).

Cheers,

On Wed, May 9, 2018 at 11:33 AM, Serhiy Storchaka <report at bugs.python.org>
wrote:

>
> Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:
>
> So this issue can be closed now?
>
> ----------
> nosy: +serhiy.storchaka
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue32288>
> _______________________________________
>

----------

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

From report at bugs.python.org  Thu May 10 08:35:35 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 10 May 2018 12:35:35 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1525955734.79.0.682650639539.issue32216@psf.upfronthosting.co.za>


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

We really need to get this done prior to 370rc1 coming up on 05-21.

----------
priority: deferred blocker -> release blocker

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

From report at bugs.python.org  Thu May 10 09:38:53 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 10 May 2018 13:38:53 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1525959533.77.0.682650639539.issue26701@psf.upfronthosting.co.za>


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


New changeset df00f048250b9a07195b0e3b1c5c0161fdcc9db8 by Nick Coghlan (Serhiy Storchaka) in branch 'master':
bpo-26701: Tweak the documentation for special methods in int(). (GH-6741)
https://github.com/python/cpython/commit/df00f048250b9a07195b0e3b1c5c0161fdcc9db8


----------

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

From report at bugs.python.org  Thu May 10 09:39:09 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 May 2018 13:39:09 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1525959549.25.0.262363346258.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +6438

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

From report at bugs.python.org  Thu May 10 09:39:55 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 May 2018 13:39:55 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1525959595.38.0.262363346258.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +6439

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

From report at bugs.python.org  Thu May 10 10:06:37 2018
From: report at bugs.python.org (R. David Murray)
Date: Thu, 10 May 2018 14:06:37 +0000
Subject: [docs] [issue33449] Documentation for email.charset confusing about
 the location of constants
In-Reply-To: <1525887538.2.0.682650639539.issue33449@psf.upfronthosting.co.za>
Message-ID: <1525961197.83.0.682650639539.issue33449@psf.upfronthosting.co.za>


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

Can you provide an example of where this occurs in the docs?

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

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

From report at bugs.python.org  Thu May 10 10:38:09 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 May 2018 14:38:09 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1525963089.48.0.682650639539.issue26701@psf.upfronthosting.co.za>


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


New changeset 22df4187c3882c6ec67180902e1151e65b03aee0 by Miss Islington (bot) in branch '3.7':
bpo-26701: Tweak the documentation for special methods in int(). (GH-6741)
https://github.com/python/cpython/commit/22df4187c3882c6ec67180902e1151e65b03aee0


----------

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

From report at bugs.python.org  Thu May 10 10:38:23 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 May 2018 14:38:23 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1525963103.07.0.682650639539.issue26701@psf.upfronthosting.co.za>


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


New changeset 7488c79b600cd173b0ccea13adb567d078e7b835 by Miss Islington (bot) in branch '3.6':
bpo-26701: Tweak the documentation for special methods in int(). (GH-6741)
https://github.com/python/cpython/commit/7488c79b600cd173b0ccea13adb567d078e7b835


----------

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

From report at bugs.python.org  Thu May 10 13:20:16 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 10 May 2018 17:20:16 +0000
Subject: [docs] [issue33448] Output_Typo_Error
In-Reply-To: <1525885359.71.0.682650639539.issue33448@psf.upfronthosting.co.za>
Message-ID: <1525972816.12.0.682650639539.issue33448@psf.upfronthosting.co.za>


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

Marking as pending; we can't take this forward without more input from the OP. As far as I can tell, the documentation is perfectly correct here: I suspect that there was a misunderstanding somewhere along the line.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> not a bug
status: open -> pending
type: resource usage -> 

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

From report at bugs.python.org  Thu May 10 16:20:07 2018
From: report at bugs.python.org (Francois Labelle)
Date: Thu, 10 May 2018 20:20:07 +0000
Subject: [docs] [issue33449] Documentation for email.charset confusing about
 the location of constants
In-Reply-To: <1525887538.2.0.682650639539.issue33449@psf.upfronthosting.co.za>
Message-ID: <1525983607.27.0.682650639539.issue33449@psf.upfronthosting.co.za>


Francois Labelle <quantum.omega at gmail.com> added the comment:

Original poster here (OpenID just wouldn't work anymore).

For instance: https://docs.python.org/2/library/email.charset.html

Under "class email.charset.Charset"

Under "header_encoding"

"If the character set must be encoded before it can be used in an email header, this attribute will be set to Charset.QP (for quoted-printable), Charset.BASE64 (for base64 encoding), or Charset.SHORTEST for the shortest of QP or BASE64 encoding. Otherwise, it will be None."

----------
nosy: +quantum.omega at gmail.com -Francois Labelle

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

From report at bugs.python.org  Thu May 10 17:17:45 2018
From: report at bugs.python.org (R. David Murray)
Date: Thu, 10 May 2018 21:17:45 +0000
Subject: [docs] [issue33449] Documentation for email.charset confusing about
 the location of constants
In-Reply-To: <1525887538.2.0.682650639539.issue33449@psf.upfronthosting.co.za>
Message-ID: <1525987065.19.0.682650639539.issue33449@psf.upfronthosting.co.za>


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

Ah, I see.  Yes, those strings are actually hardcoded in the documentation source instead of being references.  You are correct, they should be fixed.  Note, however, that Charset is part of the legacy API and isn't actually used if you use the new API in python3.

----------
stage:  -> needs patch
type: enhancement -> behavior
versions:  -Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Thu May 10 19:16:52 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 10 May 2018 23:16:52 +0000
Subject: [docs] [issue33459] Fix "tuple display" mention in Expressions
Message-ID: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

Expressions mentions "tuple displays" in 6.16 (Operator precedence).

AFAIK, there ano "tuple displays". Expressions mentions list, dict, and set displays, and then talks about generator expressions.

I guess "parenthesized expressions" should be the term that fits here?

----------
assignee: docs at python
components: Documentation
messages: 316380
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Fix "tuple display" mention in Expressions
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu May 10 19:17:21 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 10 May 2018 23:17:21 +0000
Subject: [docs] [issue33459] Fix "tuple display" mention in Expressions
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1525994241.47.0.262363346258.issue33459@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu May 10 19:33:17 2018
From: report at bugs.python.org (Lew Kurtz)
Date: Thu, 10 May 2018 23:33:17 +0000
Subject: [docs] [issue33460] ... used to indicate many different things in
 chapter 3, some are confusing
Message-ID: <1525995197.73.0.682650639539.issue33460@psf.upfronthosting.co.za>


New submission from Lew Kurtz <lew.kurtz at icloud.com>:

https://docs.python.org/3/tutorial/introduction.html
uses ... to mean 5 or 6 different things. Since ... is continuation prompt, some of these other uses on that page are confusing - at least they were to this newbie. The most confusing are where it is used to hide output in the error messages.

If someone has the patience to send me pointers on how to fix this, I would love to fix this myself. -Lew

ps. the section headers in chapter 3 also need some work, 3.1.1 is the only section that is really about python being a calculator 3.1.2 and 3.1.3 don't seem very 'calculator-y' - Id like to fix this too.

----------
assignee: docs at python
components: Documentation
messages: 316381
nosy: docs at python, lew18
priority: normal
severity: normal
status: open
title: ... used to indicate many different things in chapter 3, some are confusing
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Thu May 10 19:36:48 2018
From: report at bugs.python.org (R. David Murray)
Date: Thu, 10 May 2018 23:36:48 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1525995408.65.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

Nope, a tuple display is not equal to a parenthesized list.  For example, in:

   x = 1, 2, 3

1, 2, 3 is a tuple display.  The parenthesis are optional in that case (in the general case it is the comma that makes the tuple, not the parens).

However, as far as I can see that's the only mention of "tuple display" in the docs, which makes the doc you reference less than useful to a reader that doesn't know what it means.

----------
nosy: +r.david.murray
title: Fix "tuple display" mention in Expressions -> Define "tuple display" in the docs

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

From report at bugs.python.org  Thu May 10 19:47:23 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 10 May 2018 23:47:23 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1525996043.78.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

Actually, 'tuple display' is in the index under 'display' and links to the last paragraph in 6.2.3.  However, except for the index name, that paragraph doesn't use the phrase 'tuple display'.  So it gives the definition without saying what it is defining.

> Note that tuples are not formed by the parentheses, but rather by use of the comma operator. The exception is the empty tuple, for which parentheses are required ? allowing unparenthesized ?nothing? in expressions would cause ambiguities and allow common typos to pass uncaught.

----------
nosy: +csabella

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

From report at bugs.python.org  Fri May 11 13:56:15 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 11 May 2018 17:56:15 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1526061375.05.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

The thing is that "tuple displays" like:

nums = (n for n in range(10))

Yield a generator expression instead of a tuple.

Also, unparenthesized "tuple displays" like 1, 2, 3 can't be used in expressions, AFAIK:

>>> if 3 == 1, 2, 3:
SyntaxError: invalid syntax

So, you end up using parenthesized expressions (that may or may not shield tuples) to use tuples in expressions. So talking about "tuple expressions" in the operator precedence table doesn't make much sense to me :/

Also, if a "tuple display" doesn't yield a tuple, should it be named a "tuple display" after all?

----------

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

From report at bugs.python.org  Fri May 11 13:57:29 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 11 May 2018 17:57:29 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1526061449.49.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

Ignore the previous comment.

The thing is that "tuple displays" like:

nums = (n for n in range(10))

Yield a generator expression instead of a tuple.

Also, unparenthesized "tuple displays" like 1, 2, 3 can't be used in expressions, AFAIK:

>>> if 3 == 1, 2, 3:
SyntaxError: invalid syntax

So, you end up using parenthesized expressions to use tuples in expressions. So talking about "tuple displays" in the operator precedence table doesn't make much sense to me :/

Also, if a "tuple display" doesn't yield a tuple, should it be named a "tuple display" after all?

----------

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

From report at bugs.python.org  Fri May 11 14:25:27 2018
From: report at bugs.python.org (R. David Murray)
Date: Fri, 11 May 2018 18:25:27 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1526063127.3.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

That's a generator expression, just like [x for x in ramge(3)] is a list comprehension, not a list display.  And yes, in a number of circumstances parenthesis are required to delimit the tuple display and disambiguate the syntax.  That is, it is the 1, 2, 3 that is the tuple display, but sometimes you have to enclose it in parenthesis in order for the parser to recognize it.  Which is why it would be good to give a more thorough explanation of what a tuple display is than the unlabeled one Cheryl pointed out.  I'm not entirely sure what the exact rules are for when you get a syntax error without the parens, myself :)

----------

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

From report at bugs.python.org  Fri May 11 14:32:51 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 11 May 2018 18:32:51 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1526063571.02.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

The documentation says a display may or may not have a comprehension :/

[1, 2, 3] is a list display too.

[x for x in range(3)] is a display that has a comprehension. Acoording to the doc.

----------

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

From report at bugs.python.org  Fri May 11 15:07:56 2018
From: report at bugs.python.org (R. David Murray)
Date: Fri, 11 May 2018 19:07:56 +0000
Subject: [docs] [issue33459] Define "tuple display" in the docs
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1526065676.86.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

Hmm.  OK, I didn't think that's how we'd defined those terms, but then I don't actually work with the parser much myself :)  However, generator expressions are clearly called out as a separate thing.  All of the other display types get their own section, so I would think tuple display should too if it really is a syntax unit...but maybe it isn't.

Also, I'm not clear on what 'binding' means in that table entry.

I see now why you wanted to say "parenthesized expression", but as far as I can see the previous text is referring to it as an expression list in parenthesis form.  That's a bit wordy, which may be why someone used tuple display there.  Clearly there is some ambiguity here that it would be nice to resolve, considering this is part of the language spec, but frankly I'm not sure what to suggest.  At that level I'm not sure how the "operator precedence" is actually "resolved"...I think it is more a matter of it being implicit in the parsing, but I'm not sure.  Like I said, not my area of expertise.

----------

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

From report at bugs.python.org  Sat May 12 04:40:06 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Sat, 12 May 2018 08:40:06 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
Message-ID: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>


New submission from Miro Hron?ok <miro at hroncok.cz>:

Background: gdb fails to build with Python 3.7 as described in https://bugzilla.redhat.com/show_bug.cgi?id=1577396

This is due to _PyImport_FixupBuiltin changing it's API. I feel that _underscored functions are probably not guaranteed to not change, however I miss anything about the following changes:

https://github.com/python/cpython/pull/1638
https://github.com/python/cpython/pull/3565
https://github.com/python/cpython/pull/3575

In here:

https://docs.python.org/3.7/whatsnew/3.7.html#porting-to-python-37
(or that page generally)

That page doesn't mention PyInterpreterState at all, so even if you decide that _PyImport_FixupBuiltin doesn't deserve a mention, maybe the general change does.

Thanks

----------
assignee: docs at python
components: Documentation
messages: 316421
nosy: docs at python, eric.snow, hroncok, vstinner
priority: normal
severity: normal
status: open
title: Changes from GH-1638 (GH-3575, bpo-28411) are not documented in Porting to Python 3.7
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May 12 07:26:28 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 12 May 2018 11:26:28 +0000
Subject: [docs] [issue33427] Dead link in "The Python Standard Library" page
In-Reply-To: <1525489435.58.0.682650639539.issue33427@psf.upfronthosting.co.za>
Message-ID: <1526124388.76.0.682650639539.issue33427@psf.upfronthosting.co.za>


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

Note that while the link in the docs should be updated, the old link should redirect properly.  That change has been requested in https://github.com/pypa/warehouse/issues/3914

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

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

From report at bugs.python.org  Sat May 12 07:42:22 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 12 May 2018 11:42:22 +0000
Subject: [docs] [issue33442] Python 3 doc sidebar dosnt follow page
 scrolling like 2.7 doc sidebar.
In-Reply-To: <1525698362.62.0.682650639539.issue33442@psf.upfronthosting.co.za>
Message-ID: <1526125342.85.0.262363346258.issue33442@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti, georg.brandl

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

From report at bugs.python.org  Sat May 12 11:42:36 2018
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 12 May 2018 15:42:36 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526139756.95.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

Is it a release blocker?

----------
nosy: +ned.deily
priority: normal -> release blocker

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

From report at bugs.python.org  Sat May 12 11:42:59 2018
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 12 May 2018 15:42:59 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526139779.74.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

Miro: do you want to work on a pull request?

----------

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

From report at bugs.python.org  Sat May 12 14:09:03 2018
From: report at bugs.python.org (book book)
Date: Sat, 12 May 2018 18:09:03 +0000
Subject: [docs] [issue4934] tp_del and tp_version_tag undocumented
In-Reply-To: <1231869285.41.0.170645063597.issue4934@psf.upfronthosting.co.za>
Message-ID: <1526148543.11.0.682650639539.issue4934@psf.upfronthosting.co.za>


book book <book78987book at gmail.com> added the comment:

tp_del still undocumented.

In my opinion, tp_del corresponds to the __del__() method of classes, because there are no other variable correspondes to it, but methods using for creating(tp_new) and initializing(tp_init) an object are not.

Although __del__ method have some issue according to the offical document, but it is exist, so there must have a pointer to the function corresponding to it.

----------
nosy: +book book
versions: +Python 3.6 -Python 2.6, Python 2.7, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat May 12 14:12:40 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 12 May 2018 18:12:40 +0000
Subject: [docs] [issue4934] tp_del and tp_version_tag undocumented
In-Reply-To: <1231869285.41.0.170645063597.issue4934@psf.upfronthosting.co.za>
Message-ID: <1526148760.66.0.682650639539.issue4934@psf.upfronthosting.co.za>


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

The reason tp_del has remained undocumented is that it's now obsolete.  You should use tp_finalize instead:
https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_finalize

tp_finalize is roughly the C equivalent of __del__ (tp_del was something else, despite the name).

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

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

From report at bugs.python.org  Sat May 12 14:13:26 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 12 May 2018 18:13:26 +0000
Subject: [docs] [issue4934] tp_del and tp_version_tag undocumented
In-Reply-To: <1231869285.41.0.170645063597.issue4934@psf.upfronthosting.co.za>
Message-ID: <1526148806.44.0.682650639539.issue4934@psf.upfronthosting.co.za>


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

Both tp_del and tp_version_tag are for internal use.  Besides, tp_del is obsolete as I mentioned above.  So I'm going to close the issue.

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

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

From report at bugs.python.org  Sat May 12 20:57:30 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sun, 13 May 2018 00:57:30 +0000
Subject: [docs] [issue33477] Document that compile(code,
 'exec') has different behavior in 3.7+
Message-ID: <1526173050.51.0.682650639539.issue33477@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier <bussonniermatthias at gmail.com>:

In recent Python the following 

>>> from ast import PyCF_ONLY_AST
>>> compile("'a'", 'whatever', 'exec', PyCF_ONLY_AST).body

In 3.6 it return

   [<_ast.Expr at 0x10b7441d0>] # that contail Str('a')

While on master:

   []

This is inconveninent for alternative repl like IPython, where basically if the user is entering a single string, the result is nothing in Python 3.7+, while it _does_ return something on earlier Python [1]. 

The documentation of `compile` says:

>  ... it can be 'exec' if source consists of a sequence of statements,

Which is not technically true any more as the first statement, if a string, will be removed. 

What's happening here is that since Python 3.7 if the _first_ statement is actually an expression containing a lonely string it is assign to the module docstring. So that's basically assuming you are parsing a module, and that the docstring make sens in this context, while in a REPL you are parsing a sucesssion of statements, in which case there is no need for a docstring that make no sens in this context.


This is _usually_ not an issue, unless this lonely statement is also the last, and what the user wants to execute in a REPL, in which case it has no side effect.

I don't have any objection to the new behavior, though I was wondering if this kind of side effect was anticipated. 

If that affect IPython, it will likely effect other alternative REPLs.

Thus, I believe it would be good to have this at least documented a tiny bit better and added in what's new, and potentially clarified in the `exec` docs.

I could argue that now the  `exec` name may be a tiny bit unsuitable for the new behavior, and would love if this could be optional.

1: https://github.com/ipython/ipython/issues/11133#issuecomment-388591332

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 316441
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: Document that compile(code, 'exec') has different behavior in 3.7+
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May 12 22:10:00 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Sun, 13 May 2018 02:10:00 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526177399.7.0.682650639539.issue33470@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

The change is a bit beyond my understanding ATM. I might be able to study it and stitch something up, but I'd rather leave it to the author of the change.

----------

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

From report at bugs.python.org  Sat May 12 23:54:59 2018
From: report at bugs.python.org (Amit Saha)
Date: Sun, 13 May 2018 03:54:59 +0000
Subject: [docs] [issue33478] PEP 8 CapWords reference wrong?
Message-ID: <1526183699.39.0.682650639539.issue33478@psf.upfronthosting.co.za>


New submission from Amit Saha <amitsaha.in at gmail.com>:

PEP 8 suggests class names and type variable names to be in CapWords case. However:

>>> import string
>>> string.capwords('CapWord')
'Capword'

Wondering if this this an oversight or am I misunderstanding something?

----------
assignee: docs at python
components: Documentation
messages: 316446
nosy: Amit.Saha, docs at python
priority: normal
severity: normal
status: open
title: PEP 8 CapWords reference wrong?

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

From report at bugs.python.org  Sun May 13 00:16:15 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 13 May 2018 04:16:15 +0000
Subject: [docs] [issue16823] Python quits on running tkinter code with
 threads
In-Reply-To: <1356924189.65.0.303016065786.issue16823@psf.upfronthosting.co.za>
Message-ID: <1526184975.08.0.682650639539.issue16823@psf.upfronthosting.co.za>


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

In the message above, I asked "why this code runs in 3.x but eventually fails in 2.x?".  The answer is almost certainly that I used 3.5 with tk 8.6 compiled *with* thread support and 2.7 with tk 8.5 compiled without thread support.

Serhiy, if you use a system supplied 8.6 with thread support for all Python versions, that would explain why these thread examples work for you with all Python versions.  If non-thread tk works for you, then the code in _tkinter.c works better on Linux (where it must have been developed) than Windows.

The original failure report duplicates other similar reports.  My previous responses, including proposed doc change were incomplete, as I only learned about the tcl compile option a month ago.  I opened #33479, with more extensive proposed tkinter doc changes, in favor of this.

----------
stage:  -> resolved
status: open -> closed
superseder:  -> Document tkinter and threads

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

From report at bugs.python.org  Sun May 13 00:58:03 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 13 May 2018 04:58:03 +0000
Subject: [docs] [issue16823] Python quits on running tkinter code with
 threads
In-Reply-To: <1356924189.65.0.303016065786.issue16823@psf.upfronthosting.co.za>
Message-ID: <1526187483.65.0.262363346258.issue16823@psf.upfronthosting.co.za>


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


----------
resolution:  -> duplicate

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

From report at bugs.python.org  Sun May 13 02:13:38 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 13 May 2018 06:13:38 +0000
Subject: [docs] [issue33478] PEP 8 CapWords reference wrong?
In-Reply-To: <1526183699.39.0.682650639539.issue33478@psf.upfronthosting.co.za>
Message-ID: <1526192017.95.0.682650639539.issue33478@psf.upfronthosting.co.za>


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

'CapWord' is a single word so string.capwords() works as documented:

    Split the argument into words using str.split(), capitalize each word
    using str.capitalize(), and join the capitalized words using str.join().

https://docs.python.org/3/library/string.html#string.capwords

You can also see this in the REPL:

    >>> "CapWord".split()
    ['CapWord']
    >>> _[0].capitalize()  # '_' is a shortcut for the latest command
    'Capword'

----------
nosy: +berker.peksag
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun May 13 07:16:33 2018
From: report at bugs.python.org (Amit Saha)
Date: Sun, 13 May 2018 11:16:33 +0000
Subject: [docs] [issue33478] PEP 8 CapWords reference wrong?
In-Reply-To: <1526183699.39.0.682650639539.issue33478@psf.upfronthosting.co.za>
Message-ID: <1526210193.66.0.682650639539.issue33478@psf.upfronthosting.co.za>


Amit Saha <amitsaha.in at gmail.com> added the comment:

Thanks for the reply.  I think I was not clear - the behavior of string.capitalize() is correct as per documentation. But the PEP8 referring to CapWords as cap words case is the bit I am not clear about, since `Capwords` back when you call `string.capwords('CapWords') and not `CapWords`.

(Just reopening so that it doesn't get lost)

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

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

From report at bugs.python.org  Sun May 13 07:20:07 2018
From: report at bugs.python.org (R. David Murray)
Date: Sun, 13 May 2018 11:20:07 +0000
Subject: [docs] [issue33478] PEP 8 CapWords reference wrong?
In-Reply-To: <1526183699.39.0.682650639539.issue33478@psf.upfronthosting.co.za>
Message-ID: <1526210407.0.0.682650639539.issue33478@psf.upfronthosting.co.za>


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

In PEP 8 'CapWords" does not refer to the capwords function, as is fairly clear from context.  A big clues is that it is not spelled 'capwords', and case matters in python function names :)  I can understand your getting confused, but that sentence is trying to list the various names give to this style of naming, and "CapWords" is one of those names, so I don't know that we should delete it.

----------
nosy: +r.david.murray
status: open -> closed

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

From report at bugs.python.org  Sun May 13 20:40:41 2018
From: report at bugs.python.org (Eitan Adler)
Date: Mon, 14 May 2018 00:40:41 +0000
Subject: [docs] [issue33488] github pull request template does not satisfy
 markdownlint
Message-ID: <1526258440.92.0.682650639539.issue33488@psf.upfronthosting.co.za>


New submission from Eitan Adler <lists at eitanadler.com>:

markdownlint is, as the name implies, a tool for linting markdown files.

The current template has the following lint warnings:

```
./.github/PULL_REQUEST_TEMPLATE.md:8: MD031 Fenced code blocks should be surrounded by blank lines
./.github/PULL_REQUEST_TEMPLATE.md:10: MD031 Fenced code blocks should be surrounded by blank lines
./.github/PULL_REQUEST_TEMPLATE.md:19: MD031 Fenced code blocks should be surrounded by blank lines
./.github/PULL_REQUEST_TEMPLATE.md:21: MD031 Fenced code blocks should be surrounded by blank lines
```

These should be fixed

----------
assignee: docs at python
components: Documentation
messages: 316484
nosy: docs at python, eitan.adler
priority: normal
severity: normal
status: open
title: github pull request template does not satisfy markdownlint
type: enhancement

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

From report at bugs.python.org  Sun May 13 20:41:11 2018
From: report at bugs.python.org (Eitan Adler)
Date: Mon, 14 May 2018 00:41:11 +0000
Subject: [docs] [issue33488] github pull request template does not satisfy
 markdownlint
In-Reply-To: <1526258440.92.0.682650639539.issue33488@psf.upfronthosting.co.za>
Message-ID: <1526258471.65.0.262363346258.issue33488@psf.upfronthosting.co.za>


Change by Eitan Adler <lists at eitanadler.com>:


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

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

From report at bugs.python.org  Sun May 13 20:55:38 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 14 May 2018 00:55:38 +0000
Subject: [docs] [issue33488] github pull request template does not satisfy
 markdownlint
In-Reply-To: <1526258440.92.0.682650639539.issue33488@psf.upfronthosting.co.za>
Message-ID: <1526259338.3.0.682650639539.issue33488@psf.upfronthosting.co.za>


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


New changeset 5cd22cf2097a6dd209999cf97858d54564a3be87 by Benjamin Peterson (Eitan Adler) in branch 'master':
bpo-33488: Satisfy markdownlint for the pull request template. (GH-6786)
https://github.com/python/cpython/commit/5cd22cf2097a6dd209999cf97858d54564a3be87


----------
nosy: +benjamin.peterson

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

From report at bugs.python.org  Sun May 13 20:56:28 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 14 May 2018 00:56:28 +0000
Subject: [docs] [issue33488] github pull request template does not satisfy
 markdownlint
In-Reply-To: <1526258440.92.0.682650639539.issue33488@psf.upfronthosting.co.za>
Message-ID: <1526259388.94.0.262363346258.issue33488@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun May 13 20:59:52 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 14 May 2018 00:59:52 +0000
Subject: [docs] [issue33488] github pull request template does not satisfy
 markdownlint
In-Reply-To: <1526258440.92.0.682650639539.issue33488@psf.upfronthosting.co.za>
Message-ID: <1526259592.77.0.262363346258.issue33488@psf.upfronthosting.co.za>


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


----------
pull_requests: +6474

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

From report at bugs.python.org  Sun May 13 21:27:00 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 14 May 2018 01:27:00 +0000
Subject: [docs] [issue33488] github pull request template does not satisfy
 markdownlint
In-Reply-To: <1526258440.92.0.682650639539.issue33488@psf.upfronthosting.co.za>
Message-ID: <1526261220.48.0.682650639539.issue33488@psf.upfronthosting.co.za>


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


New changeset f1ee4a2e52d98698ec2c0a0e8acb6cd3bbc9bf1f by Benjamin Peterson in branch '3.7':
[3.7] bpo-33488: Satisfy markdownlint for the pull request template. (GH-6786)
https://github.com/python/cpython/commit/f1ee4a2e52d98698ec2c0a0e8acb6cd3bbc9bf1f


----------

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

From report at bugs.python.org  Sun May 13 23:36:43 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 14 May 2018 03:36:43 +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: <1526269003.8.0.682650639539.issue33477@psf.upfronthosting.co.za>


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

ref #32911

And it's documented already.
https://docs.python.org/3.7/whatsnew/3.7.html#changes-in-the-python-api

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

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

From report at bugs.python.org  Sun May 13 23:54:50 2018
From: report at bugs.python.org (Ivan Pozdeev)
Date: Mon, 14 May 2018 03:54:50 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526270090.46.0.682650639539.issue33479@psf.upfronthosting.co.za>


Ivan Pozdeev <ivan_pozdeev at mail.ru> added the comment:

I was composing a letter to python-dev with all I know of how tkinter works with regard to threads and Tcl, and the fixing plans so that we're all on the same page if you wish to participate.

I'm no longer sure if it belongs in the mailing list so see it in the attachment.

The plan I have for fixing the documentation is there towards the end.
It includes what you suggested but is more detailed. I'll recite it below:

---

* Document the current behaviour by rewriting https://docs.python.org/3/library/tkinter.html .

   Since I've recently learned Tkinter, I can say which critical information is missing and which existing one proved useless.

   Principles:

    * include fundamental information critical to understand the module's behaviour
    * concentrate on reference documentation for the module because it's more important to have than a user guide ( https://meta.serverfault.com/questions/8934/what-to-do-with-questions-when-the-answer-is-in-a-man-page#comment22241_8938 )
    * split off/drop anything unrelated to the above two

   Resulting scheme:

   0. Intro: +supported Tcl/Tk versions and the two flavors; the fact that Tkinter adds its own logic, and the Tkinter doc concentrates on that logic and refers to Tcl/Tk docs for details that are taken from there without changes.

   * Move external links section to be bottom.

   1. Architecture. "Unlike most other GUI toolkits, Tcl/Tk consists of a few separate modules with a clear distinction between them, and this is non-transparect to the user:..." Base on https://docs.python.org/3/library/tkinter.html#how-tk-and-tkinter-are-related , but focus on what implements what rather than what _calls_ what; drop Xlib entry (transparent implementation detail, not required for understanding).

   2. Threading model. The above-described general idea and user-visible limitations what can be called where and when. (the letter has details that this refers to, too long to recite)

   3. References for `tkinter`, `tkinter.Tk()`, `_tkinter.Tkapp` (public interface only -- `call()` at least). Mention which functions cannot be called from other threads. Do not mention the two issue33257 bugs.

   * Move widget reference to another page.
   * Drop Python-Tcl mappings unless the reference sections need them as supplemental reference.
   * Drop tutorial: too primitive to be useful. Move tutorials to another page like https://docs.python.org/3/library/logging.html does.
   * Drop https://docs.python.org/3/library/tk.html -- proved hard to find. Make https://docs.python.org/3/library/tkinter.html the head page instead.

* Discuss which of the described behaviour is as intended and which is a bug. Proceed with fixing.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +Ivan.Pozdeev, docs at python
Added file: https://bugs.python.org/file47586/[Python-Dev] Tkinter threading model description and fix plan.eml

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

From report at bugs.python.org  Mon May 14 03:38:51 2018
From: report at bugs.python.org (Ivan Gushchin)
Date: Mon, 14 May 2018 07:38:51 +0000
Subject: [docs] [issue33491] mistype of method's name
Message-ID: <1526283531.17.0.682650639539.issue33491@psf.upfronthosting.co.za>


New submission from Ivan Gushchin <gui74327 at gmail.com>:

This link 
https://docs.python.org/2/library/unittest.html#unittest.SkipTest

names method from Capital letter. At the same time method name (according to help(unittest) ) is skipTest (starting lowercase). For those who reads documentation online this mistype leads to error.

----------
assignee: docs at python
components: Documentation
messages: 316493
nosy: Ivan Gushchin, docs at python
priority: normal
severity: normal
status: open
title: mistype of method's name
type: enhancement
versions: Python 2.7

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

From report at bugs.python.org  Mon May 14 04:14:25 2018
From: report at bugs.python.org (Martijn Pieters)
Date: Mon, 14 May 2018 08:14:25 +0000
Subject: [docs] [issue33492] Updating the Evaluation order section to cover
 *expression in calls
Message-ID: <1526285664.99.0.682650639539.issue33492@psf.upfronthosting.co.za>


New submission from Martijn Pieters <mj at python.org>:

Can the *Evaluation order* (_evalorder) section in reference/expressions.rst please be updated to cover this exception in a *call* primary (quoting from the _calls section):


    A consequence of this is that although the ``*expression`` syntax may appear
    *after* explicit keyword arguments, it is processed *before* the
    keyword arguments (and any ``**expression`` arguments -- see below).  So::

This exception to the normal expression evaluation order is rather buried in the _calls section only.

----------
assignee: docs at python
components: Documentation
messages: 316494
nosy: docs at python, mjpieters
priority: normal
severity: normal
status: open
title: Updating the Evaluation order section to cover *expression in calls
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon May 14 05:21:55 2018
From: report at bugs.python.org (Martin Panter)
Date: Mon, 14 May 2018 09:21:55 +0000
Subject: [docs] [issue32393] nav menu jitter in old documentation
In-Reply-To: <1513810852.69.0.213398074469.issue32393@psf.upfronthosting.co.za>
Message-ID: <1526289715.54.0.682650639539.issue32393@psf.upfronthosting.co.za>


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

Maybe related to Issue 24712?

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

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

From 14JHarvey at stanwell.org  Wed May  9 07:28:43 2018
From: 14JHarvey at stanwell.org (14JHarvey at stanwell.org)
Date: Wed, 9 May 2018 11:28:43 +0000
Subject: [docs] issue
Message-ID: <95b68a578fed44ad8165253129b3e843@stanwell.org>

I am using Python 3.3 the main code is shown in uploaded pic "Capture1". The part in the code that is apparently broken is the Postcode1 variable.

As shown in pic "Capture2", after I have converted the entire string to a list (each letter seperated), a c is shown at the front of the list, however, this only occurs sometimes (most of the time as sometimes this does not happen) as shown in "Capture3", when the code loops back round this never occurs. The rest of the pics (4 and onwards) displays the rest of the code, I have also attatched the code. Thanks

Disclaimer

This email and any attachments are confidential. Unless you are the intended recipient, you may not use, copy or disclose either the message or any information contained within the message. If you are not the intended recipient, you should delete this email and notify the sender immediately. Any views or opinions expressed in this email are those of the sender only and not that of Stanwell School unless otherwise stated.

Stanwell School emails and any attachments have not been encrypted; they may therefore be liable to compromise. Please also note that it is your responsibility to scan emails and any attachments for viruses.

Stanwell School<http://www.stanwell.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture1.PNG
Type: image/png
Size: 32613 bytes
Desc: Capture1.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture2.PNG
Type: image/png
Size: 175703 bytes
Desc: Capture2.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture3.PNG
Type: image/png
Size: 176098 bytes
Desc: Capture3.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture4.PNG
Type: image/png
Size: 175230 bytes
Desc: Capture4.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture5.PNG
Type: image/png
Size: 184361 bytes
Desc: Capture5.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture6.PNG
Type: image/png
Size: 182700 bytes
Desc: Capture6.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture7.PNG
Type: image/png
Size: 179888 bytes
Desc: Capture7.PNG
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0013.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: module1 (1).py
URL: <http://mail.python.org/pipermail/docs/attachments/20180509/be951461/attachment-0001.ksh>

From Bjorn.Madsen at dematic.com  Fri May 11 09:59:00 2018
From: Bjorn.Madsen at dematic.com (Madsen, Bjorn)
Date: Fri, 11 May 2018 13:59:00 +0000
Subject: [docs] itertools.product - missing documentation of usage of *
Message-ID: <BN3PR1201MB1092F77392C1E30A937C3F62839F0@BN3PR1201MB1092.namprd12.prod.outlook.com>

Itertools.product has a "magic" function that isn't documented:

The usage of * as precedent to a list of lists of variable length.

Example:
>>> from itertools import product
>>> list(product(*[[-1,1], [-2,-2.5,2], [-3,3]]))
[(-1, -2, -3), (-1, -2, 3), (-1, -2.5, -3), (-1, -2.5, 3), (-1, 2, -3), (-1, 2, 3), (1, -2, -3), (1, -2, 3), (1, -2.5, -3), (1, -2.5, 3), (1, 2, -3), (1, 2, 3)]

The function works perfectly. The documentation of the usage is missing.
Please add it.

Kind regards

Bjorn Madsen, Ph.D.
Head of System Design Tools
[Beschreibung: Beschreibung: Beschreibung: Dematic Logo]
We Optimise Your Supply Chain

Dematic Limited
Banbury Business Park
Trinity Way
Adderbury
Banbury
OX17 3SN
Phone: +44 (0) 7590 306 987
bjorn.madsen at dematic.com<mailto:bjorn.madsen at dematic.com>
www.dematic.com<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__www.dematic.com_%26d%3DDwMFAg%26c%3DKapZzwhopA3IFGTjMLqImrQVuf1cLczLfYDt045Y5_Y%26r%3D0Og4eqfe8mPps1MmMhpO2Zv3zMQhO5MF5hj5B_qOcvo%26m%3DjnuBTxQ_8VdziL9939vkOaaX9LsmWv4Vd0hhr5sSVkU%26s%3DWvxE_osCyWoWlev1vGPVw-S-Wp9SVA7i9nMjuphg_B8%26e%3D&data=01%7C01%7Cmark.pickerill%40dematic.com%7C2bb6273f6c90422e118f08d5438e948d%7Cb87688c18bb44f8698754da105de8eda%7C0&sdata=6kBG2FWhTBq2tof9kSM1ApoGWKoRQjDCIJpnpQ%2Bnkrk%3D&reserved=0>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180511/43edd728/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 5942 bytes
Desc: image001.gif
URL: <http://mail.python.org/pipermail/docs/attachments/20180511/43edd728/attachment.gif>

From jpn.jha1 at gmail.com  Sun May 13 06:22:51 2018
From: jpn.jha1 at gmail.com (Jpn Jha)
Date: Sun, 13 May 2018 15:52:51 +0530
Subject: [docs] ModuleNotFoundError: No module named sklearn
Message-ID: <CACt-=wd7CrBAY3KLkAZG4DteW5DVcwTO=GfLv1Q6LrLMGz3OhQ@mail.gmail.com>

Dear
I am NEW to Python   and PyCharm

Re:  Python 3.6.5 , PyCharm 2018.1.2x64 in Window 7 professional
I have updated PIP 9.0.1 version to 10.0.1, but it is not showing in
Project Interpreter window.
Programe
Code:
from sklearn  import  linear_model
import matplotlib.pyplot as plt

all the above import  are showing  with marks.

Could you please GUIDE me step wise to resolve the issues.

Thanks
Regards
Jai Prakash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180513/d3362f2a/attachment-0001.html>

From report at bugs.python.org  Mon May 14 10:48:04 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 14 May 2018 14:48:04 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526309283.86.0.682650639539.issue22069@psf.upfronthosting.co.za>


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


New changeset 7ffd4c58fae08b29259eebd6cbcd2287820b14e8 by Mariatta (Elena Oat) in branch 'master':
bpo-22069: Update TextIO documentation (GH-6609)
https://github.com/python/cpython/commit/7ffd4c58fae08b29259eebd6cbcd2287820b14e8


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

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

From report at bugs.python.org  Mon May 14 10:49:14 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 14:49:14 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526309354.17.0.262363346258.issue22069@psf.upfronthosting.co.za>


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


----------
pull_requests: +6485

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

From report at bugs.python.org  Mon May 14 10:50:16 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 14:50:16 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526309416.45.0.262363346258.issue22069@psf.upfronthosting.co.za>


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


----------
pull_requests: +6486

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

From report at bugs.python.org  Mon May 14 10:51:13 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 14:51:13 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526309473.92.0.262363346258.issue22069@psf.upfronthosting.co.za>


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


----------
pull_requests: +6487

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

From report at bugs.python.org  Mon May 14 12:08:59 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 16:08:59 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526314139.19.0.682650639539.issue22069@psf.upfronthosting.co.za>


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


New changeset 050e041bf7e5260013a74c75a05a3f0fb16447ec by Miss Islington (bot) in branch '3.7':
bpo-22069: Update TextIO documentation (GH-6609)
https://github.com/python/cpython/commit/050e041bf7e5260013a74c75a05a3f0fb16447ec


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

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

From report at bugs.python.org  Mon May 14 12:11:44 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 16:11:44 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526314304.91.0.682650639539.issue22069@psf.upfronthosting.co.za>


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


New changeset 84fc6c59cf286fc4e6b3a700c6db36ecc2bff92b by Miss Islington (bot) in branch '2.7':
bpo-22069: Update TextIO documentation (GH-6609)
https://github.com/python/cpython/commit/84fc6c59cf286fc4e6b3a700c6db36ecc2bff92b


----------

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

From report at bugs.python.org  Mon May 14 12:18:09 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 16:18:09 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526314689.81.0.682650639539.issue22069@psf.upfronthosting.co.za>


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


New changeset 9fd5b5fdf851d35a5c1314360119850e86a1fd0d by Miss Islington (bot) in branch '3.6':
bpo-22069: Update TextIO documentation (GH-6609)
https://github.com/python/cpython/commit/9fd5b5fdf851d35a5c1314360119850e86a1fd0d


----------

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

From report at bugs.python.org  Mon May 14 12:18:27 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 14 May 2018 16:18:27 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526314707.32.0.262363346258.issue22069@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 14 12:25:06 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 14 May 2018 16:25:06 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526315106.84.0.682650639539.issue22069@psf.upfronthosting.co.za>


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

Thanks!

----------
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/issue22069>
_______________________________________

From report at bugs.python.org  Mon May 14 12:25:15 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 14 May 2018 16:25:15 +0000
Subject: [docs] [issue22069] TextIOWrapper(newline="\n",
 line_buffering=True) mistakenly treat \r as a newline
In-Reply-To: <1406306623.81.0.633771356606.issue22069@psf.upfronthosting.co.za>
Message-ID: <1526315115.21.0.262363346258.issue22069@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 14 13:18:39 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 14 May 2018 17:18:39 +0000
Subject: [docs] [issue26103] Contradiction in definition of "data
 descriptor" between (dotted lookup behavior/datamodel documentation) and
 (inspect lib/descriptor how-to)
In-Reply-To: <1452718612.1.0.925403449689.issue26103@psf.upfronthosting.co.za>
Message-ID: <1526318319.64.0.262363346258.issue26103@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 14 13:53:25 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 14 May 2018 17:53:25 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
In-Reply-To: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>
Message-ID: <1526320405.46.0.262363346258.issue33421@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 14 14:07:42 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 14 May 2018 18:07:42 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526321262.06.0.682650639539.issue32216@psf.upfronthosting.co.za>


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

Note that the documentation should make the implications of #33453 very clear.

In short, if an annotation "looks like" a ClassVar or InitVar, it will be treated as such. This is true even if it's specified as a string, or if it's a string due to "from __future__ import annotations".

I'm planning on specifying more details in #33453.

----------

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

From report at bugs.python.org  Mon May 14 14:46:22 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 14 May 2018 18:46:22 +0000
Subject: [docs] [issue14845] list(<generator expression>) != [<list
 comprehension>]
In-Reply-To: <1337294857.69.0.824992743087.issue14845@psf.upfronthosting.co.za>
Message-ID: <1526323582.11.0.262363346258.issue14845@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


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

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

From report at bugs.python.org  Mon May 14 15:05:00 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 14 May 2018 19:05:00 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526324699.88.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:


New changeset f2290fb19a9b1a5fbeef0971016f72683e8cd1ad by Ivan Levkivskyi (Andr?s Delfino) in branch 'master':
bpo-32769: Write annotation entry for glossary (GH-6657)
https://github.com/python/cpython/commit/f2290fb19a9b1a5fbeef0971016f72683e8cd1ad


----------

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

From report at bugs.python.org  Mon May 14 15:19:03 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 14 May 2018 19:19:03 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526325543.72.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

Maybe we can consider backporting this to 3.7? Andr?s, if you think it makes sense, you can cherry-pick the commit and open a PR against 3.7 branch.

----------

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

From report at bugs.python.org  Mon May 14 15:20:52 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 14 May 2018 19:20:52 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526325652.57.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Yes, Ivan, I was thinking about that.

I think it makes sense, and I'll be glad to do it.

----------

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

From report at bugs.python.org  Mon May 14 15:23:06 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 14 May 2018 19:23:06 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526325786.49.0.262363346258.issue32769@psf.upfronthosting.co.za>


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


----------
pull_requests: +6506

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

From report at bugs.python.org  Mon May 14 15:24:21 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 14 May 2018 19:24:21 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526325861.57.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Shouldn't we have this on 3.6 also?

----------

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

From report at bugs.python.org  Mon May 14 15:27:24 2018
From: report at bugs.python.org (Travis DePrato)
Date: Mon, 14 May 2018 19:27:24 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
In-Reply-To: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>
Message-ID: <1526326044.93.0.262363346258.issue33421@psf.upfronthosting.co.za>


Change by Travis DePrato <travigd at umich.edu>:


----------
pull_requests: +6507

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

From report at bugs.python.org  Mon May 14 15:28:49 2018
From: report at bugs.python.org (Travis DePrato)
Date: Mon, 14 May 2018 19:28:49 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
In-Reply-To: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>
Message-ID: <1526326129.22.0.262363346258.issue33421@psf.upfronthosting.co.za>


Change by Travis DePrato <travigd at umich.edu>:


----------
pull_requests: +6508

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

From report at bugs.python.org  Mon May 14 15:39:36 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 14 May 2018 19:39:36 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526326776.81.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

Yes, all this also applies to 3.6.

----------

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

From report at bugs.python.org  Mon May 14 15:45:13 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 14 May 2018 19:45:13 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526327113.24.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Before we backport this to 3.7 and 3.6, let's iterate on the wording a bit.

I don't think the distinction between annotations and type hints is that annotations are materialized at runtime while type hints aren't. I think syntactically they are the same, but annotations are a slightly more general concept because they may be used for other purposes than to indicate the type of a variable (or argument, attribute etc.).

So IMO in

  def f():
      x: int

'int' is both an annotation and a type hint, OTOH in

  x: 'spam eggs ham'

we have an annotation that is not a type hint.

----------

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

From report at bugs.python.org  Mon May 14 15:48:44 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 14 May 2018 19:48:44 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526327324.21.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

> ... but annotations are a slightly more general concept because they may be used for other purposes than to indicate the type of a variable ...

Yes, I agree.

----------

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

From report at bugs.python.org  Mon May 14 15:54:57 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 14 May 2018 19:54:57 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526327697.5.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

I see a conflict here in that annotations can be used for other purpouses, for example variable annotations, they are heavily intended for type hinting (PEP 526 says "This PEP aims at adding syntax to Python for annotating the types of variables (including class variables and instance variables), instead of expressing them through comments")

I think it's correct to separate annotations from type hints, and say: annotations can be used for type hinting.

I can make a new PR based on master having this in mind, and then cherry picking it for 3.7/3.6.

----------

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

From report at bugs.python.org  Mon May 14 16:22:44 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 14 May 2018 20:22:44 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526329364.93.0.262363346258.issue32769@psf.upfronthosting.co.za>


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


----------
pull_requests: +6513

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

From report at bugs.python.org  Mon May 14 16:33:57 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 14 May 2018 20:33:57 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526330037.89.0.262363346258.issue32769@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 14 18:16:56 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 May 2018 22:16:56 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
In-Reply-To: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>
Message-ID: <1526336216.35.0.262363346258.issue33421@psf.upfronthosting.co.za>


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


----------
pull_requests: +6522

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

From report at bugs.python.org  Mon May 14 20:25:37 2018
From: report at bugs.python.org (Mark Roseman)
Date: Tue, 15 May 2018 00:25:37 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526343937.04.0.682650639539.issue33479@psf.upfronthosting.co.za>


Mark Roseman <mark at markroseman.com> added the comment:

This seems very complicated. The official line on threads for Tk has always been to make all Tk calls from one thread, which is at least predictable and comprehensible. Is there any reason for Tkinter to suggest anything different?

This ignores the compilation issue of course. FYI, the Tcl core group will probably eliminate the possibility of doing non-threaded builds in the future, though with backwards compatibility issues, that's neither here nor there.

----------
nosy: +markroseman

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

From report at bugs.python.org  Mon May 14 21:33:20 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 15 May 2018 01:33:20 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526348000.37.0.682650639539.issue33479@psf.upfronthosting.co.za>


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

The official line is the claim in the docs that tkinter *is* threadsafe, repeated by Martin on at least one issue.  See the first paragraph above.  Therein lies the problem.

A reason to not just reverse the claim is that it is, at least for practical purposes, true, by default, for 8.6.  See the opening post of #11077 for one motivation for calling from threads.  (Numerous others have tried and reported failures, though usually without explaining why they tried.)

Mark, do you know how to identify the tcl/tk build on MacOS or Linux?  If so, and you have installed 3.7.0 on MacOS since b0, which includes 8.6.8, can you report which it is?  Ditto for any Linux distribution you have.

----------

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

From report at bugs.python.org  Mon May 14 22:07:56 2018
From: report at bugs.python.org (bbayles)
Date: Tue, 15 May 2018 02:07:56 +0000
Subject: [docs] [issue33491] mistype of method's name
In-Reply-To: <1526283531.17.0.682650639539.issue33491@psf.upfronthosting.co.za>
Message-ID: <1526350076.27.0.682650639539.issue33491@psf.upfronthosting.co.za>


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

I think you'll find that your link points to the exception class `SkipTest`, which does start with a capital level.

This is distinct from the `skipTest` method of `unittest.TestCase` objects, which starts with a lowercase letter.

The documentation looks right to me. See [1] for a demonstration of the difference.

[1] https://gist.github.com/bbayles/5158750b48a5accfceaa53a898b8b902

----------
nosy: +bbayles

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

From report at bugs.python.org  Mon May 14 22:16:41 2018
From: report at bugs.python.org (Ivan Pozdeev)
Date: Tue, 15 May 2018 02:16:41 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526350600.87.0.682650639539.issue33479@psf.upfronthosting.co.za>


Ivan Pozdeev <ivan_pozdeev at mail.ru> added the comment:

> This seems very complicated. The official line on threads for Tk has always been to make all Tk calls from one thread, which is at least predictable and comprehensible. Is there any reason for Tkinter to suggest anything different?

Tcl/Tk doesn't have a notion of a blocking event loop like other GUI toolkits do. Any code using Tcl must essentially call Tcl_DoOneEvent/`update` regularly at strategic points.
This allows to work completely in one thread -- i.e. even if the OS has no threads whatsoever. Tcl/Tk is very old, and this model made perfect sense back then (and still does in some scenarios -- e.g. https://stackoverflow.com/questions/4083796/how-do-i-run-unittest-on-a-tkinter-app -- so there's no point in dropping it).
If we'll be updating tutorials (the reference is a priority though), we definitly need to demonstrate this option.

The current best practice for GUI programming is different. There's one "GUI" thread that runs just the event loop constantly, and other threads submit GUI-related work items into its queue (whatever they are called - "messages", "events", "futures"...). Likewise, for any lengthy task, the GUI thread spawns worker threads that report back on their progress via the same queue.

All more or less modern GUI toolkits implement and advertize this model as the primary one -- as does Tkinter. So, at least the work item submitting API must be thread-safe (and in other GUI tooltikts, it is -- see https://mail.python.org/pipermail/python-dev/2018-May/153359.html ).
For programmer's convenience, Tkinter does this transparently: whenever and whatever Python thread a call is made from, it makes it look for the Tcl interpreter as if all calls are sequential, and it enforces correct order for interdependent calls.

A great deal of complexity comes from the fact that Tcl's threading model is very unothodox. Tcl's team seem to only have accepted threads reluctantly and to have been campaigning against threads for years before that (https://wiki.tcl.tk/38128 is arguably the most egregious case).
So, what they did is tie a Tcl interpreter to an OS thread (by using thread local storage for its data). Long story short, no-one else does it like this (at least, I've never seen or heard of anything of the kind), and this is not what thread-local storage is meant for (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4324.html lists some use cases for TLS). The best practice is to use locks to ensure orderly access to the shared state instead. My guess for the decision is it was the easiest way to migrate the code base (yet still tough as https://wiki.tcl.tk/1370 seems to hint), and it kinda lines up with that "single thread" mindset.

Tkinter thus has to jump through hoops for calls coming from other threads (since for Python, it absolutely doesn't matter which OS thread makes a call).
All the limitations when using threaded Tcl (see the letter attached to the ticket for details) come solely from this tying. With nonthreaded Tcl (bugs nonwithstanding), it's free-for-all, everything can be called from everywhere. The only upside is that with threaded Tcl, calls to different interpreters can run in parallel.

> This ignores the compilation issue of course. FYI, the Tcl core group will probably eliminate the possibility of doing non-threaded builds in the future, though with backwards compatibility issues, that's neither here nor there.

I know. Me asking them for clarifications from Tcl/Tk's side seems to have triggered it, in fact. Since the sole offender is their threading model, the way is to show them how it's defective and work towards improving it. We have at least a few years with old versions, and the limitations seem tolerable at first glance anyway, so that's not a priority.

> do you know how to identify the tcl/tk build on MacOS or Linux?

The same way Tkinter does @_tkinter.c:624 . The equivalent Python is `tkinter.Tk().tk.call("array","get","tcl_platform","threaded")`

----------

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

From report at bugs.python.org  Tue May 15 00:06:37 2018
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 15 May 2018 04:06:37 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526357197.24.0.682650639539.issue32769@psf.upfronthosting.co.za>


?ukasz Langa <lukasz at langa.pl> added the comment:

Guido, do you really want to stress at this point for Python 3.8 that annotations do not have an intended purpose? That is clearly not true.

1. PEP 526 was created purely with types in mind and was inspired by PEP 484's lack of this functionality.

2. PEP 563 defines a future import which will become the default in a future release (currently marked as 4.0). This default stops evaluating annotations at runtime, which again was inspired by the typing use case.

3. Dataclasses in PEP 557 are designed to leverage types in annotations. A few quotes from that PEP:

> A class decorator is provided which inspects a class definition for variables with type annotations as defined in PEP 526, "Syntax for Variable Annotations".

> One main design goal of Data Classes is to support static type checkers. The use of PEP 526 syntax is one example of this, but so is the design of the fields() function and the @dataclass decorator.

4. PEP 560 added support for `__class_getitem__` and `__mro_entries__` in core purely for the purpose of generic types.

5. For the above reasons, PEP 563 states that non-typing usage of annotations is deprecated:

https://www.python.org/dev/peps/pep-0563/#non-typing-usage-of-annotations

----------
nosy: +lukasz.langa

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

From report at bugs.python.org  Tue May 15 05:27:42 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Tue, 15 May 2018 09:27:42 +0000
Subject: [docs] =?utf-8?q?=5Bissue33514=5D_async_and_await_as_keywords_no?=
 =?utf-8?q?t_mentioned_in_What=E2=80=99s_New_In_Python_3=2E7?=
Message-ID: <1526376462.69.0.682650639539.issue33514@psf.upfronthosting.co.za>


New submission from Miro Hron?ok <miro at hroncok.cz>:

According to PEP 492, async and await should be full keywords in Python 3.7. That happened in https://bugs.python.org/issue30406

There is no mention of it at all at https://docs.python.org/3.7/whatsnew/3.7.html#porting-to-python-3-7 or anywhare on that page.

I consider this a blocker because it can break things:

    $ python3.6 -c 'async = 42'
    $ echo $?
    0
    $ python3.7 -c 'async = 42'
      File "<string>", line 1
        async = 42
              ^
    SyntaxError: invalid syntax

----------
assignee: docs at python
components: Documentation
messages: 316632
nosy: Jelle Zijlstra, docs at python, hroncok
priority: normal
severity: normal
status: open
title: async and await as keywords not mentioned in What?s New In Python 3.7
type: behavior
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue May 15 05:42:53 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Tue, 15 May 2018 09:42:53 +0000
Subject: [docs] =?utf-8?q?=5Bissue33514=5D_async_and_await_as_keywords_no?=
 =?utf-8?q?t_mentioned_in_What=E2=80=99s_New_In_Python_3=2E7?=
In-Reply-To: <1526376462.69.0.682650639539.issue33514@psf.upfronthosting.co.za>
Message-ID: <1526377373.74.0.682650639539.issue33514@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

I'll prep a PR

----------

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

From report at bugs.python.org  Tue May 15 06:23:58 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 15 May 2018 10:23:58 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526379838.12.0.682650639539.issue32216@psf.upfronthosting.co.za>


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

Mariatta, go ahead and take the lead on this one.

----------

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

From report at bugs.python.org  Tue May 15 06:32:34 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 May 2018 10:32:34 +0000
Subject: [docs] =?utf-8?q?=5Bissue33514=5D_async_and_await_as_keywords_no?=
 =?utf-8?q?t_mentioned_in_What=E2=80=99s_New_In_Python_3=2E7?=
In-Reply-To: <1526376462.69.0.682650639539.issue33514@psf.upfronthosting.co.za>
Message-ID: <1526380354.03.0.682650639539.issue33514@psf.upfronthosting.co.za>


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

Thanks for the report.  The 3.7 What's New document is being completed right now at the PyCon US sprints.  CCing the editors.

----------
nosy: +Elvis.Pranskevichus, ned.deily, yselivanov

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

From report at bugs.python.org  Tue May 15 06:35:20 2018
From: report at bugs.python.org (Eric Lebigot)
Date: Tue, 15 May 2018 10:35:20 +0000
Subject: [docs] [issue33492] Updating the Evaluation order section to cover
 *expression in calls
In-Reply-To: <1526285664.99.0.682650639539.issue33492@psf.upfronthosting.co.za>
Message-ID: <1526380520.05.0.262363346258.issue33492@psf.upfronthosting.co.za>


Change by Eric Lebigot <eric.lebigot at normalesup.org>:


----------
nosy: +Eric Lebigot

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

From report at bugs.python.org  Tue May 15 06:35:38 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Tue, 15 May 2018 10:35:38 +0000
Subject: [docs] =?utf-8?q?=5Bissue33514=5D_async_and_await_as_keywords_no?=
 =?utf-8?q?t_mentioned_in_What=E2=80=99s_New_In_Python_3=2E7?=
In-Reply-To: <1526376462.69.0.682650639539.issue33514@psf.upfronthosting.co.za>
Message-ID: <1526380538.61.0.262363346258.issue33514@psf.upfronthosting.co.za>


Change by Miro Hron?ok <miro at hroncok.cz>:


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

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

From report at bugs.python.org  Tue May 15 06:39:18 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Tue, 15 May 2018 10:39:18 +0000
Subject: [docs] =?utf-8?q?=5Bissue33514=5D_async_and_await_as_keywords_no?=
 =?utf-8?q?t_mentioned_in_What=E2=80=99s_New_In_Python_3=2E7?=
In-Reply-To: <1526376462.69.0.682650639539.issue33514@psf.upfronthosting.co.za>
Message-ID: <1526380758.04.0.682650639539.issue33514@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

Oh, didn't know that. Consider my PR as a remote sprint contribution. Hopefully nobody has already written this part.

----------

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

From report at bugs.python.org  Tue May 15 08:16:52 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Tue, 15 May 2018 12:16:52 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526386612.15.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

What I think Guido might mean is that some type annotations are not strictly speaking type hints. For example, `dataclasses.InitVar`, is not really a type, it is just a way to indicate how constructor should be constructed. I could see similar potential features in future (like `typing.Final` discussed recently). Even `typing.ClassVar` I would say is not a type but an access qualifier.

Also for me the two terms: annotations and hints are a bit orthogonal, first is a syntax, while second is semantics. I think Guido is right that we should say something like (approximately) `annotation is a syntax to express type hints and other related metadata` or similar. The current formulation seems a bit too restrictive.

----------

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

From report at bugs.python.org  Tue May 15 08:20:58 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 15 May 2018 12:20:58 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1526386612.15.0.682650639539.issue32769@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJJJ=aJ=h3Q-EGJZB2XvkH5c7AZJGGSXJEw6yhvWniZDUg@mail.gmail.com>


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

I actually intended to say that annotations continue to be usable for
non-typing purposes (beyond ClassVar/InitVar). It may be deprecated but the
usage still exists. This is a glossary, not a manifesto.

I'm fine with adding that the main use of annotations is for type hints of
course. And I was mostly reacting to the fact that the text that was just
committed seemed to imply that 'annotation' refers to something stored at
runtime in __annotations__ while 'type hint' was a syntactic form (and this
is borne out by the omission of *local* type hints from the section on
annotations).

----------

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

From report at bugs.python.org  Tue May 15 08:24:37 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Tue, 15 May 2018 12:24:37 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526387077.43.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

Yes, local annotations are important and should be mentioned (maybe even with an example).

----------

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

From report at bugs.python.org  Tue May 15 09:02:24 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 15 May 2018 13:02:24 +0000
Subject: [docs] [issue33518] Add PEP to glossary
Message-ID: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>


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

I think PEP should be mentioned in the glossary, as it is an important piece of how Python is developed and learned.

The PR's wording is taken from PEP1, mostly verbatim.

----------
assignee: docs at python
components: Documentation
messages: 316653
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Add PEP 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/issue33518>
_______________________________________

From report at bugs.python.org  Tue May 15 09:03:49 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 15 May 2018 13:03:49 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526389429.61.0.262363346258.issue33518@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue May 15 11:20:06 2018
From: report at bugs.python.org (Mark Roseman)
Date: Tue, 15 May 2018 15:20:06 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526397606.43.0.682650639539.issue33479@psf.upfronthosting.co.za>


Mark Roseman <mark at markroseman.com> added the comment:

Hi Ivan, thanks for your detailed response. The approach you're suggesting ("Since the sole offender is their threading model, the way is to show them how it's defective and work towards improving it.") is in the end not something I think is workable. 

Some historical context. Ousterhout had some specific ideas about how Tcl/Tk should be used, and that was well-reflected in his early control of the code base. He was certainly outspoken against threads. The main argument is that they're complicated if you don't know what you're doing, which included the "non-professional programmers" he considered the core audience. Enumerating how threads were used at the time, most of the uses could be handled (more simply) in other ways, such as event-driven and non-blocking timers and I/O (so what people today would refer to as the "node.js event model"). Threads (or separate communicating processes) were for long-running computations, things he always envisioned happening in C code (written by more "professional programmers"), not Tcl. His idea of how Tcl and C development would be split didn't match reality given faster machines, more memory, etc.

The second thing is that Tcl had multiple interpreters baked in pretty much from the beginning at the C level and exposed fairly early on (1996?) at the Tcl level, akin to PEP 554. Code isolation and resource management were the key motivators, but of course others followed. Creating and using Tcl interpreters was quick, lightweight (fast startup, low memory overhead, etc.) and easy. So in other words, the notion of multiple interpreters in Tcl vs. Python is completely different. I had one large application I built around that time that often ended up with hundreds of interpreters running.

Which brings me to threads and how they were added to the language. Your guess ("My guess for the decision is it was the easiest way to migrate the code base") is incorrect. The idea of "one thread/one interpreter" was just not seen as a restriction, and was a very natural extension of what had come before. It fit the use cases well (AOLserver was another good example) and was still very understandable from the user level. Contrast with Python's GIL, etc. 

With that all said, there would be very little motivation to change the Tcl/Tk side to allow multiple threads to access one interpreter, because in terms of the API and programming model that Tcl/Tk advertises, it's simply not a problem. Keep in mind, the people working on the Tcl/Tk core are very smart programmers, know threads very well, etc., so it's not an issue of "they should know better" or "it's old." In other words, "show them how it's defective" is a non-starter. 

The other, more practical matter in pushing for changes in the Tcl/Tk core, is that there are a fairly small number of people working on it, very part-time. Almost all of them are most interested in the Tcl side, not Tk. Changes made in Tk most often amount to bug fixes because someone's running into something in their own work. Expecting large-scale changes to happen to Tk without some way to get dedicated new resources put into it is not realistic.

A final matter on the practical side. As you've carefully noted, certain Tcl/Tk calls now happen to work when called from different threads. Consider those a side-effect of present implementation, not a guarantee. Future core changes could change what can be called from different threads, making the situation better or worse. From the Tcl/Tk perspective, this is not a problem, and would not be caught by any testing, etc. Even if it were, it likely wouldn't be fixed. It would be considered an "abuse" of their API (I think correctly).

My suggestion, given the philosophical and practical mismatch, is that Tkinter move towards operating as if the API Tk provides is inviolate. In other words, all calls into a Tcl interpreter happen from the same thread that created the Tcl interpreter. Tkinter acts as a bridge between Python and Tcl/Tk. It should present an API to Python programs compatible with the Python threading model. It's Tkinter's responsibility to map that onto Tcl/Tk's single threaded API through whatever internal mechanism is necessary (i.e. pass everything to main thread, block caller thread until get response, etc.)

I'd go so far as to suggest that all the Tkapp 'call' code (i.e. every place that Tkinter calls Tcl_Eval) check what thread it's in, and issue a warning or error (at least for testing purposes) if it's being called from the "wrong" thread. Having this available in the near future would help people who are debugging what are fairly inexplicable problems now. 

The approach of making Tkinter responsible also has the advantage of dealing with far more Tcl/Tk versions and builds.

Given in practice that few people are really running into things, and that if they are, they know enough to be able to follow the instruction "all Tkinter calls from the same thread" for now, add the warnings/errors in via whatever "turn on debugging" mechanism makes sense. A future version of Python would include a fully thread-safe Tkinter that internally makes all Tcl/Tk calls from a single thread, as per above.

Sorry this is so incredibly long-winded. I hope the context at least is useful information.

----------

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

From report at bugs.python.org  Tue May 15 11:36:59 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 15 May 2018 15:36:59 +0000
Subject: [docs] [issue24318] Better documentaiton of profile-opt (and
 release builds in general?)
In-Reply-To: <1432830865.51.0.995414707141.issue24318@psf.upfronthosting.co.za>
Message-ID: <1526398619.07.0.262363346258.issue24318@psf.upfronthosting.co.za>


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


----------
pull_requests: +6537

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

From report at bugs.python.org  Tue May 15 11:43:23 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 15 May 2018 15:43:23 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526399003.07.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Hopefully I address your comments with the last PR update.

----------

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

From report at bugs.python.org  Tue May 15 11:54:40 2018
From: report at bugs.python.org (Eric Snow)
Date: Tue, 15 May 2018 15:54:40 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526399680.61.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

Yeah, I added an extra parameter.  Since it's an internal API I didn't think anything of it.

----------

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

From report at bugs.python.org  Tue May 15 12:21:58 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 May 2018 16:21:58 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526401318.7.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

Oh, I'm sorry, I misunderstood the issue. Changes in the *private* API must not be documented. In short, you must not use the private API :-)

If you really have to use the private API, be prepared for incompatible changes in new Python releases. For the gdb issue, gdb should use an #ifdef using PY_VERSION_HEX. Depending on the Python version, the number of parameters changes.

Miro: Let's move the discussion to https://bugzilla.redhat.com/show_bug.cgi?id=1577396 to see how to fix gdb ;-)

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

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

From report at bugs.python.org  Tue May 15 12:58:35 2018
From: report at bugs.python.org (Jakub Wilk)
Date: Tue, 15 May 2018 16:58:35 +0000
Subject: [docs] [issue19124] os.execv executes in background on Windows
In-Reply-To: <1380451602.11.0.517013085188.issue19124@psf.upfronthosting.co.za>
Message-ID: <1526403515.46.0.262363346258.issue19124@psf.upfronthosting.co.za>


Change by Jakub Wilk <jwilk at jwilk.net>:


----------
nosy: +jwilk

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

From report at bugs.python.org  Tue May 15 13:39:29 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Tue, 15 May 2018 17:39:29 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526405969.45.0.682650639539.issue33470@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

Sorry for mixing two things here, but I meant that I found out about this because of the private API use in gdb, however nothing from the change is documented on whatsnew at all. This bug was a reaction for https://github.com/python/cpython/pull/1638#issuecomment-388497381

----------

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

From report at bugs.python.org  Tue May 15 13:45:15 2018
From: report at bugs.python.org (Ivan Pozdeev)
Date: Tue, 15 May 2018 17:45:15 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526406315.09.0.682650639539.issue33479@psf.upfronthosting.co.za>


Ivan Pozdeev <ivan_pozdeev at mail.ru> added the comment:

@markroseman replied to python-dev since those perspectives are off topic for this ticket.

----------

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

From report at bugs.python.org  Tue May 15 15:30:03 2018
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 15 May 2018 19:30:03 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526412603.81.0.682650639539.issue32769@psf.upfronthosting.co.za>


?ukasz Langa <lukasz at langa.pl> added the comment:

> It may be deprecated but the usage still exists. This is a glossary, not a manifesto.

Agreed.  However, based on the current wording users will argue that Python documentation itself is stressing the lack of an intended purpose for annotations, equaling the typing use case with all other use cases (including future ones).  This isn't our intent.

I think it would be clearer to change the current wording from:

> A metadata value associated with a variable, a class attribute or a
> function or method parameter or return value, that has no specific
> purpouse (i.e. it's up to the user to use it as they see fit).
> (...)
> Annotations can be used to specify :term:`type hints <type hint>`.

to:

> A metadata value associated with a variable, a class attribute or a
> function or method parameter or return value, that stores a
> :term:`type hint`.
> (...)
> Annotations can be used for other purposes unrelated to typing. This
> usage is deprecated, see :pep:`563` for details.


The `type hint` phrasing is already there, we just need to delete the word "global" that currently appears before "variable".  Note that saying that annotations in class attributes and variables have no assigned meaning contradicts PEP 526.

----------

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

From report at bugs.python.org  Tue May 15 15:37:24 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 May 2018 19:37:24 +0000
Subject: [docs] [issue33427] Dead link in "The Python Standard Library" page
In-Reply-To: <1525489435.58.0.682650639539.issue33427@psf.upfronthosting.co.za>
Message-ID: <1526413044.2.0.682650639539.issue33427@psf.upfronthosting.co.za>


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

Thanks for noticing and for providing the PR.  The proposed change is a subset of the changes for Issue33503.

----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> use pypi.org instead of pypi.python.org

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

From report at bugs.python.org  Tue May 15 15:49:03 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 15 May 2018 19:49:03 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526413743.98.0.262363346258.issue19950@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue May 15 16:10:00 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 15 May 2018 20:10:00 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1526412603.81.0.682650639539.issue32769@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJJjLY0D3K0+FGT_u0odei4n5V5rTVGKRhxdQbFDuPQzWw@mail.gmail.com>


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

Your phrasing still makes it sound like an annotation is a runtime concept
-- I think of it as a syntactic construct. (Otherwise fine.)

----------

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

From report at bugs.python.org  Tue May 15 16:17:31 2018
From: report at bugs.python.org (Eryk Sun)
Date: Tue, 15 May 2018 20:17:31 +0000
Subject: [docs] [issue33515] subprocess.Popen on a Windows batch file always
 acts as if shell=True
In-Reply-To: <1526382091.26.0.682650639539.issue33515@psf.upfronthosting.co.za>
Message-ID: <1526415451.46.0.682650639539.issue33515@psf.upfronthosting.co.za>


Eryk Sun <eryksun at gmail.com> added the comment:

There's no simple workaround for this behavior. All we can reasonably do is document that running a batch script directly has the same security risks as using shell=True. 

CMD doesn't support a file argument. It only supports running a /c or /k command, which can include running multiple commands joined by the &, &&, or || operators. CreateProcess thus executes a .bat or .cmd script by prepending "%ComSpec% /c" to the command line. If %ComSpec% isn't defined, it defaults to "%SystemRoot%\System32\cmd.exe /c".

Environment variables in a command can be escaped in most cases by inserting the "^" escape character after the first "%" character. This disrupts matching the variable name (unless a variable name happens to start with "^"). The escape character itself gets skipped as long as it isn't quoted literally.

----------
assignee:  -> docs at python
components: +Documentation
keywords: +security_issue
nosy: +docs at python, eryksun
stage:  -> needs patch
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue May 15 17:20:58 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 15 May 2018 21:20:58 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1526419258.23.0.262363346258.issue32374@psf.upfronthosting.co.za>


Change by Petr Viktorin <encukou at gmail.com>:


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

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

From report at bugs.python.org  Tue May 15 17:56:07 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 15 May 2018 21:56:07 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526421367.89.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

Guido, could you point out what parts make it sound that way to you so I can change them?

----------

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

From report at bugs.python.org  Tue May 15 19:51:13 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 15 May 2018 23:51:13 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526428272.97.0.262363346258.issue32216@psf.upfronthosting.co.za>


Change by Eric V. Smith <eric at trueblade.com>:


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

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

From report at bugs.python.org  Tue May 15 21:02:12 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 16 May 2018 01:02:12 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1526421367.89.0.682650639539.issue32769@psf.upfronthosting.co.za>
Message-ID: <CAP7+vJLTq+regAh-b5z_hbuHt40hwXpJuBBEeZ+jt5Mr=MaK2Q@mail.gmail.com>


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

(1) The word "stores" in this paragraph:

A metadata value associated with a global variable, a class attribute or a
function or method parameter or return value, that stores a type hint.

(2) The description of how annotations are stored in __annotations__ in the
following paragraph.

(3) The omission of local variables from the lists of things in those
paragraphs that can be annotated (those are the only category whose
annotation is not stored at runtime).

----------

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

From report at bugs.python.org  Tue May 15 21:10:23 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 16 May 2018 01:10:23 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1526433023.73.0.682650639539.issue32769@psf.upfronthosting.co.za>


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

I'm sorry, because of your comment, I believe you haven't read the last update on the PR. Could you take a look at it?

https://github.com/python/cpython/pull/6829

----------

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

From report at bugs.python.org  Tue May 15 21:54:36 2018
From: report at bugs.python.org (Eryk Sun)
Date: Wed, 16 May 2018 01:54:36 +0000
Subject: [docs] [issue19124] os.execv executes in background on Windows
In-Reply-To: <1380451602.11.0.517013085188.issue19124@psf.upfronthosting.co.za>
Message-ID: <1526435676.5.0.682650639539.issue19124@psf.upfronthosting.co.za>


Eryk Sun <eryksun at gmail.com> added the comment:

The exec functions provided by the Windows C runtime really are practically useless, due to creating an orphaned process, disrupting synchronous operation, and returning the wrong status code. It might be more useful for Python 3.7.x to implement an internal win32_execv[e] function that calls _wspawnv[e] with _P_NOWAIT mode. Assign the child process to a silent-breakaway, kill-on-close Job. Wait for it to end, and exit with the child's status code.

----------
nosy: +eryksun
versions: +Python 3.7, Python 3.8 -Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Tue May 15 21:55:52 2018
From: report at bugs.python.org (Eryk Sun)
Date: Wed, 16 May 2018 01:55:52 +0000
Subject: [docs] [issue19124] os.execv executes in background on Windows
In-Reply-To: <1380451602.11.0.517013085188.issue19124@psf.upfronthosting.co.za>
Message-ID: <1526435752.06.0.262363346258.issue19124@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May 16 03:53:58 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 16 May 2018 07:53:58 +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: <1526457238.03.0.682650639539.issue32392@psf.upfronthosting.co.za>


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

I agree with Xavier's comment, but I've bitten by this before so I think it would be better if we add more common arguments to the subprocess.run() signature.

Adding **kwargs wouldn't be entirely correct since subprocess.run() doesn't pass all its arguments to subprocess.Popen().

Let's add 'env=None' to the signature of subprocess.run():

.. function:: run(args, *, stdin=None, input=None, stdout=None, stderr=None,\
                  shell=False, cwd=None, timeout=None, check=False, \
                  encoding=None, errors=None, text=None)

https://github.com/python/cpython/blob/3055c947f98a078bd10d6a8cc352048a1b771d60/Doc/library/subprocess.rst#using-the-modsubprocess-module

----------
keywords: +easy
nosy: +berker.peksag
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.6, Python 3.8

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

From report at bugs.python.org  Wed May 16 04:20:53 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 16 May 2018 08:20:53 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526458853.1.0.682650639539.issue32216@psf.upfronthosting.co.za>


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


New changeset 98d50cb8f57eb227c373cb94b8680b12ec8aade5 by Eric V. Smith in branch 'master':
bpo-32216: Add documentation for dataclasses (GH-6886)
https://github.com/python/cpython/commit/98d50cb8f57eb227c373cb94b8680b12ec8aade5


----------

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

From report at bugs.python.org  Wed May 16 04:22:09 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 May 2018 08:22:09 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526458929.38.0.262363346258.issue32216@psf.upfronthosting.co.za>


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


----------
pull_requests: +6566

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

From report at bugs.python.org  Wed May 16 05:17:05 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 May 2018 09:17:05 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526462225.49.0.682650639539.issue32216@psf.upfronthosting.co.za>


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


New changeset 04e96da5e4982afeb639d6a4d232c6c221fe3a9d by Miss Islington (bot) in branch '3.7':
bpo-32216: Add documentation for dataclasses (GH-6886)
https://github.com/python/cpython/commit/04e96da5e4982afeb639d6a4d232c6c221fe3a9d


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

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

From report at bugs.python.org  Wed May 16 05:21:42 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 16 May 2018 09:21:42 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526462502.65.0.682650639539.issue32216@psf.upfronthosting.co.za>


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

I've added some initial documentation. Most of it is text from the PEP, cleaned up and sphinx-ized. It no doubt needs a lot of work, but I think it's good enough to close this issue and remove the release blocker. Changes to the documentation can be done going forward, including after 3.7.0rc1 is released.

----------
assignee: docs at python -> eric.smith
priority: release blocker -> 
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed May 16 07:31:59 2018
From: report at bugs.python.org (Hamish MacDonald)
Date: Wed, 16 May 2018 11:31:59 +0000
Subject: [docs] [issue13474] Mention of "-m" Flag Missing From Doc on
 Execution Model
In-Reply-To: <1322165458.97.0.989343856998.issue13474@psf.upfronthosting.co.za>
Message-ID: <1526470319.66.0.262363346258.issue13474@psf.upfronthosting.co.za>


Change by Hamish MacDonald <elusivenode at gmail.com>:


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

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

From report at bugs.python.org  Wed May 16 07:59:08 2018
From: report at bugs.python.org (Hamish MacDonald)
Date: Wed, 16 May 2018 11:59:08 +0000
Subject: [docs] [issue13474] Mention of "-m" Flag Missing From Doc on
 Execution Model
In-Reply-To: <1322165458.97.0.989343856998.issue13474@psf.upfronthosting.co.za>
Message-ID: <1526471948.41.0.262363346258.issue13474@psf.upfronthosting.co.za>


Change by Hamish MacDonald <elusivenode at gmail.com>:


----------
pull_requests: +6571

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

From report at bugs.python.org  Wed May 16 11:02:54 2018
From: report at bugs.python.org (Ned Deily)
Date: Wed, 16 May 2018 15:02:54 +0000
Subject: [docs] [issue33503] use pypi.org instead of pypi.python.org
In-Reply-To: <1526410718.37.0.682650639539.issue33503@psf.upfronthosting.co.za>
Message-ID: <1526482974.12.0.682650639539.issue33503@psf.upfronthosting.co.za>


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

Thanks, St?phane!

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

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

From report at bugs.python.org  Wed May 16 11:34:49 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 16 May 2018 15:34:49 +0000
Subject: [docs] [issue24318] Better documentaiton of profile-opt (and
 release builds in general?)
In-Reply-To: <1432830865.51.0.995414707141.issue24318@psf.upfronthosting.co.za>
Message-ID: <1526484889.47.0.682650639539.issue24318@psf.upfronthosting.co.za>


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


New changeset 93f9a8a5afb58b1d2e4f27bb46d3d4e0fa8c08f0 by Gregory P. Smith in branch 'master':
bpo-24318: Rewrite the README PGO section. (#6863)
https://github.com/python/cpython/commit/93f9a8a5afb58b1d2e4f27bb46d3d4e0fa8c08f0


----------

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

From report at bugs.python.org  Wed May 16 11:35:57 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 May 2018 15:35:57 +0000
Subject: [docs] [issue24318] Better documentaiton of profile-opt (and
 release builds in general?)
In-Reply-To: <1432830865.51.0.995414707141.issue24318@psf.upfronthosting.co.za>
Message-ID: <1526484957.3.0.262363346258.issue24318@psf.upfronthosting.co.za>


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


----------
pull_requests: +6577

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

From report at bugs.python.org  Wed May 16 11:38:17 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 16 May 2018 15:38:17 +0000
Subject: [docs] [issue24318] Better documentaiton of profile-opt (and
 release builds in general?)
In-Reply-To: <1432830865.51.0.995414707141.issue24318@psf.upfronthosting.co.za>
Message-ID: <1526485097.96.0.262363346258.issue24318@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May 16 12:35:00 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 May 2018 16:35:00 +0000
Subject: [docs] [issue24318] Better documentaiton of profile-opt (and
 release builds in general?)
In-Reply-To: <1432830865.51.0.995414707141.issue24318@psf.upfronthosting.co.za>
Message-ID: <1526488500.17.0.682650639539.issue24318@psf.upfronthosting.co.za>


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


New changeset 447fdd178f1007294db38bf0392a0cf74a49d460 by Miss Islington (bot) in branch '3.7':
bpo-24318: Rewrite the README PGO section. (GH-6863)
https://github.com/python/cpython/commit/447fdd178f1007294db38bf0392a0cf74a49d460


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

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

From report at bugs.python.org  Wed May 16 12:42:41 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 16:42:41 +0000
Subject: [docs] [issue33543] `make html` broken
Message-ID: <1526488961.65.0.682650639539.issue33543@psf.upfronthosting.co.za>


New submission from Barry A. Warsaw <barry at python.org>:

Building the documentation in the master (3.8) branch is currently broken:

% make html
make html
mkdir -p build
Building NEWS from Misc/NEWS.d with blurb
PATH=./venv/bin:$PATH sphinx-build -b html -d build/doctrees -D latex_elements.papersize=  . build/html 
Running Sphinx v1.7.4
loading pickled environment... not yet created

Theme error:
no theme named 'python_docs_theme' found (missing theme.conf?)
make: *** [build] Error 2

----------
assignee: docs at python
components: Documentation
messages: 316838
nosy: barry, docs at python
priority: normal
severity: normal
status: open
title: `make html` broken
versions: Python 3.8

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

From report at bugs.python.org  Wed May 16 12:44:27 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 16:44:27 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526489067.05.0.682650639539.issue32216@psf.upfronthosting.co.za>


Barry A. Warsaw <barry at python.org> added the comment:

I've got a branch that cleans up and updates the dataclasses documentation, so I'm reopening this issue and piggybacking my PR on it.

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

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

From report at bugs.python.org  Wed May 16 12:44:54 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 16:44:54 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526489094.69.0.682650639539.issue32216@psf.upfronthosting.co.za>


Barry A. Warsaw <barry at python.org> added the comment:

...although I unfortunately cannot build it because of Issue33543

----------

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

From report at bugs.python.org  Wed May 16 12:45:48 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 16:45:48 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526489148.38.0.262363346258.issue32216@psf.upfronthosting.co.za>


Change by Barry A. Warsaw <barry at python.org>:


----------
pull_requests: +6581
stage: resolved -> patch review

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

From report at bugs.python.org  Wed May 16 12:56:16 2018
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 16 May 2018 16:56:16 +0000
Subject: [docs] [issue33543] `make html` broken
In-Reply-To: <1526488961.65.0.682650639539.issue33543@psf.upfronthosting.co.za>
Message-ID: <1526489776.29.0.682650639539.issue33543@psf.upfronthosting.co.za>


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

Try `make venv && make html`.

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

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

From report at bugs.python.org  Wed May 16 13:32:45 2018
From: report at bugs.python.org (merelymoray)
Date: Wed, 16 May 2018 17:32:45 +0000
Subject: [docs] [issue33545] Docs for uuid don't mention that uuid1 can
 repeat in some circumstances
Message-ID: <1526491965.86.0.682650639539.issue33545@psf.upfronthosting.co.za>


New submission from merelymoray <arcadesrofocale at yahoo.co.uk>:

https://docs.python.org/3.6/library/uuid.html#uuid.UUID

uuid.uuid1(node=None, clock_seq=None)

Generate a UUID from a host ID, sequence number, and the current time. If node is not given, getnode() is used to obtain the hardware address. If clock_seq is given, it is used as the sequence number; otherwise a random 14-bit sequence number is chosen.


^^

This neglects to mention that if you call uuid1() in quick succession with no parameters, you can get a repeat uuid.

I had a bug because of this.

It would have been nice if the docs mentioned the fact directly. 

It's only a sentence to add, and would have saved a lot of time.

----------
assignee: docs at python
components: Documentation
messages: 316844
nosy: docs at python, merelymoray
priority: normal
severity: normal
status: open
title: Docs for uuid don't mention that uuid1 can repeat in some circumstances
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Wed May 16 13:34:05 2018
From: report at bugs.python.org (Ned Deily)
Date: Wed, 16 May 2018 17:34:05 +0000
Subject: [docs] [issue33543] `make html` broken
In-Reply-To: <1526488961.65.0.682650639539.issue33543@psf.upfronthosting.co.za>
Message-ID: <1526492045.1.0.682650639539.issue33543@psf.upfronthosting.co.za>


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

Or just "make venv html".

If you already have sphinx installed somewhere, you can just:

pip install python-docs-theme

----------
nosy: +ned.deily
resolution:  -> works for me
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed May 16 14:12:10 2018
From: report at bugs.python.org (Eric Snow)
Date: Wed, 16 May 2018 18:12:10 +0000
Subject: [docs] [issue14597] Cannot unload dll in ctypes until script exits
In-Reply-To: <1334581773.77.0.209505875468.issue14597@psf.upfronthosting.co.za>
Message-ID: <1526494330.52.0.262363346258.issue14597@psf.upfronthosting.co.za>


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


----------
nosy: +eric.snow

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

From report at bugs.python.org  Wed May 16 14:36:58 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 18:36:58 +0000
Subject: [docs] [issue33543] `make html` broken
In-Reply-To: <1526492045.1.0.682650639539.issue33543@psf.upfronthosting.co.za>
Message-ID: <BD9DCAB3-1D36-4026-A21F-DE5B87712761@python.org>


Barry A. Warsaw <barry at python.org> added the comment:

On May 16, 2018, at 13:34, Ned Deily <report at bugs.python.org> wrote:
> 
> Or just "make venv html".

Shouldn?t the html target depend on venv then?

----------

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

From report at bugs.python.org  Wed May 16 15:50:09 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 19:50:09 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526500209.75.0.682650639539.issue32216@psf.upfronthosting.co.za>


Barry A. Warsaw <barry at python.org> added the comment:


New changeset 713a9367366c88662c39ed20dd6bce22399299f1 by Barry Warsaw in branch 'master':
bpo-32216: Update dataclasses documentation (#6913)
https://github.com/python/cpython/commit/713a9367366c88662c39ed20dd6bce22399299f1


----------

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

From report at bugs.python.org  Wed May 16 15:51:17 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 May 2018 19:51:17 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526500277.29.0.262363346258.issue32216@psf.upfronthosting.co.za>


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


----------
pull_requests: +6586

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

From report at bugs.python.org  Wed May 16 15:52:10 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 19:52:10 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526500330.34.0.262363346258.issue32216@psf.upfronthosting.co.za>


Change by Barry A. Warsaw <barry at python.org>:


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

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

From report at bugs.python.org  Wed May 16 16:37:17 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 16 May 2018 20:37:17 +0000
Subject: [docs] [issue32216] Document PEP 557 Data Classes (dataclasses
 module)
In-Reply-To: <1512439511.23.0.213398074469.issue32216@psf.upfronthosting.co.za>
Message-ID: <1526503037.12.0.682650639539.issue32216@psf.upfronthosting.co.za>


Barry A. Warsaw <barry at python.org> added the comment:


New changeset 0c62e09774e445a185fd192524454ce697ca123b by Barry Warsaw (Miss Islington (bot)) in branch '3.7':
bpo-32216: Update dataclasses documentation (GH-6913) (#6918)
https://github.com/python/cpython/commit/0c62e09774e445a185fd192524454ce697ca123b


----------

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

From report at bugs.python.org  Wed May 16 16:46:34 2018
From: report at bugs.python.org (Ned Deily)
Date: Wed, 16 May 2018 20:46:34 +0000
Subject: [docs] [issue33543] `make html` broken
In-Reply-To: <1526488961.65.0.682650639539.issue33543@psf.upfronthosting.co.za>
Message-ID: <1526503594.52.0.682650639539.issue33543@psf.upfronthosting.co.za>


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

> Shouldn?t the html target depend on venv then?

Back when we added support for blurb, I tried to make it such that "make html" could easily use already installed versions of sphinx-build and blurb and not require a venv.  I had a particular use case for that.  But if someone wants to modify the Docs Makefile to require using the venv recipe, I wouldn't object too strongly.  Another approach, I guess, would be to check that the python-docs-theme is available to sphinx-build and give a better message: not sure how best to do that in the current Makefile.

----------

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

From report at bugs.python.org  Wed May 16 17:09:04 2018
From: report at bugs.python.org (Xavier de Gaye)
Date: Wed, 16 May 2018 21:09: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: <1526504944.34.0.682650639539.issue32392@psf.upfronthosting.co.za>


Xavier de Gaye <xdegaye at gmail.com> added the comment:

> Let's add 'env=None' to the signature of subprocess.run():

+1

----------

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

From report at bugs.python.org  Wed May 16 19:55:52 2018
From: report at bugs.python.org (Alfred Perlstein)
Date: Wed, 16 May 2018 23:55:52 +0000
Subject: [docs] [issue33550] Sigpipe handling issue should be documented
Message-ID: <1526514952.03.0.682650639539.issue33550@psf.upfronthosting.co.za>


New submission from Alfred Perlstein <alfred at freebsd.org>:

A common anti-pattern in python used to get rid of "ugly" brokenpipe messages is to set the SIGPIPE handler to SIG_DFL, this however will cause your program to seemingly randomly exit if it makes any socket connections during its lifetime.  (see github PR for more info)

----------
assignee: docs at python
components: Documentation
messages: 316877
nosy: docs at python, splbio
priority: normal
pull_requests: 6597
severity: normal
status: open
title: Sigpipe handling issue should be documented
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu May 17 03:15:18 2018
From: report at bugs.python.org (Derek Kim)
Date: Thu, 17 May 2018 07:15:18 +0000
Subject: [docs] [issue33553] possible documentation improvement proposal for
 multiprocessing
Message-ID: <1526541318.79.0.682650639539.issue33553@psf.upfronthosting.co.za>


New submission from Derek Kim <bluewhale8202 at gmail.com>:

>>> from multiprocessing import Pool
>>> p = Pool(5)
>>> def f(x):
...     return x*x
...
>>> p.map(f, [1,2,3])

This example in the document is confusing because this is already wrong code when run with fork method even if you run it as a script. With fork start method, f should be defined before p is created.

Also, just advising that one shouldn't use interactive shell and should run multiprocessing code in if __name__ == '__main__' is not informative becuase those conditions are generally no problem with fork method.

Can I try improving the documentation?

----------
assignee: docs at python
components: Documentation
messages: 316892
nosy: Derek Kim, docs at python
priority: normal
severity: normal
status: open
title: possible documentation improvement proposal for multiprocessing
versions: Python 3.8

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

From report at bugs.python.org  Thu May 17 03:16:56 2018
From: report at bugs.python.org (Derek Kim)
Date: Thu, 17 May 2018 07:16:56 +0000
Subject: [docs] [issue33553] Documentation improvement proposal for
 multiprocessing
In-Reply-To: <1526541318.79.0.682650639539.issue33553@psf.upfronthosting.co.za>
Message-ID: <1526541416.57.0.262363346258.issue33553@psf.upfronthosting.co.za>


Change by Derek Kim <bluewhale8202 at gmail.com>:


----------
title: possible documentation improvement proposal for multiprocessing -> Documentation improvement proposal for multiprocessing

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

From report at bugs.python.org  Thu May 17 03:17:49 2018
From: report at bugs.python.org (Derek Kim)
Date: Thu, 17 May 2018 07:17:49 +0000
Subject: [docs] [issue33553] Documentation improvement proposal for
 multiprocessing
In-Reply-To: <1526541318.79.0.682650639539.issue33553@psf.upfronthosting.co.za>
Message-ID: <1526541469.83.0.682650639539.issue33553@psf.upfronthosting.co.za>


Derek Kim <bluewhale8202 at gmail.com> added the comment:

https://docs.python.org/3.8/library/multiprocessing.html#multiprocessing-programming

here is the link to the document.

----------

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

From report at bugs.python.org  Thu May 17 03:52:00 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 17 May 2018 07:52:00 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526543520.6.0.682650639539.issue33518@psf.upfronthosting.co.za>


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


New changeset d5f144260886959c1fe06bc4506a23fd10f92348 by Victor Stinner (Andr?s Delfino) in branch 'master':
bpo-33518: Add PEP entry to documentation glossary (GH-6860)
https://github.com/python/cpython/commit/d5f144260886959c1fe06bc4506a23fd10f92348


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

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

From report at bugs.python.org  Thu May 17 07:41:49 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 17 May 2018 11:41:49 +0000
Subject: [docs] [issue13474] Mention of "-m" Flag Missing From Doc on
 Execution Model
In-Reply-To: <1322165458.97.0.989343856998.issue13474@psf.upfronthosting.co.za>
Message-ID: <1526557309.11.0.682650639539.issue13474@psf.upfronthosting.co.za>


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

I've assigned the PR and issue to myself, as the proposed addition in the PR isn't quite right, but it isn't immediately obvious why not.

The gist of the problem is that the current docs are actually correct and complete: modules are the first thing listed as being code blocks, and whether you import them or execute them as __main__ doesn't change that.

However, I can also see why 2011-Eric thought it looked incomplete, so I'm thinking it may make sense to restructure that entire paragraph as a bulleted list, where it would be possible to mention both imported modules and modules executed as main, without giving the impression that those are inherently different things.

----------
assignee: docs at python -> ncoghlan

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

From report at bugs.python.org  Thu May 17 08:03:47 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 17 May 2018 12:03:47 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526558627.86.0.262363346258.issue33518@psf.upfronthosting.co.za>


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


----------
pull_requests: +6604

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

From report at bugs.python.org  Thu May 17 08:04:46 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 17 May 2018 12:04:46 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526558686.63.0.262363346258.issue33518@psf.upfronthosting.co.za>


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


----------
pull_requests: +6605

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

From nkemp1165 at gmail.com  Wed May 16 09:37:09 2018
From: nkemp1165 at gmail.com (Nick Kemp)
Date: Wed, 16 May 2018 08:37:09 -0500
Subject: [docs] Python Install location bug (Maybe?)
Message-ID: <17b609dc-a18c-1589-e699-ada905cbbc41@gmail.com>

The documentation 
(https://docs.python.org/3.6/tutorial/interpreter.html) states: "Python 
installation is usually placed in|C:\Python36"|

On my install on a Widows 10 machine, I think it is installed in: 
"C:\Users\/MyUserName/\AppData\Local\Programs\Python\Python36\python.exe"

This may or may not be a problem but it does cause concern for novices 
like me.

----------------------------
The problem I'm having is that I want to begin using Python to recreate 
a rather extensive program I created using Excel. Python being new there 
is lots to learn and this should be fun .... but I'm spending way too 
much time learning about setting up Python, setting up an IDE and 
setting up a GUI designer feature.

So you could say I'm chasing rats down rat holes and not making any 
progress against the fundamental problem of setting up a development 
tool and getting into Python.? And the discrepancy listed above appears 
to me to be another rat hole to chase.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180516/ca55774f/attachment.html>

From report at bugs.python.org  Thu May 17 08:35:41 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 17 May 2018 12:35:41 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526560541.66.0.262363346258.issue33518@psf.upfronthosting.co.za>


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


----------
pull_requests: +6606

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

From report at bugs.python.org  Thu May 17 11:08:48 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 17 May 2018 15:08:48 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526569728.18.0.682650639539.issue19950@psf.upfronthosting.co.za>


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


New changeset dff46758f267ad6c13096c69c4e1dee17f9969aa by Gregory P. Smith in branch 'master':
bpo-19950: Clarify unittest TestCase instance use. (GH-6875)
https://github.com/python/cpython/commit/dff46758f267ad6c13096c69c4e1dee17f9969aa


----------
nosy: +gregory.p.smith

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

From report at bugs.python.org  Thu May 17 11:08:57 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 May 2018 15:08:57 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526569737.12.0.262363346258.issue19950@psf.upfronthosting.co.za>


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


----------
pull_requests: +6608

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

From report at bugs.python.org  Thu May 17 11:09:55 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 May 2018 15:09:55 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526569795.59.0.262363346258.issue19950@psf.upfronthosting.co.za>


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


----------
pull_requests: +6609

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

From report at bugs.python.org  Thu May 17 12:04:58 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 17 May 2018 16:04:58 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
Message-ID: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>


New submission from Miro Hron?ok <miro at hroncok.cz>:

Python 3.6.5 ...
>>> Exception('foo',)
Exception('foo',)

Python 3.7.0b4 ...
>>> Exception('foo',)
Exception('foo')

This is a change that might bit people who rely on doctesting.

It is not documented at https://docs.python.org/3.7/whatsnew/3.7.html

I'll send a PR.

----------
assignee: docs at python
components: Documentation
messages: 316953
nosy: Elvis.Pranskevichus, docs at python, hroncok, ned.deily, yselivanov
priority: normal
severity: normal
status: open
title: Exception's repr change not documented
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu May 17 12:05:11 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 17 May 2018 16:05:11 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526573111.37.0.262363346258.issue33559@psf.upfronthosting.co.za>


Change by Miro Hron?ok <miro at hroncok.cz>:


----------
type:  -> behavior

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

From report at bugs.python.org  Thu May 17 12:22:29 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 17 May 2018 16:22:29 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526574149.35.0.262363346258.issue33559@psf.upfronthosting.co.za>


Change by Miro Hron?ok <miro at hroncok.cz>:


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

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

From report at bugs.python.org  Thu May 17 13:44:55 2018
From: report at bugs.python.org (Steve Dower)
Date: Thu, 17 May 2018 17:44:55 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526579095.53.0.682650639539.issue33559@psf.upfronthosting.co.za>


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


New changeset 631753fcc5e88bbbad402933e77295675cfe1fee by Steve Dower (Miro Hron?ok) in branch 'master':
bpo-33559: Document changed repr of exceptions (GH-6943)
https://github.com/python/cpython/commit/631753fcc5e88bbbad402933e77295675cfe1fee


----------
nosy: +steve.dower

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

From report at bugs.python.org  Thu May 17 13:46:10 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 May 2018 17:46:10 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526579170.84.0.262363346258.issue33559@psf.upfronthosting.co.za>


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


----------
pull_requests: +6613

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

From report at bugs.python.org  Thu May 17 14:05:22 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 17 May 2018 18:05:22 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526580322.03.0.682650639539.issue33559@psf.upfronthosting.co.za>


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

This was done in issue30399, and I was not sure that this change is worth adding in What's New. Add a reference to the issue.

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

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

From report at bugs.python.org  Thu May 17 14:17:49 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 17 May 2018 18:17:49 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526581069.6.0.262363346258.issue33559@psf.upfronthosting.co.za>


Change by Miro Hron?ok <miro at hroncok.cz>:


----------
pull_requests: +6614

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

From report at bugs.python.org  Thu May 17 14:35:03 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 17 May 2018 18:35:03 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526582103.16.0.682650639539.issue33559@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

I was bit by this, so that's why I think this is worth documenting. https://github.com/testing-cabal/testtools/issues/270

----------

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

From report at bugs.python.org  Thu May 17 14:41:15 2018
From: report at bugs.python.org (Steve Dower)
Date: Thu, 17 May 2018 18:41:15 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526582475.83.0.682650639539.issue33559@psf.upfronthosting.co.za>


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


New changeset 54fc49737a6a79f6e2ece16e22b233858b836567 by Steve Dower (Miss Islington (bot)) in branch '3.7':
bpo-33559: Document changed repr of exceptions (GH-6943) (GH-6950)
https://github.com/python/cpython/commit/54fc49737a6a79f6e2ece16e22b233858b836567


----------

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

From report at bugs.python.org  Thu May 17 14:41:18 2018
From: report at bugs.python.org (Steve Dower)
Date: Thu, 17 May 2018 18:41:18 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526582478.89.0.682650639539.issue33559@psf.upfronthosting.co.za>


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

It's worth documenting. I'll merge the next PR with the attribution.

----------

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

From report at bugs.python.org  Thu May 17 15:05:10 2018
From: report at bugs.python.org (Steve Dower)
Date: Thu, 17 May 2018 19:05:10 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526583910.43.0.682650639539.issue33559@psf.upfronthosting.co.za>


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


New changeset fb9dd8915314d857161de89fcbbb041f2b49fc22 by Steve Dower (Miro Hron?ok) in branch 'master':
bpo-33559: Attribute changed repr of exceptions (GH-6954)
https://github.com/python/cpython/commit/fb9dd8915314d857161de89fcbbb041f2b49fc22


----------

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

From report at bugs.python.org  Thu May 17 15:06:12 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 May 2018 19:06:12 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526583972.86.0.262363346258.issue33559@psf.upfronthosting.co.za>


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


----------
pull_requests: +6615

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

From report at bugs.python.org  Thu May 17 16:10:07 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 May 2018 20:10:07 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526587807.13.0.682650639539.issue33559@psf.upfronthosting.co.za>


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


New changeset efa642779739b5af028b0f6ebb9033395e124273 by Miss Islington (bot) in branch '3.7':
bpo-33559: Attribute changed repr of exceptions (GH-6954)
https://github.com/python/cpython/commit/efa642779739b5af028b0f6ebb9033395e124273


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

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

From report at bugs.python.org  Thu May 17 16:49:23 2018
From: report at bugs.python.org (Thomas Kluyver)
Date: Thu, 17 May 2018 20:49:23 +0000
Subject: [docs] [issue28418] Raise Deprecation warning for
 tokenize.generate_tokens
In-Reply-To: <1476212697.92.0.408666384378.issue28418@psf.upfronthosting.co.za>
Message-ID: <1526590163.05.0.682650639539.issue28418@psf.upfronthosting.co.za>


Thomas Kluyver <thomas at kluyver.me.uk> added the comment:

I've opened a PR moving in the other direction (making this public rather than deprecating it):

https://github.com/python/cpython/pull/6957

----------
nosy: +takluyver

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

From report at bugs.python.org  Thu May 17 18:21:42 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Thu, 17 May 2018 22:21:42 +0000
Subject: [docs] [issue33459] Fix "tuple display" mention in Expressions
In-Reply-To: <1525994212.08.0.682650639539.issue33459@psf.upfronthosting.co.za>
Message-ID: <1526595702.77.0.682650639539.issue33459@psf.upfronthosting.co.za>


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

I'm restoring the original title since we are not sure it was incorrect after all.

I have also updated the PR to remove the tuple display entry from the index.

----------
title: Define "tuple display" in the docs -> Fix "tuple display" mention in Expressions
versions: +Python 2.7, Python 3.6, Python 3.7

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

From report at bugs.python.org  Thu May 17 21:23:00 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 18 May 2018 01:23:00 +0000
Subject: [docs] [issue28418] Raise Deprecation warning for
 tokenize.generate_tokens
In-Reply-To: <1476212697.92.0.408666384378.issue28418@psf.upfronthosting.co.za>
Message-ID: <1526606580.63.0.682650639539.issue28418@psf.upfronthosting.co.za>


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

Thanks Thomas.  I've been a long term user of tokenize.generate_tokens() and would be sad to see it go.  

The underlying _tokenize() functionality is used else within the module, so there the no benefit to removing the API.

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

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

From report at bugs.python.org  Fri May 18 04:07:01 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 May 2018 08:07:01 +0000
Subject: [docs] [issue33559] Exception's repr change not documented
In-Reply-To: <1526573098.08.0.682650639539.issue33559@psf.upfronthosting.co.za>
Message-ID: <1526630821.85.0.682650639539.issue33559@psf.upfronthosting.co.za>


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

Thank you for your report and PR Miro!

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

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

From ChunHsia_Tang at mazak.co.jp  Fri May 18 05:13:46 2018
From: ChunHsia_Tang at mazak.co.jp (ChunHsia_Tang at mazak.co.jp)
Date: Fri, 18 May 2018 17:13:46 +0800
Subject: [docs] bug
Message-ID: <OF601775BC.105F9E09-ON48258291.003239BC-48258291.0032D3C5@MazakInternetDomain>

Hi,



https://docs.python.org/3/tutorial/modules.html#more-on-modules



Isn't no 0?


With regards,
Tang

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180518/b9ff64ec/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 55674 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180518/b9ff64ec/attachment-0001.gif>

From report at bugs.python.org  Fri May 18 09:49:39 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 18 May 2018 13:49:39 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
Message-ID: <1526651379.0.0.262363346258.issue33571@psf.upfronthosting.co.za>


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


----------
assignee: docs at python
components: Documentation
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Add triple quotes to list of delimiters that trigger '...' prompt
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/issue33571>
_______________________________________

From report at bugs.python.org  Fri May 18 09:50:23 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 18 May 2018 13:50:23 +0000
Subject: [docs] [issue33571] Add triple quotes to list of delimiters that
 trigger '...' prompt
Message-ID: <1526651423.86.0.262363346258.issue33571@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri May 18 12:37:58 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 18 May 2018 16:37:58 +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: <1526661478.72.0.682650639539.issue33477@psf.upfronthosting.co.za>


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

Any comments?
Would you close this issue?

----------

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

From report at bugs.python.org  Fri May 18 13:02:04 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Fri, 18 May 2018 17:02:04 +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: <1526662924.85.0.682650639539.issue33477@psf.upfronthosting.co.za>


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

Fair enough that what's new include things about Module


> The first statement in their body is not considered as a docstring anymore.

Note that this sentence read backward to me. I understand what is meant because I know the new behavior. It might be good to clarify. potentially:

> The first statement in the `body` attribute of should not be considered the docstring of the module anymore, the `docstring` attribute  is reserved for that.


Though the documentation of `compile()` does not say that `compile(...,'exec')` compile a module. It says:

> The mode argument specifies what kind of code must be compiled;
> it can be 'exec' if source consists of a sequence of statements

Which now is incorrect. I was expecting `compile(..., 'exec')` to return a Module with `None` or empty string as the docstring attribute ? which is also a perfectly reasonable request.

I think that `compile`  documentation should be changed to reflect what it does. 


Or (but I see why this is un-reasonable) split add the `mode='module'` that has new behavior, while `exec` does not.

----------

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

From report at bugs.python.org  Fri May 18 13:36:41 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 May 2018 17:36:41 +0000
Subject: [docs] [issue33492] Updating the Evaluation order section to cover
 *expression in calls
In-Reply-To: <1526285664.99.0.682650639539.issue33492@psf.upfronthosting.co.za>
Message-ID: <1526665001.89.0.262363346258.issue33492@psf.upfronthosting.co.za>


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


----------
versions:  -Python 3.5

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

From report at bugs.python.org  Fri May 18 13:41:17 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Fri, 18 May 2018 17:41:17 +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: <1526665277.66.0.262363346258.issue33477@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri May 18 15:21:44 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 May 2018 19:21:44 +0000
Subject: [docs] [issue33572] False/True as dictionary keys treated as
 integers
In-Reply-To: <1526656790.96.0.682650639539.issue33572@psf.upfronthosting.co.za>
Message-ID: <1526671304.11.0.262363346258.issue33572@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri May 18 15:44:10 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 May 2018 19:44:10 +0000
Subject: [docs] [issue33572] Better document mixed-type comparison of set
 items, dict keys
In-Reply-To: <1526656790.96.0.682650639539.issue33572@psf.upfronthosting.co.za>
Message-ID: <1526672650.81.0.682650639539.issue33572@psf.upfronthosting.co.za>


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

With Tim's addition

>>> from fractions import Fraction as F
>>> from decimal import Decimal as D
>>> s = {0, 1, 0.0, 1.0, F(0,1), F(1, 1), D(0), D(1), False, True}
>>> s
{0, 1}

I think we should consider moving the main discussion of the general comparison and hashing principle and example to the set entry.  (Sets ars simpler and are when people new to Python already know about.) Point out that for displays, the first of equals is kept and not replaced (this is also true of dicts).  Then, in the dict entry, say that dict keys are treated like set items, give an equivalent dict example, and link to the discussion of set items.

>>> x = None
>>> d = {0:x, 1:x, 0.0:x, 1.0:x, F(0,1):x, F(1, 1):x, D(0):x, D(1):x, False:x, True:x}
>>> d
{0: None, 1: None}
>>>

----------
title: False/True as dictionary keys treated as integers -> Better document mixed-type comparison of set items, dict keys

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

From report at bugs.python.org  Fri May 18 18:40:28 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Fri, 18 May 2018 22:40:28 +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: <1526683228.43.0.262363346258.issue32996@psf.upfronthosting.co.za>


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


----------
pull_requests: +6633

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

From report at bugs.python.org  Fri May 18 19:44:25 2018
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 May 2018 23:44:25 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526687065.47.0.682650639539.issue33518@psf.upfronthosting.co.za>


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


New changeset a3a554a536599189166843cd80e62d02b2b68aa8 by Victor Stinner (Andr?s Delfino) in branch '3.7':
[3.7] bpo-33518: Add PEP entry to documentation glossary (GH-6860) (#6934)
https://github.com/python/cpython/commit/a3a554a536599189166843cd80e62d02b2b68aa8


----------

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

From report at bugs.python.org  Fri May 18 19:44:26 2018
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 May 2018 23:44:26 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526687066.13.0.682650639539.issue33518@psf.upfronthosting.co.za>


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


New changeset fb5d0aa116125dfb29a3c4d8819a38dfb2760bb9 by Victor Stinner (Andr?s Delfino) in branch '3.6':
[3.6] bpo-33518: Add PEP entry to documentation glossary (GH-6860) (#6935)
https://github.com/python/cpython/commit/fb5d0aa116125dfb29a3c4d8819a38dfb2760bb9


----------

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

From report at bugs.python.org  Fri May 18 20:25:40 2018
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 19 May 2018 00:25:40 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526689540.13.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

> Sorry for mixing two things here, but I meant that I found out about this because of the private API use in gdb, however nothing from the change is documented on whatsnew at all.

It seems like there is at least one change in the public API: the removal of the PyInterpreterState.modules field. Are the members of the PyInterpreterState structure part of the public API?

@Eric: do you consider that it should be documented?

----------

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

From report at bugs.python.org  Fri May 18 20:55:08 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 19 May 2018 00:55:08 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526691308.72.0.682650639539.issue19950@psf.upfronthosting.co.za>


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


New changeset a5f33a899f6450de96f5e4cd154de4486d50bdd7 by Gregory P. Smith (Miss Islington (bot)) in branch '3.6':
bpo-19950: Clarify unittest TestCase instance use. (GH-6875) (GH-6939)
https://github.com/python/cpython/commit/a5f33a899f6450de96f5e4cd154de4486d50bdd7


----------

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

From report at bugs.python.org  Fri May 18 20:55:47 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 19 May 2018 00:55:47 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526691347.58.0.682650639539.issue19950@psf.upfronthosting.co.za>


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


New changeset 436972e295f5057fe7cdd7312f543c2fa884705d by Gregory P. Smith (Miss Islington (bot)) in branch '3.7':
bpo-19950: Clarify unittest TestCase instance use. (GH-6875) (GH-6938)
https://github.com/python/cpython/commit/436972e295f5057fe7cdd7312f543c2fa884705d


----------

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

From report at bugs.python.org  Fri May 18 20:57:20 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 19 May 2018 00:57:20 +0000
Subject: [docs] [issue19950] Document that unittest.TestCase.__init__ is
 called once per test
In-Reply-To: <1386714858.72.0.878231586551.issue19950@psf.upfronthosting.co.za>
Message-ID: <1526691440.26.0.262363346258.issue19950@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May 19 04:27:52 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 May 2018 08:27:52 +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: <1526718472.68.0.682650639539.issue32996@psf.upfronthosting.co.za>


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

Sorry, I appreciate your work, Elvis, but the current version of PR 6978 seems containing too much insignificant details, which are not worth an entry in What's New. They distract attention from important changes. I think this PR should be significantly shortened.

To me, What's New is not a structured copy of Misc/NEWS. It serves two purposes:

1. Advertising new features.

2. Warning about possible breaks or future breaks.

If the change doesn't add a new way of doing something and doesn't break significant part of code, it is not worth mentioning in What's New.

PR 6978 also adds entries for bug fixes, which shouldn't be in this document.

----------

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

From report at bugs.python.org  Sat May 19 07:03:45 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 19 May 2018 11:03:45 +0000
Subject: [docs] [issue33448] Output_Typo_Error
In-Reply-To: <1525885359.71.0.682650639539.issue33448@psf.upfronthosting.co.za>
Message-ID: <1526727825.43.0.262363346258.issue33448@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May 19 07:11:25 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Sat, 19 May 2018 11:11:25 +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: <1526728285.31.0.682650639539.issue32996@psf.upfronthosting.co.za>


Elvis Pranskevichus <elvis at magic.io> added the comment:

Thanks for the feedback Serhiy!  I'll make an editorial pass to address the comments shortly.  In general, I prefer thoroughness in the initial What's New edit to make sure we don't miss something important.

----------

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

From report at bugs.python.org  Sat May 19 11:04:03 2018
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 19 May 2018 15:04:03 +0000
Subject: [docs] [issue33430] Import secrets module in secrets examples
In-Reply-To: <1525510452.55.0.682650639539.issue33430@psf.upfronthosting.co.za>
Message-ID: <1526742243.33.0.682650639539.issue33430@psf.upfronthosting.co.za>


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

Unless I've mucked it up, I just committed your patch on Github so I'm closing this ticket. Thanks.

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

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

From report at bugs.python.org  Sat May 19 15:55:27 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 19 May 2018 19:55:27 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526759727.76.0.262363346258.issue33479@psf.upfronthosting.co.za>


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


----------
keywords: +patch
pull_requests: +6642

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

From report at bugs.python.org  Sat May 19 16:13:09 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 19 May 2018 20:13:09 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
Message-ID: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>


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

While most entries don't show "see also" as a separate block, binary/text file entries do.

I'm proposing to change this.

----------
assignee: docs at python
components: Documentation
messages: 317135
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Make binary/text file glossary entries follow most common "see also" style
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May 19 16:13:38 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 19 May 2018 20:13:38 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526760818.52.0.262363346258.issue33580@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May 19 18:00:07 2018
From: report at bugs.python.org (Antony Lee)
Date: Sat, 19 May 2018 22:00:07 +0000
Subject: [docs] [issue33581] Document "optional components that are commonly
 included in Python distributions."
Message-ID: <1526767207.27.0.682650639539.issue33581@psf.upfronthosting.co.za>


New submission from Antony Lee <anntzer.lee at gmail.com>:

The stdlib docs intro include the following sentences:

    It also describes some of the optional components that are commonly included in Python distributions.

    For Unix-like operating systems Python is normally provided as a collection of packages, so it may be necessary to use the packaging tools provided with the operating system to obtain some or all of the optional components.

However, as far as I can tell, there is no easy way to actually know what parts of the stdlib are "optional".  The _thread module's doc does state "The module is optional.", and the threading module's doc also implies that it is optional ("The dummy_threading module is provided for situations where threading cannot be used because _thread is missing.") (yes, I know support for threadless builds is going away in 3.7; that's irrelevant here.), but even ensurepip's docs don't state that it may be missing (even though I believe(?) that it is indeed removed (and intended to be so) from some linux distribution's Pythons).

A master list of "optional" features would thus be welcome.  Its usefulness is to know what parts of the stdlib we can actually rely on; e.g. in https://github.com/matplotlib/matplotlib/issues/10866 a Matplotlib user noted that bz2 is not present in all Python installs.

----------
assignee: docs at python
components: Documentation
messages: 317140
nosy: Antony.Lee, docs at python
priority: normal
severity: normal
status: open
title: Document "optional components that are commonly included in Python distributions."

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

From report at bugs.python.org  Sat May 19 18:18:20 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sat, 19 May 2018 22:18:20 +0000
Subject: [docs] [issue17972] inspect module docs omits many functions
In-Reply-To: <1368501068.91.0.677640111487.issue17972@psf.upfronthosting.co.za>
Message-ID: <1526768300.63.0.682650639539.issue17972@psf.upfronthosting.co.za>


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

Just came across the same issue.

It think that the exact behavior may depend on  functions. IT is also unclear when to use what sometime. 

For example, `getsource` seem to be preferable to findsource, getsource cannot be use to get the source of wrapping function as it follows `__wrapped__`.

----------
nosy: +mbussonn

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

From report at bugs.python.org  Sat May 19 18:31:14 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sat, 19 May 2018 22:31:14 +0000
Subject: [docs] [issue17972] inspect module docs omits many functions
In-Reply-To: <1368501068.91.0.677640111487.issue17972@psf.upfronthosting.co.za>
Message-ID: <1526769074.8.0.262363346258.issue17972@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May 19 18:55:50 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sat, 19 May 2018 22:55:50 +0000
Subject: [docs] [issue33582] formatargspec deprecated but does nto emit
 DeprecationWarning.
Message-ID: <1526770549.95.0.682650639539.issue33582@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier <bussonniermatthias at gmail.com>:

Documentation says formatargspec is deprecated since 3.5, but no DeprecationWarnings are emitted, the docstring also does not mention this fact.

----------
assignee: docs at python
components: Documentation
messages: 317142
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: formatargspec deprecated but does nto emit DeprecationWarning.
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat May 19 19:00:05 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Sat, 19 May 2018 23:00:05 +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: <1526770805.12.0.262363346258.issue33582@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May 19 22:18:34 2018
From: report at bugs.python.org (Ivan Pozdeev)
Date: Sun, 20 May 2018 02:18:34 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1526782714.22.0.682650639539.issue33479@psf.upfronthosting.co.za>


Ivan Pozdeev <ivan_pozdeev at mail.ru> added the comment:

I'm currently rewriting the docs, too, according to the plan @ #msg316492. WIP @ https://github.com/native-api/cpython/tree/tkinter_docs .

You PR lines up fine though is made redundant by https://github.com/native-api/cpython/commit/79b195a9028fd7bf6e8186dfced0fad6a41e87fa -- instead of removing Doc\library\tk.rst, I reduced it to a summary of chapter content without any claims about it whatsoever, like other chapter head pages.

----------

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

From report at bugs.python.org  Sat May 19 23:15:10 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Sun, 20 May 2018 03:15:10 +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: <1526786110.09.0.682650639539.issue32996@psf.upfronthosting.co.za>


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


New changeset 63536bd286097e770909052052a21804a5e09b66 by Yury Selivanov (Elvis Pranskevichus) in branch 'master':
bpo-32996: The bulk of What's New in Python 3.7 (GH-6978)
https://github.com/python/cpython/commit/63536bd286097e770909052052a21804a5e09b66


----------

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

From report at bugs.python.org  Sat May 19 23:34:07 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Sun, 20 May 2018 03:34:07 +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: <1526787247.65.0.262363346258.issue32996@psf.upfronthosting.co.za>


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


----------
pull_requests: +6651

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

From report at bugs.python.org  Sat May 19 23:39:47 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Sun, 20 May 2018 03:39:47 +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: <1526787587.85.0.682650639539.issue32996@psf.upfronthosting.co.za>


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


New changeset 15f3d0cc7660ee62c7a1c0420afaee18c26a2a1f by Yury Selivanov (Elvis Pranskevichus) in branch '3.7':
[3.7] bpo-32996: The bulk of What's New in Python 3.7 (GH-6978). (GH-6998)
https://github.com/python/cpython/commit/15f3d0cc7660ee62c7a1c0420afaee18c26a2a1f


----------

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

From report at bugs.python.org  Sun May 20 11:00:24 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 May 2018 15:00:24 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1526828424.39.0.682650639539.issue30940@psf.upfronthosting.co.za>


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


New changeset 900c48dba3f3eb8fb03ea766a5646f81c3bf3e9c by Serhiy Storchaka (Lisa Roach) in branch 'master':
bpo-30940: Updating round() docs. (GH-6342)
https://github.com/python/cpython/commit/900c48dba3f3eb8fb03ea766a5646f81c3bf3e9c


----------

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

From report at bugs.python.org  Sun May 20 11:01:27 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 May 2018 15:01:27 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1526828487.43.0.262363346258.issue30940@psf.upfronthosting.co.za>


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


----------
pull_requests: +6659

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

From report at bugs.python.org  Sun May 20 11:02:27 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 May 2018 15:02:27 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1526828547.11.0.262363346258.issue30940@psf.upfronthosting.co.za>


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


----------
pull_requests: +6660

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

From report at bugs.python.org  Sun May 20 11:12:52 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 May 2018 15:12:52 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526829172.6.0.682650639539.issue33580@psf.upfronthosting.co.za>


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


New changeset 0c4be82890858f874ff2158b0fcfdb8f261569c0 by Serhiy Storchaka (Andr?s Delfino) in branch 'master':
bpo-33580: Make binary/text file glossary entries follow most common "see also" style. (GH-6991)
https://github.com/python/cpython/commit/0c4be82890858f874ff2158b0fcfdb8f261569c0


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

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

From report at bugs.python.org  Sun May 20 11:13:59 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 May 2018 15:13:59 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526829239.09.0.262363346258.issue33580@psf.upfronthosting.co.za>


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


----------
pull_requests: +6662

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

From report at bugs.python.org  Sun May 20 11:14:59 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 May 2018 15:14:59 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526829299.74.0.262363346258.issue33580@psf.upfronthosting.co.za>


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


----------
pull_requests: +6663

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

From report at bugs.python.org  Sun May 20 11:28:18 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 May 2018 15:28:18 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1526830098.08.0.682650639539.issue30940@psf.upfronthosting.co.za>


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


New changeset 736e3b32194b52b1779ce88a2c13862f0f913a7a by Serhiy Storchaka (Miss Islington (bot)) in branch '3.7':
bpo-30940: Updating round() docs. (GH-6342) (GH-7009)
https://github.com/python/cpython/commit/736e3b32194b52b1779ce88a2c13862f0f913a7a


----------

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

From report at bugs.python.org  Sun May 20 11:29:47 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 May 2018 15:29:47 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1526830187.59.0.682650639539.issue30940@psf.upfronthosting.co.za>


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


New changeset 82c9adb3f94e5d889f03205d03a76a5ff0928531 by Miss Islington (bot) in branch '3.6':
bpo-30940: Updating round() docs. (GH-6342)
https://github.com/python/cpython/commit/82c9adb3f94e5d889f03205d03a76a5ff0928531


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

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

From report at bugs.python.org  Sun May 20 11:57:44 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 May 2018 15:57:44 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526831864.92.0.682650639539.issue33580@psf.upfronthosting.co.za>


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


New changeset 983e9653e0584b65a6ec66543ce1631f888aa285 by Miss Islington (bot) in branch '3.6':
bpo-33580: Make binary/text file glossary entries follow most common "see also" style. (GH-6991)
https://github.com/python/cpython/commit/983e9653e0584b65a6ec66543ce1631f888aa285


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

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

From report at bugs.python.org  Sun May 20 12:28:28 2018
From: report at bugs.python.org (Eric N. Vander Weele)
Date: Sun, 20 May 2018 16:28:28 +0000
Subject: [docs] [issue33586] 2.7.15 missing release notes on download page
Message-ID: <1526833708.19.0.682650639539.issue33586@psf.upfronthosting.co.za>


New submission from Eric N. Vander Weele <ericvw at gmail.com>:

When visiting https://www.python.org/downloads/ and attempting to look at the 2.7.15 release notes, the 'Release Notes' link on the far right of the table, it resolves to https://www.python.org/downloads/.

----------
assignee: docs at python
components: Documentation
messages: 317185
nosy: docs at python, ericvw
priority: normal
severity: normal
status: open
title: 2.7.15 missing release notes on download page
versions: Python 2.7

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

From report at bugs.python.org  Sun May 20 18:51:39 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 May 2018 22:51:39 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526856699.44.0.682650639539.issue33580@psf.upfronthosting.co.za>


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


New changeset 4ecdc1110df211686a4406ba666a7f8106e0f618 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.7':
bpo-33580: Make binary/text file glossary entries follow most common "see also" style. (GH-6991) (GH-7012)
https://github.com/python/cpython/commit/4ecdc1110df211686a4406ba666a7f8106e0f618


----------

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

From report at bugs.python.org  Sun May 20 19:46:44 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 May 2018 23:46:44 +0000
Subject: [docs] [issue26103] Contradiction in definition of "data
 descriptor" between (dotted lookup behavior/datamodel documentation) and
 (inspect lib/descriptor how-to)
In-Reply-To: <1452718612.1.0.925403449689.issue26103@psf.upfronthosting.co.za>
Message-ID: <1526860004.71.0.682650639539.issue26103@psf.upfronthosting.co.za>


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


New changeset 4054b172ab59054715a2aaf4979bd84ac23e3ada by Serhiy Storchaka (Aaron Hall, MBA) in branch 'master':
bpo-26103: Fix inspect.isdatadescriptor() and a data descriptor definition. (GH-1959)
https://github.com/python/cpython/commit/4054b172ab59054715a2aaf4979bd84ac23e3ada


----------

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

From report at bugs.python.org  Sun May 20 20:17:53 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 21 May 2018 00:17:53 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526861873.98.0.262363346258.issue33583@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon May 21 00:21:43 2018
From: report at bugs.python.org (Carol Willing)
Date: Mon, 21 May 2018 04:21:43 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1526876503.48.0.682650639539.issue29428@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

I've closed the associated PR https://github.com/python/cpython/pull/45 with a recommendation to resubmit a smaller, more atomic PR if desired.

----------
nosy: +willingc
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon May 21 05:35:50 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 21 May 2018 09:35:50 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526895350.5.0.682650639539.issue33583@psf.upfronthosting.co.za>


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


New changeset 1179f4b40f375af5c59cd4b6be9cc313fa0e1a37 by INADA Naoki in branch 'master':
bpo-33583: Add note in PyObject_GC_Resize() doc (GH-7021)
https://github.com/python/cpython/commit/1179f4b40f375af5c59cd4b6be9cc313fa0e1a37


----------

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

From report at bugs.python.org  Mon May 21 05:36:50 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 May 2018 09:36:50 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526895410.93.0.262363346258.issue33583@psf.upfronthosting.co.za>


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


----------
pull_requests: +6674

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

From report at bugs.python.org  Mon May 21 05:37:52 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 May 2018 09:37:52 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526895472.16.0.262363346258.issue33583@psf.upfronthosting.co.za>


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


----------
pull_requests: +6675

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

From report at bugs.python.org  Mon May 21 05:38:50 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 May 2018 09:38:50 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526895530.9.0.262363346258.issue33583@psf.upfronthosting.co.za>


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


----------
pull_requests: +6676

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

From report at bugs.python.org  Mon May 21 09:03:16 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 21 May 2018 13:03:16 +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: <1526907796.68.0.262363346258.issue33586@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> 
nosy: +benjamin.peterson

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

From report at bugs.python.org  Mon May 21 10:05:19 2018
From: report at bugs.python.org (R. David Murray)
Date: Mon, 21 May 2018 14:05:19 +0000
Subject: [docs] [issue33581] Document "optional components that are commonly
 included in Python distributions."
In-Reply-To: <1526767207.27.0.682650639539.issue33581@psf.upfronthosting.co.za>
Message-ID: <1526911519.23.0.682650639539.issue33581@psf.upfronthosting.co.za>


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

As I understand it, we don't control or know what that list is, it depends on each distribution's policies.

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

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

From report at bugs.python.org  Mon May 21 10:10:30 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 May 2018 14:10:30 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526911830.56.0.682650639539.issue33583@psf.upfronthosting.co.za>


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


New changeset 3ccc31386da5f35f83756a265429831d650db731 by Miss Islington (bot) in branch '2.7':
bpo-33583: Add note in PyObject_GC_Resize() doc (GH-7021)
https://github.com/python/cpython/commit/3ccc31386da5f35f83756a265429831d650db731


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

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

From report at bugs.python.org  Mon May 21 10:51:02 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 21 May 2018 14:51:02 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526914262.84.0.682650639539.issue33583@psf.upfronthosting.co.za>


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


New changeset 2b4ed5da1d599190c3be0084ee235b0a8f0a75ea by INADA Naoki (Miss Islington (bot)) in branch '3.7':
bpo-33583: Add note in PyObject_GC_Resize() doc (GH-7021)
https://github.com/python/cpython/commit/2b4ed5da1d599190c3be0084ee235b0a8f0a75ea


----------

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

From christopher.eliot at nagrastar.com  Mon May 21 00:59:06 2018
From: christopher.eliot at nagrastar.com (Eliot, Christopher)
Date: Mon, 21 May 2018 04:59:06 +0000
Subject: [docs] Suggested improvement for glossary:  define "tuple"
Message-ID: <8E46FDB22B1F5746A32B543FA8D74DA0C3A1484F@Nstar-Server11.windows.nagrastar.com>

Greetings:

I've  been using this glossary<https://docs.python.org/3/glossary.html#glossary>, and wished it defined the word "tuple".

Thank you for all that you do,

Topher Eliot
christopher.eliot at nagrastar.com<mailto:christopher.eliot at nagrastar.com>
+01 303 706-5766

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

From report at bugs.python.org  Mon May 21 13:28:44 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Mon, 21 May 2018 17:28:44 +0000
Subject: [docs] [issue33592] Document contextvars C API
Message-ID: <1526923723.99.0.682650639539.issue33592@psf.upfronthosting.co.za>


New submission from Elvis Pranskevichus <elvis at magic.io>:

The C API for PEP 567 is currently missing.

----------
assignee: docs at python
components: Documentation
messages: 317244
nosy: Elvis.Pranskevichus, docs at python, yselivanov
priority: normal
severity: normal
status: open
title: Document contextvars C API
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Mon May 21 13:31:23 2018
From: report at bugs.python.org (Elvis Pranskevichus)
Date: Mon, 21 May 2018 17:31:23 +0000
Subject: [docs] [issue33592] Document contextvars C API
In-Reply-To: <1526923723.99.0.682650639539.issue33592@psf.upfronthosting.co.za>
Message-ID: <1526923883.85.0.262363346258.issue33592@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 21 17:34:32 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 21 May 2018 21:34:32 +0000
Subject: [docs] [issue33594] add deprecation since 3.5 for a few methods of
 inspect.
Message-ID: <1526938472.55.0.682650639539.issue33594@psf.upfronthosting.co.za>


New submission from Matthias Bussonnier <bussonniermatthias at gmail.com>:

inspect's getargspec, as well as Signature's from_function, and from_builtin are deprecated. 

They all emits DeprecationWarning but: 

The deprecation warning does not say since which version since are deprecated. 
For the two Signature's methods, there is no documentation available, so finding this information is difficult. 

Many tool rely on introspection to provide object help via docstring, which also did not include this deprecation notice. 

Adding the deprecation informations to these 3 function/methods would be good to foster migration to newer ways.

----------
assignee: docs at python
components: Documentation
messages: 317252
nosy: docs at python, mbussonn
priority: normal
severity: normal
status: open
title: add deprecation since 3.5 for a few methods of inspect.
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon May 21 17:37:06 2018
From: report at bugs.python.org (Matthias Bussonnier)
Date: Mon, 21 May 2018 21:37:06 +0000
Subject: [docs] [issue33594] add deprecation since 3.5 for a few methods of
 inspect.
In-Reply-To: <1526938472.55.0.682650639539.issue33594@psf.upfronthosting.co.za>
Message-ID: <1526938626.77.0.262363346258.issue33594@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 21 18:45:53 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 21 May 2018 22:45:53 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
Message-ID: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>


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

There a couple of references to lambda parameters mentioned as arguments. I'm proposing fixing them.

----------
assignee: docs at python
components: Documentation
messages: 317255
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: FIx references to lambda "arguments"
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/issue33595>
_______________________________________

From report at bugs.python.org  Mon May 21 18:49:07 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Mon, 21 May 2018 22:49:07 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1526942947.07.0.262363346258.issue33595@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 21 19:36:31 2018
From: report at bugs.python.org (Eric Snow)
Date: Mon, 21 May 2018 23:36:31 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526945791.42.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

Under Py_LIMITED_API:

    typedef struct _is PyInterpreterState;

Also, the actual removal of the "modules" field was reverted.  The field is still there until I get back to fixing https://github.com/python/cpython/pull/3606.

----------

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

From report at bugs.python.org  Mon May 21 22:18:49 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 May 2018 02:18:49 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526955529.41.0.682650639539.issue33583@psf.upfronthosting.co.za>


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


New changeset 0c1e7d8122808d42f9fdb7019061dc2e78a78efa by Miss Islington (bot) in branch '3.6':
bpo-33583: Add note in PyObject_GC_Resize() doc (GH-7021)
https://github.com/python/cpython/commit/0c1e7d8122808d42f9fdb7019061dc2e78a78efa


----------

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

From report at bugs.python.org  Tue May 22 01:33:08 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 22 May 2018 05:33:08 +0000
Subject: [docs] [issue33583] PyObject_GC_Resize() doesn't relink GCHead
In-Reply-To: <1526802151.18.0.682650639539.issue33583@psf.upfronthosting.co.za>
Message-ID: <1526967188.45.0.262363346258.issue33583@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/issue33583>
_______________________________________

From report at bugs.python.org  Tue May 22 02:00:08 2018
From: report at bugs.python.org (Julien Palard)
Date: Tue, 22 May 2018 06:00:08 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1526968808.39.0.262363346258.issue33595@psf.upfronthosting.co.za>


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


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

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

From marco at perniciaro.com  Tue May 22 05:30:14 2018
From: marco at perniciaro.com (marco at perniciaro.com)
Date: Tue, 22 May 2018 11:30:14 +0200
Subject: [docs] Bug in Python3 with numpy ('arange' method)
Message-ID: <70dcade950acb75683df6eb5c3a3d9cd@perniciaro.com>

Dear support team,
during a test I found out a possible issue in Python I would like to
report. 

Please, confirm if this is a bug or let me know why my expectation are
incorrect: 

> python3
Python 3.4.3 (default, Nov 28 2017, 16:41:13) 
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as np
>>> x = np.arange(0, 0.5, 0.0001)
>>> 0.4 in x
True
>>> 0.41 in x # expected to be True!
False
>>> 0.42 in x # expected to be True!
False
>>> 0.43 in x
True 

>>> 0.429 in x # expected to be True!
False
>>> 0.431 in x
True

Regards,
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180522/e64d6cf2/attachment.html>

From report at bugs.python.org  Tue May 22 05:33:46 2018
From: report at bugs.python.org (Alex Walters)
Date: Tue, 22 May 2018 09:33:46 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
Message-ID: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>


New submission from Alex Walters <tritium-list at sdamon.com>:

ActiveState has stopped accepting new recipes on their website, and migrated all current recipes to a Github repo.  I have seen no official announcement of a shutdown date for the code.activestate.com website, but it's future has to be in question considering the migration.

I propose we go through the docs for all the recipes, and either rescue them to a section of the docs (perhaps to a new "Code Examples" section), incorporate the recipes into the doc pages where appropriate, or excise them entirely.

Another option would be to update the links to the GitHub repo, but I am less enthusiastic about that option - GitHub repos come and go, and mutate structure easily.  I don't think it would be a good idea to deep link into a repository not controlled by the Python project.

It would stink to have a bunch of suddenly dead links in the docs.

----------
assignee: docs at python
components: Documentation
messages: 317265
nosy: docs at python, rhettinger, tritium
priority: normal
severity: normal
status: open
title: ActiveState Recipes links in docs, and the apparent closure of Recipes

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

From prashant.raju at columbia.edu  Mon May 21 21:39:40 2018
From: prashant.raju at columbia.edu (Prashant Chama Raju)
Date: Mon, 21 May 2018 21:39:40 -0400
Subject: [docs] download documentation
Message-ID: <CAD=Xj2JiYk18Y8utFEj6Yctz8Hp66_WF2Z4+t0mF8rjf4KqTbQ@mail.gmail.com>

Hi,

Is there a way for me to download the entire python documentation?
Specifically this https://docs.python.org/2/library/functions.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180521/6e8e9da9/attachment-0001.html>

From report at bugs.python.org  Tue May 22 07:59:13 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 22 May 2018 11:59:13 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526990353.02.0.682650639539.issue33580@psf.upfronthosting.co.za>


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

This one can be closed, right?

----------

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

From report at bugs.python.org  Tue May 22 08:03:13 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 May 2018 12:03:13 +0000
Subject: [docs] [issue33580] Make binary/text file glossary entries follow
 most common "see also" style
In-Reply-To: <1526760789.23.0.682650639539.issue33580@psf.upfronthosting.co.za>
Message-ID: <1526990593.35.0.262363346258.issue33580@psf.upfronthosting.co.za>


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


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

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

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


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

The platform.linux_distribution() function has been removed from the future Python 3.8. The removal should be documented in Python 2.7 documentation, and mention the alternative.

Python 2 documenation:
https://docs.python.org/2/library/platform.html#platform.linux_distribution

Python 3 documentation with the deprecation warning:
https://docs.python.org/3/library/platform.html#platform.linux_distribution

IMHO it's too late to deprecate the function from Python 2. We should only add a quick note.

Function removed in: bpo-28167.

----------
assignee: docs at python
components: Documentation
messages: 317275
nosy: docs at python, vstinner
priority: normal
severity: normal
status: open
title: [EASY DOC] Python 2: document that platform.linux_distribution() has been removed
versions: Python 2.7

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

From report at bugs.python.org  Tue May 22 09:06:10 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 May 2018 13:06:10 +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: <1526994370.8.0.262363346258.issue33600@psf.upfronthosting.co.za>


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


----------
keywords: +easy

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

From report at bugs.python.org  Tue May 22 09:37:27 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 May 2018 13:37:27 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526996247.41.0.682650639539.issue33518@psf.upfronthosting.co.za>


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


New changeset 8cbde8a43769641373a681af4b0d72944af43f95 by Victor Stinner (Andr?s Delfino) in branch '2.7':
[2.7] bpo-33518: Add PEP entry to documentation glossary (GH-6860). (#6936)
https://github.com/python/cpython/commit/8cbde8a43769641373a681af4b0d72944af43f95


----------

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

From report at bugs.python.org  Tue May 22 09:38:22 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 May 2018 13:38:22 +0000
Subject: [docs] [issue33518] Add PEP to glossary
In-Reply-To: <1526389344.41.0.682650639539.issue33518@psf.upfronthosting.co.za>
Message-ID: <1526996302.06.0.682650639539.issue33518@psf.upfronthosting.co.za>


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

Thank you Andr?s Delfino. I applied your PR to 2.7, 3.6, 3.7 and master.

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

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

From report at bugs.python.org  Tue May 22 09:49:41 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 May 2018 13:49:41 +0000
Subject: [docs] [issue33601] Py_UTF8Mode is not documented
Message-ID: <1526996981.47.0.682650639539.issue33601@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Py_UTF8Mode was added to the limited API in 3.7, but it is not documented anywhere.

----------
assignee: docs at python
components: Documentation
messages: 317286
nosy: docs at python, ncoghlan, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: Py_UTF8Mode is not documented
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue May 22 09:52:10 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 May 2018 13:52:10 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1526997130.23.0.682650639539.issue33470@psf.upfronthosting.co.za>


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

> Also, the actual removal of the "modules" field was reverted.

Oh... I didn't understand that part :-) Ok. In this case it's fine to close this documentation issue. Nothing should be documented for 3.7 ;-)

----------

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

From report at bugs.python.org  Tue May 22 10:05:17 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 May 2018 14:05:17 +0000
Subject: [docs] [issue33601] [EASY DOC] Py_UTF8Mode is not documented
In-Reply-To: <1526996981.47.0.682650639539.issue33601@psf.upfronthosting.co.za>
Message-ID: <1526997917.82.0.682650639539.issue33601@psf.upfronthosting.co.za>


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

I wasn't sure if I should document it, but after talking with Serhiy on IRC, I now agree that the new variable should be documented.

It should be documented at:
https://docs.python.org/dev/c-api/init.html#global-configuration-variables

----------
keywords: +easy
title: Py_UTF8Mode is not documented -> [EASY DOC] Py_UTF8Mode is not documented

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

From report at bugs.python.org  Tue May 22 10:28:08 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 22 May 2018 14:28:08 +0000
Subject: [docs] [issue33602] Remove set and queue references from Data Types
Message-ID: <1526999288.77.0.682650639539.issue33602@psf.upfronthosting.co.za>


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

Data Types mentions sets (which are now built-in) and synchronized queues (now mentioned in Concurrent Execution). I'm proposing fixing this.

PR also adds mention to bytearray.

----------
assignee: docs at python
components: Documentation
messages: 317293
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Remove set and queue references from Data Types
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue May 22 10:30:19 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 22 May 2018 14:30:19 +0000
Subject: [docs] [issue33602] Remove set and queue references from Data Types
In-Reply-To: <1526999288.77.0.682650639539.issue33602@psf.upfronthosting.co.za>
Message-ID: <1526999419.93.0.262363346258.issue33602@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue May 22 10:35:06 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 May 2018 14:35:06 +0000
Subject: [docs] [issue33601] [EASY DOC] Py_UTF8Mode is not documented
In-Reply-To: <1526996981.47.0.682650639539.issue33601@psf.upfronthosting.co.za>
Message-ID: <1526999706.74.0.682650639539.issue33601@psf.upfronthosting.co.za>


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

If there are reasons of including it in the limited API, it should be documented.

----------

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

From report at bugs.python.org  Tue May 22 13:32:02 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 22 May 2018 17:32:02 +0000
Subject: [docs] [issue33592] Document contextvars C API
In-Reply-To: <1526923723.99.0.682650639539.issue33592@psf.upfronthosting.co.za>
Message-ID: <1527010322.77.0.682650639539.issue33592@psf.upfronthosting.co.za>


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


New changeset b2f5f59ae15564b991f3ca4850e6ad28d9faacbc by Yury Selivanov (Elvis Pranskevichus) in branch 'master':
bpo-33592: Document the C API in PEP 567 (contextvars) (GH-7033)
https://github.com/python/cpython/commit/b2f5f59ae15564b991f3ca4850e6ad28d9faacbc


----------

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

From report at bugs.python.org  Tue May 22 13:33:08 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 May 2018 17:33:08 +0000
Subject: [docs] [issue33592] Document contextvars C API
In-Reply-To: <1526923723.99.0.682650639539.issue33592@psf.upfronthosting.co.za>
Message-ID: <1527010388.97.0.262363346258.issue33592@psf.upfronthosting.co.za>


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


----------
pull_requests: +6691

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

From report at bugs.python.org  Tue May 22 13:58:04 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 May 2018 17:58:04 +0000
Subject: [docs] [issue33592] Document contextvars C API
In-Reply-To: <1526923723.99.0.682650639539.issue33592@psf.upfronthosting.co.za>
Message-ID: <1527011884.56.0.682650639539.issue33592@psf.upfronthosting.co.za>


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


New changeset afec2d583a06849c5080c6cd40266743c8e04b3e by Miss Islington (bot) in branch '3.7':
bpo-33592: Document the C API in PEP 567 (contextvars) (GH-7033)
https://github.com/python/cpython/commit/afec2d583a06849c5080c6cd40266743c8e04b3e


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

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

From report at bugs.python.org  Tue May 22 14:16:59 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 May 2018 18:16:59 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1527013019.25.0.262363346258.issue30940@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue May 22 16:30:13 2018
From: report at bugs.python.org (Aaron Hall)
Date: Tue, 22 May 2018 20:30:13 +0000
Subject: [docs] [issue32400] inspect.isdatadescriptor  false negative
In-Reply-To: <1513882624.99.0.213398074469.issue32400@psf.upfronthosting.co.za>
Message-ID: <1527021013.53.0.262363346258.issue32400@psf.upfronthosting.co.za>


Change by Aaron Hall <aaronchall at yahoo.com>:


----------
nosy: +Aaron Hall

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

From report at bugs.python.org  Tue May 22 17:07:30 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 22 May 2018 21:07:30 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
Message-ID: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>


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

I don't see it documented that dicts preserve insertion order. 3.7 what's new points to [1], but that section doesn't have a "version changed" tag.

IMO, [1] should have two version changed tags: one for 3.6, and one for 3.7.

Also, it would be great if we could document how the order is preserved when a key is deleted from the dict etc.

[1] https://docs.python.org/3.7/library/stdtypes.html#mapping-types-dict

----------
assignee: docs at python
components: Documentation
messages: 317346
nosy: docs at python, inada.naoki, ned.deily, vstinner, yselivanov
priority: normal
severity: normal
status: open
title: Document that dicts preserve insertion order
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Wed May 23 06:42:32 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Wed, 23 May 2018 10:42:32 +0000
Subject: [docs] =?utf-8?q?=5Bissue33514=5D_async_and_await_as_keywords_no?=
 =?utf-8?q?t_mentioned_in_What=E2=80=99s_New_In_Python_3=2E7?=
In-Reply-To: <1526376462.69.0.682650639539.issue33514@psf.upfronthosting.co.za>
Message-ID: <1527072152.83.0.682650639539.issue33514@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

This was fixed via issue32996

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

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

From report at bugs.python.org  Wed May 23 08:33:08 2018
From: report at bugs.python.org (Sebastian Rittau)
Date: Wed, 23 May 2018 12:33:08 +0000
Subject: [docs] [issue33616] typing.NoReturn is undocumented
Message-ID: <1527078788.95.0.682650639539.issue33616@psf.upfronthosting.co.za>


New submission from Sebastian Rittau <srittau at rittau.biz>:

This exists at least in Python 3.6.5's typing module. https://github.com/python/typing/issues/165 has background on why it was added.

----------
assignee: docs at python
components: Documentation
messages: 317395
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: typing.NoReturn is undocumented
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Wed May 23 11:08:48 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 23 May 2018 15:08:48 +0000
Subject: [docs] [issue33616] typing.NoReturn is undocumented
In-Reply-To: <1527078788.95.0.682650639539.issue33616@psf.upfronthosting.co.za>
Message-ID: <1527088128.9.0.262363346258.issue33616@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May 23 11:15:27 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 23 May 2018 15:15:27 +0000
Subject: [docs] [issue33421] Missing documentation for
 typing.AsyncContextManager
In-Reply-To: <1525390394.87.0.682650639539.issue33421@psf.upfronthosting.co.za>
Message-ID: <1527088527.73.0.682650639539.issue33421@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

This is now fixed.

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

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

From report at bugs.python.org  Wed May 23 12:23:06 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 May 2018 16:23:06 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1527092586.52.0.682650639539.issue33609@psf.upfronthosting.co.za>


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

As reference, issue32337 made some changes documenting that the dicts preserve insertion order.  Also, issue33218 was marked as being superseded by #32337.

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

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

From report at bugs.python.org  Wed May 23 16:41:22 2018
From: report at bugs.python.org (Ned Deily)
Date: Wed, 23 May 2018 20:41:22 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1527108082.86.0.682650639539.issue33609@psf.upfronthosting.co.za>


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

I agree with Yury's suggestions; the entry in the "Dictionary view objects" section, that Cheryl points to, is not sufficient.  Is somebody willing to write a PR?

----------
priority: normal -> high
stage:  -> needs patch
type: enhancement -> 

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

From report at bugs.python.org  Wed May 23 19:26:46 2018
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 May 2018 23:26:46 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527118006.7.0.262363346258.issue33216@psf.upfronthosting.co.za>


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


----------
title: Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW -> [3.5] Wrong order of stack for CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW

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

From report at bugs.python.org  Wed May 23 19:29:52 2018
From: report at bugs.python.org (Larry Hastings)
Date: Wed, 23 May 2018 23:29:52 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527118192.09.0.682650639539.issue33216@psf.upfronthosting.co.za>


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

Serhiy, why did you mark this as a release blocker?  This is a proposed documentation fix.

----------
priority: release blocker -> low

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

From report at bugs.python.org  Wed May 23 19:32:12 2018
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 May 2018 23:32:12 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527118331.99.0.682650639539.issue33216@psf.upfronthosting.co.za>


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

If the issue is specific to Python 3.5, we can no longer fix it since 3.5 doesn't accept bugfixes anymore. No?

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

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

From report at bugs.python.org  Wed May 23 19:32:56 2018
From: report at bugs.python.org (Larry Hastings)
Date: Wed, 23 May 2018 23:32:56 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527118376.12.0.682650639539.issue33216@psf.upfronthosting.co.za>


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

Documentation changes are okay.

----------

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

From report at bugs.python.org  Wed May 23 22:13:45 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 May 2018 02:13:45 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527128025.8.0.393789816046.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +6726

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

From report at bugs.python.org  Wed May 23 22:15:59 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 May 2018 02:15:59 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527128159.37.0.682650639539.issue32374@psf.upfronthosting.co.za>


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

MultiPhaseExtensionModuleTests.test_bad_traverse() of Lib/test/test_importlib/extension/test_loader.py does create a coredump file. The script run by the test trigger a segfault. Is it deliberate? See bpo-33629 and my PR 7090.

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

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

From report at bugs.python.org  Thu May 24 00:38:16 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 May 2018 04:38:16 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527136696.16.0.682650639539.issue33216@psf.upfronthosting.co.za>


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

Because I don't want that this fix be missed in the next bugfix release. I think this documentation is important enough. There may be no chance to document it later.

----------

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

From report at bugs.python.org  Thu May 24 02:00:22 2018
From: report at bugs.python.org (Larry Hastings)
Date: Thu, 24 May 2018 06:00:22 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527141622.54.0.682650639539.issue33216@psf.upfronthosting.co.za>


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

Marking an issue as "Release Blocker" is completely inappropriate for "I'd like to see this documentation change get into the next bugfix release."

Our Python Dev Guide discusses priority, here:

https://devguide.python.org/triaging/#priority

It says:

"As a guideline, critical and above are usually reserved for crashes, serious regressions or breakage of very important APIs. Whether a bug is a release blocker for the current release schedule is decided by the release manager. Triagers may recommend this priority and should add the release manager to the nosy list. If needed, consult the release schedule and the release?s associated PEP for the release manager?s name."


Please do not mark any bugs as "Release Blocker" in the future unless you are the release manager for that version.

----------

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

From report at bugs.python.org  Thu May 24 02:13:35 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 May 2018 06:13:35 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1527142415.27.0.682650639539.issue33216@psf.upfronthosting.co.za>


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

Sorry. I have attracted your attention, and this was the only purpose of this mark. You are aware of this issue now, and the further fate of it is up to you.

----------

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

From report at bugs.python.org  Thu May 24 05:06:45 2018
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 24 May 2018 09:06:45 +0000
Subject: [docs] [issue33609] Document that dicts preserve insertion order
In-Reply-To: <1527023250.35.0.682650639539.issue33609@psf.upfronthosting.co.za>
Message-ID: <1527152805.26.0.262363346258.issue33609@psf.upfronthosting.co.za>


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


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

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

From riyazsk14 at gmail.com  Wed May 23 10:35:12 2018
From: riyazsk14 at gmail.com (riyaz shaik)
Date: Wed, 23 May 2018 20:05:12 +0530
Subject: [docs] Python material or manual
Message-ID: <CALji7ByLwNexHHvDC=EDn8P+VWByGKKtvXmRkFLcpOU4S56yjw@mail.gmail.com>

Please send a python documents to this mail and relevant interview
questions with answer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180523/c29e2d5e/attachment-0001.html>

From sawantamitm at gmail.com  Wed May 23 17:27:22 2018
From: sawantamitm at gmail.com (amit sawant)
Date: Wed, 23 May 2018 14:27:22 -0700
Subject: [docs] can not install version on 3.6.5
Message-ID: <CAHBtQUyuV1pgUbNQeQ8=2CVqFi1UAu1JDSGTd1-1o6WjfrHTsw@mail.gmail.com>

(myvenv) trial #$ pip --version

pip 10.0.1 from
/Users/amit.sawant/.virtualenvs/myvenv/lib/python3.6/site-packages/pip
(python 3.6)

(myvenv) trial #$ pip install version

Collecting version

  Using cached
https://files.pythonhosted.org/packages/fd/b6/fa3b2c859d4d8817a106e4272029d78a2afbca0a27139997a4e5515bbf60/version-0.1.1.tar.gz

    Complete output from command python setup.py egg_info:

    Traceback (most recent call last):

      File "<string>", line 1, in <module>

      File
"/private/var/folders/44/0b94tr3s683c67gqgxgfp7mc0000gp/T/pip-install-hbbewl3s/version/setup.py",
line 4, in <module>

        from version import __version__

      File
"/private/var/folders/44/0b94tr3s683c67gqgxgfp7mc0000gp/T/pip-install-hbbewl3s/version/version.py",
line 2, in <module>

        from itertools import izip_longest

    ImportError: cannot import name 'izip_longest'



    ----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in
/private/var/folders/44/0b94tr3s683c67gqgxgfp7mc0000gp/T/pip-install-hbbewl3s/version/

(myvenv) trial #$


-- 
Thanks and Regards,
Amit Sawant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180523/67f9340a/attachment-0001.html>

From report at bugs.python.org  Thu May 24 16:19:37 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 May 2018 20:19:37 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527193177.1.0.262363346258.issue32374@psf.upfronthosting.co.za>


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


New changeset 483000e164ec68717d335767b223ae31b4b720cf by Victor Stinner in branch 'master':
bpo-33629: Prevent coredump in test_importlib (GH-7090)
https://github.com/python/cpython/commit/483000e164ec68717d335767b223ae31b4b720cf


----------

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

From report at bugs.python.org  Thu May 24 16:20:56 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 May 2018 20:20:56 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527193256.15.0.393789816046.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +6739

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

From report at bugs.python.org  Thu May 24 16:21:52 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 May 2018 20:21:52 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527193312.98.0.393789816046.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +6741

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

From report at bugs.python.org  Thu May 24 16:24:02 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 May 2018 20:24:02 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527193442.91.0.682650639539.issue32374@psf.upfronthosting.co.za>


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

MultiPhaseExtensionModuleTests.test_bad_traverse() of Lib/test/test_importlib/extension/test_loader.py runs the following code:
---
import importlib.util as util
spec = util.find_spec('_testmultiphase')
spec.name = '_testmultiphase_with_bad_traverse'
m = spec.loader.create_module(spec)
---

And then check that the Python "failed": that the exit code is non-zero...

That's a weak test: if the script fails before calling spec.loader.create_module(), the test also pass. If the function raises an exception but don't crash, the test pass as well.

More generally, I'm not sure about the idea of making sure that doing bad stuff with traverse does crash. What is the purpose of the test?

In the meanwhile, I fixed bpo-33629 by adding test.support.SuppressCrashReport().

I'm not asking to do something. Maybe it's fine to keep the current test.

----------

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

From report at bugs.python.org  Thu May 24 16:45:00 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 May 2018 20:45:00 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527194700.13.0.262363346258.issue32374@psf.upfronthosting.co.za>


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


New changeset d9eb22c67c38b45764dd924801c72092770d200f by Miss Islington (bot) in branch '3.7':
bpo-33629: Prevent coredump in test_importlib (GH-7090)
https://github.com/python/cpython/commit/d9eb22c67c38b45764dd924801c72092770d200f


----------

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

From report at bugs.python.org  Thu May 24 17:07:46 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 May 2018 21:07:46 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527196066.94.0.262363346258.issue32374@psf.upfronthosting.co.za>


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


New changeset fc0356d2a34719df517a5056bf1a3709850776cf by Miss Islington (bot) in branch '3.6':
bpo-33629: Prevent coredump in test_importlib (GH-7090)
https://github.com/python/cpython/commit/fc0356d2a34719df517a5056bf1a3709850776cf


----------

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

From report at bugs.python.org  Thu May 24 17:08:45 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 May 2018 21:08:45 +0000
Subject: [docs] [issue33640] uuid: endian of the bytes argument is not
 documented
Message-ID: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>


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

I don't understand what is the endian of the 'bytes' parameter of the uuid.UUID constructor:
https://docs.python.org/dev/library/uuid.html#uuid.UUID

According to examples, it seems like the endian is big endian, but I'm not sure.

Related issue: bpo-32493.

----------
assignee: docs at python
components: Documentation
messages: 317626
nosy: docs at python, vstinner
priority: normal
severity: normal
status: open
title: uuid: endian of the bytes argument is not documented
versions: Python 2.7, Python 3.6, Python 3.7

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

From report at bugs.python.org  Thu May 24 18:14:54 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 May 2018 22:14:54 +0000
Subject: [docs] [issue33641] Add links to RFCs
Message-ID: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

The proposed PR replaces "RFC XYZ" with ":rfc:`XYZ`". This adds hyperlinks to RFC documents. Actually 85% of all RFC references already use this markup, the PR change the rest 15% written as plain text.

----------
assignee: docs at python
components: Documentation
messages: 317629
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Add links to RFCs
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu May 24 18:17:21 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 May 2018 22:17:21 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527200241.84.0.262363346258.issue33641@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu May 24 18:25:18 2018
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 May 2018 22:25:18 +0000
Subject: [docs] [issue33640] uuid: endian of the bytes argument is not
 documented
In-Reply-To: <1527196125.95.0.682650639539.issue33640@psf.upfronthosting.co.za>
Message-ID: <1527200717.99.0.682650639539.issue33640@psf.upfronthosting.co.za>


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

At least, the UUID.bytes *attribute* is documented as using big endian:
https://docs.python.org/dev/library/uuid.html#uuid.UUID.bytes

----------

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

From report at bugs.python.org  Thu May 24 21:58:11 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 25 May 2018 01:58:11 +0000
Subject: [docs] [issue33616] typing.NoReturn is undocumented
In-Reply-To: <1527078788.95.0.682650639539.issue33616@psf.upfronthosting.co.za>
Message-ID: <1527213491.71.0.262363346258.issue33616@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri May 25 00:37:12 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 25 May 2018 04:37:12 +0000
Subject: [docs] [issue33616] typing.NoReturn is undocumented
In-Reply-To: <1527078788.95.0.682650639539.issue33616@psf.upfronthosting.co.za>
Message-ID: <1527223032.41.0.262363346258.issue33616@psf.upfronthosting.co.za>


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


----------
pull_requests: +6747

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

From report at bugs.python.org  Fri May 25 00:39:31 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 25 May 2018 04:39:31 +0000
Subject: [docs] [issue33616] typing.NoReturn is undocumented
In-Reply-To: <1527078788.95.0.682650639539.issue33616@psf.upfronthosting.co.za>
Message-ID: <1527223171.45.0.262363346258.issue33616@psf.upfronthosting.co.za>


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


----------
pull_requests: +6748

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

From report at bugs.python.org  Fri May 25 04:02:54 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Fri, 25 May 2018 08:02:54 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527235374.1.0.682650639539.issue32374@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

> That's a weak test: if the script fails before calling spec.loader.create_module(), the test also pass. If the function raises an exception but don't crash, the test pass as well.

That's a good argument, thanks.
Marcel, would you mind adding a patch for that?

> More generally, I'm not sure about the idea of making sure that doing bad stuff with traverse does crash. What is the purpose of the test?

This particular kind of bad traverse is quite easy to write if an extension author doesn't read docs carefully, or has read an old version of them (before the fix here). And resulting errors aren't too obvious. So, there's code to crash early and loudly in "--with-pydebug" for simple oversight cases. See comment at the call site of bad_traverse_test in Objects/moduleobject.c
And since there's code, there's a test to make sure it works :)

> In the meanwhile, I fixed bpo-33629 by adding test.support.SuppressCrashReport().

Thanks! Didn't know about that one, will keep it in mind for next time!

----------

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

From report at bugs.python.org  Fri May 25 11:48:02 2018
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 25 May 2018 15:48:02 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527263282.76.0.682650639539.issue32374@psf.upfronthosting.co.za>


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

"""
This particular kind of bad traverse is quite easy to write if an extension author doesn't read docs carefully, or has read an old version of them (before the fix here). And resulting errors aren't too obvious. So, there's code to crash early and loudly in "--with-pydebug" for simple oversight cases. See comment at the call site of bad_traverse_test in Objects/moduleobject.c
And since there's code, there's a test to make sure it works :)
"""

Oh ok, it makes sense. Maybe the test should test at least just before spec.loader.create_module(). Maybe using a print().

"Thanks! Didn't know about that one, will keep it in mind for next time!"

The problem is that by default, on Linux, we don't dump core files on the current directory. So such bug is silent on Linux. But it's commonly detected on FreeBSD since I configured the test runner to fail if it leaves a new file.

----------

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

From report at bugs.python.org  Fri May 25 13:56:21 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 17:56:21 +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: <1527270980.94.0.682650639539.issue33573@psf.upfronthosting.co.za>


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

I agree.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, terry.reedy
resolution: not a bug -> 
stage:  -> needs patch
title: statistics.median does not work with ordinal scale -> statistics.median does not work with ordinal scale, add doc
type: behavior -> enhancement
versions: +Python 3.6, Python 3.8

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

From report at bugs.python.org  Fri May 25 14:06:23 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 18:06:23 +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: <1527271583.71.0.262363346258.issue33582@psf.upfronthosting.co.za>


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


----------
nosy: +yselivanov
versions:  -Python 3.5

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

From report at bugs.python.org  Fri May 25 14:13:09 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 18:13:09 +0000
Subject: [docs] [issue33594] add deprecation since 3.5 for a few methods of
 inspect.
In-Reply-To: <1526938472.55.0.682650639539.issue33594@psf.upfronthosting.co.za>
Message-ID: <1527271989.33.0.682650639539.issue33594@psf.upfronthosting.co.za>


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

See also #33582 for 'formatargspec'.

----------
nosy: +terry.reedy, yselivanov
versions:  -Python 3.5

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

From report at bugs.python.org  Fri May 25 14:15:26 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 25 May 2018 18:15:26 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1527272126.51.0.262363346258.issue33595@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri May 25 14:18:52 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 25 May 2018 18:18:52 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1527272332.1.0.262363346258.issue33595@psf.upfronthosting.co.za>


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


----------
pull_requests: +6755

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

From report at bugs.python.org  Fri May 25 14:31:37 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 18:31:37 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1527273097.49.0.262363346258.issue33595@psf.upfronthosting.co.za>


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


----------
pull_requests: +6757

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

From report at bugs.python.org  Fri May 25 14:38:11 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 18:38:11 +0000
Subject: [docs] [issue33595] FIx references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1527273491.85.0.682650639539.issue33595@psf.upfronthosting.co.za>


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


New changeset 804fcf66559992db9d23695e501c502ab20b7712 by Terry Jan Reedy in branch '2.7':
[2.7] bpo-33595: Fix lambda parameters being refered as arguments (GH-7037) (GH-7122)
https://github.com/python/cpython/commit/804fcf66559992db9d23695e501c502ab20b7712


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

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

From report at bugs.python.org  Fri May 25 14:39:57 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 18:39:57 +0000
Subject: [docs] [issue33595] Fix references to lambda "arguments"
In-Reply-To: <1526942753.14.0.682650639539.issue33595@psf.upfronthosting.co.za>
Message-ID: <1527273597.19.0.682650639539.issue33595@psf.upfronthosting.co.za>


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

Thanks for the fix.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
title: FIx references to lambda "arguments" -> Fix references to lambda "arguments"

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

From report at bugs.python.org  Fri May 25 15:46:18 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 25 May 2018 19:46:18 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>
Message-ID: <1527277578.06.0.682650639539.issue30145@psf.upfronthosting.co.za>


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

Closing this issue. I'll open a new one for the planned asyncio docs overhaul.

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

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

From report at bugs.python.org  Fri May 25 15:48:42 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 25 May 2018 19:48:42 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
Message-ID: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>


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

An overhaul of asyncio documentation is long overdue.  Here's the structure for it that I have in mind:

- Introduction
(what is asyncio and async/await)

- A quick tutorial
(show how to use asyncio.run() and basic functions like asyncio.sleep() and teach that asyncio programs are all about async/await and *not* about callbacks or event loops)

- High-level APIs
(Tasks, Streams, Subprocesses, few other functions)

- Low-level APIs
  - Preface (talk a bit about everything: what's an event loop, what is a Future and a Transport)
  - Futures
  - Event loop APIs
  - Transports and Protocols (when to use and when not to use them)

- Tutorials
  - High-level networking server
  - HTTP application
  - Low-level protocol implementation using Transports
  - etc

----------
assignee: docs at python
components: Documentation, asyncio
messages: 317709
nosy: akuchling, asvetlov, docs at python, yselivanov
priority: normal
severity: normal
status: open
title: asyncio docs overhaul
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri May 25 16:00:49 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 20:00:49 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
In-Reply-To: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>
Message-ID: <1527278449.48.0.682650639539.issue33598@psf.upfronthosting.co.za>


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

Can you check the copyright and license of the recipe text and code?

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

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

From report at bugs.python.org  Fri May 25 16:02:22 2018
From: report at bugs.python.org (Barry A. Warsaw)
Date: Fri, 25 May 2018 20:02:22 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1527278542.9.0.262363346258.issue33649@psf.upfronthosting.co.za>


Change by Barry A. Warsaw <barry at python.org>:


----------
nosy: +barry

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

From report at bugs.python.org  Fri May 25 16:10:16 2018
From: report at bugs.python.org (Alex Walters)
Date: Fri, 25 May 2018 20:10:16 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
In-Reply-To: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>
Message-ID: <1527279016.5.0.682650639539.issue33598@psf.upfronthosting.co.za>


Alex Walters <tritium-list at sdamon.com> added the comment:

All recipes are MIT licensed unless otherwise noted on the recipe itself.

However, AFAICT, all the recipes that are linked to in the docs are written by Raymond Hettinger, so I don't think licensing will be that big of an issue.  We know where he is, we can ask him, and he has signed a CLA.

----------

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

From report at bugs.python.org  Fri May 25 16:11:28 2018
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Fri, 25 May 2018 20:11:28 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
In-Reply-To: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>
Message-ID: <1527279088.89.0.682650639539.issue33598@psf.upfronthosting.co.za>


Marc-Andre Lemburg <mal at egenix.com> added the comment:

I'd suggest to contact ActiveState first before jumping to conclusions.

----------
nosy: +lemburg

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

From report at bugs.python.org  Fri May 25 16:15:02 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 May 2018 20:15:02 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
In-Reply-To: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>
Message-ID: <1527279302.59.0.682650639539.issue33598@psf.upfronthosting.co.za>


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

The Python Cookbook, based on the site, says that copyright of each recipe is retained by original authors.  If so authors who have signed the PSF CLA can contribute their own work.

Since Active State must have collectively licensed the recipes to O'Reilly, they could do the same for us.  But if Raymond is the only author concerned, that should not be necessary.

----------
nosy:  -lemburg

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

From report at bugs.python.org  Fri May 25 23:22:21 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 26 May 2018 03:22:21 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
In-Reply-To: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>
Message-ID: <1527304941.19.0.682650639539.issue33598@psf.upfronthosting.co.za>


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

> I have seen no official announcement of a shutdown date for 
> the code.activestate.com website, but it's future has to be
> in question considering the migration.

We can check with ActiveState but my understanding is that they're leaving the existing web pages up (they already reduced the maintenance burden to zero by eliminating new updates so that the site wouldn't be spammed).  

So, I don't think there is a real issue here.  Also, I prefer the existing links because they include more than code (there is also exposition, commentary, history, and fork references).

----------
priority: normal -> low

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

From report at bugs.python.org  Sat May 26 08:43:42 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sat, 26 May 2018 12:43:42 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1527338622.44.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:


New changeset 6e33f810c9e3a549c9379f24cf1d1752c29195f0 by Ivan Levkivskyi (Andr?s Delfino) in branch 'master':
bpo-32769: A new take on annotations/type hinting glossary entries (GH-6829)
https://github.com/python/cpython/commit/6e33f810c9e3a549c9379f24cf1d1752c29195f0


----------

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

From report at bugs.python.org  Sat May 26 08:56:36 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sat, 26 May 2018 12:56:36 +0000
Subject: [docs] [issue33616] typing.NoReturn is undocumented
In-Reply-To: <1527078788.95.0.682650639539.issue33616@psf.upfronthosting.co.za>
Message-ID: <1527339396.18.0.262363346258.issue33616@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat May 26 08:57:06 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 26 May 2018 12:57:06 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1527339426.81.0.262363346258.issue32769@psf.upfronthosting.co.za>


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


----------
pull_requests: +6762

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

From report at bugs.python.org  Sat May 26 09:02:21 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sat, 26 May 2018 13:02:21 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1527339741.19.0.262363346258.issue33649@psf.upfronthosting.co.za>


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


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

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

From ramasamy_k at hcl.com  Fri May 25 02:52:14 2018
From: ramasamy_k at hcl.com (Ramasamy K)
Date: Fri, 25 May 2018 06:52:14 +0000
Subject: [docs] Found a bug in Python Documentation - Strings Chapter
In-Reply-To: <TY2PR04MB2686BA04E0B811EE04DE1DFFFF690@TY2PR04MB2686.apcprd04.prod.outlook.com>
References: <TY2PR04MB2686BA04E0B811EE04DE1DFFFF690@TY2PR04MB2686.apcprd04.prod.outlook.com>
Message-ID: <TY2PR04MB26863B2DDD09D9B4CD05686AFF690@TY2PR04MB2686.apcprd04.prod.outlook.com>

Sorry, I thing its correct only.

________________________________
From: Ramasamy K
Sent: Friday, May 25, 2018 12:18:27 PM
To: docs at python.org
Subject: Found a bug in Python Documentation - Strings Chapter


Hi


I found the below small bug on your docs, please correct it.


Go to: https://docs.python.org/3/tutorial/introduction.html#strings


Find below code:


>>> '"Isn\'t," she said.'
'"Isn\'t," she said.'

# The "\" symbol wont come on output.





::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180525/308e6fdb/attachment-0001.html>

From ramasamy_k at hcl.com  Fri May 25 02:48:27 2018
From: ramasamy_k at hcl.com (Ramasamy K)
Date: Fri, 25 May 2018 06:48:27 +0000
Subject: [docs] Found a bug in Python Documentation - Strings Chapter
Message-ID: <TY2PR04MB2686BA04E0B811EE04DE1DFFFF690@TY2PR04MB2686.apcprd04.prod.outlook.com>

Hi


I found the below small bug on your docs, please correct it.


Go to: https://docs.python.org/3/tutorial/introduction.html#strings


Find below code:


>>> '"Isn\'t," she said.'
'"Isn\'t," she said.'

# The "\" symbol wont come on output.





::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180525/7d177fc9/attachment.html>

From werner.wenzel at netcologne.de  Sat May 26 02:54:29 2018
From: werner.wenzel at netcologne.de (Werner Wenzel)
Date: Sat, 26 May 2018 08:54:29 +0200
Subject: [docs] Editorial slips in the Python Library Reference,
 Release 3.6.5
Message-ID: <1347fa4a-4ff1-2758-d3b4-7fac84735bea@netcologne.de>

The Python Library Reference, Release 3.6.5, paragraph "16.16 ctypes", 
is afflicted with at least 2 editorial slips:

The code snippets in "Incomplete Types" use a "c_char_p" but assign 
Unicode strings to it, resulting in a TypeError.

The same pertains to the last code snippet in "Surprises".

From report at bugs.python.org  Sat May 26 09:20:19 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 26 May 2018 13:20:19 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1527340819.74.0.262363346258.issue32769@psf.upfronthosting.co.za>


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


----------
pull_requests: +6763

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

From report at bugs.python.org  Sat May 26 13:17:36 2018
From: report at bugs.python.org (Guido van Rossum)
Date: Sat, 26 May 2018 17:17:36 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1527355056.59.0.682650639539.issue32769@psf.upfronthosting.co.za>


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


New changeset e69657df244135a232117f692640e0568b04e999 by Guido van Rossum (Andr?s Delfino) in branch '3.7':
[3.7] bpo-32769: A new take on annotations/type hinting glossary entries (GH-6829) (#7127)
https://github.com/python/cpython/commit/e69657df244135a232117f692640e0568b04e999


----------

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

From report at bugs.python.org  Sat May 26 13:41:15 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sat, 26 May 2018 17:41:15 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1527356475.88.0.682650639539.issue32769@psf.upfronthosting.co.za>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:


New changeset 717204ffcccfe04a34b6c4a52f0e844fde3cdebe by Ivan Levkivskyi (Andr?s Delfino) in branch '3.6':
[3.6] bpo-32769: A new take on annotations/type hinting glossary entries (GH-6829) (GH-7128)
https://github.com/python/cpython/commit/717204ffcccfe04a34b6c4a52f0e844fde3cdebe


----------

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

From report at bugs.python.org  Sat May 26 13:44:11 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 26 May 2018 17:44:11 +0000
Subject: [docs] [issue32769] Add 'annotations' to the glossary
In-Reply-To: <1518019777.95.0.467229070634.issue32769@psf.upfronthosting.co.za>
Message-ID: <1527356651.65.0.262363346258.issue32769@psf.upfronthosting.co.za>


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


----------
pull_requests: +6765

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

From report at bugs.python.org  Sat May 26 14:44:35 2018
From: report at bugs.python.org (Nathaniel Manista)
Date: Sat, 26 May 2018 18:44:35 +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: <1527360275.68.0.262363346258.issue23495@psf.upfronthosting.co.za>


Change by Nathaniel Manista <nathaniel at google.com>:


----------
nosy: +Nathaniel Manista

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

From report at bugs.python.org  Sun May 27 13:36:52 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 27 May 2018 17:36:52 +0000
Subject: [docs] [issue33598] ActiveState Recipes links in docs,
 and the apparent closure of Recipes
In-Reply-To: <1526981626.86.0.682650639539.issue33598@psf.upfronthosting.co.za>
Message-ID: <1527442612.59.0.682650639539.issue33598@psf.upfronthosting.co.za>


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

Marking this a closed. It can be reopened if ActiveState makes an announcement that they're actually going to kill the existing links.  Otherwise, this is pure speculation and not an actual problem to be solved.

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

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

From report at bugs.python.org  Sun May 27 17:06:34 2018
From: report at bugs.python.org (Yuwei Ren)
Date: Sun, 27 May 2018 21:06:34 +0000
Subject: [docs] [issue33601] [EASY DOC] Py_UTF8Mode is not documented
In-Reply-To: <1526996981.47.0.682650639539.issue33601@psf.upfronthosting.co.za>
Message-ID: <1527455194.93.0.262363346258.issue33601@psf.upfronthosting.co.za>


Change by Yuwei Ren <yuweiren at fb.com>:


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

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

From report at bugs.python.org  Mon May 28 05:06:09 2018
From: report at bugs.python.org (Marcel Plch)
Date: Mon, 28 May 2018 09:06:09 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527498369.57.0.262363346258.issue32374@psf.upfronthosting.co.za>


Change by Marcel Plch <gmarcel.plch at gmail.com>:


----------
pull_requests: +6779

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

From report at bugs.python.org  Mon May 28 05:16:46 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 28 May 2018 09:16:46 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527499005.91.0.682650639539.issue32374@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

> That's a weak test: if the script fails before calling spec.loader.create_module(), the test also pass. If the function raises an exception but don't crash, the test pass as well.

Marcel added PR 7145 for that -- it wraps things in try/except to catch Python-level exceptions sounds like a good solution to me.

----------

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

From report at bugs.python.org  Mon May 28 06:53:25 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 May 2018 10:53:25 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527504805.21.0.262363346258.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +6781

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

From report at bugs.python.org  Mon May 28 08:11:23 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 28 May 2018 12:11:23 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527509483.08.0.682650639539.issue32374@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:


New changeset 08c5aca9d13b24b35faf89ebd26fc348ae1731b2 by Petr Viktorin (Marcel Plch) in branch 'master':
bpo-32374: Ignore Python-level exceptions in test_bad_traverse (GH-7145)
https://github.com/python/cpython/commit/08c5aca9d13b24b35faf89ebd26fc348ae1731b2


----------

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

From report at bugs.python.org  Mon May 28 08:11:37 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 May 2018 12:11:37 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527509497.69.0.262363346258.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +6784

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

From report at bugs.python.org  Mon May 28 08:52:09 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 28 May 2018 12:52:09 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527511929.11.0.682650639539.issue32374@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:


New changeset 983c1ba94aef945386001932c5744f8ce9757fec by Petr Viktorin (Miss Islington (bot)) in branch '3.7':
bpo-32374: Ignore Python-level exceptions in test_bad_traverse (GH-7145) (GH-7150)
https://github.com/python/cpython/commit/983c1ba94aef945386001932c5744f8ce9757fec


----------

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

From report at bugs.python.org  Mon May 28 09:06:57 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Mon, 28 May 2018 13:06:57 +0000
Subject: [docs] [issue33666] os.errno gone AWOL
Message-ID: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>


New submission from Miro Hron?ok <miro at hroncok.cz>:

In 3.7.0b4 I see the following traceback:

>>> import os
>>> os.errno
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'os' has no attribute 'errno'

This was not the case for Python 3.6:

>>> import os
>>> os.errno
<module 'errno' (built-in)>

os.errno might not have been documented, however there are projects out there that use it:

https://github.com/intel/bmap-tools/issues/34
https://bugzilla.redhat.com/show_bug.cgi?id=1583196

So I suggest the removal of os.errno is something worth documenting at https://docs.python.org/3.7/whatsnew/3.7.html

The root of the change is in https://github.com/python/cpython/pull/1269/files#diff-405b29928f2a3ae216e45afe9b5d0c60

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 317847
nosy: docs at python, hroncok
priority: normal
severity: normal
status: open
title: os.errno gone AWOL
type: behavior
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon May 28 09:33:13 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 May 2018 13:33:13 +0000
Subject: [docs] [issue33666] os.errno gone AWOL
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527514393.57.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

os.errno as well as os.sys or os.abc is an implementation detail. It can be changed without notice even in a bugfix release. Projects that depend on it are incorrect and should be fixed.

----------
nosy: +serhiy.storchaka
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon May 28 10:29:44 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 28 May 2018 14:29:44 +0000
Subject: [docs] [issue33666] os.errno gone AWOL
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527517784.88.0.682650639539.issue33666@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

I think this was closed prematurely.

> Projects that depend on it are incorrect and should be fixed.

That's definitely correct; no one here is arguing against it.
However, there are projects out there depending on it -- it worked since around Python 2.5, and is readily available in `os.` tab completion.
I think that documenting the removal would be good for our users.

Furthermore, not all of its uses can be fixed. I've seen it printed in books. There are many answers/guides/tutorials around mentioning os.errno, for example:
http://nullege.com/codes/search/os.errno.EACCES
https://ubuntuforums.org/showthread.php?t=1459923
http://code.activestate.com/recipes/580759-show-os-error-codes-and-messages-from-the-oserrno-/
https://www.georgevreilly.com/blog/2016/03/24/RaisingIOErrorForFileNotFound.html

... and people tend based their code on such recipes, rather than checking what's documented.


And, of course, projects run into this:
https://github.com/intel/bmap-tools/issues/34
https://bugzilla.redhat.com/show_bug.cgi?id=1583196
https://github.com/python/typeshed/issues/1646

----------
nosy: +petr.viktorin
resolution: not a bug -> 
status: closed -> open

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

From report at bugs.python.org  Mon May 28 10:34:17 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 May 2018 14:34:17 +0000
Subject: [docs] [issue33666] os.errno gone AWOL
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527518057.01.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

> os.errno as well as os.sys or os.abc is an implementation detail.

I agree but...

> It can be changed without notice even in a bugfix release. Projects that depend on it are incorrect and should be fixed.

I don't think that it would hurt to document the removal of "os.errno" in "Porting to Python 3.7":
https://docs.python.org/dev/whatsnew/3.7.html#changes-in-python-behavior

Miro: are you volunteer to write such change?

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

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

From report at bugs.python.org  Mon May 28 10:36:21 2018
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Mon, 28 May 2018 14:36:21 +0000
Subject: [docs] [issue33666] os.errno gone AWOL
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527518181.95.0.682650639539.issue33666@psf.upfronthosting.co.za>


Miro Hron?ok <miro at hroncok.cz> added the comment:

I can document this, yes. I've opened this issue so I could prep a PR.

----------

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

From report at bugs.python.org  Mon May 28 10:57:55 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 May 2018 14:57:55 +0000
Subject: [docs] [issue33666] os.errno gone AWOL
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527519475.01.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

If document disappearing of os.errno, we should document disappearing of all other names in other modules in all versions. It is possible to write a script that outputs dir(mod) for all modules and compare results between different Python versions. Are you volunteer to do this work?

----------

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

From report at bugs.python.org  Mon May 28 10:58:46 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 May 2018 14:58:46 +0000
Subject: [docs] [issue33666] os.errno gone absent without official leave
 (AWOL)
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527519526.44.0.262363346258.issue33666@psf.upfronthosting.co.za>


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


----------
title: os.errno gone AWOL -> os.errno gone absent without official leave (AWOL)

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

From report at bugs.python.org  Mon May 28 11:00:20 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 May 2018 15:00:20 +0000
Subject: [docs] [issue33666] os.errno gone absent without official leave
 (AWOL)
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527519620.49.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

> If document disappearing of os.errno, we should document disappearing of all other names in other modules in all versions.

Miro proposed to document the removal of os.errno since errno is a commonly used module, as the os module.

I don't think that the removal of other aliases are as important as that one.

By the way, os.errno has been removed by bpo-30152: PR 1269.

----------

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

From report at bugs.python.org  Mon May 28 11:17:48 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 28 May 2018 15:17:48 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527520668.7.0.262363346258.issue33666@psf.upfronthosting.co.za>


Change by Petr Viktorin <encukou at gmail.com>:


----------
title: os.errno gone absent without official leave (AWOL) -> Document removal of os.errno

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

From report at bugs.python.org  Mon May 28 11:32:17 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 May 2018 15:32:17 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527521537.16.0.262363346258.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +6791

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

From report at bugs.python.org  Mon May 28 11:58:46 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 May 2018 15:58:46 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527523126.59.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

Here is a list of all names removed in 3.7 (except modules that was removed as a whole):

abc.WeakSet
argparse._collections
argparse._copy
argparse._ensure_value
argparse._textwrap
ast._NUM_TYPES
asyncio.async
asyncio.base_events.compat
asyncio.base_events.coroutine
asyncio.base_events._ensure_resolved
asyncio.base_events.inspect
asyncio.base_events._is_dgram_socket
asyncio.base_events._is_stream_socket
asyncio.base_futures.events
asyncio.base_subprocess.compat
asyncio.base_subprocess.coroutine
asyncio.coroutines._AwaitableABC
asyncio.coroutines.compat
asyncio.coroutines._CoroutineABC
asyncio.coroutines.debug_wrapper
asyncio.coroutines.events
asyncio.coroutines._inspect_iscoroutinefunction
asyncio.coroutines.opcode
asyncio.coroutines._types_coroutine
asyncio.coroutines._types_CoroutineType
asyncio.coroutines._YIELD_FROM
asyncio.coroutines._YIELD_FROM_BUG
asyncio.events.compat
asyncio.events.constants
asyncio.events.extract_stack
asyncio.events._format_args_and_kwargs
asyncio.events._format_callback
asyncio.events._format_callback_source
asyncio.events.functools
asyncio.events._get_function_source
asyncio.events.inspect
asyncio.events.reprlib
asyncio.events.traceback
asyncio.futures.compat
asyncio.futures.traceback
asyncio.futures._TracebackLogger
asyncio.locks.compat
asyncio.proactor_events.compat
asyncio.queues.compat
asyncio.queues.coroutine
asyncio.selector_events.compat
asyncio.selector_events.coroutine
asyncio.selector_events._SelectorSslTransport
asyncio.selectors
asyncio.sslproto.compat
asyncio.sslproto._is_sslproto_available
asyncio.streams.compat
asyncio.streams.coroutine
asyncio.subprocess.coroutine
asyncio.tasks.async
asyncio.tasks.compat
asyncio.transports.compat
asyncio.unix_events.compat
asyncio.unix_events.coroutine
asyncio.unix_events._fspath
asyncio.unix_events._set_inheritable
asyncio.unix_events._set_nonblocking
code.argparse
collections.AsyncGenerator
collections.AsyncIterable
collections.AsyncIterator
collections.Awaitable
collections.ByteString
collections.Callable
collections._class_template
collections.Collection
collections.Container
collections.Coroutine
collections._field_template
collections.Generator
collections.Hashable
collections.ItemsView
collections.Iterable
collections.Iterator
collections.KeysView
collections.Mapping
collections.MappingView
collections.MutableMapping
collections.MutableSequence
collections.MutableSet
collections._repr_template
collections.Reversible
collections.Sequence
collections.Set
collections.Sized
collections.ValuesView
concurrent.futures.process.multiprocessing
concurrent.futures.process._shutdown
concurrent.futures.process.SimpleQueue
concurrent.futures.process._threads_queues
concurrent.futures.thread
concurrent.futures.ThreadPoolExecutor
distutils.cmd.install_misc
distutils.command.sdist.AsyncGeneratorType
distutils.command.sdist.BuiltinFunctionType
distutils.command.sdist.BuiltinMethodType
distutils.command.sdist.CCompilerError
distutils.command.sdist.CodeType
distutils.command.sdist.CompileError
distutils.command.sdist.coroutine
distutils.command.sdist.CoroutineType
distutils.command.sdist.dep_util
distutils.command.sdist.DistutilsArgError
distutils.command.sdist.DistutilsByteCompileError
distutils.command.sdist.DistutilsClassError
distutils.command.sdist.DistutilsError
distutils.command.sdist.DistutilsExecError
distutils.command.sdist.DistutilsFileError
distutils.command.sdist.DistutilsGetoptError
distutils.command.sdist.DistutilsInternalError
distutils.command.sdist.DistutilsModuleError
distutils.command.sdist.DistutilsPlatformError
distutils.command.sdist.DistutilsSetupError
distutils.command.sdist.DynamicClassAttribute
distutils.command.sdist.FrameType
distutils.command.sdist.FunctionType
distutils.command.sdist.GeneratorType
distutils.command.sdist.GetSetDescriptorType
distutils.command.sdist.LambdaType
distutils.command.sdist.LibError
distutils.command.sdist.LinkError
distutils.command.sdist.MappingProxyType
distutils.command.sdist.MemberDescriptorType
distutils.command.sdist.MethodType
distutils.command.sdist.ModuleType
distutils.command.sdist.new_class
distutils.command.sdist.prepare_class
distutils.command.sdist.PreprocessError
distutils.command.sdist.SimpleNamespace
distutils.command.sdist.TracebackType
distutils.command.sdist.UnknownFileError
doctest.argparse
email.utils.ecre
enum._or_
enum.reduce
functools.MappingProxyType
functools.WeakKeyDictionary
gettext.copy
gettext.ENOENT
gettext.io
gettext.struct
http.client.os
http.cookies._warn_deprecated_setter
http.server.argparse
importlib._bootstrap_external._code_to_bytecode
importlib._bootstrap_external._validate_bytecode_header
inspect.ast
json.tool.collections
lib2to3.pgen2.grammar.tokenize
lib2to3.pgen2.tokenize.t
lib2to3.pytree.warnings
lib2to3.refactor._from_system_newlines
lib2to3.refactor._open_with_encoding
lib2to3.refactor._to_system_newlines
locale.collections
logging.config.thread
modulefinder.struct
multiprocessing.forkserver.read_unsigned
multiprocessing.forkserver.UNSIGNED_STRUCT
multiprocessing.forkserver.write_unsigned
multiprocessing.reduction.abstractmethod
ntpath.splitunc
os.errno
os.stat_float_times
pathlib.contextmanager
plistlib.Dict
plistlib._InternalDict
plistlib.Plist
profile.OptionParser
profile.os
re._alphanum_bytes
re._alphanum_str
re._pattern_type
socketserver.errno
sre_compile.RANGE_IGNORE
sre_constants.RANGE_IGNORE
sre_parse._parse_sub_cond
sre_parse.RANGE_IGNORE
ssl.ipaddress
ssl.re
ssl.textwrap
statistics.chain
statistics.decimal
subprocess._PLATFORM_DEFAULT_CLOSE_FDS
tabnanny.getopt
tarfile.__cvsid__
tarfile.__date__
token.ASYNC
token.AWAIT
tokenize.ASYNC
tokenize.AWAIT
trace.argparse
types._collections_abc
types._functools
typing._Any
typing.CallableMeta
typing._ClassVar
typing._collections_abc
typing.collections_abc
typing._FinalTypingBase
typing._ForwardRef
typing._G_base
typing.GenericMeta
typing._generic_new
typing._get_type_vars
typing._make_subclasshook
typing._next_in_mro
typing._NoReturn
typing._no_slots_copy
typing._Optional
typing._PY36
typing._qualname
typing._replace_arg
typing._subs_tree
typing._trim_name
typing.TupleMeta
typing._TypeAlias
typing._type_vars
typing._TypingBase
typing.TypingMeta
typing._Union
unittest.util._ordered_count
unittest.util.OrderedDict
urllib.request.collections
uuid.ctypes
uuid.lib
uuid.libname
uuid._unixdll_getnode
uuid._uuid_generate_time
weakref.collections
zipfile.re

----------

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

From report at bugs.python.org  Mon May 28 12:24:57 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 May 2018 16:24:57 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527524697.74.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

And here is a list of names removed in 3.6:

asynchat.fifo
asyncio.coroutines.futures
asyncio.futures.Error
asyncio.futures.reprlib
asyncio.tasks.linecache
asyncio.tasks.traceback
copy.builtins
copy._copy_with_constructor
copy._copy_with_copy_method
copy._EmptyClass
copy.name
copy.PyStringMap
copy.t
copy.weakref
datetime._divide_and_round
distutils.command.config.sys
distutils.command.register.os
distutils.command.register.string
distutils.command.sdist.string
distutils.extension.sys
distutils.text_file.os
email.feedparser.message
email.header._embeded_header
email._header_value_parser._Folded
email.message.warnings
ensurepip._MISSING_SSL_MESSAGE
ensurepip._require_ssl_for_pip
ensurepip.ssl
fileinput.DEFAULT_BUFSIZE
ftplib.os
ftplib.warnings
glob.glob2
http.server._quote_html
importlib._bootstrap_external._BACKCOMPAT_MAGIC_NUMBER
importlib._bootstrap_external._verbose_message
importlib._bootstrap.FileFinder
importlib._bootstrap._ManageReload
importlib._bootstrap._POPULATE
importlib._bootstrap.SourceFileLoader
importlib.util._BACKCOMPAT_MAGIC_NUMBER
importlib.util._Module
inspect.getmoduleinfo
inspect.ModuleInfo
lib2to3.fixer_util.islice
lib2to3.fixes.fix_dict.ArgList
lib2to3.fixes.fix_dict.LParen
lib2to3.fixes.fix_dict.RParen
lib2to3.fixes.fix_dict.token
lib2to3.fixes.fix_exec.pytree
lib2to3.fixes.fix_filter.Call
lib2to3.fixes.fix_filter.token
lib2to3.fixes.fix_has_key.token
lib2to3.fixes.fix_metaclass.Name
lib2to3.fixes.fix_nonzero.syms
lib2to3.fixes.fix_print.is_tuple
lib2to3.fixes.fix_types.token
lib2to3.fixes.fix_urllib.fixer_base
lib2to3.fixes.fix_zip.Call
lib2to3.patcomp.os
lib2to3.patcomp._PATTERN_GRAMMAR_FILE
lib2to3.refactor.bu
lib2to3.refactor.with_statement
multiprocessing.connection.ForkingPickler
multiprocessing.heap.context
multiprocessing.managers.context
multiprocessing.popen_forkserver.context
multiprocessing.popen_spawn_posix.context
multiprocessing.queues.ForkingPickler
multiprocessing.sharedctypes.ForkingPickler
multiprocessing.spawn.pickle
os._DummyDirEntry
os._dummy_scandir
pathlib._cached
pyclbr.itemgetter
pyclbr.os
_pyio.array
re._cache_repl
re.sys
site.aliasmbcs
site.CONFIG_LINE
sre_parse.isdigit
sre_parse.isident
sre_parse.isname
ssl._import_symbols
statistics._decimal_to_ratio
tarfile.TarIter
trace._err_exit
trace.find_executable_linenos
trace.find_lines
trace.find_lines_from_code
trace.find_strings
trace.fullmodname
trace.Ignore
trace.modname
trace.rx_blank
trace.usage
trace._usage
trace._warn
turtledemo.bytedesign.math
turtledemo.planet_and_moon.sleep
typing._geqv
typing._gorg
unittest.mock.DescriptorTypes
unittest.mock._slotted
wsgiref.simple_server.BufferedWriter
xml.etree.ElementTree._IterParseIterator

----------

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

From report at bugs.python.org  Mon May 28 12:37:14 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 May 2018 16:37:14 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1527525434.38.0.682650639539.issue32374@psf.upfronthosting.co.za>


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


New changeset 6ec325d48348fb52a421354ba563ff9c1f368054 by Miss Islington (bot) in branch '3.6':
bpo-32374: Ignore Python-level exceptions in test_bad_traverse (GH-7145)
https://github.com/python/cpython/commit/6ec325d48348fb52a421354ba563ff9c1f368054


----------

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

From report at bugs.python.org  Mon May 28 15:59:49 2018
From: report at bugs.python.org (Ned Deily)
Date: Mon, 28 May 2018 19:59:49 +0000
Subject: [docs] [issue32523] inconsistent spacing in changelog.html
In-Reply-To: <1515514882.86.0.467229070634.issue32523@psf.upfronthosting.co.za>
Message-ID: <1527537589.46.0.682650639539.issue32523@psf.upfronthosting.co.za>


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

@mdk, Would you have time to take a look at this?  Thanks!

----------
nosy: +mdk
versions: +Python 3.8

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

From report at bugs.python.org  Mon May 28 20:35:42 2018
From: report at bugs.python.org (A.M. Kuchling)
Date: Tue, 29 May 2018 00:35:42 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1527554142.68.0.682650639539.issue33649@psf.upfronthosting.co.za>


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

The plan for updating things looks good, and I think the ordering of
tasks is good -- rearranging the APIs is a pretty simple first step,
and it matches other chapters in the Library Reference, which list
more important modules first and more specialized obscure modules
later.  Then we can work on writing the additional material.

Yury: do you want to do the re-organization into high- and low-level APIs?  If you'd like me to do it, I'll need a more explicit listing of which APIs fall into which category.  Also, do we want to create an explicit high-level and low-level sections and push everything else down a level, or just leave it implicit in the ordering?

----------

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

From report at bugs.python.org  Tue May 29 05:06:14 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 29 May 2018 09:06:14 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527584774.36.0.682650639539.issue33666@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

Nothing there strikes me to be as prevalent or as discoverable as os.errno.

----------

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

From report at bugs.python.org  Tue May 29 05:21:01 2018
From: report at bugs.python.org (INADA Naoki)
Date: Tue, 29 May 2018 09:21:01 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527585661.7.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

Even if it is documented, arn't people know it by running their code on Python 3.7?  How the document help them?
It's very easy to know `errno` module when find ImportError.  And it's much easier than checking "waht's new" document.  So I doubt it's worth.

And if people see the document, people may think "all removed subimports should be documented" although only os.errno is special.

If document os.errno removal, please note about all undocumented subimports are implementation detail and will be removed without any timing, even on micro version.  (We will remove subimports for various reasons; avoiding huge unnecessary dependency, fixing regression caused by circular imports, etc...)

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

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

From report at bugs.python.org  Tue May 29 05:30:57 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 May 2018 09:30:57 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527586257.72.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

Actually removing re._pattern_type, uuid._uuid_generate_time and some private names in the typing module broke several third-party projects. See for example:

https://github.com/search?q=_pattern_type&type=Issues
https://github.com/search?q=_uuid_generate_time&type=Issues
https://github.com/bintoro/overloading.py/issues/5
https://github.com/hsolbrig/PyShEx/issues/17

I'm sure there are examples for other removed names. I don't understand why os.errno should be special.

Books can contain errors (e.g. the claim that Python 3 is not Turing complete).

----------

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

From report at bugs.python.org  Tue May 29 05:33:07 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 29 May 2018 09:33:07 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527586387.11.0.682650639539.issue33666@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

> Even if it is documented, arn't people know it by running their code on Python 3.7?  How the document help them?

"What's new" is the right place to check if something breaks for you on Python 3.7. Let's make it useful.

> It's very easy to know `errno` module when find ImportError.  And it's much easier than checking "waht's new" document.  So I doubt it's worth.

I disagree. Sure, some people will find answers on Stack Overflow or blog posts, but all those should link to official docs.

> And if people see the document, people may think "all removed subimports should be documented" although only os.errno is special.
> If document os.errno removal, please note about all undocumented subimports are implementation detail and will be removed without any timing, even on micro version.  (We will remove subimports for various reasons; avoiding huge unnecessary dependency, fixing regression caused by circular imports, etc...)

+1. Let's make that the main point. Something like the text below?

Several undocumented internal imports were removed. One example is that `os.errno` is no longer available; use `import errno` directly instead.
Note that such undocumented internal imports may be removed any time without notice, even in micro version releases.

----------

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

From report at bugs.python.org  Tue May 29 05:40:44 2018
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 29 May 2018 09:40:44 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527586844.9.0.682650639539.issue33666@psf.upfronthosting.co.za>


Petr Viktorin <encukou at gmail.com> added the comment:

> Actually removing re._pattern_type, uuid._uuid_generate_time and some private names in the typing module broke several third-party projects.

Those have underscores; that explicitly marks them as private/use at your own risk/will break in future versions.

----------

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

From report at bugs.python.org  Tue May 29 06:41:44 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 May 2018 10:41:44 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527590504.87.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

I like the idea of a generic sentence explaining that regularly we removed aliases to speedup Python startup time can remove aliases on purpose.

msg317876: "Here is a list of all names removed in 3.7 (except modules that was removed as a whole): (... long list ...)"

I agree that this list is very long. But I don't think that it would make sense to document all these removed symbols (aliases). IHMO it's more unlikely that someone gets the re module from "zipfile.re", than getting WeakSet from "abc.WeakSet". For "code.argparse", it's similar: the code module is a rarely used module, whereas argparse is a commonly used and known module.


My comments on the list.

Is already documented:

* os.stat_float_times: https://docs.python.org/dev/whatsnew/3.7.html#api-and-feature-removals
* collections.<many ABC classes>: https://docs.python.org/dev/whatsnew/3.7.html#id3
* token.ASYNC, token.AWAIT, tokenize.ASYNC, tokenize.AWAIT: they became keywords

Should be documented:

* os.errno: errno and os are tighly coupled, for example there is a os.strerror() function and OSError exception (named starting with "os") have an errno attribute

May be documented:

* inspect.ast: ast and inspect are tighly coupled to inspect code

Should not be documented:

* asyncio.*
* distutils.*
* concurrent.futures.*
* gettext.*

* code.argparse
* doctest.argparse
* profile.os
* ssl.ipaddress
* ssl.re
* ssl.textwrap
* statistics.decimal
* tabnanny.getopt
* zipfile.re

* email.utils.ecre
* functools.MappingProxyType
* functools.WeakKeyDictionary
* locale.collections
* ...

----------

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

From report at bugs.python.org  Tue May 29 06:42:23 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 May 2018 10:42:23 +0000
Subject: [docs] [issue33666] Document removal of os.errno
In-Reply-To: <1527512817.93.0.682650639539.issue33666@psf.upfronthosting.co.za>
Message-ID: <1527590543.45.0.682650639539.issue33666@psf.upfronthosting.co.za>


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

Petr Viktorin started a thread on python-ideas as well:
https://mail.python.org/pipermail/python-ideas/2018-May/051098.html

----------

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

From report at bugs.python.org  Tue May 29 14:37:11 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 29 May 2018 18:37:11 +0000
Subject: [docs] [issue30935] document the new behavior of get_event_loop()
 in Python 3.6
In-Reply-To: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
Message-ID: <1527619031.43.0.682650639539.issue30935@psf.upfronthosting.co.za>


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


New changeset e55de2d77f10d524be0b426e587fbc820f76de71 by Yury Selivanov (Mandeep Singh) in branch 'master':
bpo-30935: update get_event_loop docs (GH-2731)
https://github.com/python/cpython/commit/e55de2d77f10d524be0b426e587fbc820f76de71


----------

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

From report at bugs.python.org  Tue May 29 14:38:29 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 May 2018 18:38:29 +0000
Subject: [docs] [issue30935] document the new behavior of get_event_loop()
 in Python 3.6
In-Reply-To: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
Message-ID: <1527619109.04.0.262363346258.issue30935@psf.upfronthosting.co.za>


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


----------
keywords: +patch
pull_requests: +6845

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

From report at bugs.python.org  Tue May 29 14:39:19 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 May 2018 18:39:19 +0000
Subject: [docs] [issue30935] document the new behavior of get_event_loop()
 in Python 3.6
In-Reply-To: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
Message-ID: <1527619159.47.0.262363346258.issue30935@psf.upfronthosting.co.za>


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


----------
pull_requests: +6846

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

From report at bugs.python.org  Tue May 29 15:29:00 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 May 2018 19:29:00 +0000
Subject: [docs] [issue30935] document the new behavior of get_event_loop()
 in Python 3.6
In-Reply-To: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
Message-ID: <1527622140.27.0.682650639539.issue30935@psf.upfronthosting.co.za>


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


New changeset ca64f3ee5acf61e096eb1bb9fba3baeff0610de4 by Miss Islington (bot) in branch '3.7':
bpo-30935: update get_event_loop docs (GH-2731)
https://github.com/python/cpython/commit/ca64f3ee5acf61e096eb1bb9fba3baeff0610de4


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

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

From report at bugs.python.org  Tue May 29 15:33:31 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 May 2018 19:33:31 +0000
Subject: [docs] [issue30935] document the new behavior of get_event_loop()
 in Python 3.6
In-Reply-To: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
Message-ID: <1527622411.51.0.682650639539.issue30935@psf.upfronthosting.co.za>


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


New changeset 51bf38f796c74c7dac5a3d09ad0004494470091c by Miss Islington (bot) in branch '3.6':
bpo-30935: update get_event_loop docs (GH-2731)
https://github.com/python/cpython/commit/51bf38f796c74c7dac5a3d09ad0004494470091c


----------

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

From report at bugs.python.org  Tue May 29 16:20:33 2018
From: report at bugs.python.org (Mark Roseman)
Date: Tue, 29 May 2018 20:20:33 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1527625232.95.0.682650639539.issue33479@psf.upfronthosting.co.za>


Mark Roseman <mark at markroseman.com> added the comment:

Ivan, thanks for making a good first pass of this. The thread section still feels a lot like 'fighting' with the model. Do you mind if I take a crack at it? Won't get to it for a few days, but in case you have any stuff you're in the middle of. 

I should clarify too that Tk apps almost universally do use a blocking event loop (i.e. 'vwait forever' at the end of a script). Application-level event handlers are supposed to respond quickly so control goes back to the event loop.

It's when control doesn't return there that things like the 'update idletasks' hacks are needed. In practice, I've noticed that's what seems to trip people up when they first start, as they try to emulate the flow of their non-GUI code, which frequently blocks. Far better that the program is restructured so that the event handler completes quickly. It's actually worse than it looks, because you can end up having nested event loops if you start randomly throwing this stuff in. That's conceptually hard for most people and a good source of bugs.

----------

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

From report at bugs.python.org  Tue May 29 17:31:01 2018
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 May 2018 21:31:01 +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: <1527629461.68.0.262363346258.issue33640@psf.upfronthosting.co.za>


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


----------
keywords: +easy
title: uuid: endian of the bytes argument is not documented -> [EASY DOC] uuid: endian of the bytes argument is not documented

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

From report at bugs.python.org  Tue May 29 18:39:30 2018
From: report at bugs.python.org (Tobias Kunze)
Date: Tue, 29 May 2018 22:39:30 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1527633570.01.0.682650639539.issue22021@psf.upfronthosting.co.za>


Tobias Kunze <r at rixx.de> added the comment:

I'm similarly confused by this issue. If somebody can help me understand what's going on, I'll put my understanding into a documentation patch.

I have created this minimal example to demonstrate what I don't understand: I've created a directory structure within /tmp like this:

issue22021
??? root
    ??? structure
        ??? content
        ??? ??? please_add.txt
        ??? do_not_add.txt


Now I'd like to create a zip archive that contains the directories "structure" and "content", and the file "please_add.txt", but not the file "do_not_add.txt". My understanding of the documentation was that I'd have to do this:

>>> shutil.make_archive(base_name='/tmp/issue22021archive', format='zip', root_dir='/tmp/issue22021/root', base_dir='/tmp/issue22021/root/structure/content')

But on my system, the created file (/tmp/issue22021archive.zip) looks like this according to unzip -l:

Archive:  issue22021archive.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  2018-05-30 00:26   tmp/issue22021/root/structure/content/
        0  2018-05-30 00:26   tmp/issue22021/root/structure/content/please_add.txt
---------                     -------
        0                     2 files

This is consistent with my experience that created archives will always contain directories from / on, which is unexpected to me.

It appears this happens whenever base_dir and root_dir is set, but to my understanding the documentation does not warn against this.

I've confirmed this behaviour with Python 3.6.5 and Python 3.5.3, but I suspect that doesn't really matter, as it seems to be a documentation issue.

----------
nosy: +rixx

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

From report at bugs.python.org  Tue May 29 18:50:47 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 29 May 2018 22:50:47 +0000
Subject: [docs] [issue30935] document the new behavior of get_event_loop()
 in Python 3.6
In-Reply-To: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
Message-ID: <1527634247.66.0.262363346258.issue30935@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue May 29 22:14:49 2018
From: report at bugs.python.org (Ivan Pozdeev)
Date: Wed, 30 May 2018 02:14:49 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1527625232.95.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <24adc805-6c6d-231e-c3f7-5be53f75d881@mail.ru>


Ivan Pozdeev <ivan_pozdeev at mail.ru> added the comment:

On 29.05.2018 23:20, Mark Roseman wrote:
> Mark Roseman <mark at markroseman.com> added the comment:
>
> Ivan, thanks for making a good first pass of this. The thread section still feels a lot like 'fighting' with the model. Do you mind if I take a crack at it? Won't get to it for a few days, but in case you have any stuff you're in the middle of.
>
> I should clarify too that Tk apps almost universally do use a blocking event loop (i.e. 'vwait forever' at the end of a script). Application-level event handlers are supposed to respond quickly so control goes back to the event loop.
>
> It's when control doesn't return there that things like the 'update idletasks' hacks are needed. In practice, I've noticed that's what seems to trip people up when they first start, as they try to emulate the flow of their non-GUI code, which frequently blocks. Far better that the program is restructured so that the event handler completes quickly. It's actually worse than it looks, because you can end up having nested event loops if you start randomly throwing this stuff in. That's conceptually hard for most people and a good source of bugs.
>
I'm pretty much done with the threading section but if you think it 
could use more clarification, sure. You can make a PR against my branch 
to integrate changes (or vice versa).

In line with the aforementioned plan, the "Threading model" section 
needs to tell these things critical to interstanding the module's 
behavior and usage patterns:

* There are two basic GUI execution models (stricty speaking, these are 
event-driven models in general, but no need to go that deep): single 
thread with pumping messages by hand (read: cooperative multitasking), 
and UI thread + worker threads (read: preemptive mulitasking). The 
latter is prevalent now so the reader is more likely to be familiar with it.
* Tcl/Tk implements the former model (which is unusual), Tkinter 
emulates the latter with its own logic (so Tcl/Tk docs won't have info 
on this) but supports the former one as well. (So update() is not a 
"hack" at all, it's just intended for a different use case that doesn't 
come up often.)
* Tkinter calls can and should be made from any threads (this is also 
unusual), but there are user-visible limitations.
* Tcl event loop is shared (another unusual gimmick), which is also 
user-visible.

This section is not the place to showcase concrete usage patterns, 
that's what tutorials are for. But it can make references to relevant 
Tkinter functions as long as this doesn't garble the narration.

I imagine tutorial as a separate page (see the plan how it should be 
linked to), with the following sections, each illustrated with code. 
It's not meant to be an essential part of this ticket because it's of 
lower priority.

* Create initial UI, then run mainloop(). All the rest is done with ui 
commands and events. (a hello world example)
* Start a worker thread for any action that may take more than a 
fraction of a second. Make Tkinter calls from the worker thread to pass 
back info on its progress.
* Collect worker threads and do other cleanup at exit via a cleanup 
function. Call it from both a special exit command, if any, _and_ from 
.protocol("WM_DELETE_WINDOW"). Lengthy/perpetual worker threads' logic 
must be interruptable for this.
* For more complex logic, use the Model-View-Presenter pattern.
* ?Something about exception handling? (Propagating exceptions? Making 
unhandled exceptions visible to the user? I dunno atm)
* An example of using Tcl's execution model, i.e. with 
dooneevent()/update()/update_idletasks() instead of mainloop(), like a 
Tcl program would do.

----------
nosy: +__Vano

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

From report at bugs.python.org  Tue May 29 23:50:59 2018
From: report at bugs.python.org (bananaappletw)
Date: Wed, 30 May 2018 03:50:59 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1527652259.43.0.682650639539.issue22021@psf.upfronthosting.co.za>


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

I think this snippet might help you.

shutil.make_archive(base_name='/tmp/issue22021archive', format='zip', root_dir='/tmp/issue22021/root/', base_dir='structure/content/')

unzip -l /tmp/issue22021archive.zip

Archive:  /tmp/issue22021archive.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  2018-05-30 11:14   structure/content/
        0  2018-05-30 11:02   structure/content/please_add.txt
---------                     -------
        0                     2 files

----------

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

From report at bugs.python.org  Tue May 29 23:53:59 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 30 May 2018 03:53:59 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1527652439.79.0.682650639539.issue33649@psf.upfronthosting.co.za>


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

> Yury: do you want to do the re-organization into high- and low-level APIs?  If you'd like me to do it, I'll need a more explicit listing of which APIs fall into which category.

Sure, I'll update this issue tomorrow or the day after with a more detailed plan.  Or maybe I'll start working on the 1st PR and will just give you push privileges to my repo.  Would be cool if we can push the first rewrite live as soon as possible.

> Also, do we want to create an explicit high-level and low-level sections and push everything else down a level, or just leave it implicit in the ordering?

Yes, I'd go for 2 explicitly separate sections.  I think it's important to focus average readers' attention at the high-level bits and pieces, leaving low-level APIs and details to framework/library authors.

And, again, thanks for help.

Adding Carol to the nosy list as she seems to be interested in this topic too.

----------
nosy: +willingc

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

From report at bugs.python.org  Wed May 30 07:45:44 2018
From: report at bugs.python.org (Tobias Kunze)
Date: Wed, 30 May 2018 11:45:44 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1527680744.57.0.682650639539.issue22021@psf.upfronthosting.co.za>


Tobias Kunze <r at rixx.de> added the comment:

Thank you, that's what I figured out later last evening. To my understanding, the docs don't give any indication that base_dir is supposed to be relative to root_dir, so I'd add this information, and maybe add a similar example to the one above, if that's appropriate?

----------

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

From report at bugs.python.org  Wed May 30 08:35:16 2018
From: report at bugs.python.org (R. David Murray)
Date: Wed, 30 May 2018 12:35:16 +0000
Subject: [docs] [issue22021] shutil.make_archive()  root_dir do not work
In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za>
Message-ID: <1527683715.93.0.682650639539.issue22021@psf.upfronthosting.co.za>


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

Sounds reasonable to me.

----------

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

From report at bugs.python.org  Wed May 30 13:12:41 2018
From: report at bugs.python.org (Vladimir Chebotarev)
Date: Wed, 30 May 2018 17:12:41 +0000
Subject: [docs] [issue33698] `._pth` does not allow to populate `sys.path`
 empty entry
Message-ID: <1527700361.05.0.682650639539.issue33698@psf.upfronthosting.co.za>


New submission from Vladimir Chebotarev <vladimir.chebotarev at gmail.com>:

Moving from bpo-29326
====
Hi Steve.

I'll try to explain what is my motivation.

I need a reliable way to run Python (not matter embedded or not) in isolated mode, but still having current directory in `sys.path` (empty entry).

Ironically I could misuse normal mode to simulate isolated mode with specified %PYTHONPATH% (which is not much handy, by the way), but hiding Windows Registry keys would look pretty hard (it is impossible to make a bat/cmd wrapper). Possibility to search %PYTHONPATH% in HKLM entries makes it even worse.

Empty entry in `sys.path` is a extremely popular thing, and many software depend on it. It looks like a bug that isolated mode cannot support such entry.

# How would I fix it.

Possibly we should allow another keyword for adding an empty entry (like we have an exclusion for `import site`).

Ideas are appreciated.

----------
assignee: docs at python
components: Documentation, Windows
messages: 318202
nosy: docs at python, excitoon, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
pull_requests: 6878
severity: normal
status: open
title: `._pth` does not allow to populate `sys.path` empty entry
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Wed May 30 13:32:53 2018
From: report at bugs.python.org (Vladimir Chebotarev)
Date: Wed, 30 May 2018 17:32:53 +0000
Subject: [docs] [issue33698] `._pth` does not allow to populate `sys.path`
 with empty entry
In-Reply-To: <1527700361.05.0.682650639539.issue33698@psf.upfronthosting.co.za>
Message-ID: <1527701573.33.0.262363346258.issue33698@psf.upfronthosting.co.za>


Change by Vladimir Chebotarev <vladimir.chebotarev at gmail.com>:


----------
title: `._pth` does not allow to populate `sys.path` empty entry -> `._pth` does not allow to populate `sys.path` with empty entry

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

From report at bugs.python.org  Wed May 30 15:39:42 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 30 May 2018 19:39:42 +0000
Subject: [docs] [issue33699] Don't describe try's else clause in a footnote
Message-ID: <1527709182.68.0.682650639539.issue33699@psf.upfronthosting.co.za>


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

This behavior has not changed in 11 years so I think it's safe to describe the "else" clause along the rest of the "try" clause.

Attached PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 318205
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Don't describe try's else clause in a footnote
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/issue33699>
_______________________________________

From report at bugs.python.org  Wed May 30 15:40:33 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 30 May 2018 19:40:33 +0000
Subject: [docs] [issue33699] Don't describe try's else clause in a footnote
In-Reply-To: <1527709182.68.0.682650639539.issue33699@psf.upfronthosting.co.za>
Message-ID: <1527709233.22.0.262363346258.issue33699@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May 30 16:55:07 2018
From: report at bugs.python.org (Mark Roseman)
Date: Wed, 30 May 2018 20:55:07 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1527713707.84.0.682650639539.issue33479@psf.upfronthosting.co.za>


Mark Roseman <mark at markroseman.com> added the comment:

I've made some changes to what Ivan started, which you can find here: https://github.com/roseman/cpython/tree/tkinter_docs

The first two commits are minor updates/improvements not really related to threading, and I suspect are uncontroversial. 

The last commit rewrites the thread model section. The main focus is on how things work in practice, and to eliminate what I previously referred to as "fighting" between the two models. 

It explains how Python and Tcl differ on threads, the mappings between threads and interpreters, etc.

It plays down the comparison to other GUI toolkit event models. It still highlights the difference for people familiar with them. It doesn't try to teach both models for those who don't know either (which includes those who may not have done much if any GUI programming) since that is extraneous to their present needs. It talks simply about why event handlers blocking is a bad thing. It avoids what I think are unnecessary details about Tcl in this context.

There is then an area for special cases that highlight the various actual trouble spots when it comes to threads, what can cause them, and how to avoid them. 

I hope this covers the real issues without overly complicating things. Any thoughts?

----------

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

From report at bugs.python.org  Wed May 30 17:45:56 2018
From: report at bugs.python.org (Steve Dower)
Date: Wed, 30 May 2018 21:45:56 +0000
Subject: [docs] [issue33698] `._pth` does not allow to populate `sys.path`
 with empty entry
In-Reply-To: <1527700361.05.0.682650639539.issue33698@psf.upfronthosting.co.za>
Message-ID: <1527716756.06.0.682650639539.issue33698@psf.upfronthosting.co.za>


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

If your ._pth includes `import site`, then including a blank line in a `anything.pth` file should add the entry.

Alternatively, if you can add "import sys; sys.path.insert(0, '')" to the start of your code that depends on it you should be fine.

----------

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

From report at bugs.python.org  Wed May 30 19:51:42 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 30 May 2018 23:51:42 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
Message-ID: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>


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

There are some missing links in production lists (try, with, from __future__ import), and function and coroutines definitions production lists have too long lines.

PR fixes this and does some polish on whitespace.

----------
assignee: docs at python
components: Documentation
messages: 318231
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Add some missings links in production lists and a little polish
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/issue33702>
_______________________________________

From report at bugs.python.org  Wed May 30 19:52:49 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Wed, 30 May 2018 23:52:49 +0000
Subject: [docs] [issue33702] Add some missings links in production lists and
 a little polish
In-Reply-To: <1527724302.5.0.682650639539.issue33702@psf.upfronthosting.co.za>
Message-ID: <1527724369.07.0.262363346258.issue33702@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed May 30 23:03:20 2018
From: report at bugs.python.org (Farhaan Bukhsh)
Date: Thu, 31 May 2018 03:03: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: <1527735800.56.0.262363346258.issue33640@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu May 31 00:39:03 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 May 2018 04:39:03 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527741543.32.0.682650639539.issue33641@psf.upfronthosting.co.za>


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


New changeset 0a36ac1a09587735237c5978ebd046313922869c by Serhiy Storchaka in branch 'master':
bpo-33641: Convert RFC references into links. (GH-7103)
https://github.com/python/cpython/commit/0a36ac1a09587735237c5978ebd046313922869c


----------

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

From report at bugs.python.org  Thu May 31 00:40:13 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 31 May 2018 04:40:13 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527741613.05.0.262363346258.issue33641@psf.upfronthosting.co.za>


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


----------
pull_requests: +6898

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

From report at bugs.python.org  Thu May 31 01:21:50 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 May 2018 05:21:50 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527744110.0.0.262363346258.issue33641@psf.upfronthosting.co.za>


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


----------
pull_requests: +6901

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

From report at bugs.python.org  Thu May 31 01:33:25 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 31 May 2018 05:33:25 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527744805.58.0.682650639539.issue33641@psf.upfronthosting.co.za>


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


New changeset 0f1a18326902ad3d0a30fdecbe40513cc5d85879 by Miss Islington (bot) in branch '3.7':
bpo-33641: Convert RFC references into links. (GH-7103)
https://github.com/python/cpython/commit/0f1a18326902ad3d0a30fdecbe40513cc5d85879


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

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

From report at bugs.python.org  Thu May 31 02:11:09 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 May 2018 06:11:09 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527747069.47.0.682650639539.issue33641@psf.upfronthosting.co.za>


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


New changeset 55d9e865cb3b50587c17c8a7beee090c4ac8d535 by Serhiy Storchaka in branch '3.6':
[3.6] bpo-33641: Convert RFC references into links. (GH-7103) (GH-7276)
https://github.com/python/cpython/commit/55d9e865cb3b50587c17c8a7beee090c4ac8d535


----------

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

From report at bugs.python.org  Thu May 31 02:26:33 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 May 2018 06:26:33 +0000
Subject: [docs] [issue33641] Add links to RFCs
In-Reply-To: <1527200094.65.0.682650639539.issue33641@psf.upfronthosting.co.za>
Message-ID: <1527747993.45.0.262363346258.issue33641@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu May 31 04:05:28 2018
From: report at bugs.python.org (Ivan Pozdeev)
Date: Thu, 31 May 2018 08:05:28 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1527753927.96.0.682650639539.issue33479@psf.upfronthosting.co.za>


Ivan Pozdeev <ivan_pozdeev at mail.ru> added the comment:

@markroseman I'm about 50% okay with your changes. Could you create a PR against my branch so we can work out the specifics?

----------

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

From report at bugs.python.org  Thu May 31 04:45:08 2018
From: report at bugs.python.org (Vladimir Chebotarev)
Date: Thu, 31 May 2018 08:45:08 +0000
Subject: [docs] [issue33698] `._pth` does not allow to populate `sys.path`
 with empty entry
In-Reply-To: <1527700361.05.0.682650639539.issue33698@psf.upfronthosting.co.za>
Message-ID: <1527756308.21.0.682650639539.issue33698@psf.upfronthosting.co.za>


Vladimir Chebotarev <vladimir.chebotarev at gmail.com> added the comment:

Unfortunately this is not true: "Blank lines and lines beginning with # are skipped." (https://docs.python.org/3/library/site.html#index-1)
I'm not sure we should change this behavior as it would make huge impact on usage of `pth` files by users (`._pth`, on the contrary, is the only one per distribution and managed by the distribution).

I could easily add `''` to `sys.path` manually if I had one script or even dozen of them, but as the solution that alternative is not acceptable. :(

----------

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

From report at bugs.python.org  Thu May 31 04:46:40 2018
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Thu, 31 May 2018 08:46:40 +0000
Subject: [docs] [issue33707] Doc:
Message-ID: <1527756400.46.0.682650639539.issue33707@psf.upfronthosting.co.za>


New submission from ???? ????????? <socketpair at gmail.com>:

https://docs.python.org/3/library/asyncio-sync.html#asyncio.Event :

Class implementing event objects. An event manages a flag that can be set to true with the set() method and reset to false with the clear() method. The ----->  wait()  <----- method blocks until the flag is true. The flag is initially false.

this link points to wrong place.

----------
assignee: docs at python
components: Documentation, asyncio
messages: 318268
nosy: asvetlov, docs at python, socketpair, yselivanov
priority: normal
severity: normal
status: open
title: Doc:
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu May 31 04:47:15 2018
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Thu, 31 May 2018 08:47:15 +0000
Subject: [docs] [issue33707] Doc:
In-Reply-To: <1527756400.46.0.682650639539.issue33707@psf.upfronthosting.co.za>
Message-ID: <1527756435.88.0.682650639539.issue33707@psf.upfronthosting.co.za>


???? ????????? <socketpair at gmail.com> added the comment:

Sorry, I did not

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

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

From report at bugs.python.org  Thu May 31 04:48:14 2018
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Thu, 31 May 2018 08:48:14 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
Message-ID: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>


New submission from ???? ????????? <socketpair at gmail.com>:

https://docs.python.org/3/library/asyncio-sync.html#asyncio.Event :

Class implementing event objects. An event manages a flag that can be set to true with the set() method and reset to false with the clear() method. The ----->  wait()  <----- method blocks until the flag is true. The flag is initially false.

this link points to wrong place.

----------
assignee: docs at python
components: Documentation, asyncio
messages: 318270
nosy: asvetlov, docs at python, socketpair, yselivanov
priority: normal
severity: normal
status: open
title: Doc: Asyncio's Event documentation typo.
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu May 31 05:02:46 2018
From: report at bugs.python.org (Paul Moore)
Date: Thu, 31 May 2018 09:02:46 +0000
Subject: [docs] [issue33698] `._pth` does not allow to populate `sys.path`
 with empty entry
In-Reply-To: <1527700361.05.0.682650639539.issue33698@psf.upfronthosting.co.za>
Message-ID: <1527757366.46.0.682650639539.issue33698@psf.upfronthosting.co.za>


Paul Moore <p.f.moore at gmail.com> added the comment:

You could add the line

    import sys; sys.path.insert(0, '')

to a .pth file. The documentation you pointed out states that lines starting with "import" are executed...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33698>
_______________________________________

From report at bugs.python.org  Thu May 31 05:31:01 2018
From: report at bugs.python.org (Timo Furrer)
Date: Thu, 31 May 2018 09:31:01 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
In-Reply-To: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>
Message-ID: <1527759061.6.0.682650639539.issue33708@psf.upfronthosting.co.za>


Timo Furrer <tuxtimo at gmail.com> added the comment:

It seems like it's pointing to the correct location, it's just that depending on the size of your screen the "wait" section is too far to the bottom and therefore it can't quite scroll to the heading of the wait heading so that it's on top of your screen ;)

----------
nosy: +tuxtimo

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33708>
_______________________________________

From report at bugs.python.org  Thu May 31 05:32:41 2018
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Thu, 31 May 2018 09:32:41 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
In-Reply-To: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>
Message-ID: <1527759161.09.0.682650639539.issue33708@psf.upfronthosting.co.za>


???? ????????? <socketpair at gmail.com> added the comment:

NO! it points to asyncio.wait() but should point to asyncio.Event.wait()

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33708>
_______________________________________

From report at bugs.python.org  Thu May 31 05:50:23 2018
From: report at bugs.python.org (Timo Furrer)
Date: Thu, 31 May 2018 09:50:23 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
In-Reply-To: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>
Message-ID: <1527760223.59.0.682650639539.issue33708@psf.upfronthosting.co.za>


Timo Furrer <tuxtimo at gmail.com> added the comment:

Yes, sorry, my bad.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33708>
_______________________________________

From report at bugs.python.org  Thu May 31 05:51:55 2018
From: report at bugs.python.org (Timo Furrer)
Date: Thu, 31 May 2018 09:51:55 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
In-Reply-To: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>
Message-ID: <1527760315.23.0.682650639539.issue33708@psf.upfronthosting.co.za>


Timo Furrer <tuxtimo at gmail.com> added the comment:

The link to the set method is also wrong. It points to https://docs.python.org/3/library/stdtypes.html#set instead of https://docs.python.org/3/library/asyncio-sync.html#asyncio.Event.set

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33708>
_______________________________________

From report at bugs.python.org  Thu May 31 06:15:47 2018
From: report at bugs.python.org (Timo Furrer)
Date: Thu, 31 May 2018 10:15:47 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
In-Reply-To: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>
Message-ID: <1527761747.37.0.682650639539.issue33708@psf.upfronthosting.co.za>


Timo Furrer <tuxtimo at gmail.com> added the comment:

I'm working on a patch :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33708>
_______________________________________

From report at bugs.python.org  Thu May 31 06:48:21 2018
From: report at bugs.python.org (Timo Furrer)
Date: Thu, 31 May 2018 10:48:21 +0000
Subject: [docs] [issue33708] Doc: Asyncio's Event documentation typo.
In-Reply-To: <1527756494.64.0.682650639539.issue33708@psf.upfronthosting.co.za>
Message-ID: <1527763701.11.0.262363346258.issue33708@psf.upfronthosting.co.za>


Change by Timo Furrer <tuxtimo at gmail.com>:


----------
keywords: +patch
pull_requests: +6905
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33708>
_______________________________________

From report at bugs.python.org  Thu May 31 07:12:06 2018
From: report at bugs.python.org (Timo Furrer)
Date: Thu, 31 May 2018 11:12:06 +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: <1527765126.96.0.262363346258.issue33600@psf.upfronthosting.co.za>


Change by Timo Furrer <tuxtimo at gmail.com>:


----------
keywords: +patch
pull_requests: +6906
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33600>
_______________________________________

From report at bugs.python.org  Thu May 31 10:57:16 2018
From: report at bugs.python.org (Mark Roseman)
Date: Thu, 31 May 2018 14:57:16 +0000
Subject: [docs] [issue33479] Document tkinter and threads
In-Reply-To: <1526184152.45.0.682650639539.issue33479@psf.upfronthosting.co.za>
Message-ID: <1527778636.92.0.262363346258.issue33479@psf.upfronthosting.co.za>


Change by Mark Roseman <mark at markroseman.com>:


----------
pull_requests: +6913

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33479>
_______________________________________

From report at bugs.python.org  Thu May 31 14:35:34 2018
From: report at bugs.python.org (Jay Crotts)
Date: Thu, 31 May 2018 18:35:34 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
Message-ID: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>


New submission from Jay Crotts <crotts.jay at gmail.com>:

The examples on using mock_open only include instances where objects are mocked in the REPL, so '__main__'.open is replaced. Commonly objects are mocked for use in other test modules, so builtins.open would be used instead.

A note about this in the documentation would be useful not familiar with python internals. I'm happy to do a PR for it.

----------
assignee: docs at python
components: Documentation
messages: 318337
nosy: docs at python, jcrotts
priority: normal
severity: normal
status: open
title: Document builtins in mock_open
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33722>
_______________________________________

From report at bugs.python.org  Thu May 31 16:20:01 2018
From: report at bugs.python.org (Tobias Kunze)
Date: Thu, 31 May 2018 20:20:01 +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: <1527798001.21.0.262363346258.issue32392@psf.upfronthosting.co.za>


Change by Tobias Kunze <r at rixx.de>:


----------
keywords: +patch
pull_requests: +6916
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32392>
_______________________________________

From report at bugs.python.org  Thu May 31 16:43:02 2018
From: report at bugs.python.org (Paul Koning)
Date: Thu, 31 May 2018 20:43:02 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1527799382.89.0.682650639539.issue33470@psf.upfronthosting.co.za>


Paul Koning <paulkoning at comcast.net> added the comment:

FYI, I'm the one who created this problem back in 2012.  I just submitted a GDB patch for this, using PyImport_AppendInittab to define the built-in module at startup.  I'm not sure how I missed this originally; perhaps the documentation was not as clear back then or maybe I just overlooked the information.  The patch eliminates the call to _PyImport_FixBuiltins.

----------
nosy: +pkoning

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33470>
_______________________________________

From report at bugs.python.org  Thu May 31 16:50:32 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 31 May 2018 20:50:32 +0000
Subject: [docs] [issue33470] Changes from GH-1638 (GH-3575,
 bpo-28411) are not documented in Porting to Python 3.7
In-Reply-To: <1526114406.62.0.682650639539.issue33470@psf.upfronthosting.co.za>
Message-ID: <1527799832.76.0.262363346258.issue33470@psf.upfronthosting.co.za>


Change by Ned Deily <nad at python.org>:


----------
nosy:  -ned.deily
priority: release blocker -> 
versions:  -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33470>
_______________________________________

From report at bugs.python.org  Thu May 31 23:03:25 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 01 Jun 2018 03:03:25 +0000
Subject: [docs] [issue33726] Add short descriptions to PEP references in
 seealso
Message-ID: <1527822205.22.0.682650639539.issue33726@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

There are a couple of PEP references with no description in Simple/Compound Statements.

Attached PR fixes this.

----------
assignee: docs at python
components: Documentation
messages: 318359
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: Add short descriptions to PEP references in seealso
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33726>
_______________________________________

From report at bugs.python.org  Thu May 31 23:03:42 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Fri, 01 Jun 2018 03:03:42 +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: <1527822222.8.0.262363346258.issue33726@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


----------
keywords: +patch
pull_requests: +6922
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33726>
_______________________________________

From atokarchuk at gazprom-media.tech  Wed May 30 16:37:18 2018
From: atokarchuk at gazprom-media.tech (=?utf-8?B?0KLQvtC60LDRgNGH0YPQuiDQkNGA0YLRg9GA?=)
Date: Wed, 30 May 2018 20:37:18 +0000
Subject: [docs] typo in
 https://docs.python.org/3.6/library/functions.html#max
Message-ID: <08D3A6BE-D317-4C04-8C55-D5EF12E34570@gazprom-media.tech>

max(iterable, *[, key, default])?

extra asterisk here,
optional params key and default are surrounded just by square brackets.

From dheintz at proterna.com  Tue May 29 14:52:30 2018
From: dheintz at proterna.com (David Heintz)
Date: Tue, 29 May 2018 11:52:30 -0700
Subject: [docs] Error on docs page?
Message-ID: <b9474c37-f463-f92e-8f88-eef3d9f8d2f8@proterna.com>

H'mm. The epubs link seems to point to a zip file containing HTML files. Was 
this the intent?
If not could you point me to epub version of documents.

Thanks for your help,

David Heintz

From rossano.giandomenico at live.com  Sun May 27 08:22:17 2018
From: rossano.giandomenico at live.com (rossano giandomenico)
Date: Sun, 27 May 2018 12:22:17 +0000
Subject: [docs] Info
Message-ID: <AM5P194MB00981A48EE760F26EDA55CEDF96F0@AM5P194MB0098.EURP194.PROD.OUTLOOK.COM>

Dear Python

https://docs.python.org/3/tutorial/venv.html

The venv module does not wotk how I may solve the problem to install package on Python 3.6 x64

Thanks for your attention

Regards

Rossano

Inviato da Posta<https://go.microsoft.com/fwlink/?LinkId=550986> per Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180527/a0af892c/attachment.html>

From slow.rabbit at free.fr  Sun May 27 09:33:40 2018
From: slow.rabbit at free.fr (SlowRabbit)
Date: Sun, 27 May 2018 15:33:40 +0200
Subject: [docs] I can't DL any of various manual version
Message-ID: <9d059f8e-286e-a0d9-db4a-a0e1c4b60bd5@free.fr>

Hi,

https://docs.python.org/fr/3/download.html

All I get is 404 error.

With 'save link as' I get a 1ko zip-file.

Solved, seems to be FR page behavior only.


-- 

      SlowRabbit