From report at bugs.python.org  Mon Apr  1 01:37:23 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 01 Apr 2019 05:37:23 +0000
Subject: [docs] [issue36490] Modernize function signature format in
 Archiving section of shutil doc
In-Reply-To: <1554005288.19.0.789880523073.issue36490@roundup.psfhosted.org>
Message-ID: <1554097042.98.0.0388563165224.issue36490@roundup.psfhosted.org>


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

I don' think they are modern-style vs legacy-style.

When explicit default value is present, the default value is documented in signature like `param=42`.
On the other hand, when default value is not explicit (just an placeholder), the parameter is expressed using optional group `[param]`.

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

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

From report at bugs.python.org  Mon Apr  1 05:27:07 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 01 Apr 2019 09:27:07 +0000
Subject: [docs] [issue27992] Clarify %(prog)s in argparse help formatter
 returns basename of sys.argv[0] by default
In-Reply-To: <1473217852.97.0.553971829799.issue27992@psf.upfronthosting.co.za>
Message-ID: <1554110827.4.0.196215111207.issue27992@roundup.psfhosted.org>


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

Thanks for the report. To be little more clear it returns the "basename of sys.argv[0]" at [0] than the attached patch that says "uses part of ``sys.argv[0]``" .

[0] https://github.com/python/cpython/blob/62f9588663ebfea1735e9d142ef527395a6c2b95/Lib/argparse.py#L1638

----------
nosy: +paul.j3, xtreak
title: In the argparse there is a misleading words about %(prog)s value -> Clarify %(prog)s in argparse help formatter returns basename of sys.argv[0] by default
versions: +Python 3.7, Python 3.8 -Python 3.6

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

From report at bugs.python.org  Mon Apr  1 09:57:00 2019
From: report at bugs.python.org (SilentGhost)
Date: Mon, 01 Apr 2019 13:57:00 +0000
Subject: [docs] [issue36497] Undocumented behavior in csv.Sniffer (preferred
 delimiters)
In-Reply-To: <1554126856.48.0.397677994988.issue36497@roundup.psfhosted.org>
Message-ID: <1554127020.16.0.948473518933.issue36497@roundup.psfhosted.org>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.8

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

From report at bugs.python.org  Mon Apr  1 11:08:59 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 01 Apr 2019 15:08:59 +0000
Subject: [docs] [issue36157] Document PyInterpreterState_Main().
In-Reply-To: <1551458200.72.0.727788487318.issue36157@roundup.psfhosted.org>
Message-ID: <1554131339.9.0.188170393069.issue36157@roundup.psfhosted.org>


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


New changeset 8c61739defd88c7f79e86537886c33745843ce01 by Miss Islington (bot) (Joannah Nanjekye) in branch 'master':
bpo-36157:Document PyInterpreterState_Main() (GH-12238)
https://github.com/python/cpython/commit/8c61739defd88c7f79e86537886c33745843ce01


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

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

From report at bugs.python.org  Mon Apr  1 11:09:34 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 01 Apr 2019 15:09:34 +0000
Subject: [docs] [issue36157] Document PyInterpreterState_Main().
In-Reply-To: <1551458200.72.0.727788487318.issue36157@roundup.psfhosted.org>
Message-ID: <1554131374.27.0.199614648991.issue36157@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +12581
stage: commit review -> patch review

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

From report at bugs.python.org  Mon Apr  1 11:15:16 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 01 Apr 2019 15:15:16 +0000
Subject: [docs] [issue36157] Document PyInterpreterState_Main().
In-Reply-To: <1551458200.72.0.727788487318.issue36157@roundup.psfhosted.org>
Message-ID: <1554131716.43.0.966264859307.issue36157@roundup.psfhosted.org>


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


New changeset 35fc38e5e82d18ceec95af9af2103319497e2eaf by Miss Islington (bot) in branch '3.7':
bpo-36157:Document PyInterpreterState_Main() (GH-12238)
https://github.com/python/cpython/commit/35fc38e5e82d18ceec95af9af2103319497e2eaf


----------

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

From report at bugs.python.org  Mon Apr  1 11:22:42 2019
From: report at bugs.python.org (Eric Snow)
Date: Mon, 01 Apr 2019 15:22:42 +0000
Subject: [docs] [issue36157] Document PyInterpreterState_Main().
In-Reply-To: <1551458200.72.0.727788487318.issue36157@roundup.psfhosted.org>
Message-ID: <1554132162.16.0.574392597077.issue36157@roundup.psfhosted.org>


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

Thanks for working on this, Joannah!  :)

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

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

From report at bugs.python.org  Mon Apr  1 12:45:51 2019
From: report at bugs.python.org (=?utf-8?q?Lars_Gust=C3=A4bel?=)
Date: Mon, 01 Apr 2019 16:45:51 +0000
Subject: [docs] [issue30661] Support tarfile.PAX_FORMAT in
 shutil.make_archive
In-Reply-To: <1497403539.2.0.760105950979.issue30661@psf.upfronthosting.co.za>
Message-ID: <1554137151.49.0.17274807453.issue30661@roundup.psfhosted.org>


Lars Gust?bel <lars at gustaebel.de> added the comment:

tarfile does not use the `format` argument for reading, it will be detected. You can even mix different formats in one archive and tarfile will be fine with it.

----------
nosy: +lars.gustaebel

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

From report at bugs.python.org  Mon Apr  1 16:23:38 2019
From: report at bugs.python.org (C.A.M. Gerlach)
Date: Mon, 01 Apr 2019 20:23:38 +0000
Subject: [docs] [issue30661] Support tarfile.PAX_FORMAT in
 shutil.make_archive
In-Reply-To: <1497403539.2.0.760105950979.issue30661@psf.upfronthosting.co.za>
Message-ID: <1554150218.59.0.367868758984.issue30661@roundup.psfhosted.org>


C.A.M. Gerlach <CAM.Gerlach at Gerlach.CAM> added the comment:

Thanks for the confirmation!

----------

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

From davipereirarocha at gmail.com  Mon Apr  1 10:55:00 2019
From: davipereirarocha at gmail.com (Davi Px)
Date: Mon, 1 Apr 2019 11:55:00 -0300
Subject: [docs] Translation of documentation
Message-ID: <CAB1qQ3sT6PBFnS19RH-eHNtY1RF+Xr4KQTrOs8hx63zoyttOqw@mail.gmail.com>

Hello!
I want to contribute by translating the python documentation from english
to portuguese - brazil. Where i can find the tools to help?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190401/446ae1ea/attachment.html>

From report at bugs.python.org  Mon Apr  1 17:54:37 2019
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 01 Apr 2019 21:54:37 +0000
Subject: [docs] [issue32413] Document that locals() may return globals()
In-Reply-To: <1514008362.41.0.213398074469.issue32413@psf.upfronthosting.co.za>
Message-ID: <1554155677.7.0.795208640499.issue32413@roundup.psfhosted.org>


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


----------
nosy: +brett.cannon

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

From report at bugs.python.org  Mon Apr  1 23:37:38 2019
From: report at bugs.python.org (Davin Potts)
Date: Tue, 02 Apr 2019 03:37:38 +0000
Subject: [docs] [issue36364] errors in multiprocessing.shared_memory examples
In-Reply-To: <1553006397.24.0.439789667635.issue36364@roundup.psfhosted.org>
Message-ID: <1554176258.42.0.99674086481.issue36364@roundup.psfhosted.org>


Davin Potts <python at discontinuity.net> added the comment:

Very much agreed, they're moving over to the main docs.

----------

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

From report at bugs.python.org  Tue Apr  2 00:52:44 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 02 Apr 2019 04:52:44 +0000
Subject: [docs] [issue36377] Python 'datastructures.html' docs page needs
 improvement because of ambiguity
In-Reply-To: <1553049009.71.0.761140685062.issue36377@roundup.psfhosted.org>
Message-ID: <1554180764.92.0.988743614473.issue36377@roundup.psfhosted.org>


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


New changeset b00479d42aaaed589d8b374bf5e5c6f443b0b499 by Raymond Hettinger (Emmanuel Arias) in branch 'master':
bpo-36377: Specify that range() can not be compared (GH-12468)
https://github.com/python/cpython/commit/b00479d42aaaed589d8b374bf5e5c6f443b0b499


----------

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

From report at bugs.python.org  Tue Apr  2 00:53:09 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 02 Apr 2019 04:53:09 +0000
Subject: [docs] [issue36377] Python 'datastructures.html' docs page needs
 improvement because of ambiguity
In-Reply-To: <1553049009.71.0.761140685062.issue36377@roundup.psfhosted.org>
Message-ID: <1554180789.99.0.762473971205.issue36377@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue Apr  2 02:36:07 2019
From: report at bugs.python.org (Jun)
Date: Tue, 02 Apr 2019 06:36:07 +0000
Subject: [docs] [issue36502] The behavior of str.isspace() for U+00A0 and
 U+202F is different from what is documented
Message-ID: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>


New submission from Jun <jkuroda.isa at gmail.com>:

I was looking for a list of Unicode codepoints that str.isspace() returns true.

According to https://docs.python.org/3/library/stdtypes.html#str.isspace, it's 
"Whitespace characters are those characters defined in the Unicode character database as ?Other? or ?Separator? and those with bidirectional property being one of ?WS?, ?B?, or ?S?."

However, for U+202F(https://www.fileformat.info/info/unicode/char/202f/index.htm) which is a "Separator" and its bidirectional property is "CS", str.isspace() returns True while it shouldn't if we follow the definition above. 

>>> "\u202f".isspace()
True

I'm not sure either the documentation should be updated or behavior should be updated, but at least those should be consistent.

----------
assignee: docs at python
components: Documentation, Unicode
messages: 339317
nosy: Jun, docs at python, ezio.melotti, vstinner
priority: normal
severity: normal
status: open
title: The behavior of str.isspace() for U+00A0 and U+202F is different from what is documented
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Apr  2 02:45:21 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 02 Apr 2019 06:45:21 +0000
Subject: [docs] [issue36502] The behavior of str.isspace() for U+00A0 and
 U+202F is different from what is documented
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1554187521.05.0.976247030824.issue36502@roundup.psfhosted.org>


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


----------
nosy: +lemburg

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

From report at bugs.python.org  Tue Apr  2 02:59:53 2019
From: report at bugs.python.org (SilentGhost)
Date: Tue, 02 Apr 2019 06:59:53 +0000
Subject: [docs] [issue36502] The behavior of str.isspace() for U+00A0 and
 U+202F is different from what is documented
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1554188393.77.0.52880789212.issue36502@roundup.psfhosted.org>


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

I think you have to read that "and" as "or". It's sufficient that '\u202f' is a separator for it to be considered a whitespace character.

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

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

From report at bugs.python.org  Tue Apr  2 05:39:08 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 02 Apr 2019 09:39:08 +0000
Subject: [docs] [issue34677] Event scheduler page example
In-Reply-To: <1536927469.93.0.956365154283.issue34677@psf.upfronthosting.co.za>
Message-ID: <1554197948.41.0.339749091741.issue34677@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue Apr  2 07:33:30 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 02 Apr 2019 11:33:30 +0000
Subject: [docs] [issue34677] Event scheduler page example
In-Reply-To: <1536927469.93.0.956365154283.issue34677@psf.upfronthosting.co.za>
Message-ID: <1554204810.63.0.939283845388.issue34677@roundup.psfhosted.org>


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

enter takes a relative time and priority is taken into consideration only when time is equal. So in the example enter(0.001, 2) is executed first and there is some delay in executing enter(0.001, 2). You can also view the queue with s.queue which is a heap. So even though they look similar the first call is scheduled earlier than the second one even with lower priority. 

Your report is correct if the example used enterabs where the time is absolute and then the two events are ordered based on priority with keyword executed first in the heapq used . In your script you can print s.sched and maybe add the same to the report?

# enter and s.sched prints different time with positional scheduled to be executed first in time.

?  cpython git:(master) cat /tmp/bar.py
import sched, time
s = sched.scheduler(time.time, time.sleep)

def print_time(a='default'):
    print("From print_time", time.time(), a)

def print_some_times():
    print(time.time())
    s.enter(0.001, 2, print_time, argument=('positional',))
    s.enter(0.001, 1, print_time, kwargs={'a': 'keyword'})
    print(s.queue)
    s.run()
    print(time.time())

print_some_times()
?  cpython git:(master) ./python.exe /tmp/bar.py
1554204002.401897
[Event(time=1554204002.40309, priority=2, action=<function print_time at 0x10e9747e0>, argument=('positional',), kwargs={}), Event(time=1554204002.403158, priority=1, action=<function print_time at 0x10e9747e0>, argument=(), kwargs={'a': 'keyword'})]
>From print_time 1554204002.40331 positional
>From print_time 1554204002.403441 keyword
1554204002.403517

# enterabs and s.sched prints same time with keyword ordered first based on priority with time being equal.

?  cpython git:(master) cat /tmp/baz.py
import sched, time
s = sched.scheduler(time.time, time.sleep)

def print_time(a='default'):
    print("From print_time", time.time(), a)

def print_some_times():
    print(time.time())
    s.enterabs(0.001, 2, print_time, argument=('positional',))
    s.enterabs(0.001, 1, print_time, kwargs={'a': 'keyword'})
    print(s.queue)
    s.run()
    print(time.time())

print_some_times()
?  cpython git:(master) ./python.exe /tmp/baz.py
1554204136.854676
[Event(time=0.001, priority=1, action=<function print_time at 0x1042767e0>, argument=(), kwargs={'a': 'keyword'}), Event(time=0.001, priority=2, action=<function print_time at 0x1042767e0>, argument=('positional',), kwargs={})]
>From print_time 1554204136.855422 keyword
>From print_time 1554204136.855669 positional
1554204136.855788

----------
nosy: +giampaolo.rodola, xtreak

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

From report at bugs.python.org  Tue Apr  2 10:32:57 2019
From: report at bugs.python.org (amazon kurodaju)
Date: Tue, 02 Apr 2019 14:32:57 +0000
Subject: [docs] [issue36502] The behavior of str.isspace() for U+00A0 and
 U+202F is different from what is documented
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1554215577.43.0.151239042562.issue36502@roundup.psfhosted.org>


amazon kurodaju <kurodaju.amazon at gmail.com> added the comment:

Do you mean read the statement as follows?

Whitespace characters are characters that satisfy either one of:
1. Character type is "Other"
2. Character type is "Separator"
3. Characters with "WS", "B", or "S" bidirectional property

If that's the case, this is also not reflect the behavior as most of characters in "Other" are not whitespace characters and in fact str.isspace() returns False for those characters.

----------
nosy: +amazon kurodaju

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

From report at bugs.python.org  Tue Apr  2 10:56:28 2019
From: report at bugs.python.org (SilentGhost)
Date: Tue, 02 Apr 2019 14:56:28 +0000
Subject: [docs] [issue36502] The behavior of str.isspace() for U+00A0 and
 U+202F is different from what is documented
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1554216988.65.0.311858813626.issue36502@roundup.psfhosted.org>


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

According to comment for _PyUnicode_IsWhitespace it's supposed to include Zs category, plus documented BIDI properties. So, I'm not sure where "Other" came from.

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

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

From report at bugs.python.org  Tue Apr  2 13:59:08 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 02 Apr 2019 17:59:08 +0000
Subject: [docs] [issue32413] Document that locals() may return globals()
In-Reply-To: <1514008362.41.0.213398074469.issue32413@psf.upfronthosting.co.za>
Message-ID: <1554227948.32.0.651819643083.issue32413@roundup.psfhosted.org>


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


----------
pull_requests: +12592

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

From report at bugs.python.org  Tue Apr  2 14:05:40 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 02 Apr 2019 18:05:40 +0000
Subject: [docs] [issue36364] errors in multiprocessing.shared_memory examples
In-Reply-To: <1553006397.24.0.439789667635.issue36364@roundup.psfhosted.org>
Message-ID: <1554228340.07.0.119330339089.issue36364@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

@Davin is there an issue for that and thus this issue can then be closed? Or did you want to re-purpose this issue to track that? Either way I'm assigning the issue to you to let you decide which way you want to go. :)

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

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

From report at bugs.python.org  Tue Apr  2 14:14:56 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 02 Apr 2019 18:14:56 +0000
Subject: [docs] [issue32413] Document that locals() may return globals()
In-Reply-To: <1514008362.41.0.213398074469.issue32413@psf.upfronthosting.co.za>
Message-ID: <1554228896.51.0.51384833401.issue32413@roundup.psfhosted.org>


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


New changeset ef516d11c1a0f885dba0aba8cf5366502077cdd4 by Miss Islington (bot) in branch '3.7':
bpo-32413: Add documentation that at the module level, locals(), globals() are the  same dictionary (GH-5004)
https://github.com/python/cpython/commit/ef516d11c1a0f885dba0aba8cf5366502077cdd4


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

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

From report at bugs.python.org  Tue Apr  2 14:15:54 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 02 Apr 2019 18:15:54 +0000
Subject: [docs] [issue32413] Document that locals() may return globals()
In-Reply-To: <1514008362.41.0.213398074469.issue32413@psf.upfronthosting.co.za>
Message-ID: <1554228954.86.0.169287752831.issue32413@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed Apr  3 12:59:37 2019
From: report at bugs.python.org (Aaron Hall)
Date: Wed, 03 Apr 2019 16:59:37 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1554310777.82.0.249387659464.issue35625@roundup.psfhosted.org>


Change by Aaron Hall <aaronchall at yahoo.com>:


----------
nosy: +Aaron Hall

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

From report at bugs.python.org  Wed Apr  3 20:53:24 2019
From: report at bugs.python.org (Rune Tynan)
Date: Thu, 04 Apr 2019 00:53:24 +0000
Subject: [docs] [issue18697] Unify arguments names in Unicode object C API
 documentation
In-Reply-To: <1376074126.58.0.40251146149.issue18697@psf.upfronthosting.co.za>
Message-ID: <1554339204.73.0.9152543464.issue18697@roundup.psfhosted.org>


Rune Tynan <runetynan at gmail.com> added the comment:

Another inconsistency I've noticed is that the code sometimes refers to Py_ssize_t instances as a 'length' and sometimes as a 'size'. It seems like 'size' is the more common one in the docs, but the headers more often use 'length'. Which would be the better one to keep for the common case?

----------

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

From report at bugs.python.org  Wed Apr  3 21:15:23 2019
From: report at bugs.python.org (Rune Tynan)
Date: Thu, 04 Apr 2019 01:15:23 +0000
Subject: [docs] [issue18697] Unify arguments names in Unicode object C API
 documentation
In-Reply-To: <1376074126.58.0.40251146149.issue18697@psf.upfronthosting.co.za>
Message-ID: <1554340523.94.0.802522636024.issue18697@roundup.psfhosted.org>


Change by Rune Tynan <runetynan at gmail.com>:


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

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

From report at bugs.python.org  Thu Apr  4 04:03:57 2019
From: report at bugs.python.org (Marcin Niemira)
Date: Thu, 04 Apr 2019 08:03:57 +0000
Subject: [docs] [issue36523] missing docs for IOBase writelines
Message-ID: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>


New submission from Marcin Niemira <marcin.niemira at gmail.com>:

Hey,

There is a missing function doc in `io.IOBase`

```python
import os
help(io.IOBase.writelines)
```

produces output like:
```
Help on method_descriptor:

writelines(self, lines, /)
```

I'll be happy to provide PR for this issue.

Cheers,
Marcin

----------
assignee: docs at python
components: Documentation
messages: 339434
nosy: Marcin Niemira, docs at python
priority: normal
severity: normal
status: open
title: missing docs for IOBase writelines
versions: Python 3.8

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

From report at bugs.python.org  Thu Apr  4 04:13:01 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 04 Apr 2019 08:13:01 +0000
Subject: [docs] [issue36523] missing docs for IOBase writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1554365581.34.0.865043677631.issue36523@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr  4 04:17:29 2019
From: report at bugs.python.org (Marcin Niemira)
Date: Thu, 04 Apr 2019 08:17:29 +0000
Subject: [docs] [issue36523] missing docs for IOBase writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1554365849.41.0.27449464787.issue36523@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr  4 06:00:05 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 04 Apr 2019 10:00:05 +0000
Subject: [docs] [issue16954] Add docstrings for ElementTree module
In-Reply-To: <1358090813.12.0.93631082121.issue16954@psf.upfronthosting.co.za>
Message-ID: <1554372005.34.0.351730538723.issue16954@roundup.psfhosted.org>


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


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

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

From yk3b.bw.ggxwkimobz at gmail.com  Thu Apr  4 11:03:43 2019
From: yk3b.bw.ggxwkimobz at gmail.com (YK)
Date: Thu, 4 Apr 2019 18:03:43 +0300
Subject: [docs] Python documentation well designed to confuse newbies
Message-ID: <CAL=gYCUff3StaPe1fgUTzLCtGiwfZT-oDaahfhzVdh+=92G7qg@mail.gmail.com>

I'm getting quite frustrated with this poorly designed documentation. Info
about a specific topic I'm interested in is usually split between 2 places,
if not 3. Which forces me to search the whole documentation for locations
where they were, which location had that specific part which I seek. Why
can't each topic simply be in one place? Documentation is so fragmented.
Any love for newbies? Whole documentation is a huge wreck, it should be
done over, with better details, explanations, examples and without
excess jumping. Have you seen how neat and tidy *w3schools* is?

Today I stepped on another landmine in Python's documentation. Was checking
out "*secrets ? Generate secure random numbers for managing secrets*". At
some point of writing code, I wondered to myself, gee, why doesn't secrets
module simply have a shuffling function to shuffle object contents. So
instead I wrote a manual thing that picked items randomly into a new list.
Few days later, I accidentally stumbled upon a code piece on the internet: "
*secrets.SystemRandom().shuffle(obj)*". I again opened up secrets topic in
documentation. I could not see anything directly as that. Instead I have
not much telling info about a class and then "*See random.SystemRandom for
additional details.*". Alright, I'll click that. And again, info about a
class and nothing related to "*secrets.SystemRandom().shuffle(obj)*". But
that expression works. How? Why? No idea. Great. Checking in *Wing IDE*, I
noticed that it points to "*random.shuffle()*" instead. How, why are they
related? I have no idea. How am I, as a non-expert to Python, supposed to
know and understand this feature? Documentation is poorly designed, I will
soon have a hole in my front of my head from rubbing out of frustration. Is
the documentation designed so on purpose? Do I have to hand out a 3 digit
figure of cash to go to Python school? Python is free, so why can't proper
education about Python be free too...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190404/d05428ee/attachment.html>

From julien at palard.fr  Thu Apr  4 12:47:21 2019
From: julien at palard.fr (Julien Palard)
Date: Thu, 04 Apr 2019 16:47:21 +0000
Subject: [docs] Translation of documentation
In-Reply-To: <CAB1qQ3sT6PBFnS19RH-eHNtY1RF+Xr4KQTrOs8hx63zoyttOqw@mail.gmail.com>
References: <CAB1qQ3sT6PBFnS19RH-eHNtY1RF+Xr4KQTrOs8hx63zoyttOqw@mail.gmail.com>
Message-ID: <KJ2ibh5Z4LhtIqplT8Nb79j2Vi9nSf0q76dC_NZzZRpyDKv103wK_5MWd8y15_jZ6VqF9WMxhBhWoDtUv3UuCfw-3pL32n1Cyb45DLnaPrc=@palard.fr>

Hi Davi,

Here's some info about the pt-br translation:

Coordinator: Marco Rougeth (https://mail.python.org/pipermail/doc-sig/2017-June/003975.html)
Translated: ~19% (as of 2017-12) on transifex (https://www.transifex.com/python-doc/public/)
Repository: https://github.com/python/python-docs-pt-br/
Wiki: http://python.org.br/traducao

Don't hesitate to ask Marco or me about the translations :)

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190404/5899969a/attachment.html>

From report at bugs.python.org  Thu Apr  4 18:26:09 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 04 Apr 2019 22:26:09 +0000
Subject: [docs] [issue36530] Document codecs decode_encode() and
 encode_decode() APIs
Message-ID: <1554416769.95.0.261313535534.issue36530@roundup.psfhosted.org>


New submission from Gregory P. Smith <greg at krypto.org>:

The codecs module has public decode_encode() and encode_decode() functions.  They have never been documented, but are recommended for some uses such as:

https://stackoverflow.com/questions/14820429/how-do-i-decodestring-escape-in-python3/23151714#23151714

As public APIs, we should document them.

----------
assignee: docs at python
components: Documentation
messages: 339467
nosy: docs at python, gregory.p.smith, njs
priority: normal
severity: normal
stage: needs patch
status: open
title: Document codecs decode_encode() and encode_decode() APIs
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Apr  4 21:02:19 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 05 Apr 2019 01:02:19 +0000
Subject: [docs] [issue36530] Document codecs decode_encode() and
 encode_decode() APIs
In-Reply-To: <1554416769.95.0.261313535534.issue36530@roundup.psfhosted.org>
Message-ID: <1554426139.54.0.231271361312.issue36530@roundup.psfhosted.org>


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


----------
superseder:  -> Missing documentation for codecs.escape_decode

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

From report at bugs.python.org  Thu Apr  4 21:02:33 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 05 Apr 2019 01:02:33 +0000
Subject: [docs] [issue36530] Document codecs decode_encode() and
 encode_decode() APIs
In-Reply-To: <1554416769.95.0.261313535534.issue36530@roundup.psfhosted.org>
Message-ID: <1554426153.58.0.876295223008.issue36530@roundup.psfhosted.org>


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


----------
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Apr  4 21:03:29 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 05 Apr 2019 01:03:29 +0000
Subject: [docs] [issue30588] Missing documentation for codecs.escape_decode
In-Reply-To: <1496847775.57.0.842403144977.issue30588@psf.upfronthosting.co.za>
Message-ID: <1554426209.5.0.476019568668.issue30588@roundup.psfhosted.org>


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

We can't change it or remove it, it is public by virtue of its name.  We should document it.

Removing or renaming it to be _private requires a PendingDeprecationWarning -> DeprecationWarning -> removal cycle.  it is well known and used.

https://stackoverflow.com/questions/14820429/how-do-i-decodestring-escape-in-python3/23151714#23151714

----------
nosy: +gregory.p.smith, njs
versions: +Python 3.8 -Python 3.3, Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Thu Apr  4 21:03:44 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 05 Apr 2019 01:03:44 +0000
Subject: [docs] [issue30588] Missing documentation for codecs.escape_decode
In-Reply-To: <1496847775.57.0.842403144977.issue30588@psf.upfronthosting.co.za>
Message-ID: <1554426224.79.0.817681281776.issue30588@roundup.psfhosted.org>


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


----------
stage:  -> needs patch

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

From report at bugs.python.org  Fri Apr  5 01:14:14 2019
From: report at bugs.python.org (spaceman_spiff)
Date: Fri, 05 Apr 2019 05:14:14 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
Message-ID: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>


New submission from spaceman_spiff <accounts at sgerber.de>:

It was not quite clear how to use the logging library with the new str.format style so I added an example in the logging cookbook

----------
assignee: docs at python
components: Documentation
messages: 339470
nosy: docs at python, spaceman_spiff
priority: normal
severity: normal
status: open
title: Example of logging.formatter with new str.format style
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Fri Apr  5 01:14:22 2019
From: report at bugs.python.org (spaceman_spiff)
Date: Fri, 05 Apr 2019 05:14:22 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554441262.11.0.791187796038.issue36532@roundup.psfhosted.org>


Change by spaceman_spiff <accounts at sgerber.de>:


----------
type:  -> enhancement

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

From report at bugs.python.org  Fri Apr  5 01:15:28 2019
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 05 Apr 2019 05:15:28 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554441328.43.0.963801554798.issue36532@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr  5 01:48:28 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 05 Apr 2019 05:48:28 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554443308.13.0.0562543708479.issue36532@roundup.psfhosted.org>


Change by Fred L. Drake, Jr. <fdrake at gmail.com>:


----------
nosy: +fdrake

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

From report at bugs.python.org  Fri Apr  5 02:29:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 05 Apr 2019 06:29:00 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554445740.76.0.385156203546.issue36532@roundup.psfhosted.org>


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


----------
nosy: +vinay.sajip
versions:  -Python 3.5, Python 3.6, Python 3.9

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

From marco at rougeth.com  Thu Apr  4 15:35:14 2019
From: marco at rougeth.com (Marco Rougeth)
Date: Thu, 4 Apr 2019 20:35:14 +0100
Subject: [docs] Translation of documentation
In-Reply-To: <KJ2ibh5Z4LhtIqplT8Nb79j2Vi9nSf0q76dC_NZzZRpyDKv103wK_5MWd8y15_jZ6VqF9WMxhBhWoDtUv3UuCfw-3pL32n1Cyb45DLnaPrc=@palard.fr>
References: <CAB1qQ3sT6PBFnS19RH-eHNtY1RF+Xr4KQTrOs8hx63zoyttOqw@mail.gmail.com>
 <KJ2ibh5Z4LhtIqplT8Nb79j2Vi9nSf0q76dC_NZzZRpyDKv103wK_5MWd8y15_jZ6VqF9WMxhBhWoDtUv3UuCfw-3pL32n1Cyb45DLnaPrc=@palard.fr>
Message-ID: <31C25DEA-D75F-4BC6-842D-0D81E325D812@rougeth.com>

Hi Davi,

There's a Telegram group with a few people discussing about the pt-br translation, if you have an account, please join us [1].

I writing a serie of blog posts about the pt-br translation and the first two published [1][2] covers the current state, the community, what is missing, what are the priorities, etc. It may help to see the big picture.

Feel free to message me if you need anything else.

Thanks Julien for forwarding to me.

1 - https://t.me/pybr_i18n
2 - http://rgth.co/blog/python-ptbr-cenario-atual
3 - http://rgth.co/blog/python-ptbr-cenario-atual

> On 4 Apr 2019, at 17:47, Julien Palard <julien at palard.fr> wrote:
> 
> Hi Davi,
> 
> Here's some info about the pt-br translation:
> 
> Coordinator: Marco Rougeth (https://mail.python.org/pipermail/doc-sig/2017-June/003975.html)
> Translated: ~19% (as of 2017-12) on transifex (https://www.transifex.com/python-doc/public/)
> Repository: https://github.com/python/python-docs-pt-br/
> Wiki: http://python.org.br/traducao
> 
> Don't hesitate to ask Marco or me about the translations :)
> 
> Bests,
> -- 
> Julien Palard
> https://mdk.fr
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190404/fffe2943/attachment-0001.html>

From julien at palard.fr  Fri Apr  5 04:07:31 2019
From: julien at palard.fr (Julien Palard)
Date: Fri, 05 Apr 2019 08:07:31 +0000
Subject: [docs] Python documentation well designed to confuse newbies
In-Reply-To: <CAL=gYCUff3StaPe1fgUTzLCtGiwfZT-oDaahfhzVdh+=92G7qg@mail.gmail.com>
References: <CAL=gYCUff3StaPe1fgUTzLCtGiwfZT-oDaahfhzVdh+=92G7qg@mail.gmail.com>
Message-ID: <WHeUjB_hQxXQgusqZ99FKb6b4uX81s57wsHRfq1KEhMRnfCUIETlQq3rqEKwvE3XQaQNiFA5VDqF9A1sw_gRyelx5TRpqQU63bvdRN84KxY=@palard.fr>

Hi anonymous, thanks for your feeback!

> Why can't each topic simply be in one place?

That's because there's multiple levels of details, take typically:

- https://docs.python.org/3/tutorial/controlflow.html#for-statements
- https://docs.python.org/3/reference/compound_stmts.html#the-for-statement

those are describing the exact same thing, but with different level of detail.

A newcomer don't want the level of detail given by reference/, but after a few years may start to be interested about those details, so it's simply split to multiple places to give to one only what's matter.


> Today I stepped on another landmine in Python's documentation

This is the exact moment you should tell yourself "let's fix this", and open a pull request on github (to add a paragraph or simply a link from a page to another in this case), to make content more discoverable.

I alone am not able to find all those little possible improvements, but if anyone while finding a "landmines" fixes it, the doc becomes better over time, and this is what's already happening, there's on average one edit per day on the documentation to enhance it.

You know, after reading that doc for 15 years, and translating it for like 5 years, I can navigate thrue it and read it blindfolded, so it really takes new pairs of eyes like yours to spot those little improvements, just come and help :)

Bests,
--?
Julien Palard
https://mdk.fr


From report at bugs.python.org  Fri Apr  5 04:54:30 2019
From: report at bugs.python.org (Inada Naoki)
Date: Fri, 05 Apr 2019 08:54:30 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning as deprecated
Message-ID: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>


New submission from Inada Naoki <songofacandy at gmail.com>:


New changeset 176d26364bb67801fa522f52f20cbe44420d6942 by Inada Naoki in branch 'master':
bpo-36404: recommend DeprecationWarning over PendingDeprecationWarning (GH-12505)
https://github.com/python/cpython/commit/176d26364bb67801fa522f52f20cbe44420d6942


----------

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

From report at bugs.python.org  Fri Apr  5 04:55:46 2019
From: report at bugs.python.org (Inada Naoki)
Date: Fri, 05 Apr 2019 08:55:46 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning is not so
 useful.
In-Reply-To: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>
Message-ID: <1554454546.26.0.804052073759.issue36404@roundup.psfhosted.org>


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

After discussion on ML, I just recommend DeprecationWarning
over PendingDeprecationWarning in this time.
PendingDeprecationWarning is not deprecated for now.

----------
title: Document PendingDeprecationWarning as deprecated -> Document PendingDeprecationWarning is not so useful.

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

From report at bugs.python.org  Fri Apr  5 04:55:51 2019
From: report at bugs.python.org (Inada Naoki)
Date: Fri, 05 Apr 2019 08:55:51 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning is not so
 useful.
In-Reply-To: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>
Message-ID: <1554454551.67.0.84499113541.issue36404@roundup.psfhosted.org>


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

From report at bugs.python.org  Fri Apr  5 04:59:32 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 05 Apr 2019 08:59:32 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning is not so
 useful.
In-Reply-To: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>
Message-ID: <1554454772.16.0.648974968589.issue36404@roundup.psfhosted.org>


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


----------
pull_requests: +12621

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

From report at bugs.python.org  Fri Apr  5 05:07:28 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 05 Apr 2019 09:07:28 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning is not so
 useful.
In-Reply-To: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>
Message-ID: <1554455248.74.0.968239536738.issue36404@roundup.psfhosted.org>


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


New changeset 86fbe0287dd774022fd2b6c2dcbfbb5573a0b874 by Miss Islington (bot) in branch '3.7':
bpo-36404: recommend DeprecationWarning over PendingDeprecationWarning (GH-12505)
https://github.com/python/cpython/commit/86fbe0287dd774022fd2b6c2dcbfbb5573a0b874


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

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

From report at bugs.python.org  Fri Apr  5 11:25:32 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 05 Apr 2019 15:25:32 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554477932.65.0.710829896847.issue36532@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

But there is an example in the cookbook already:

https://docs.python.org/3/howto/logging-cookbook.html#use-of-alternative-formatting-styles

It's right there in the first code sample in that section.

You might want to amend your change to point to this section from the one where you want to make the change.

----------

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

From report at bugs.python.org  Fri Apr  5 14:28:55 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Apr 2019 18:28:55 +0000
Subject: [docs] [issue36486] Bugs and inconsistencies in unicodedata
In-Reply-To: <1553956873.19.0.268771747568.issue36486@roundup.psfhosted.org>
Message-ID: <1554488935.4.0.241890770847.issue36486@roundup.psfhosted.org>


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


----------
stage:  -> needs patch
versions: +Python 3.8

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

From report at bugs.python.org  Fri Apr  5 14:33:48 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Apr 2019 18:33:48 +0000
Subject: [docs] [issue36490] Modernize function signature in Archiving
 section of shutil doc
In-Reply-To: <1554005288.19.0.789880523073.issue36490@roundup.psfhosted.org>
Message-ID: <1554489228.37.0.358029062258.issue36490@roundup.psfhosted.org>


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


----------
stage:  -> needs patch
title: Modernize function signature format in Archiving section of shutil doc -> Modernize function signature  in Archiving section of shutil doc

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

From report at bugs.python.org  Fri Apr  5 14:38:44 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Apr 2019 18:38:44 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1554489524.47.0.256229565962.issue36502@roundup.psfhosted.org>


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


----------
title: The behavior of str.isspace() for U+00A0 and U+202F is different from what is documented -> str.isspace() for U+00A0 and U+202F differs from document
versions:  -Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri Apr  5 15:07:11 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 05 Apr 2019 19:07:11 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554491231.35.0.952806803497.issue36532@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

Good catch, Vinay!  Thanks.

----------

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

From report at bugs.python.org  Fri Apr  5 15:18:21 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Apr 2019 19:18:21 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1554491901.41.0.634703584176.issue36523@roundup.psfhosted.org>


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

Verified.  
>>> import io
>>> io.IOBase.writelines.__doc__
>>>

----------
nosy: +terry.reedy
title: missing docs for IOBase writelines -> Add docstring to io.IOBase.writelines

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

From report at bugs.python.org  Fri Apr  5 15:20:37 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Apr 2019 19:20:37 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1554492037.91.0.338431587299.issue36523@roundup.psfhosted.org>


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

I assume that this can be backported even though it touches .c rather than .rst.

----------
versions: +Python 3.7

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

From report at bugs.python.org  Fri Apr  5 16:07:07 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 05 Apr 2019 20:07:07 +0000
Subject: [docs] [issue36538] _thread.interrupt_main() no longer interrupts
 Lock.wait
Message-ID: <1554494827.92.0.565969475506.issue36538@roundup.psfhosted.org>


New submission from Gregory P. Smith <greg at krypto.org>:

In Python 2.7 our threading implementation was so poor that a thread join ultimately called our lock wait implementation that busy looped polling and sleeping to check for a lock acquisition success.  calling thread.interrupt_main() which is just PyErr_SetInterrupt() C API in disguise successfully broke out of that lock wait loop.

In Python 3 with our drastically improved threading implementation, a lock wait is a pthreads sem_timedwait() or sem_trywait() API call, blocking within the pthreads library or OS kernel.  PyErr_SetInterrupt() obviously has no effect on that.  Only an actual signal arriving can interrupt that.

Thus instead of code using _thread.interrupt_main() - in 2and3 compatible applications, six.moves._thread.interrupt_main() - they should instead write:

 os.kill(os.getpid(), signal.SIGINT)

Given that _thread is a private module making _thread.interrupt_main() a private API, do we need to keep it?  If we do, we should at least document this behavior and recommend actually sending the signal.  It is less capable of actually interrupting the main thread from some common blocking operations today.  Sending the signal seems like it would always be better.

----------
assignee: docs at python
components: Documentation, Extension Modules, Library (Lib)
messages: 339518
nosy: docs at python, gregory.p.smith
priority: normal
severity: normal
stage: needs patch
status: open
title: _thread.interrupt_main() no longer interrupts Lock.wait
type: behavior
versions: Python 3.8

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

From report at bugs.python.org  Sat Apr  6 02:44:03 2019
From: report at bugs.python.org (spaceman_spiff)
Date: Sat, 06 Apr 2019 06:44:03 +0000
Subject: [docs] [issue36532] Example of logging.formatter with new
 str.format style
In-Reply-To: <1554441254.46.0.943587700045.issue36532@roundup.psfhosted.org>
Message-ID: <1554533043.19.0.958507482406.issue36532@roundup.psfhosted.org>


spaceman_spiff <accounts at sgerber.de> added the comment:

I was under the impression that this was all it takes to use loggers with the normal string.format syntax.
e.g.:
   log.info('{}', 'Test')
Turns out when I tested it I used f-strings in the first parameters - so I got it wrong.
Imho this can be closed and the pr rejected.
Sorry for wasting your time :)

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

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

From report at bugs.python.org  Sat Apr  6 03:28:06 2019
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 06 Apr 2019 07:28:06 +0000
Subject: [docs] [issue36538] _thread.interrupt_main() no longer interrupts
 Lock.wait
In-Reply-To: <1554494827.92.0.565969475506.issue36538@roundup.psfhosted.org>
Message-ID: <1554535686.19.0.830037870996.issue36538@roundup.psfhosted.org>


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

Windows doesn't implement POSIX signals in the kernel, so _thread.interrupt_main (i.e. PyErr_SetInterrupt) can be useful as an abstraction. 

Currently PyErr_SetInterrupt (Modules/signalmodule.c) doesn't set our SIGINT event in Windows. It was suggested in issue 29926 to replace the trip_signal call with raise(SIGINT). That works for Windows -- as long as we're not concerned about emulating Ctrl+C exactly as if the user typed it in the console (if we're attached to a console). In POSIX, raise(SIGINT) won't interrupt the main thread if it's in a blocking system call, since it targets pthread_self(), so PyErr_SetInterrupt can instead call kill(getpid(), SIGINT), as you suggest, or pthread_kill(main_thread, SIGINT). 

3.8 adds signal.raise_signal (see issue 35568), so it's possible to implement this in pure Python. Either way, it would be nice to keep it as a cross-platform function, and hopefully make it public and documented.

Another option would be to enhance our Windows implementation of os.kill to more closely match POSIX kill(), such that os.kill(os.getpid(), signal.SIGINT) is implemented as raise(SIGINT). That would be a breaking change since currently it calls TerminateProcess (an abrupt termination like POSIX SIGKILL).

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

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

From lambertj123 at gmail.com  Sat Apr  6 08:51:05 2019
From: lambertj123 at gmail.com (Julien Lambert)
Date: Sat, 6 Apr 2019 14:51:05 +0200
Subject: [docs] Unicode HOWTO - French example
Message-ID: <93DCBD9A-96EC-4398-ACC4-C8F115B465AC@gmail.com>

Here: https://docs.python.org/3.3/howto/unicode.html <https://docs.python.org/3.3/howto/unicode.html>

PRINT "FICHIER EST COMPLETE."

? LE FICHIER EST COMPLETE. ? would be used in French, as you cannot omit the article when the word is the subject of a verb.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190406/838d4d02/attachment.html>

From julien at palard.fr  Sat Apr  6 13:06:27 2019
From: julien at palard.fr (Julien Palard)
Date: Sat, 06 Apr 2019 17:06:27 +0000
Subject: [docs] Unicode HOWTO - French example
In-Reply-To: <93DCBD9A-96EC-4398-ACC4-C8F115B465AC@gmail.com>
References: <93DCBD9A-96EC-4398-ACC4-C8F115B465AC@gmail.com>
Message-ID: <KkRh7d71-drlV4FCtGZgzMkcNyLCdctgIKPZfLUiJR5C5UWLNpIPmS-Des1ajosUQ1jy4tLMQ2EsxpFxsGSCI48pZ-_qx_Viz1bjUy5nEfs=@palard.fr>

Hi Julien,

Thanks for reporting! Sadly it's the documentation of Python 3.3 (from 2012), we're no longer touching it, and the string does no longer appear on 3.7 doc.

While I'm at it, feel free to join the translation effort at https://github.com/python/python-docs-fr :)

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190406/c0d45a77/attachment.html>

From report at bugs.python.org  Sat Apr  6 17:30:18 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sat, 06 Apr 2019 21:30:18 +0000
Subject: [docs] [issue31369] re.RegexFlag is not included in __all__,
 makes type inference less useful
In-Reply-To: <1504730402.58.0.544251648863.issue31369@psf.upfronthosting.co.za>
Message-ID: <1554586218.43.0.903986591176.issue31369@roundup.psfhosted.org>


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

I am totally fine with making RegexFlag public (this may be indeed useful for static typing purposes).

----------

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

From report at bugs.python.org  Sun Apr  7 00:47:54 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 07 Apr 2019 04:47:54 +0000
Subject: [docs] [issue30661] Support tarfile.PAX_FORMAT in
 shutil.make_archive
In-Reply-To: <1497403539.2.0.760105950979.issue30661@psf.upfronthosting.co.za>
Message-ID: <1554612473.96.0.731322426599.issue30661@roundup.psfhosted.org>


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


New changeset 89a894403cfa880d7f9d1d67070f61456d14cbde by Nick Coghlan (CAM Gerlach) in branch 'master':
bpo-30661: Improve docs for tarfile pax change and effect on shutil (GH-12635)
https://github.com/python/cpython/commit/89a894403cfa880d7f9d1d67070f61456d14cbde


----------

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

From report at bugs.python.org  Sun Apr  7 00:50:17 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 07 Apr 2019 04:50:17 +0000
Subject: [docs] [issue30661] Support tarfile.PAX_FORMAT in
 shutil.make_archive
In-Reply-To: <1497403539.2.0.760105950979.issue30661@psf.upfronthosting.co.za>
Message-ID: <1554612617.3.0.0380598822995.issue30661@roundup.psfhosted.org>


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

Thanks for the technical clarification Lars, and for the docs update C.A.M.

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

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

From report at bugs.python.org  Sun Apr  7 02:46:19 2019
From: report at bugs.python.org (py.user)
Date: Sun, 07 Apr 2019 06:46:19 +0000
Subject: [docs] [issue27992] Clarify %(prog)s in argparse help formatter
 returns basename of sys.argv[0] by default
In-Reply-To: <1473217852.97.0.553971829799.issue27992@psf.upfronthosting.co.za>
Message-ID: <1554619579.01.0.544108051552.issue27992@roundup.psfhosted.org>


py.user <bugzilla-mail-box at yandex.ru> added the comment:

@Karthikeyan Singaravelan
Thank you for the point. I added a new patch.

----------
Added file: https://bugs.python.org/file48245/argparse_sys-argv-0-basename.diff

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

From report at bugs.python.org  Sun Apr  7 02:48:42 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 07 Apr 2019 06:48:42 +0000
Subject: [docs] [issue27992] Clarify %(prog)s in argparse help formatter
 returns basename of sys.argv[0] by default
In-Reply-To: <1473217852.97.0.553971829799.issue27992@psf.upfronthosting.co.za>
Message-ID: <1554619722.5.0.749180541109.issue27992@roundup.psfhosted.org>


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

CPython now accepts GitHub PRs. Please see the workflow at https://devguide.python.org . You can raise a PR against master branch.

----------

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

From report at bugs.python.org  Sun Apr  7 07:49:32 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 07 Apr 2019 11:49:32 +0000
Subject: [docs] [issue36384] ipaddress Should not reject IPv4 addresses with
 leading zeroes as ambiguously octal
In-Reply-To: <1553125209.55.0.0358803413865.issue36384@roundup.psfhosted.org>
Message-ID: <1554637772.21.0.43095820994.issue36384@roundup.psfhosted.org>


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

The recommended handling in the article that Serhiy mentions is to strip the leading zeroes, which the ipaddress module will still do - it's only being made more tolerant on input. That means it will become usable as a prefilter step (pass string with potentially leading zeroes to ipaddress, get string with no leading zeroes out).

So that means the one part we missed is the docs update (together with a versionchanged note in the module docs themselves)

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

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

From report at bugs.python.org  Sun Apr  7 11:27:29 2019
From: report at bugs.python.org (py.user)
Date: Sun, 07 Apr 2019 15:27:29 +0000
Subject: [docs] [issue27992] Clarify %(prog)s in argparse help formatter
 returns basename of sys.argv[0] by default
In-Reply-To: <1473217852.97.0.553971829799.issue27992@psf.upfronthosting.co.za>
Message-ID: <1554650849.44.0.347141404473.issue27992@roundup.psfhosted.org>


Change by py.user <bugzilla-mail-box at yandex.ru>:


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

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

From report at bugs.python.org  Mon Apr  8 17:40:47 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 08 Apr 2019 21:40:47 +0000
Subject: [docs] [issue36567] DOC: manpage directive doesn't create hyperlink
Message-ID: <1554759647.95.0.266283511597.issue36567@roundup.psfhosted.org>


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

The `manpage` directive in the docs is not creating a hyperlink to the Unix manual page.  As of Sphinx 1.7, the `manpage` directive needs to have a `manpages_url` defined in the conf.py file.

[1] http://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-manpage

----------
assignee: docs at python
components: Documentation
messages: 339676
nosy: cheryl.sabella, docs at python, eric.araujo, ezio.melotti, mdk, willingc
priority: normal
severity: normal
stage: needs patch
status: open
title: DOC: manpage directive doesn't create hyperlink
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Mon Apr  8 17:48:35 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 08 Apr 2019 21:48:35 +0000
Subject: [docs] [issue33456] site.py: by default,
 a virtual environment is *not* isolated from the system-level
 site-packages directories
In-Reply-To: <1525964254.05.0.682650639539.issue33456@psf.upfronthosting.co.za>
Message-ID: <1554760115.1.0.792588112497.issue33456@roundup.psfhosted.org>


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


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +cheryl.sabella, docs at python, vinay.sajip
versions:  -Python 3.6

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

From report at bugs.python.org  Mon Apr  8 18:45:54 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 08 Apr 2019 22:45:54 +0000
Subject: [docs] [issue19992] subprocess documentation not explicit about
 fileno()
In-Reply-To: <1387158760.79.0.499761911724.issue19992@psf.upfronthosting.co.za>
Message-ID: <1554763554.3.0.241228997455.issue19992@roundup.psfhosted.org>


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

Assigning to @Mariatta for the sprints.

----------
assignee: docs at python -> Mariatta
nosy: +Mariatta, cheryl.sabella
type:  -> enhancement
versions: +Python 3.7, Python 3.8 -Python 2.7, Python 3.5, Python 3.6

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

From report at bugs.python.org  Mon Apr  8 18:47:44 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 08 Apr 2019 22:47:44 +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: <1554763664.51.0.562471100292.issue33601@roundup.psfhosted.org>


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


----------
assignee: docs at python -> Mariatta
keywords:  -patch
nosy: +Mariatta
stage: patch review -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Mon Apr  8 22:17:39 2019
From: report at bugs.python.org (Carl Cerecke)
Date: Tue, 09 Apr 2019 02:17:39 +0000
Subject: [docs] [issue36568] Typo in socket.CAN_RAW_FD_FRAMES library
 documentation
Message-ID: <1554776259.35.0.774393301329.issue36568@roundup.psfhosted.org>


New submission from Carl Cerecke <carl at free.org.nz>:

https://docs.python.org/3/library/socket.html#socket.CAN_RAW_FD_FRAMES

The wording "...however, you one must accept..." doesn't make sense. I think the "you one" should be "your application", but I'm not sure.

----------
assignee: docs at python
components: Documentation
messages: 339691
nosy: Carl Cerecke, docs at python
priority: normal
severity: normal
status: open
title: Typo in socket.CAN_RAW_FD_FRAMES library documentation
versions: Python 3.7

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

From report at bugs.python.org  Mon Apr  8 22:23:52 2019
From: report at bugs.python.org (Carl Cerecke)
Date: Tue, 09 Apr 2019 02:23:52 +0000
Subject: [docs] [issue36568] Typo in socket.CAN_RAW_FD_FRAMES library
 documentation
In-Reply-To: <1554776259.35.0.774393301329.issue36568@roundup.psfhosted.org>
Message-ID: <1554776632.19.0.311705571833.issue36568@roundup.psfhosted.org>


Carl Cerecke <carl at free.org.nz> added the comment:

See section 4.1.5 at https://www.kernel.org/doc/Documentation/networking/can.txt

----------

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

From report at bugs.python.org  Tue Apr  9 01:43:14 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 05:43:14 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554788594.51.0.47358989206.issue30134@roundup.psfhosted.org>


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


New changeset d012d64b6a513e760abb6745f7f7ce5e6a31f274 by Inada Naoki (cocoatomo) in branch '2.7':
bpo-30134: add an explanation of BytesWarning (GH-1249)
https://github.com/python/cpython/commit/d012d64b6a513e760abb6745f7f7ce5e6a31f274


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

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

From report at bugs.python.org  Tue Apr  9 01:43:23 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 05:43:23 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554788603.82.0.207013840395.issue30134@roundup.psfhosted.org>


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

From report at bugs.python.org  Tue Apr  9 01:59:24 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 09 Apr 2019 05:59:24 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554789564.89.0.907957153297.issue30134@roundup.psfhosted.org>


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

This PR was not ready to merge. Please address my and Martin's comments.

----------

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

From report at bugs.python.org  Tue Apr  9 02:00:16 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 09 Apr 2019 06:00:16 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554789616.88.0.417647496828.issue30134@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue Apr  9 02:31:56 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 06:31:56 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554791516.52.0.553273058374.issue30134@roundup.psfhosted.org>


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

I addressed Martin's comment (buffer -> bytesarray).
But I missed your point, sorry.

----------

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

From report at bugs.python.org  Tue Apr  9 02:33:32 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 06:33:32 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554791612.6.0.347585978332.issue30134@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue Apr  9 03:00:55 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 07:00:55 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554793255.12.0.743235086703.issue30134@roundup.psfhosted.org>


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


New changeset 87ed1beb3e15c619f25b9a9308d1ec35659feffd by Inada Naoki in branch '2.7':
bpo-30134: add BytesWarning in warnings.rst (GH-12738)
https://github.com/python/cpython/commit/87ed1beb3e15c619f25b9a9308d1ec35659feffd


----------

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

From report at bugs.python.org  Tue Apr  9 03:08:44 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 07:08:44 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554793724.62.0.71915444162.issue30134@roundup.psfhosted.org>


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


----------
pull_requests: +12661

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

From report at bugs.python.org  Tue Apr  9 03:27:40 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 09 Apr 2019 07:27:40 +0000
Subject: [docs] [issue33456] site.py: by default,
 a virtual environment is *not* isolated from the system-level
 site-packages directories
In-Reply-To: <1525964254.05.0.682650639539.issue33456@psf.upfronthosting.co.za>
Message-ID: <1554794860.68.0.845734125664.issue33456@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset c324c748871804f31f56b3bd02a8650b3bf1bae7 by Vinay Sajip (Lukas Waymann) in branch 'master':
bpo-33456: site module documentation - fix wrong default for key in pyvenv.cfg (GH-6755)
https://github.com/python/cpython/commit/c324c748871804f31f56b3bd02a8650b3bf1bae7


----------

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

From report at bugs.python.org  Tue Apr  9 03:30:51 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 09 Apr 2019 07:30:51 +0000
Subject: [docs] [issue33456] site.py: by default,
 a virtual environment is *not* isolated from the system-level
 site-packages directories
In-Reply-To: <1525964254.05.0.682650639539.issue33456@psf.upfronthosting.co.za>
Message-ID: <1554795051.2.0.383595207715.issue33456@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


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

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

From zeaforus at gmail.com  Mon Apr  8 18:03:56 2019
From: zeaforus at gmail.com (Klaas `Z4us` Van B. V)
Date: Tue, 9 Apr 2019 00:03:56 +0200
Subject: [docs] Improvement suggestion to Python docs
Message-ID: <CAKNgXXZWyMv6iWRHTUqxFBUiHu_yAKC2JYEJOB_bk2uJPr66MA@mail.gmail.com>

Dear documentation writers for Python,

Better late than never I started to learn Python after some other like
Perl, Ruby & C

In the beginning of your tutorial
<https://docs.python.org/2.7/tutorial/interpreter.html> (2.1) is written:
... usually installed as /usr/local/bin/python on those ...
Perhaps better, because more generic if you write something like:

*To find out where Python is located type 'which python' ...*
[then you may remove a line or two like the one about consulting a guru as
well]


*BTW *
On Snow Leopard 2.6 installed and works great

Kind regards | Vriendelijke groeten | Cordiali saluti,
Klaas `Z4us` van B V, EFIG
<https://nl.linkedin.com/in/klaas-van-buiten-0325b2102>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190409/71bcfaf6/attachment.html>

From julien at palard.fr  Tue Apr  9 03:55:37 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 09 Apr 2019 07:55:37 +0000
Subject: [docs] Improvement suggestion to Python docs
In-Reply-To: <CAKNgXXZWyMv6iWRHTUqxFBUiHu_yAKC2JYEJOB_bk2uJPr66MA@mail.gmail.com>
References: <CAKNgXXZWyMv6iWRHTUqxFBUiHu_yAKC2JYEJOB_bk2uJPr66MA@mail.gmail.com>
Message-ID: <wTCdnyuXr5A4k-4n1bRwtaPui8MY7agkkF4RIXbM8N1pkQbQz1MKU7H4BTJoQV7EAnvQiVykESZ0NNL8-aoH-9IG1z9sQLKeoZAbv8cnDYk=@palard.fr>

Thanks for reporting!

Sadly telling people to use `which` won't help them in adding Python's installation path to their PATH, as `which` itself uses PATH.

If you feed you can rewrite this to be cleaner, don't hesitate to open an issue on bugs.python.org and if you can even open a pull request on https://github.com/python/cpython/ (the file you have to modify is Doc/tutorial/interpreter.rst).

BTW if you're starting to lean Python in 2019 you better start with Python 3.7, not 2.6. The Python 2 end of life is jan 1 2020. 2.6 has not received any patch since 2013, better not touch this snake, even with a stick ;)

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190409/d64012f7/attachment.html>

From report at bugs.python.org  Tue Apr  9 04:16:18 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 09 Apr 2019 08:16:18 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554797778.26.0.197244002352.issue30134@roundup.psfhosted.org>


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

In 2.7 BytesWarning is emitted only on comparison between bytearray and unicode. All descriptions and comments should be corrected.

----------

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

From zeaforus at gmail.com  Tue Apr  9 06:55:48 2019
From: zeaforus at gmail.com (Klaas `Z4us` Van B. V)
Date: Tue, 9 Apr 2019 12:55:48 +0200
Subject: [docs] Improvement suggestion to Python docs
In-Reply-To: <wTCdnyuXr5A4k-4n1bRwtaPui8MY7agkkF4RIXbM8N1pkQbQz1MKU7H4BTJoQV7EAnvQiVykESZ0NNL8-aoH-9IG1z9sQLKeoZAbv8cnDYk=@palard.fr>
References: <CAKNgXXZWyMv6iWRHTUqxFBUiHu_yAKC2JYEJOB_bk2uJPr66MA@mail.gmail.com>
 <wTCdnyuXr5A4k-4n1bRwtaPui8MY7agkkF4RIXbM8N1pkQbQz1MKU7H4BTJoQV7EAnvQiVykESZ0NNL8-aoH-9IG1z9sQLKeoZAbv8cnDYk=@palard.fr>
Message-ID: <CAKNgXXb=mu8jY=6EUz6S5P8cY+UzVF8i1HdSfcgSbFiGJrxoLg@mail.gmail.com>

Awesome, thanks!

Next to Snow Leopard I use Mojave as well; factually my wife's puter, but I
have my own account there as well 8-D
Will see to upgrade from 2.7 to 3 one of these days

You don't have to follow anyone
...
We are all individuals! <https://www.youtube.com/watch?v=QereR0CViMY>

Kind regards | Vriendelijke groeten | Cordiali saluti,
Klaas `Z4us` van B V, innovative communicator
<https://www.linkedin.com/in/klaas-van-buiten-0325b2102/>
@In0?=?rt(EU)&KnightsWhoDon'tSay'ni'


On Tue, Apr 9, 2019 at 9:55 AM Julien Palard <julien at palard.fr> wrote:

> Thanks for reporting!
>
> Sadly telling people to use `which` won't help them in adding Python's
> installation path to their PATH, as `which` itself uses PATH.
>
> If you feed you can rewrite this to be cleaner, don't hesitate to open an
> issue on bugs.python.org and if you can even open a pull request on
> https://github.com/python/cpython/ (the file you have to modify is
> Doc/tutorial/interpreter.rst).
>
> BTW if you're starting to lean Python in 2019 you better start with Python
> 3.7, not 2.6. The Python 2 end of life is jan 1 2020. 2.6 has not received
> any patch since 2013, better not touch this snake, even with a stick ;)
>
> Bests,
> --
> Julien Palard
> https://mdk.fr
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190409/78dae5b4/attachment-0001.html>

From report at bugs.python.org  Tue Apr  9 08:49:52 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 12:49:52 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554814192.9.0.873565349822.issue30134@roundup.psfhosted.org>


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


New changeset 4e8e8aabc6e6ae1c989ef288be7bddfdbbc3187d by Inada Naoki in branch '2.7':
bpo-30134: fix BytesWarning doc, docstring and message (GH-12739)
https://github.com/python/cpython/commit/4e8e8aabc6e6ae1c989ef288be7bddfdbbc3187d


----------

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

From report at bugs.python.org  Tue Apr  9 08:50:05 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 09 Apr 2019 12:50:05 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1554814205.34.0.9039949193.issue30134@roundup.psfhosted.org>


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

From report at bugs.python.org  Tue Apr  9 13:29:41 2019
From: report at bugs.python.org (Vy Nguyen)
Date: Tue, 09 Apr 2019 17:29:41 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1554830981.98.0.746684156118.issue34172@roundup.psfhosted.org>


Change by Vy Nguyen <thaovy231011 at gmail.com>:


----------
nosy: +Vy Nguyen

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

From report at bugs.python.org  Tue Apr  9 19:00:30 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 09 Apr 2019 23:00:30 +0000
Subject: [docs] [issue35181] Doc: Namespace Packages: Inconsistent
 documentation of __loader__ being None
In-Reply-To: <1541543349.68.0.788709270274.issue35181@psf.upfronthosting.co.za>
Message-ID: <1554850830.22.0.630414238364.issue35181@roundup.psfhosted.org>


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

@barry, you started a review of PR10016 and I believe all your requested changes have been made, so please review again when you get a chance.  Please also take a look at PR10376.  Thanks!

----------
nosy: +cheryl.sabella
type:  -> enhancement
versions: +Python 3.8

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

From report at bugs.python.org  Wed Apr 10 03:27:12 2019
From: report at bugs.python.org (zheng)
Date: Wed, 10 Apr 2019 07:27:12 +0000
Subject: [docs] [issue36417] unicode.isdecimal bug in online Python 2
 documentation
In-Reply-To: <1553438833.3.0.95385374587.issue36417@roundup.psfhosted.org>
Message-ID: <1554881232.07.0.388057714002.issue36417@roundup.psfhosted.org>


Change by zheng <zheng0.tao at gmail.com>:


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

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

From report at bugs.python.org  Wed Apr 10 03:31:29 2019
From: report at bugs.python.org (zheng)
Date: Wed, 10 Apr 2019 07:31:29 +0000
Subject: [docs] [issue36417] unicode.isdecimal bug in online Python 2
 documentation
In-Reply-To: <1553438833.3.0.95385374587.issue36417@roundup.psfhosted.org>
Message-ID: <1554881489.53.0.133351889668.issue36417@roundup.psfhosted.org>


zheng <zheng0.tao at gmail.com> added the comment:

I propose we copy over the exact changes made to the Python 3 documentation.

I looked through the code mentioned in the other thread. Namely, `Objects/unicodeobject.c` and `Tools/unicode/makeunicodedata.py`. The implementation is identical between python 2 and python 3. The only difference appears to be the unicode version used.

    # decimal digit, integer digit
                decimal = 0
                if record[6]:
                    flags |= DECIMAL_MASK
                    decimal = int(record[6])
                digit = 0
                if record[7]:
                    flags |= DIGIT_MASK
                    digit = int(record[7])
                if record[8]:
                    flags |= NUMERIC_MASK
                    numeric.setdefault(record[8], []).append(char)

Another form of validation I did was enumerate all the digits and decimals and compare between versions. It looks like the general change is that there are a bunch of new unicode characters introduced in python 3. The exception is NEW TAI LUE THAM DIGIT ONE which gets recategorized as a digit.

python 2, compiled with UCS4
for u in map(unichr, list(range(0x10FFFF))):
    if unicode.isdigit(u):
        print(unicodedata.name(u))

python 3
for u in map(chr, range(0x10FFFF)):
    if str.isdigit(u):
        print(name(u))

----------
nosy: +zheng

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

From nuclearrazor at gmail.com  Tue Apr  9 18:01:22 2019
From: nuclearrazor at gmail.com (=?UTF-8?B?0JjQstCw0L0g0JHQu9Cw0LPQvtC/0L7Qu9GD0YfQvdGL0Lk=?=)
Date: Wed, 10 Apr 2019 01:01:22 +0300
Subject: [docs] Bug on the site page - descriptor
Message-ID: <CA+k3JwATUUm=XGreCwkBsqNFGUTWOeaRcV5dmh9vL0xpSj_6vw@mail.gmail.com>

Hello! I was found next issue:

https://docs.python.org/3.3/howto/descriptor.html

On this page, in the text block:

For objects, the machinery is in object.__getattribute__() which transforms
b.x into type(b).__dict__['x'].__get__(b, type(b)). The implementation
works through a precedence chain that gives data descriptors priority over
instance variables, instance variables priority over non-data descriptors,
and assigns lowest priority to __getattr__() if provided. The full C
implementation can be found in PyObject_GenericGetAttr() in
Objects/object.c.

There not found page while refereed by click on Onject.c

http://svn.python.org/view/python/trunk/Objects/object.c?view=markup

[image: image.png]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190410/a7b6ff93/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 21028 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190410/a7b6ff93/attachment-0001.png>

From songofacandy at gmail.com  Wed Apr 10 06:04:45 2019
From: songofacandy at gmail.com (Inada Naoki)
Date: Wed, 10 Apr 2019 19:04:45 +0900
Subject: [docs] Bug on the site page - descriptor
In-Reply-To: <CA+k3JwATUUm=XGreCwkBsqNFGUTWOeaRcV5dmh9vL0xpSj_6vw@mail.gmail.com>
References: <CA+k3JwATUUm=XGreCwkBsqNFGUTWOeaRcV5dmh9vL0xpSj_6vw@mail.gmail.com>
Message-ID: <CAEfz+TwN0JqqtXAfEbfHyp9vj8QH5i1K-SixmWk1gH9-n0GPPQ@mail.gmail.com>

You are reading Python 3.3 document.  It is not maintained.
Read it here.

https://docs.python.org/3.7/howto/descriptor.html#invoking-descriptors


On Wed, Apr 10, 2019 at 6:53 PM ???? ?????????????
<nuclearrazor at gmail.com> wrote:
>
> Hello! I was found next issue:
>
> https://docs.python.org/3.3/howto/descriptor.html
>
> On this page, in the text block:
>
> For objects, the machinery is in object.__getattribute__() which transforms b.x into type(b).__dict__['x'].__get__(b, type(b)). The implementation works through a precedence chain that gives data descriptors priority over instance variables, instance variables priority over non-data descriptors, and assigns lowest priority to __getattr__() if provided. The full C implementation can be found in PyObject_GenericGetAttr() in Objects/object.c.
>
> There not found page while refereed by click on Onject.c
>
> http://svn.python.org/view/python/trunk/Objects/object.c?view=markup
>
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs



-- 
Inada Naoki  <songofacandy at gmail.com>

From report at bugs.python.org  Wed Apr 10 08:08:39 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 10 Apr 2019 12:08:39 +0000
Subject: [docs] [issue29284] Include thread_name_prefix in the
 concurrent.futures.ThreadPoolExecutor example 17.4.2.1
In-Reply-To: <1484584964.59.0.239435362381.issue29284@psf.upfronthosting.co.za>
Message-ID: <1554898119.86.0.14024893981.issue29284@roundup.psfhosted.org>


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

This seems like a reasonable request.  A description of `thread_name_prefix` should probably also be added to the body of the class description instead of just in the versionadded directive.

Assigning to @Mariatta for the sprints.

Nosying @gregory.p.smith as he added the parameter in issue 27664.

----------
assignee: docs at python -> Mariatta
nosy: +Mariatta, gregory.p.smith
stage:  -> needs patch
versions: +Python 3.7, Python 3.8 -Python 3.6

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

From report at bugs.python.org  Wed Apr 10 08:12:25 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 10 Apr 2019 12:12:25 +0000
Subject: [docs] [issue32008] Example suggest to use a TLSv1 socket
In-Reply-To: <1510428965.62.0.213398074469.issue32008@psf.upfronthosting.co.za>
Message-ID: <1554898345.6.0.929207425359.issue32008@roundup.psfhosted.org>


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

@christian.heimes, this one looks ready to merge and close.  Please take a look when you get a chance.  Thanks!

----------

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

From report at bugs.python.org  Wed Apr 10 08:19:35 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 10 Apr 2019 12:19:35 +0000
Subject: [docs] [issue28626] Tutorial: rearrange discussion of output
 formatting to encourage f-strings
In-Reply-To: <1478452855.22.0.932657206329.issue28626@psf.upfronthosting.co.za>
Message-ID: <1554898775.3.0.654818221309.issue28626@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed Apr 10 10:02:12 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 10 Apr 2019 14:02:12 +0000
Subject: [docs] [issue30612] Unusual Windows registry path syntax
In-Reply-To: <1497000804.0.0.079840477122.issue30612@psf.upfronthosting.co.za>
Message-ID: <1554904932.16.0.169960584221.issue30612@roundup.psfhosted.org>


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

@chrullrich, were you still interested in creating a PR for this?  Thanks!

----------
nosy: +cheryl.sabella
versions: +Python 3.8 -Python 3.6

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

From report at bugs.python.org  Wed Apr 10 15:37:48 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 10 Apr 2019 19:37:48 +0000
Subject: [docs] [issue30274] Make
 importlib.abc.ExtensionFileLoader.__init__() documentation match code
In-Reply-To: <1493936689.45.0.0881901800669.issue30274@psf.upfronthosting.co.za>
Message-ID: <1554925068.85.0.21023617294.issue30274@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

I realized another solution to this is to make the argument positional-only, then the name simply doesn't matter. Probably unnecessary breakage, though.

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

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

From report at bugs.python.org  Wed Apr 10 22:25:09 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 11 Apr 2019 02:25:09 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554949509.32.0.171260352972.issue33722@roundup.psfhosted.org>


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

My *guess* is that you created the branch for PR 7491 when your local master branch was months out of date.  Or you branched off of the 3.7 branch.  Whatever, your patch proposed to revert recent changes to master, touching about 1000 files.  When you pushed the button on the github web page to compare and possibly make a PR, you should have seen a list of +- 1000 changes in the proposed PR, closed the window, deleted the branch on the fork and your repository, and started over with a new branch from freshly updated master.  You are right that the review requests were automatic.  However, I am not sure how the 6 month delay factors into what happened.

Since Guido closed the PR rather than suggest fixing it further, I suggest that you start over as suggested above and look closely before pressing 'Create PR'.  It appears that you already deleted the branch from the fork.

>From my limited knowledge of how to use unitest.mock correctly, I agree that the example looks plausible.

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

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

From report at bugs.python.org  Wed Apr 10 22:41:33 2019
From: report at bugs.python.org (Jay Crotts)
Date: Thu, 11 Apr 2019 02:41:33 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554950492.98.0.327858288054.issue33722@roundup.psfhosted.org>


Jay Crotts <crotts.jay at gmail.com> added the comment:

Yeah the PR had been stale for a while, and I re-based my fork without closing the PR, so when I pushed it to the fork it updated the PR reviewer list. Silly mistake by me, I should have made sure the diff wasn't huge before pushing it. I know review time is valuable and did not mean to waste it.

If you think it is a worthwhile change I'm happy to start over with another PR.

----------

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

From report at bugs.python.org  Wed Apr 10 22:49:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 02:49:25 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
Message-ID: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>


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

On my https://github.com/python/cpython/pull/12770 the doctest job of Travis CI failed with:

https://travis-ci.org/python/cpython/jobs/518572326

mkdir -p build
Building NEWS from Misc/NEWS.d with blurb
PATH=./venv/bin:$PATH sphinx-build -b doctest -d build/doctrees -D latex_elements.papersize= -q -W -j4 -W . build/doctest 
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
/home/travis/build/python/cpython/Doc/tools/extensions/pyspecific.py:274: RemovedInSphinx30Warning: env.note_versionchange() is deprecated. Please use ChangeSetDomain.note_changeset() instead.
  env.note_versionchange('deprecated', version[0], node, self.lineno)
Warning, treated as error:
**********************************************************************
File "library/unittest.mock-examples.rst", line ?, in default
Failed example:
    m.one().two().three()
Expected:
    <MagicMock name='mock.one().two().three()' id='...'>
Got:
    obj dead or exiting
    <MagicMock name='mock.one().two().three()' id='140222049958880'>
Makefile:44: recipe for target 'build' failed
make[1]: *** [build] Error 2

--

I can reproduce this issue on Linux with:

$ cd Doc
$ make venv
$ PATH=./venv/bin:$PATH sphinx-build -b doctest -d build/doctrees -D latex_elements.papersize= -q -W -j4 -W . build/doctest 

I get random errors:

Warning, treated as error:
**********************************************************************
File "library/datetime.rst", line 686, in default
Failed example:
    d.strftime("%A %d. %B %Y")
Expected:
    'Monday 11. March 2002'
Got:
    'lundi 11. mars 2002'

Warning, treated as error:
**********************************************************************
File "library/collections.rst", line 914, in default
Failed example:
    p._asdict()
Expected:
    {'x': 11, 'y': 22}
Got:
    OrderedDict([('x', 11), ('y', 22)])

Warning, treated as error:
**********************************************************************
File "library/unittest.mock.rst", line ?, in default
Failed example:
    mock.call_args.args
Expected:
    (3, 4)
Got:
    args


The virtual environment uses Sphinx 2.0.1. Can it be a change in Sphinx 2 default configuration?

----------
assignee: docs at python
components: Documentation
messages: 339919
nosy: docs at python, vstinner
priority: normal
severity: normal
status: open
title: Travis CI: doctest failure
versions: Python 3.8

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

From report at bugs.python.org  Wed Apr 10 23:02:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 11 Apr 2019 03:02:00 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554951720.51.0.0895071006237.issue36597@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed Apr 10 23:05:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 11 Apr 2019 03:05:49 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554951949.96.0.0366063068625.issue33722@roundup.psfhosted.org>


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

The example looks like a good addition to me since mocking builtins.open is not documented for this use case. Please start a new PR.

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

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

From report at bugs.python.org  Wed Apr 10 23:19:38 2019
From: report at bugs.python.org (Jay Crotts)
Date: Thu, 11 Apr 2019 03:19:38 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554952778.59.0.0530942819228.issue33722@roundup.psfhosted.org>


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


----------
pull_requests: +12700

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

From report at bugs.python.org  Thu Apr 11 00:37:25 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 11 Apr 2019 04:37:25 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554957445.84.0.852140949296.issue33722@roundup.psfhosted.org>


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

After looking at the context of the patch and thinking more about whether the patch is a good idea, I am reversing what I said before and think that this issue and the new patch (sorry) should be closed.

1. The new example duplicates the current example.  The only difference is that one module name,'__main__', is replaced with another, 'builtins'.  Mechanically, there is no difference, so the duplicate adds nothing.

2. The current example, contrary to the claim, "'__main__'.open is replaced", adds .open to __main__ and thereby masks builtins.open in, and only in, __main__.  In use, '__main__' in all the current doc examples should be replaced by the name of the module where open is called.  This would usually, but not necessarily, be the module being tested. This is explained in the section on where to patch.

3. Touching builtins is generally a bad idea unless one really understands and wants to affect *all* modules in the process, including the test code and unittest code.  Beginners should *not* be encouraged to do this.  If one replaces a builtin needed by test code or other untested mdoules before the replacement is undone, one disables the test code.

The real problem, if any, with the mock examples, is that they usually do everything in one module (usually __main__) while real use involves code and execution in at least two modules.  Users are left to work out which examples lines belong in text_xyz, which would be in xyz, and what essential code is missing.

----------

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

From report at bugs.python.org  Thu Apr 11 01:38:20 2019
From: report at bugs.python.org (Jay Crotts)
Date: Thu, 11 Apr 2019 05:38:20 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554961100.34.0.22301856421.issue33722@roundup.psfhosted.org>


Jay Crotts <crotts.jay at gmail.com> added the comment:

No worries, I think all of your points make sense, especially number one after looking at the patch again. I looked at the docs again, and there is even an example of another built in being patched.

Thanks for taking the time to review it.

I'm okay with closing it if you don't think there is any value add.

----------

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

From report at bugs.python.org  Thu Apr 11 02:11:39 2019
From: report at bugs.python.org (Jay Crotts)
Date: Thu, 11 Apr 2019 06:11:39 +0000
Subject: [docs] [issue33722] Document builtins in mock_open
In-Reply-To: <1527791734.24.0.682650639539.issue33722@psf.upfronthosting.co.za>
Message-ID: <1554963099.63.0.683457623505.issue33722@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr 11 02:21:37 2019
From: report at bugs.python.org (Michal)
Date: Thu, 11 Apr 2019 06:21:37 +0000
Subject: [docs] [issue34788] ipaddress module fails on rfc4007 scoped IPv6
 addresses
In-Reply-To: <1537799403.03.0.956365154283.issue34788@psf.upfronthosting.co.za>
Message-ID: <1554963697.93.0.855812160841.issue34788@roundup.psfhosted.org>


Michal <crossner90 at gmail.com> added the comment:

I would like to fix this problem if nobody is against that. I stumbled upon the very same thing recently and I think it would be a nice opportunity to contribute.

----------
nosy: +mic4ael

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

From report at bugs.python.org  Thu Apr 11 02:56:45 2019
From: report at bugs.python.org (Ben Creasy)
Date: Thu, 11 Apr 2019 06:56:45 +0000
Subject: [docs] [issue13282] the table of contents in epub file is too long
In-Reply-To: <1319796506.79.0.347343158897.issue13282@psf.upfronthosting.co.za>
Message-ID: <1554965805.74.0.171444035237.issue13282@roundup.psfhosted.org>


Change by Ben Creasy <ben at bencreasy.com>:


----------
nosy: +jcrben

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

From report at bugs.python.org  Thu Apr 11 02:58:49 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 06:58:49 +0000
Subject: [docs] [issue36416] bytes.rpartition bug in online documentation
In-Reply-To: <1553437427.15.0.469399643284.issue36416@roundup.psfhosted.org>
Message-ID: <1554965929.78.0.931326689171.issue36416@roundup.psfhosted.org>


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


New changeset efc48701496ef020e896fc6a91af3c0c612ac69a by Inada Naoki (pewscorner) in branch 'master':
bpo-36416: Correct bytes.rpartition documentation (GH-12543)
https://github.com/python/cpython/commit/efc48701496ef020e896fc6a91af3c0c612ac69a


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

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

From report at bugs.python.org  Thu Apr 11 03:05:55 2019
From: report at bugs.python.org (Ben Creasy)
Date: Thu, 11 Apr 2019 07:05:55 +0000
Subject: [docs] [issue13282] the table of contents in epub file is too long
In-Reply-To: <1319796506.79.0.347343158897.issue13282@psf.upfronthosting.co.za>
Message-ID: <1554966355.51.0.256011114889.issue13282@roundup.psfhosted.org>


Ben Creasy <ben at bencreasy.com> added the comment:

Not sure if this is filed elsewhere, but the contents on the page at https://docs.python.org/3/contents.html could really use a collapse button, and could start automatically collapsed. The first half of the page is "What's new" for the past few Python versions and the Changelog.

I looked around for an issue in the upstream tracker and didn't see one https://github.com/sphinx-doc/sphinx/issues - I don't know much about Sphinx but it seems like it should be possible with a bit of Javascript and CSS.

----------

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

From report at bugs.python.org  Thu Apr 11 03:25:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:25:37 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554967537.9.0.399048164685.issue36597@roundup.psfhosted.org>


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

Well, same problem with Sphinx 1.8.5. No idea why the job started to fail.

----------

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

From report at bugs.python.org  Thu Apr 11 03:30:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:30:00 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554967800.38.0.943002444566.issue36597@roundup.psfhosted.org>


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


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

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

From songofacandy at gmail.com  Thu Apr 11 03:33:07 2019
From: songofacandy at gmail.com (Inada Naoki)
Date: Thu, 11 Apr 2019 16:33:07 +0900
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
References: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <CAEfz+TxHoHLH8uW=37DDWvuYYpdgF4ndX+xY5yWxWcBnjLS7nA@mail.gmail.com>

On Thu, Apr 11, 2019 at 11:49 AM STINNER Victor <report at bugs.python.org> wrote:
>
> File "library/unittest.mock-examples.rst", line ?, in default
> Failed example:
>     m.one().two().three()
> Expected:
>     <MagicMock name='mock.one().two().three()' id='...'>
> Got:
>     obj dead or exiting
>     <MagicMock name='mock.one().two().three()' id='140222049958880'>

I'm not sure where "obj is dead or exiting" came from.

> File "library/datetime.rst", line 686, in default
> Failed example:
>     d.strftime("%A %d. %B %Y")
> Expected:
>     'Monday 11. March 2002'
> Got:
>     'lundi 11. mars 2002'

It seems it is caused by non English locale.

> File "library/collections.rst", line 914, in default
> Failed example:
>     p._asdict()
> Expected:
>     {'x': 11, 'y': 22}
> Got:
>     OrderedDict([('x', 11), ('y', 22)])

You may run doctest with existing Python, not Python 3.8.

> File "library/unittest.mock.rst", line ?, in default
> Failed example:
>     mock.call_args.args
> Expected:
>     (3, 4)
> Got:
>     args

I'm not sure about this.
-- 
Inada Naoki  <songofacandy at gmail.com>

From report at bugs.python.org  Thu Apr 11 03:36:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:36:33 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554968193.44.0.8029488405.issue36597@roundup.psfhosted.org>


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

> It seems it is caused by non English locale.

Right, but why did it start to fail since yesterday?


> You may run doctest with existing Python, not Python 3.8.

I used the command from the .travis.yml job: "... make -C Doc/ PYTHON=../python "...". It explicitly picks the Python it just compiled.

Why would we like to check the doctests using a random Python version, whereas it's Python 3.8 documentation?

----------

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

From report at bugs.python.org  Thu Apr 11 03:46:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:46:22 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554968782.82.0.07117297106.issue36597@roundup.psfhosted.org>


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

8 hours ago, the job still passed at the top of the the master branch (commit a9bd8925c7fa50dd3cfab125b824ec192133ef49):

https://travis-ci.org/python/cpython/jobs/518281237

"Successfully installed Jinja2-2.10.1 MarkupSafe-1.1.1 Pygments-2.3.1 Sphinx-2.0.1 alabaster-0.7.12 babel-2.6.0 blurb-1.0.7 certifi-2019.3.9 chardet-3.0.4 docutils-0.14 idna-2.8 imagesize-1.1.0 packaging-19.0 pyparsing-2.4.0 python-docs-theme-2018.7 pytz-2019.1 requests-2.21.0 six-1.12.0 snowballstemmer-1.2.1 sphinxcontrib-applehelp-1.0.1 sphinxcontrib-devhelp-1.0.1 sphinxcontrib-htmlhelp-1.0.1 sphinxcontrib-jsmath-1.0.1 sphinxcontrib-qthelp-1.0.2 sphinxcontrib-serializinghtml-1.1.3 urllib3-1.24.1"
...
PATH=./venv/bin:$PATH sphinx-build -b doctest -d build/doctrees -D latex_elements.papersize= -q -W -j4 -W . build/doctest 
...
The command "xvfb-run make -C Doc/ PYTHON=../python SPHINXOPTS="-q -W -j4" doctest" exited with 0.

---

6 hours ago, it failed:

https://travis-ci.org/python/cpython/jobs/518572326

Successfully installed Jinja2-2.10.1 MarkupSafe-1.1.1 Pygments-2.3.1 Sphinx-2.0.1 alabaster-0.7.12 babel-2.6.0 blurb-1.0.7 certifi-2019.3.9 chardet-3.0.4 docutils-0.14 idna-2.8 imagesize-1.1.0 packaging-19.0 pyparsing-2.4.0 python-docs-theme-2018.7 pytz-2019.1 requests-2.21.0 six-1.12.0 snowballstemmer-1.2.1 sphinxcontrib-applehelp-1.0.1 sphinxcontrib-devhelp-1.0.1 sphinxcontrib-htmlhelp-1.0.1 sphinxcontrib-jsmath-1.0.1 sphinxcontrib-qthelp-1.0.2 sphinxcontrib-serializinghtml-1.1.3 urllib3-1.24.1

Warning, treated as error: (...)

--

In the 2 builds, pip installed the the same Python modules versions.

I compared the raw logs of the 2 builds. In short, they are the same.

Maybe the job already failed previously, but only randomly?

----------

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

From report at bugs.python.org  Thu Apr 11 03:46:44 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 07:46:44 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554968193.44.0.8029488405.issue36597@roundup.psfhosted.org>
Message-ID: <CAEfz+Tyq26UCWmJKVQoTc1BAaGONxzy--RvVT1rhchNLW=tVKw@mail.gmail.com>


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

> > It seems it is caused by non English locale.
>
> Right, but why did it start to fail since yesterday?

Is it an error start to fail since yesterday?
As far as reading your first report, this is happen only in your local
environment.

> > You may run doctest with existing Python, not Python 3.8.
>
> I used the command from the .travis.yml job: "... make -C Doc/ PYTHON=../python "...". It explicitly picks the Python it just compiled.

This error is in your environment too.  Maybe you re-used old venv?

>
> Why would we like to check the doctests using a random Python version, whereas it's Python 3.8 documentation?
>

Because it "doctest".  Python behavior (repr) can be changed.
Python 3.8 replaces some OrderedDict usage with regular dict.

----------

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

From report at bugs.python.org  Thu Apr 11 03:46:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:46:57 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554968817.85.0.671891278716.issue36597@roundup.psfhosted.org>


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


New changeset adff01e81d291c698581eadd693caa43ae5c78ac by Victor Stinner in branch 'master':
bpo-36597: Disable Travis CI doctest job (GH-12775)
https://github.com/python/cpython/commit/adff01e81d291c698581eadd693caa43ae5c78ac


----------

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

From report at bugs.python.org  Thu Apr 11 03:47:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:47:47 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554968867.25.0.414771293084.issue36597@roundup.psfhosted.org>


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

I mark this issue as a release blocker to not forget it. I disabled the Travis CI doctest job to repair the CI, but we have to investigate why it started to fail yesterday.

----------
nosy: +lukasz.langa
priority: normal -> release blocker

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

From report at bugs.python.org  Thu Apr 11 03:49:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 07:49:11 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554968951.38.0.076578067272.issue36597@roundup.psfhosted.org>


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

> As far as reading your first report, this is happen only in your local
environment.

See the beginning of my first message, the doctest prevents me to merge a PR. But I tested on the master branch without my change, and I get the same issue locally, and the issues seems to be unrelated to my change.

"""
On my https://github.com/python/cpython/pull/12770 the doctest job of Travis CI failed with:

https://travis-ci.org/python/cpython/jobs/518572326
"""

----------

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

From report at bugs.python.org  Thu Apr 11 03:54:13 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 11 Apr 2019 07:54:13 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554969253.97.0.235164911398.issue36597@roundup.psfhosted.org>


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

"Object dead or exiting" is a less frequent random error with doctest. I am not sure from where it occurs but occurs for different tests at different times and is overlooked in Travis since the next runs are fine.

Sample old builds : 

https://travis-ci.org/python/cpython/jobs/517606752
https://travis-ci.org/python/cpython/jobs/510847596

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

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

From report at bugs.python.org  Thu Apr 11 03:57:50 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 07:57:50 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554969470.37.0.247721878812.issue36597@roundup.psfhosted.org>


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

> See the beginning of my first message, the doctest prevents me to merge a PR.


You did not show travis build link which failed other than "obj dead or exiting" error.
Don't all other errors happened only on your environment?  If no, please link to travis build link.

As far as I can confirm now, only "obj dead or exiting" error is problem in Travis.


> But I tested on the master branch without my change, and I get the same issue locally, and the issues seems to be unrelated to my change.

I suspect your environment (locale and venv used to run doctest), not your changes.

> """
> On my https://github.com/python/cpython/pull/12770 the doctest job of Travis CI failed with:
> 
> https://travis-ci.org/python/cpython/jobs/518572326
> """

Only "obj dead or exiting" happened in the job.

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

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

From report at bugs.python.org  Thu Apr 11 04:09:05 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 08:09:05 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554970145.46.0.958101520742.issue36597@roundup.psfhosted.org>


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

https://github.com/python/cpython/blob/master/Doc/library/weakref.rst#finalizer-objects

    >>> obj = Object()
    >>> weakref.finalize(obj, print, "obj dead or exiting")  #doctest:+ELLIPSIS
    <finalize object at ...; for 'Object' at ...>
    >>> exit()                                               #doctest:+SKIP
    obj dead or exiting

Note that "#doctest:+SKIP".  print("obj dead or exiting") is called after weakref test.
This may caused random doctest fail.

----------

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

From report at bugs.python.org  Thu Apr 11 04:15:40 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 08:15:40 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554970540.2.0.0852723382799.issue36597@roundup.psfhosted.org>


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


----------
pull_requests: +12703

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

From report at bugs.python.org  Thu Apr 11 04:19:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 08:19:16 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554970756.8.0.388766404616.issue36597@roundup.psfhosted.org>


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

> You did not show travis build link which failed other than "obj dead or exiting" error.

Really? When I click on https://travis-ci.org/python/cpython/jobs/518572326 (the second link of my first message), I still see:

"""
Warning, treated as error:
**********************************************************************
File "library/unittest.mock-examples.rst", line ?, in default
Failed example:
    m.one().two().three()
Expected:
    <MagicMock name='mock.one().two().three()' id='...'>
Got:
    obj dead or exiting
    <MagicMock name='mock.one().two().three()' id='140222049958880'>
Makefile:44: recipe for target 'build' failed
make[1]: *** [build] Error 2
"""

This error comes from Travis CI.

> I suspect your environment (locale and venv used to run doctest), not your changes.

You can ignore the date failure, but how is the following error related to my environment?

"""
File "library/collections.rst", line 914, in default
Failed example:
    p._asdict()
Expected:
    {'x': 11, 'y': 22}
Got:
    OrderedDict([('x', 11), ('y', 22)])
"""

I used the same commands than .travis.yml. If we are unable to get the same environment than in Travis CI, we have a big problem.

I agree to ignore the locale, this is a lower priority issue.

----------

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

From report at bugs.python.org  Thu Apr 11 04:23:41 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 08:23:41 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554970756.8.0.388766404616.issue36597@roundup.psfhosted.org>
Message-ID: <CAEfz+TxJ1118Bi4=AYwkcKA0Xid_yJPchNUHv_diNZ2nnuyjzQ@mail.gmail.com>


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

On Thu, Apr 11, 2019 at 5:19 PM STINNER Victor <report at bugs.python.org> wrote:
> Really? When I click on https://travis-ci.org/python/cpython/jobs/518572326 (the second link of my first message), I still see:
>
> """
> Warning, treated as error:
> **********************************************************************
> File "library/unittest.mock-examples.rst", line ?, in default
> Failed example:
>     m.one().two().three()
> Expected:
>     <MagicMock name='mock.one().two().three()' id='...'>
> Got:
>     obj dead or exiting
>     <MagicMock name='mock.one().two().three()' id='140222049958880'>
> Makefile:44: recipe for target 'build' failed
> make[1]: *** [build] Error 2
> """
>
> This error comes from Travis CI.

It is "obj dead or exiting" error.  I didn't say it is caused by your
environment.
It is only error happened in Travis.

>
> > I suspect your environment (locale and venv used to run doctest), not your changes.
>
> You can ignore the date failure, but how is the following error related to my environment?
>
> """
> File "library/collections.rst", line 914, in default
> Failed example:
>     p._asdict()
> Expected:
>     {'x': 11, 'y': 22}
> Got:
>     OrderedDict([('x', 11), ('y', 22)])

namedtuple._asdict() changed to return dict instead of OrderedDict.
If your venv is created before the change, this error can be happened.

----------

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

From report at bugs.python.org  Thu Apr 11 04:25:16 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 08:25:16 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554971116.6.0.478602554454.issue36597@roundup.psfhosted.org>


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

I think PR-12776 fixed "obj dead or exiting" error.
https://travis-ci.org/python/cpython/jobs/518656385

----------

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

From report at bugs.python.org  Thu Apr 11 04:53:53 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 08:53:53 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554972833.78.0.382160744574.issue36597@roundup.psfhosted.org>


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


New changeset 57b1a2862a99677f09614e9e456d36aae9ddd87c by Inada Naoki in branch 'master':
bpo-36597: fix random doctest failure (GH-12776)
https://github.com/python/cpython/commit/57b1a2862a99677f09614e9e456d36aae9ddd87c


----------

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

From report at bugs.python.org  Thu Apr 11 04:56:29 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 08:56:29 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554972989.09.0.0116957385476.issue36597@roundup.psfhosted.org>


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


----------
pull_requests: +12705

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

From report at bugs.python.org  Thu Apr 11 05:30:26 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 09:30:26 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554975026.76.0.582219594224.issue36597@roundup.psfhosted.org>


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


----------
pull_requests: +12706

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

From report at bugs.python.org  Thu Apr 11 06:05:39 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 10:05:39 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554977139.13.0.659112485895.issue36597@roundup.psfhosted.org>


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


New changeset b3c92c6ae923ffb2b9ac5f80b28ecd689de48662 by Inada Naoki in branch 'master':
bpo-36597: fix weakref example code (GH-12779)
https://github.com/python/cpython/commit/b3c92c6ae923ffb2b9ac5f80b28ecd689de48662


----------

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

From report at bugs.python.org  Thu Apr 11 06:11:10 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 10:11:10 +0000
Subject: [docs] [issue36599] weakref document says dict order is unstable
Message-ID: <1554977470.77.0.948736759807.issue36599@roundup.psfhosted.org>


New submission from Inada Naoki <songofacandy at gmail.com>:

https://docs.python.org/3/library/doctest.html#warnings

"For example, when printing a dict, Python doesn?t guarantee that the key-value pairs will be printed in any particular order,"

This example should be rewritten with set.

----------
assignee: docs at python
components: Documentation
messages: 339952
nosy: docs at python, inada.naoki
priority: normal
severity: normal
status: open
title: weakref document says dict order is unstable
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Apr 11 06:13:03 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 11 Apr 2019 10:13:03 +0000
Subject: [docs] [issue36416] bytes.rpartition bug in online documentation
In-Reply-To: <1553437427.15.0.469399643284.issue36416@roundup.psfhosted.org>
Message-ID: <1554977583.4.0.170365475588.issue36416@roundup.psfhosted.org>


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


----------
pull_requests: +12708

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

From report at bugs.python.org  Thu Apr 11 06:18:00 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 10:18:00 +0000
Subject: [docs] [issue36599] doctest document says dict order is unstable
In-Reply-To: <1554977470.77.0.948736759807.issue36599@roundup.psfhosted.org>
Message-ID: <1554977880.42.0.245554108575.issue36599@roundup.psfhosted.org>


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


----------
title: weakref document says dict order is unstable -> doctest document says dict order is unstable

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

From report at bugs.python.org  Thu Apr 11 06:18:50 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 11 Apr 2019 10:18:50 +0000
Subject: [docs] [issue36416] bytes.rpartition bug in online documentation
In-Reply-To: <1553437427.15.0.469399643284.issue36416@roundup.psfhosted.org>
Message-ID: <1554977930.8.0.31032325142.issue36416@roundup.psfhosted.org>


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


New changeset 04b114eede82c7ffd7b3d9b40e8bf707780b022b by Miss Islington (bot) in branch '3.7':
bpo-36416: Correct bytes.rpartition documentation (GH-12543)
https://github.com/python/cpython/commit/04b114eede82c7ffd7b3d9b40e8bf707780b022b


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

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

From report at bugs.python.org  Thu Apr 11 06:20:02 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 10:20:02 +0000
Subject: [docs] [issue36416] bytes.rpartition bug in online documentation
In-Reply-To: <1553437427.15.0.469399643284.issue36416@roundup.psfhosted.org>
Message-ID: <1554978002.85.0.939433466704.issue36416@roundup.psfhosted.org>


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

From report at bugs.python.org  Thu Apr 11 06:37:55 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 10:37:55 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554979075.43.0.880008273669.issue36597@roundup.psfhosted.org>


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


New changeset ac31da8f3710f9f9b8dbb4c36b2108fb1e5b4a48 by Inada Naoki in branch '3.7':
bpo-36597: fix random doctest failure (GH-12778)
https://github.com/python/cpython/commit/ac31da8f3710f9f9b8dbb4c36b2108fb1e5b4a48


----------

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

From report at bugs.python.org  Thu Apr 11 06:38:52 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 11 Apr 2019 10:38:52 +0000
Subject: [docs] [issue36597] Travis CI: doctest failure
In-Reply-To: <1554950965.55.0.0913094506207.issue36597@roundup.psfhosted.org>
Message-ID: <1554979132.49.0.0831892130127.issue36597@roundup.psfhosted.org>


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

From report at bugs.python.org  Thu Apr 11 09:20:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 11 Apr 2019 13:20:50 +0000
Subject: [docs] [issue18697] Unify arguments names in Unicode object C API
 documentation
In-Reply-To: <1376074126.58.0.40251146149.issue18697@psf.upfronthosting.co.za>
Message-ID: <1554988850.41.0.488739638444.issue18697@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr 11 10:11:50 2019
From: report at bugs.python.org (Jeremy McMillan)
Date: Thu, 11 Apr 2019 14:11:50 +0000
Subject: [docs] [issue34788] ipaddress module fails on rfc4007 scoped IPv6
 addresses
In-Reply-To: <1537799403.03.0.956365154283.issue34788@psf.upfronthosting.co.za>
Message-ID: <1554991910.91.0.865080945307.issue34788@roundup.psfhosted.org>


Jeremy McMillan <jeremy.mcmillan at gmail.com> added the comment:

I think the code in SaltStack to handle scoped IPv6 addresses is mature, so please look at these examples.

https://github.com/saltstack/salt/blob/2085cb1078f187adf82a0cf19b39d350ff1bbd50/salt/_compat.py#L125

----------

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

From report at bugs.python.org  Thu Apr 11 11:57:05 2019
From: report at bugs.python.org (SilentGhost)
Date: Thu, 11 Apr 2019 15:57:05 +0000
Subject: [docs] [issue36604] Add recipe to itertools
In-Reply-To: <1554998010.79.0.74047877309.issue36604@roundup.psfhosted.org>
Message-ID: <1554998225.94.0.651712225535.issue36604@roundup.psfhosted.org>


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


----------
assignee:  -> docs at python
components: +Documentation -Extension Modules
nosy: +docs at python, rhettinger
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Apr 11 14:50:28 2019
From: report at bugs.python.org (Paul Ganssle)
Date: Thu, 11 Apr 2019 18:50:28 +0000
Subject: [docs] [issue34249] Full set of format codes applies to strftime
 only
In-Reply-To: <1532704035.87.0.56676864532.issue34249@psf.upfronthosting.co.za>
Message-ID: <1555008628.85.0.279703926308.issue34249@roundup.psfhosted.org>


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

To clarify, as far as I know, this note *does* apply to both strftime and strptime, as CPython doesn't have its own implementation of either. I'm not sure if any guarantees are made that the supported formatting codes will be the same between the two.

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

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

From report at bugs.python.org  Thu Apr 11 17:13:40 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 11 Apr 2019 21:13:40 +0000
Subject: [docs] [issue20582] socket.getnameinfo() does not document flags
In-Reply-To: <1392042265.22.0.885252016144.issue20582@psf.upfronthosting.co.za>
Message-ID: <1555017220.42.0.247346172594.issue20582@roundup.psfhosted.org>


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


New changeset 3993ccb6820d4239ce3d9e1c5d31f13b86e0000b by Miss Islington (bot) (Emmanuel Arias) in branch 'master':
bpo-20582: add link for manpage for flags on getnameinfo() (GH-11977)
https://github.com/python/cpython/commit/3993ccb6820d4239ce3d9e1c5d31f13b86e0000b


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

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

From report at bugs.python.org  Thu Apr 11 18:41:55 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 11 Apr 2019 22:41:55 +0000
Subject: [docs] [issue26205] Inconsistency concerning nested scopes
In-Reply-To: <1453774587.84.0.143729632402.issue26205@psf.upfronthosting.co.za>
Message-ID: <1555022515.72.0.350572878067.issue26205@roundup.psfhosted.org>


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

Assigning to @Mariatta for the sprints.

----------
assignee: docs at python -> Mariatta
nosy: +Mariatta, cheryl.sabella
versions: +Python 3.7, Python 3.8 -Python 2.7, Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri Apr 12 01:04:24 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 12 Apr 2019 05:04:24 +0000
Subject: [docs] [issue36604] Add recipe to itertools
In-Reply-To: <1554998010.79.0.74047877309.issue36604@roundup.psfhosted.org>
Message-ID: <1555045464.19.0.0247096800909.issue36604@roundup.psfhosted.org>


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

Thank you for the suggestion and the nice work.

I'm going to decline adding this to our docs because it isn't in the spirit of the other recipes (reasonably common task, reasonably simple, and/or showing off effective combinations of the other itertools).

Though the docs aren't the right place for this, it would be nice if you published a blog post or some such to show off your work, detail the though processes, and illustrate how you measured performance).  Another option is to submit this to the more-itertools project.

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

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

From report at bugs.python.org  Fri Apr 12 01:30:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 12 Apr 2019 05:30:20 +0000
Subject: [docs] [issue36599] doctest document says dict order is unstable
In-Reply-To: <1554977470.77.0.948736759807.issue36599@roundup.psfhosted.org>
Message-ID: <1555047020.41.0.288932282478.issue36599@roundup.psfhosted.org>


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

Go ahead and change it to:   "For example, when printing a set, Python doesn?t guarantee that the else will be printed in any particular order,"

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

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

From report at bugs.python.org  Fri Apr 12 02:20:25 2019
From: report at bugs.python.org (Inada Naoki)
Date: Fri, 12 Apr 2019 06:20:25 +0000
Subject: [docs] [issue36599] doctest document says dict order is unstable
In-Reply-To: <1554977470.77.0.948736759807.issue36599@roundup.psfhosted.org>
Message-ID: <1555050025.84.0.763207870654.issue36599@roundup.psfhosted.org>


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

Oh, #34839 had fixed this already.
It was not backported to 3.7 yet.

----------

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

From report at bugs.python.org  Fri Apr 12 02:21:25 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 12 Apr 2019 06:21:25 +0000
Subject: [docs] [issue34839] doctest: Change example under warnings section
In-Reply-To: <1538180284.16.0.545547206417.issue34839@psf.upfronthosting.co.za>
Message-ID: <1555050085.21.0.519840195458.issue34839@roundup.psfhosted.org>


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


----------
pull_requests: +12720

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

From report at bugs.python.org  Fri Apr 12 02:21:28 2019
From: report at bugs.python.org (Inada Naoki)
Date: Fri, 12 Apr 2019 06:21:28 +0000
Subject: [docs] [issue36599] doctest document says dict order is unstable
In-Reply-To: <1554977470.77.0.948736759807.issue36599@roundup.psfhosted.org>
Message-ID: <1555050088.32.0.933571064154.issue36599@roundup.psfhosted.org>


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


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> doctest: Change example under warnings section

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

From report at bugs.python.org  Fri Apr 12 02:27:31 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 12 Apr 2019 06:27:31 +0000
Subject: [docs] [issue34839] doctest: Change example under warnings section
In-Reply-To: <1538180284.16.0.545547206417.issue34839@psf.upfronthosting.co.za>
Message-ID: <1555050451.77.0.745436368511.issue34839@roundup.psfhosted.org>


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


New changeset a910c2c6f3542b61f084de2ece0d8dab09c5a0fa by Miss Islington (bot) in branch '3.7':
bpo-34839: Add a 'before 3.6' in the section 'warnings' of doctest (GH-9736)
https://github.com/python/cpython/commit/a910c2c6f3542b61f084de2ece0d8dab09c5a0fa


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

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

From report at bugs.python.org  Fri Apr 12 08:09:53 2019
From: report at bugs.python.org (Vratko Polak)
Date: Fri, 12 Apr 2019 12:09:53 +0000
Subject: [docs] [issue36612] Unittest document is not clear on SetUpClass
 calls
Message-ID: <1555070993.71.0.91547720267.issue36612@roundup.psfhosted.org>


New submission from Vratko Polak <vrpolak at cisco.com>:

One particular paragraph from unittest.rst is not clear enough:

"If you want the setUpClass and tearDownClass on base classes called then you must call up to them yourself. The implementations in TestCase are empty."

It has sparkled a debate here [0].

Example:
A class SuperTestCase, which inherits from unittest.TestCase, defines some non-trivial setUpClass class method. Then a class SubTestCase, which inherits from SuperTestCase, wants to have SuperTestCase.setUpClass executed as its setUpClass.
Does SubTestCase need to override setUpClass just to call SuperTestCase.setUpClass (as the paragraphs might suggest), or can it rely in inheritance to have it executed without overriding?

I will create GitHub PR soon.

[0] https://gerrit.fd.io/r/#/c/18579/1/test/test_sparse_vec.py at 14

----------
assignee: docs at python
components: Documentation
messages: 340028
nosy: docs at python, vrpolakatcisco
priority: normal
severity: normal
status: open
title: Unittest document is not clear on SetUpClass calls
type: enhancement
versions: Python 3.9

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

From report at bugs.python.org  Fri Apr 12 08:23:16 2019
From: report at bugs.python.org (Vratko Polak)
Date: Fri, 12 Apr 2019 12:23:16 +0000
Subject: [docs] [issue36612] Unittest document is not clear on SetUpClass
 calls
In-Reply-To: <1555070993.71.0.91547720267.issue36612@roundup.psfhosted.org>
Message-ID: <1555071796.24.0.220043493745.issue36612@roundup.psfhosted.org>


Change by Vratko Polak <vrpolak at cisco.com>:


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

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

From report at bugs.python.org  Fri Apr 12 08:35:33 2019
From: report at bugs.python.org (SilentGhost)
Date: Fri, 12 Apr 2019 12:35:33 +0000
Subject: [docs] [issue36612] Unittest document is not clear on SetUpClass
 calls
In-Reply-To: <1555070993.71.0.91547720267.issue36612@roundup.psfhosted.org>
Message-ID: <1555072533.72.0.57423524499.issue36612@roundup.psfhosted.org>


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

Normal inheritance rules apply to TestCase and its subclasses, as can be demonstrated by a trivial example.

----------
nosy: +SilentGhost
versions: +Python 3.7, Python 3.8 -Python 3.9

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

From report at bugs.python.org  Fri Apr 12 14:13:17 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 12 Apr 2019 18:13:17 +0000
Subject: [docs] [issue25361] Is python-3-5-0.exe compiled with SSE2
 instrutions? If so should we mention this?
In-Reply-To: <1444473804.35.0.126289501902.issue25361@psf.upfronthosting.co.za>
Message-ID: <1555092797.65.0.899660340564.issue25361@roundup.psfhosted.org>


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

For 3.8 we support as far back as Win7 SP1 with the update for secure DLL loading, neither of which require SSE2. So we should hold this for 3.9 when we drop Win7 completely.

----------

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

From report at bugs.python.org  Fri Apr 12 16:09:17 2019
From: report at bugs.python.org (Charles Merriam)
Date: Fri, 12 Apr 2019 20:09:17 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
Message-ID: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>


New submission from Charles Merriam <charles.merriam at gmail.com>:

On page:
https://docs.python.org/3.8/library/itertools.html

In the heading summary, in the "Iterators terminating on the shortest input sequence:" section, in the "zip_longest()" table row, in the "Arguments" column, the text "p, q, ..." should be "p, q, ... [, fillvalue=None]"

----------
assignee: docs at python
components: Documentation
messages: 340107
nosy: CharlesMerriam, docs at python
priority: normal
severity: normal
status: open
title: Documentation missing parameter for Itertools.zip_longest
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Fri Apr 12 16:13:14 2019
From: report at bugs.python.org (SilentGhost)
Date: Fri, 12 Apr 2019 20:13:14 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1555099994.97.0.848125808589.issue36620@roundup.psfhosted.org>


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


----------
stage:  -> needs patch
versions: +Python 3.7

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

From report at bugs.python.org  Fri Apr 12 16:27:58 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 12 Apr 2019 20:27:58 +0000
Subject: [docs] [issue28809] mention asyncio.gather non-deterministic task
 starting order
In-Reply-To: <1480183522.09.0.687431688906.issue28809@psf.upfronthosting.co.za>
Message-ID: <1555100878.2.0.0406821840225.issue28809@roundup.psfhosted.org>


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

I believe the issue mentioned here was addressed by the doc rewrite in issue 33649.  I'm going to mark this as a duplicate of that issue, but if the concern here still exists, then please re-open this issue.

----------
nosy: +cheryl.sabella
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> asyncio docs overhaul

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

From report at bugs.python.org  Fri Apr 12 17:27:16 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 12 Apr 2019 21:27:16 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1555104436.13.0.755841693909.issue36620@roundup.psfhosted.org>


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

Good catch!  In the same section, accumulate() is missing the `initial` argument.  

Would you be interested in submitting a pull request for this?

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

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

From report at bugs.python.org  Fri Apr 12 18:26:52 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 12 Apr 2019 22:26:52 +0000
Subject: [docs] [issue33922] [Windows] Document the launcher's -64 suffix
In-Reply-To: <1529538222.45.0.56676864532.issue33922@psf.upfronthosting.co.za>
Message-ID: <1555108012.09.0.894939944645.issue33922@roundup.psfhosted.org>


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


New changeset 1e2ad6c275d2b09e76b7cbba7281d5a125a593c1 by Steve Dower (mrh1997) in branch 'master':
bpo-33922: Adding documentation for new "-64" suffix of Python launcher (GH-7849)
https://github.com/python/cpython/commit/1e2ad6c275d2b09e76b7cbba7281d5a125a593c1


----------

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

From report at bugs.python.org  Fri Apr 12 18:26:59 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 12 Apr 2019 22:26:59 +0000
Subject: [docs] [issue33922] [Windows] Document the launcher's -64 suffix
In-Reply-To: <1529538222.45.0.56676864532.issue33922@psf.upfronthosting.co.za>
Message-ID: <1555108019.14.0.534508897881.issue33922@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +12737

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

From report at bugs.python.org  Fri Apr 12 18:32:37 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 12 Apr 2019 22:32:37 +0000
Subject: [docs] [issue33922] [Windows] Document the launcher's -64 suffix
In-Reply-To: <1529538222.45.0.56676864532.issue33922@psf.upfronthosting.co.za>
Message-ID: <1555108357.26.0.85174915162.issue33922@roundup.psfhosted.org>


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


New changeset 395bb94a7f1c3ec9c29976738dfc6cb5d31f9aee by Miss Islington (bot) in branch '3.7':
bpo-33922: Adding documentation for new "-64" suffix of Python launcher (GH-7849)
https://github.com/python/cpython/commit/395bb94a7f1c3ec9c29976738dfc6cb5d31f9aee


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

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

From report at bugs.python.org  Fri Apr 12 18:33:43 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 12 Apr 2019 22:33:43 +0000
Subject: [docs] [issue35581] Document @typing.type_check_only
In-Reply-To: <1545742357.2.0.712150888896.issue35581@roundup.psfhosted.org>
Message-ID: <1555108423.76.0.620744952868.issue35581@roundup.psfhosted.org>


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


New changeset 1e8295402bf5e81d327ed2b5eb88a6b6de449d63 by Guido van Rossum (Sebastian Rittau) in branch 'master':
bpo-35581: Document @typing.type_check_only (GH-11312)
https://github.com/python/cpython/commit/1e8295402bf5e81d327ed2b5eb88a6b6de449d63


----------

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

From report at bugs.python.org  Fri Apr 12 18:34:24 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 12 Apr 2019 22:34:24 +0000
Subject: [docs] [issue35581] Document @typing.type_check_only
In-Reply-To: <1545742357.2.0.712150888896.issue35581@roundup.psfhosted.org>
Message-ID: <1555108464.51.0.274401356757.issue35581@roundup.psfhosted.org>


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


----------
pull_requests: +12739

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

From report at bugs.python.org  Fri Apr 12 18:36:12 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 12 Apr 2019 22:36:12 +0000
Subject: [docs] [issue35581] Document @typing.type_check_only
In-Reply-To: <1545742357.2.0.712150888896.issue35581@roundup.psfhosted.org>
Message-ID: <1555108572.96.0.0567245924189.issue35581@roundup.psfhosted.org>


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

Now waiting for the backport to 3.7. Once that's done I'll close this as fixed.

----------

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

From report at bugs.python.org  Fri Apr 12 18:48:01 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 12 Apr 2019 22:48:01 +0000
Subject: [docs] [issue35581] Document @typing.type_check_only
In-Reply-To: <1545742357.2.0.712150888896.issue35581@roundup.psfhosted.org>
Message-ID: <1555109281.88.0.0673920901937.issue35581@roundup.psfhosted.org>


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


New changeset b759a2c5b9612a03c8b30514aa93444268931e5e by Miss Islington (bot) in branch '3.7':
bpo-35581: Document @typing.type_check_only (GH-11312)
https://github.com/python/cpython/commit/b759a2c5b9612a03c8b30514aa93444268931e5e


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

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

From report at bugs.python.org  Fri Apr 12 18:51:09 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 12 Apr 2019 22:51:09 +0000
Subject: [docs] [issue35581] Document @typing.type_check_only
In-Reply-To: <1545742357.2.0.712150888896.issue35581@roundup.psfhosted.org>
Message-ID: <1555109469.21.0.312693043198.issue35581@roundup.psfhosted.org>


Change by Guido van Rossum <guido at python.org>:


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

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

From report at bugs.python.org  Fri Apr 12 19:11:50 2019
From: report at bugs.python.org (Charles Merriam)
Date: Fri, 12 Apr 2019 23:11:50 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555104436.13.0.755841693909.issue36620@roundup.psfhosted.org>
Message-ID: <CACYynckT=qH+zKqwXvJWBtHCex8=Gw9v06QNfL+-WT3_gwi5QA@mail.gmail.com>


Charles Merriam <charles.merriam at gmail.com> added the comment:

Hi Cheryl,

No.  I've dealt with the Team Python long cycles for random pull requests
before.

Charles

On Fri, Apr 12, 2019 at 2:27 PM Cheryl Sabella <report at bugs.python.org>
wrote:

>
> Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:
>
> Good catch!  In the same section, accumulate() is missing the `initial`
> argument.
>
> Would you be interested in submitting a pull request for this?
>
> ----------
> nosy: +cheryl.sabella
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue36620>
> _______________________________________
>

----------
nosy: +Charles.Merriam

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

From report at bugs.python.org  Fri Apr 12 19:15:09 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 12 Apr 2019 23:15:09 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1555110909.17.0.759161670948.issue36620@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 12 19:59:21 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 12 Apr 2019 23:59:21 +0000
Subject: [docs] [issue36620] Documentation missing parameter for
 Itertools.zip_longest
In-Reply-To: <1555099757.43.0.201440165942.issue36620@roundup.psfhosted.org>
Message-ID: <1555113561.77.0.43104738122.issue36620@roundup.psfhosted.org>


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

Thanks, Charles.  I'm going to assign this to @Mariatta for the sprints.

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

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

From report at bugs.python.org  Sat Apr 13 06:55:55 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 10:55:55 +0000
Subject: [docs] [issue33922] [Windows] Document the launcher's -64 suffix
In-Reply-To: <1529538222.45.0.56676864532.issue33922@psf.upfronthosting.co.za>
Message-ID: <1555152955.37.0.356683988214.issue33922@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Apr 13 07:00:03 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 11:00:03 +0000
Subject: [docs] [issue31743] Proportional Width Font on Generated Python
 Docs PDFs
In-Reply-To: <1507633217.5.0.213398074469.issue31743@psf.upfronthosting.co.za>
Message-ID: <1555153203.91.0.920349841022.issue31743@roundup.psfhosted.org>


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


----------
nosy: +eric.araujo, ezio.melotti, mdk, willingc

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

From report at bugs.python.org  Sat Apr 13 08:01:19 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 12:01:19 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1555156879.72.0.589540881189.issue18610@roundup.psfhosted.org>


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


New changeset f8716c88f13f035c126fc1db499ae0ea309c7ece by Cheryl Sabella in branch 'master':
bpo-18610: Update wsgiref.validate docstring for wsgi.input read() (GH-11663)
https://github.com/python/cpython/commit/f8716c88f13f035c126fc1db499ae0ea309c7ece


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

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

From report at bugs.python.org  Sat Apr 13 08:04:58 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 12:04:58 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1555157098.26.0.365633718612.issue18610@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Apr 13 08:29:46 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 12:29:46 +0000
Subject: [docs] [issue17259] Document round half to even rule for floats
In-Reply-To: <1361395314.25.0.489128727343.issue17259@psf.upfronthosting.co.za>
Message-ID: <1555158586.41.0.797300250856.issue17259@roundup.psfhosted.org>


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

It doesn't seem there have been other bugs reported related to this.  However, if it's still agreed that the documentation should be clarified, I think a link from `locale.format_string()` (note, format() has been deprecated, hence the change in the name) to the Format Specification Mini-Language might helpful.  Also, Terry's suggestion in msg182706 specific to %f rounding could be added.

----------
nosy: +cheryl.sabella
versions: +Python 3.7, Python 3.8 -Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Apr 13 18:58:43 2019
From: report at bugs.python.org (=?utf-8?q?Jakub_Moli=C5=84ski?=)
Date: Sat, 13 Apr 2019 22:58:43 +0000
Subject: [docs] [issue36625] Obsolete comments in docstrings in fractions
 module
Message-ID: <1555196323.81.0.314132124963.issue36625@roundup.psfhosted.org>


New submission from Jakub Moli?ski <jakub at molinski.dev>:

3 docstrings in fractions.Fraction contain comments referring to python 3.0. 

def __floor__(a):
    """Will be math.floor(a) in 3.0."""

def __ceil__(a):
    """Will be math.ceil(a) in 3.0."""

def __round__(self, ndigits=None):
    """Will be round(self, ndigits) in 3.0.

    Rounds half toward even.
    """


To make it consistent with other docstrings in the module these should be changed to """math.floor(a)""", """math.ceil(a)""", and 
    """round(self, ndigits)

    Rounds half toward even.
    """

----------
assignee: docs at python
components: Documentation
messages: 340174
nosy: docs at python, jakub.molinski
priority: normal
severity: normal
status: open
title: Obsolete comments in docstrings in fractions module
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Sat Apr 13 19:08:55 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 23:08:55 +0000
Subject: [docs] [issue36625] Obsolete comments in docstrings in fractions
 module
In-Reply-To: <1555196323.81.0.314132124963.issue36625@roundup.psfhosted.org>
Message-ID: <1555196935.4.0.835396195454.issue36625@roundup.psfhosted.org>


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


----------
nosy: +mark.dickinson, rhettinger

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

From report at bugs.python.org  Sat Apr 13 19:14:47 2019
From: report at bugs.python.org (=?utf-8?q?Jakub_Moli=C5=84ski?=)
Date: Sat, 13 Apr 2019 23:14:47 +0000
Subject: [docs] [issue36625] Obsolete comments in docstrings in fractions
 module
In-Reply-To: <1555196323.81.0.314132124963.issue36625@roundup.psfhosted.org>
Message-ID: <1555197287.44.0.463259417852.issue36625@roundup.psfhosted.org>


Change by Jakub Moli?ski <jakub at molinski.dev>:


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

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

From report at bugs.python.org  Sat Apr 13 19:26:34 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 13 Apr 2019 23:26:34 +0000
Subject: [docs] [issue24417] Type-specific documentation for __format__
 methods
In-Reply-To: <1433857085.94.0.53514781812.issue24417@psf.upfronthosting.co.za>
Message-ID: <1555197994.46.0.376884529783.issue24417@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun Apr 14 04:33:57 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 14 Apr 2019 08:33:57 +0000
Subject: [docs] [issue36625] Obsolete comments in docstrings in fractions
 module
In-Reply-To: <1555196323.81.0.314132124963.issue36625@roundup.psfhosted.org>
Message-ID: <1555230837.26.0.0731943356333.issue36625@roundup.psfhosted.org>


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

Agreed that these should be fixed.

----------

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

From report at bugs.python.org  Sun Apr 14 09:11:34 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 14 Apr 2019 13:11:34 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
In-Reply-To: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>
Message-ID: <1555247494.82.0.490009002407.issue13127@roundup.psfhosted.org>


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

Stefan,

Do you think this should be documented?

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

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

From report at bugs.python.org  Sun Apr 14 10:14:24 2019
From: report at bugs.python.org (Stefan Behnel)
Date: Sun, 14 Apr 2019 14:14:24 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
In-Reply-To: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>
Message-ID: <1555251264.46.0.308491119128.issue13127@roundup.psfhosted.org>


Stefan Behnel <stefan_ml at behnel.de> added the comment:

The intended interface seems to be to change .name rather than .localName, so yes, that should be documented somewhere.

The implementation seems a bit funny in that a "self._localName", if set, takes precedence, but there doesn't seem to be an official way to set it. The Attr() constructor even takes a "localname" argument, which it then ignores. o_O

----------
components: +XML
stage: test needed -> needs patch
versions: +Python 3.8

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

From alex_zaz at hotmail.com  Sat Apr 13 23:34:41 2019
From: alex_zaz at hotmail.com (Alejandro Zazueta)
Date: Sun, 14 Apr 2019 03:34:41 +0000
Subject: [docs] Documentation bug report
Message-ID: <SN6PR03MB4143A3782C338E2C73D0066EE12A0@SN6PR03MB4143.namprd03.prod.outlook.com>

In the document name ?5. Data Structures?:


                https://docs.python.org/3/tutorial/datastructures.html?highlight=matrix


there is an example with syntax error, in the section:

            5.1.3. List Comprehensions


It seems that the following example:

>>> [x, x**2 for x in range(6)]
  File "<stdin>", line 1, in <module>
    [x, x**2 for x in range(6)]


Is missing the parentheses for the tuple.

The suggested correction is:

>>> [(x, x**2) for x in range(6)]
[(0, 0), (1, 1), (2, 4), (3, 9), (4, 16), (5, 25)]


Hope it helps,
Alex Zazueta

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

From report at bugs.python.org  Sun Apr 14 15:44:55 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 14 Apr 2019 19:44:55 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1555271095.97.0.865599027976.issue30840@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


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

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

From berker.peksag at gmail.com  Sun Apr 14 18:48:42 2019
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Mon, 15 Apr 2019 01:48:42 +0300
Subject: [docs] Documentation bug report
In-Reply-To: <SN6PR03MB4143A3782C338E2C73D0066EE12A0@SN6PR03MB4143.namprd03.prod.outlook.com>
References: <SN6PR03MB4143A3782C338E2C73D0066EE12A0@SN6PR03MB4143.namprd03.prod.outlook.com>
Message-ID: <CAF4280LsH=V7hJsTD7=a4LW8ZNcngkHtH=dEXcwRJaL-gXvZ7A@mail.gmail.com>

On Sun, Apr 14, 2019 at 5:40 PM Alejandro Zazueta <alex_zaz at hotmail.com> wrote:
> It seems that the following example:
>
> >>> [x, x**2 for x in range(6)]
>   File "<stdin>", line 1, in <module>
>     [x, x**2 for x in range(6)]
>
> Is missing the parentheses for the tuple.

Hi Alex,

Thank you for your report! The point of the example is to show that it
is invalid Python code. See the comment above the example:

# the tuple must be parenthesized, otherwise an error is raised

--Berker

From alex_zaz at hotmail.com  Mon Apr 15 01:45:42 2019
From: alex_zaz at hotmail.com (Alejandro Zazueta)
Date: Mon, 15 Apr 2019 05:45:42 +0000
Subject: [docs] Documentation bug report
In-Reply-To: <CAF4280LsH=V7hJsTD7=a4LW8ZNcngkHtH=dEXcwRJaL-gXvZ7A@mail.gmail.com>
References: <SN6PR03MB4143A3782C338E2C73D0066EE12A0@SN6PR03MB4143.namprd03.prod.outlook.com>,
 <CAF4280LsH=V7hJsTD7=a4LW8ZNcngkHtH=dEXcwRJaL-gXvZ7A@mail.gmail.com>
Message-ID: <SN6PR03MB4143B56ED86600CA5C90267CE12B0@SN6PR03MB4143.namprd03.prod.outlook.com>

Oh, ok, I understand. Thanks for your explanation, I can see what you mean now.
Sorry for the mistake. I apologize.

Alex.


________________________________
From: Berker Peksa? <berker.peksag at gmail.com>
Sent: Sunday, April 14, 2019 5:48 PM
To: Alejandro Zazueta
Cc: docs at python.org
Subject: Re: [docs] Documentation bug report

On Sun, Apr 14, 2019 at 5:40 PM Alejandro Zazueta <alex_zaz at hotmail.com> wrote:
> It seems that the following example:
>
> >>> [x, x**2 for x in range(6)]
>   File "<stdin>", line 1, in <module>
>     [x, x**2 for x in range(6)]
>
> Is missing the parentheses for the tuple.

Hi Alex,

Thank you for your report! The point of the example is to show that it
is invalid Python code. See the comment above the example:

# the tuple must be parenthesized, otherwise an error is raised

--Berker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190415/912cbb98/attachment.html>

From report at bugs.python.org  Mon Apr 15 07:53:13 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 15 Apr 2019 11:53:13 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning is not so
 useful.
In-Reply-To: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>
Message-ID: <1555329193.25.0.139270008011.issue36404@roundup.psfhosted.org>


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


----------
pull_requests: +12762

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

From report at bugs.python.org  Mon Apr 15 08:37:12 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 15 Apr 2019 12:37:12 +0000
Subject: [docs] [issue36625] Obsolete comments in docstrings in fractions
 module
In-Reply-To: <1555196323.81.0.314132124963.issue36625@roundup.psfhosted.org>
Message-ID: <1555331832.84.0.211202481248.issue36625@roundup.psfhosted.org>


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


New changeset a9a28808e5a03d2e68e421227c113a38edc40946 by Mark Dickinson (Jakub Molinski) in branch 'master':
bpo-36625: Remove obsolete comments from docstrings in fractions module (GH-12822)
https://github.com/python/cpython/commit/a9a28808e5a03d2e68e421227c113a38edc40946


----------

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

From report at bugs.python.org  Mon Apr 15 08:38:17 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 15 Apr 2019 12:38:17 +0000
Subject: [docs] [issue36625] Obsolete comments in docstrings in fractions
 module
In-Reply-To: <1555196323.81.0.314132124963.issue36625@roundup.psfhosted.org>
Message-ID: <1555331897.22.0.276973531907.issue36625@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Mon Apr 15 08:41:38 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 15 Apr 2019 12:41:38 +0000
Subject: [docs] [issue36404] Document PendingDeprecationWarning is not so
 useful.
In-Reply-To: <1554454470.93.0.363997208929.issue36404@roundup.psfhosted.org>
Message-ID: <1555332098.54.0.167090546656.issue36404@roundup.psfhosted.org>


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


----------
pull_requests: +12763

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

From report at bugs.python.org  Mon Apr 15 12:00:02 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Mon, 15 Apr 2019 16:00:02 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1555344002.46.0.395184277228.issue30840@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

I actually opened a PR with the relevant documentation suggested by @ncoghlan but what am wondering is. 

when @ncoghlan says That part of the PEP was never implemented - relative imports have never been allowed to cross package boundaries in practice, does it mean we dont need this to work anymore as was earlier put in the PEP?  In which case this issue will be closed if my PR is merged or we should actually implement it to complete everything the PEP specified?

----------
nosy: +nanjekyejoannah

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

From report at bugs.python.org  Mon Apr 15 14:27:39 2019
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 15 Apr 2019 18:27:39 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1555352859.36.0.042118248595.issue30840@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

RE: "does it mean we dont need this to work anymore as was earlier put in the PEP?"

Correct, we aren't going to implement that part of the PEP ever.

----------

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

From report at bugs.python.org  Mon Apr 15 15:14:12 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Mon, 15 Apr 2019 19:14:12 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1555355652.12.0.312517216312.issue30840@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

Great, thanks for clarity.

----------

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

From report at bugs.python.org  Mon Apr 15 16:18:17 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 15 Apr 2019 20:18:17 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1555359497.23.0.186633129715.issue35329@roundup.psfhosted.org>


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

Hi Hans,

Would you be interested in making a pull request with this change?  Thanks!

----------
nosy: +cheryl.sabella
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.8

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

From 15061116790 at 163.com  Mon Apr 15 23:40:11 2019
From: 15061116790 at 163.com (=?UTF-8?B?6JKL5b636ZGr?=)
Date: Tue, 16 Apr 2019 11:40:11 +0800 (GMT+08:00)
Subject: [docs] Consultation: Free publication of the Chinese simplified
 version of python documents, whether I need to be authorized
Message-ID: <238fa84f.2423.16a243b113e.Coremail.15061116790@163.com>

Dear Sir / Madam?
        I am writing a letter to you. I want to know if I translate the python's document into Chinese and publish it freely. Do I need to be authorized?
Thank you for taking the time to check this email.  Hope to receive your reply as soon as possible.
                                                                                                                                                                                        A student from Shanghai University of China
                                                                                                                                                                                                                   Dexin Jiang
                                                                                                                                                                                                                    2019.4.16


                                                                                                                                                                                                                            
| |
???
Dexin Jiang
|
|
15061116790 at 163.com
|
???????????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190416/5d93bab2/attachment-0001.html>

From report at bugs.python.org  Tue Apr 16 08:53:14 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 16 Apr 2019 12:53:14 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1555419194.33.0.494102648612.issue36345@roundup.psfhosted.org>


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


New changeset 2b7f93b99afbe78e4e567d9252d9470d29f387c8 by St?phane Wirtel in branch 'master':
bpo-36345: Update wsgiref example (GH-12562)
https://github.com/python/cpython/commit/2b7f93b99afbe78e4e567d9252d9470d29f387c8


----------

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

From avmo at kth.se  Tue Apr 16 04:18:29 2019
From: avmo at kth.se (Ashwin Vishnu)
Date: Tue, 16 Apr 2019 10:18:29 +0200
Subject: [docs] Clean up dead links in the docs
Message-ID: <31f485e7-216c-ca27-dca7-cd6d1c4a2305@kth.se>

Hi,

I took some time to filter out all the links and check them using cURL
with the script attached. The full output (test_links.log) is also
attached, and ignoring the links which returned 200, we get:

$ grep -v 200 test_links.log

https://pythonhosted.org/pyobjc/ 404
https://www.jwz.org/doc/content-length.html 403
https://www.jwz.org/doc/content-length.html 403
https://www.jwz.org/doc/content-length.html 403
http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html 000
https://cnswww.cns.cwru.edu/php/chet/readline/rluserman.html#SEC9 000
http://tcl.activestate.com/ 000
http://www.tldp.org/HOWTO/XML-RPC-HOWTO/index.html 000
https://www.microsoft.com/com/ 404
http://oldwiki.mingw.org/index.php/Python        0.000000e+00xtensions 404
http://catb.org/~esr/trove/ 000
http://sphinx-doc.org/examples.html 404
https://hg.python.org/cpython/file/3.2/Misc/NEWS 504
https://parlab.eecs.berkeley.edu/wiki/_media/patterns/paraplop_g1_3.pdf 500
http://greenteapress.com/semaphores/downey08semaphores.pdf 404
http://hginit.com 000


I think a good majority of the above links are dead. Please find an
alternative for those links in the docs.

Best,
Ashwin Vishnu Mohanan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_links.log
Type: text/x-log
Size: 32865 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190416/063647ed/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test_links.sh
Type: application/x-shellscript
Size: 203 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190416/063647ed/attachment-0003.bin>

From report at bugs.python.org  Tue Apr 16 16:43:52 2019
From: report at bugs.python.org (PEW's Corner)
Date: Tue, 16 Apr 2019 20:43:52 +0000
Subject: [docs] [issue36644] Improve documentation of slice.indices()
Message-ID: <1555447432.64.0.0569137704921.issue36644@roundup.psfhosted.org>


New submission from PEW's Corner <pewscorner at gmail.com>:

The slice class is described in the Built-In Functions document:

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

... but that entry fails to mention the indices() method, and states that slice objects "have no other explicit functionality" beyond the start, stop, and step attributes. The entry links only to a glossary item which doesn't provide more info.

However, it turns out that there is another description of slice objects - including the indices() method - in the Data model document:

https://docs.python.org/3/reference/datamodel.html#slice.indices

... but (as the rejected issue 11842 in my opinion correctly argues) this entry is not clear about how to interpret the return values from the indices() method, i.e. that they are appropriate as arguments to range() - not as arguments to a new slice().

So, right now the best documentation of the indices() method is the old Python 2.3 "what's new" documentation of extended slices:

https://docs.python.org/2.3/whatsnew/section-slices.html

"To simplify implementing sequences that support extended slicing, slice objects now have a method indices(length) which, given the length of a sequence, returns a (start, stop, step) tuple that can be passed directly to range(). indices() handles omitted and out-of-bounds indices in a manner consistent with regular slices (and this innocuous phrase hides a welter of confusing details!)."

I would propose to at least:
* Add a link from the slice class in the Built-In Functions doc to the slice object section of the Data model doc.
* Delete the statement about "no other explicit functionality" in the Built-In Functions doc.
* Mention in the Data model doc that the return values from indices() can be passed to range() to obtain the sequence of indices described by the slice when applied to a sequence object of the specified length, and perhaps make it clear that the indices() values do not in general represent the new start, stop, and step attributes of a truncated slice object.

----------
assignee: docs at python
components: Documentation
messages: 340364
nosy: docs at python, pewscorner
priority: normal
severity: normal
status: open
title: Improve documentation of slice.indices()
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Apr 16 18:40:12 2019
From: report at bugs.python.org (Caleb Donovick)
Date: Tue, 16 Apr 2019 22:40:12 +0000
Subject: [docs] [issue35297] untokenize documentation is not correct
In-Reply-To: <1542921902.22.0.788709270274.issue35297@psf.upfronthosting.co.za>
Message-ID: <1555454412.73.0.689652750157.issue35297@roundup.psfhosted.org>


Change by Caleb Donovick <donovick at cs.stanford.edu>:


----------
nosy: +donovick

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

From report at bugs.python.org  Tue Apr 16 18:42:59 2019
From: report at bugs.python.org (mollison)
Date: Tue, 16 Apr 2019 22:42:59 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
Message-ID: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>


New submission from mollison <mollison at cs.unc.edu>:

This is regarding the change to re.sub() between 3.6 and 3.7 that results in different behavior even for simple cases like the following:

re.sub('a*','b', 'a') returns 'b' in 3.6 and 'bb' in 3.7

This change is well documented here:
https://docs.python.org/3/whatsnew/3.7.html#changes-in-the-python-api

However, it is not well documented here:
https://docs.python.org/3.7/library/re.html

The latter document does actually contain the appropriate text: "Empty matches for the pattern are replaced when adjacent to a previous non-empty match."

However, the formatting makes this text look like it was always there, and is not part of the 3.7 changes announcement.

That is how I interpreted it, leading to some lost productivity.

After so many years, people don't expect the regex engine to change like this, and that only makes it easier to misinterpret that text as always have been there vs. being new to 3.7.

Related:
https://bugs.python.org/issue32308

----------
assignee: docs at python
components: Documentation
messages: 340370
nosy: docs at python, mollison
priority: normal
severity: normal
status: open
title: re.sub() library entry does not adequately document surprising change in behavior between versions
versions: Python 3.7

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

From report at bugs.python.org  Tue Apr 16 20:49:55 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 17 Apr 2019 00:49:55 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555462195.28.0.561170939792.issue36645@roundup.psfhosted.org>


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

I believe the second note under "Changed in 3.7" is intended to address this:

> Empty matches for the pattern are replaced when adjacent to a previous non-empty match.

Obviously not as detailed as the What's New entry, but it's there.

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

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

From report at bugs.python.org  Tue Apr 16 21:25:00 2019
From: report at bugs.python.org (mollison)
Date: Wed, 17 Apr 2019 01:25:00 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555464300.61.0.590464961281.issue36645@roundup.psfhosted.org>


mollison <mollison at cs.unc.edu> added the comment:

You have not understood my message. I know that text is already there.

My point is that because it's in a separate paragraph, it looks like it's not part of Changed in 3.7.

There is nowhere else on the page where a change description is in a separate paragraph from the "Changed in version X.X:" text.

When I came across this I thought, this probably goes with the paragraph before it, right? In other words, it's probably another change from 3.7, just in a different paragraph?

But then I thought, no, they probably wouldn't change something like that (i.e. basic regex stuff) after so many years.

So it's not that obvious.

----------

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

From ansari.walatima at outlook.com  Wed Apr 17 02:15:12 2019
From: ansari.walatima at outlook.com (Shayer Ansari)
Date: Wed, 17 Apr 2019 06:15:12 +0000
Subject: [docs] Python.remove() function working on all list instead of one.
Message-ID: <KL1PR0201MB2117AB45470D7CEA444E8D88FE250@KL1PR0201MB2117.apcprd02.prod.outlook.com>


a =[1,2,3,4,5]
b=a
c=a
a.remove(3)
print(a)
print(b)
print(c)
Output-
>[1,2,4,5]
>[1,2,4,5]
>[1,2,4,5]

Sent from Windows Mail

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190417/017ab8ff/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Bug.png
Type: image/png
Size: 5347 bytes
Desc: Bug.png
URL: <http://mail.python.org/pipermail/docs/attachments/20190417/017ab8ff/attachment-0001.png>

From report at bugs.python.org  Wed Apr 17 13:48:46 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 17 Apr 2019 17:48:46 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555523326.68.0.0329420225029.issue36645@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

@mollison: would you like to open a PR w/ how you would expect it to be formatted?

----------
nosy: +brett.cannon

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

From report at bugs.python.org  Wed Apr 17 14:53:02 2019
From: report at bugs.python.org (Enrico Carbognani)
Date: Wed, 17 Apr 2019 18:53:02 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
Message-ID: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>


New submission from Enrico Carbognani <enrico.carbognani at gmail.com>:

In the documentation for the call_later and the call_at methods there is a note which says that the delay cannot be longer than a day, but both methods have a note saying that this limitation was removed in Python 3.8.

----------
assignee: docs at python
components: Documentation
files: documenation_incosistency.png
messages: 340434
nosy: Enrico Carbognani, docs at python
priority: normal
severity: normal
status: open
title: Asyncio Event Loop documentation inconsistency (call_later and call_at methods)
versions: Python 3.8
Added file: https://bugs.python.org/file48273/documenation_incosistency.png

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

From report at bugs.python.org  Wed Apr 17 16:12:11 2019
From: report at bugs.python.org (Enrico Carbognani)
Date: Wed, 17 Apr 2019 20:12:11 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555531931.8.0.868897063106.issue36651@roundup.psfhosted.org>


Change by Enrico Carbognani <enrico.carbognani at gmail.com>:


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

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

From report at bugs.python.org  Wed Apr 17 17:01:20 2019
From: report at bugs.python.org (mollison)
Date: Wed, 17 Apr 2019 21:01:20 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555534880.7.0.860437918426.issue36645@roundup.psfhosted.org>


mollison <mollison at cs.unc.edu> added the comment:

@brett.cannon: Yes, I will submit a PR. I have the code ready to go already. I just submitted the Python contributor agreement. I think it will take the system a day or two to register that. Then, I will submit the PR.

----------

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

From report at bugs.python.org  Wed Apr 17 18:22:57 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 17 Apr 2019 22:22:57 +0000
Subject: [docs] [issue36277] pdb's recursive debug command is not listed in
 the docs
In-Reply-To: <1552441297.14.0.332408963845.issue36277@roundup.psfhosted.org>
Message-ID: <1555539777.17.0.131260344864.issue36277@roundup.psfhosted.org>


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


----------
keywords: +easy
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Wed Apr 17 18:43:11 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 17 Apr 2019 22:43:11 +0000
Subject: [docs] [issue33039] int() and math.trunc don't accept objects that
 only define __index__
In-Reply-To: <1520672231.04.0.467229070634.issue33039@psf.upfronthosting.co.za>
Message-ID: <1555540991.86.0.222293671986.issue33039@roundup.psfhosted.org>


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

R?mi,

Are you still working on the patch for this?  Thanks!

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

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

From report at bugs.python.org  Wed Apr 17 18:43:42 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 17 Apr 2019 22:43:42 +0000
Subject: [docs] [issue32913] Improve regular expression HOWTO
In-Reply-To: <1519330200.78.0.467229070634.issue32913@psf.upfronthosting.co.za>
Message-ID: <1555541021.98.0.9473619584.issue32913@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:


New changeset a6de52c74d831e45ee0ff105196da8a58b9e43cd by Brett Cannon (josh) in branch 'master':
bpo-32913: Added re.Match.groupdict example to regex HOWTO (GH-5821)
https://github.com/python/cpython/commit/a6de52c74d831e45ee0ff105196da8a58b9e43cd


----------
nosy: +brett.cannon

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

From report at bugs.python.org  Wed Apr 17 23:43:56 2019
From: report at bugs.python.org (Windson Yang)
Date: Thu, 18 Apr 2019 03:43:56 +0000
Subject: [docs] [issue36654] Add example to tokenize.tokenize
Message-ID: <1555559036.7.0.0522143852215.issue36654@roundup.psfhosted.org>


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

> The tokenize() generator requires one argument, readline, which must be a callable object which provides the same interface as the io.IOBase.readline() method of file objects. Each call to the function should return one line of input as bytes.

Add an example like this should be easier to understand:

# example.py
def foo:
    pass

# tokenize_example.py
import tokenize
f = open('example.py', 'rb')
token_gen = tokenize.tokenize(f.readline)

for token in token_gen:
    # Something like this
    # TokenInfo(type=1 (NAME), string='class', start=(1, 0), end=(1, 5), line='class Foo:\n')
    # TokenInfo(type=1 (NAME), string='Foo', start=(1, 6), end=(1, 9), line='class Foo:\n')
    # TokenInfo(type=53 (OP), string=':', start=(1, 9), end=(1, 10), line='class Foo:\n')
    print(token)

----------
assignee: docs at python
components: Documentation
messages: 340467
nosy: Windson Yang, docs at python
priority: normal
severity: normal
status: open
title: Add example to tokenize.tokenize
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/issue36654>
_______________________________________

From report at bugs.python.org  Wed Apr 17 23:58:46 2019
From: report at bugs.python.org (Dave Nguyen)
Date: Thu, 18 Apr 2019 03:58:46 +0000
Subject: [docs] [issue36277] pdb's recursive debug command is not listed in
 the docs
In-Reply-To: <1552441297.14.0.332408963845.issue36277@roundup.psfhosted.org>
Message-ID: <1555559926.63.0.452054709641.issue36277@roundup.psfhosted.org>


Change by Dave Nguyen <dv at dvnguyen.com>:


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

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

From report at bugs.python.org  Thu Apr 18 02:08:30 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Thu, 18 Apr 2019 06:08:30 +0000
Subject: [docs] [issue35297] untokenize documentation is not correct
In-Reply-To: <1542921902.22.0.788709270274.issue35297@psf.upfronthosting.co.za>
Message-ID: <1555567710.86.0.174889801884.issue35297@roundup.psfhosted.org>


Utkarsh Gupta <guptautkarsh2102 at gmail.com> added the comment:

I am not sure if that's a documentation problem, is it?
If so, I'll be happy to send a PR :)

----------
nosy: +utkarsh2102

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

From report at bugs.python.org  Thu Apr 18 02:18:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 18 Apr 2019 06:18:25 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555568305.43.0.395506695211.issue36651@roundup.psfhosted.org>


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


----------
components: +asyncio
nosy: +asvetlov, yselivanov

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

From report at bugs.python.org  Thu Apr 18 02:24:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 18 Apr 2019 06:24:25 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555568665.56.0.00289059775523.issue36645@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr 18 03:07:26 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Thu, 18 Apr 2019 07:07:26 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1555571246.68.0.107190154105.issue36008@roundup.psfhosted.org>


Utkarsh Gupta <guptautkarsh2102 at gmail.com> added the comment:

Hey,

I am a new contributor, looking for an issue to start with.
Since this is a "good first issue", I wanted to know if I could take it?

I am myself at a dev sprint and would like to get it fixed :)
Mariatta, let me know if you have any problems with the same?

----------
nosy: +utkarsh2102

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

From report at bugs.python.org  Thu Apr 18 05:20:09 2019
From: report at bugs.python.org (Antony Lee)
Date: Thu, 18 Apr 2019 09:20:09 +0000
Subject: [docs] [issue36277] pdb's recursive debug command is not listed in
 the docs
In-Reply-To: <1552441297.14.0.332408963845.issue36277@roundup.psfhosted.org>
Message-ID: <1555579209.4.0.861783291254.issue36277@roundup.psfhosted.org>


Change by Antony Lee <anntzer.lee at gmail.com>:


----------
nosy:  -Antony.Lee

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

From report at bugs.python.org  Thu Apr 18 08:43:18 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 18 Apr 2019 12:43:18 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555591398.75.0.970718373633.issue36651@roundup.psfhosted.org>


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


New changeset 7e954e7de4f3777b5ce239640bd2b76aced09561 by Miss Islington (bot) (Enrico Alarico Carbognani) in branch 'master':
bpo-36651: Fixed Asyncio Event Loop documentation inconsistency (GH-12866)
https://github.com/python/cpython/commit/7e954e7de4f3777b5ce239640bd2b76aced09561


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

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

From report at bugs.python.org  Thu Apr 18 08:43:34 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 18 Apr 2019 12:43:34 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555591414.16.0.950652675425.issue36651@roundup.psfhosted.org>


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


----------
pull_requests: +12798

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

From report at bugs.python.org  Thu Apr 18 08:44:36 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Thu, 18 Apr 2019 12:44:36 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555591476.6.0.567260468617.issue36651@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


----------
versions: +Python 3.7

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

From report at bugs.python.org  Thu Apr 18 08:49:28 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 18 Apr 2019 12:49:28 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555591768.23.0.637233320563.issue36651@roundup.psfhosted.org>


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


New changeset d29b3dd9227cfc4a23f77e99d62e20e063272de1 by Miss Islington (bot) in branch '3.7':
bpo-36651: Fixed Asyncio Event Loop documentation inconsistency (GH-12866)
https://github.com/python/cpython/commit/d29b3dd9227cfc4a23f77e99d62e20e063272de1


----------

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

From report at bugs.python.org  Thu Apr 18 09:28:53 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Thu, 18 Apr 2019 13:28:53 +0000
Subject: [docs] [issue36651] Asyncio Event Loop documentation inconsistency
 (call_later and call_at methods)
In-Reply-To: <1555527182.24.0.96593759188.issue36651@roundup.psfhosted.org>
Message-ID: <1555594133.89.0.937798536248.issue36651@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


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

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

From report at bugs.python.org  Thu Apr 18 10:42:24 2019
From: report at bugs.python.org (maak)
Date: Thu, 18 Apr 2019 14:42:24 +0000
Subject: [docs] [issue36657] AttributeError
Message-ID: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>


New submission from maak <sanaraba at gmail.com>:

elif path == '' or path.endswith('/'):
AttributeError: 'bool' object has no attribute 'endswith'

----------
assignee: docs at python
components: Documentation
messages: 340490
nosy: docs at python, maakvol
priority: normal
severity: normal
status: open
title: AttributeError
type: compile error
versions: Python 2.7

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

From report at bugs.python.org  Thu Apr 18 10:46:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 18 Apr 2019 14:46:00 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555598760.63.0.497675647831.issue36657@roundup.psfhosted.org>


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

Please add a short script and explain the problem over why it's a bug in CPython and not a problem with the program. The error says path has a boolean value and doesn't have endswith which is a method on string object.

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

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

From report at bugs.python.org  Thu Apr 18 10:50:15 2019
From: report at bugs.python.org (maak)
Date: Thu, 18 Apr 2019 14:50:15 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555599015.06.0.254107685866.issue36657@roundup.psfhosted.org>


maak <sanaraba at gmail.com> added the comment:

File "/home/maak/PycharmProjects/Fyp/venv/local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 48, in run
    _sys.exit(main(_sys.argv[:1] + flags_passthrough))
  File "main.py", line 132, in main
    bestmodel_dir = os.path.join(FLAGS.train_dir, "best_checkpoint")
  File "/home/maak/PycharmProjects/Fyp/venv/lib/python2.7/posixpath.py", line 70, in join
    elif path == '' or path.endswith('/'):
AttributeError: 'bool' object has no attribute 'endswith'

----------

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

From report at bugs.python.org  Thu Apr 18 10:59:22 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 18 Apr 2019 14:59:22 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555599562.36.0.398222757912.issue36657@roundup.psfhosted.org>


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

Please check the value of FLAGS.train_dir which I guess has a boolean value. This is not a bug with CPython.

$ python2
Python 2.7.14 (default, Mar 12 2018, 13:54:56)
[GCC 4.2.1 Compatible Apple LLVM 7.0.2 (clang-700.1.81)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.path.join(True, 'best_checkpoint')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/Cellar/python at 2/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/posixpath.py", line 70, in join
    elif path == '' or path.endswith('/'):
AttributeError: 'bool' object has no attribute 'endswith'

----------

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

From report at bugs.python.org  Thu Apr 18 11:12:43 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Thu, 18 Apr 2019 15:12:43 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555599562.36.0.398222757912.issue36657@roundup.psfhosted.org>
Message-ID: <20190418151239.wpahm4flhw44zeao@xps>


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

Hi Karthikeyan,

I think we could close this issue, it's not related to CPython itself.

What do you think?

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

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

From report at bugs.python.org  Thu Apr 18 11:14:52 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 18 Apr 2019 15:14:52 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555600492.86.0.509435785489.issue36657@roundup.psfhosted.org>


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

> I think we could close this issue, it's not related to CPython itself.

Closing it. OP can reopen if needed. Thanks.

----------
assignee: docs at python -> 
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
type: compile error -> behavior

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

From report at bugs.python.org  Thu Apr 18 11:39:00 2019
From: report at bugs.python.org (maak)
Date: Thu, 18 Apr 2019 15:39:00 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555601940.43.0.26679751316.issue36657@roundup.psfhosted.org>


maak <sanaraba at gmail.com> added the comment:

FLAGS.train_dir has a boolean value which is checking true or false  
and i also have same issue import os
>>> os.path.join(True, 'best_checkpoint')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/Cellar/python at 2/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/posixpath.py", line 70, in join
    elif path == '' or path.endswith('/'):
AttributeError: 'bool' object has no attribute 'endswith'

can you give me a solution or idea how to solve issue

----------

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

From report at bugs.python.org  Thu Apr 18 11:50:26 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 18 Apr 2019 15:50:26 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555602626.14.0.0761051096761.issue36657@roundup.psfhosted.org>


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

Hi Maakvol,

Please remember that this is a bug tracker for bugs in the Python language and standard library, not a help desk.

As a beginner, 99.9% of the times you think that you have found a bug in Python, you haven't, it will be a bug in your own code. There are many forums where you can ask for help with your code, such as the tutor mailing list 

https://mail.python.org/mailman/listinfo/tutor

Stackoverflow, Reddit's /r/learnpython, and more. You should check with other, more experienced programmers before reporting things as bugs.

Thank you.

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

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

From report at bugs.python.org  Thu Apr 18 12:00:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 18 Apr 2019 16:00:50 +0000
Subject: [docs] [issue36657] AttributeError
In-Reply-To: <1555598544.39.0.0302839002466.issue36657@roundup.psfhosted.org>
Message-ID: <1555603250.34.0.0243508171832.issue36657@roundup.psfhosted.org>


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

... maak opened a second issue... bpo-36660.

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

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

From report at bugs.python.org  Thu Apr 18 13:25:26 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 18 Apr 2019 17:25:26 +0000
Subject: [docs] [issue32913] Improve regular expression HOWTO
In-Reply-To: <1519330200.78.0.467229070634.issue32913@psf.upfronthosting.co.za>
Message-ID: <1555608326.66.0.509436331625.issue32913@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr 18 15:36:48 2019
From: report at bugs.python.org (Merlin Fisher-Levine)
Date: Thu, 18 Apr 2019 19:36:48 +0000
Subject: [docs] [issue36661] Missing import in docs
Message-ID: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>


New submission from Merlin Fisher-Levine <merlin.fisherlevine at gmail.com>:

Dataclasses docs don't mention needing import for @dataclass decorator

https://docs.python.org/3/library/dataclasses.html

----------
assignee: docs at python
components: Documentation
messages: 340510
nosy: docs at python, mfisherlevine
priority: normal
severity: normal
status: open
title: Missing import in docs
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Thu Apr 18 21:22:08 2019
From: report at bugs.python.org (mollison)
Date: Fri, 19 Apr 2019 01:22:08 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555636928.57.0.24411764299.issue36645@roundup.psfhosted.org>


Change by mollison <mollison at cs.unc.edu>:


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

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

From report at bugs.python.org  Thu Apr 18 21:33:26 2019
From: report at bugs.python.org (mollison)
Date: Fri, 19 Apr 2019 01:33:26 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555637606.19.0.321256831963.issue36645@roundup.psfhosted.org>


mollison <mollison at cs.unc.edu> added the comment:

@brett.cannon: PR is at https://github.com/python/cpython/pull/12879

----------

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

From report at bugs.python.org  Fri Apr 19 01:26:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 19 Apr 2019 05:26:25 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555651585.97.0.635825435487.issue36661@roundup.psfhosted.org>


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

I think the import is implied in the example since the docs page is for dataclasses module but adding an explicit import to InventoryItem at the top won't hurt too.

----------
nosy: +eric.smith, xtreak
title: Missing import in docs -> Missing dataclass decorator import in dataclasses module docs
versions: +Python 3.8

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

From report at bugs.python.org  Fri Apr 19 04:34:54 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 19 Apr 2019 08:34:54 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555651585.97.0.635825435487.issue36661@roundup.psfhosted.org>
Message-ID: <20190419083450.mozqaiwn4qhk6rxb@xps>


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

We could change the example with 

```
from dataclasses import dataclass

@dataclass
class InventoryItem:
    ...
```

Because it's not specified in the documentation (header, that we need to
import dataclass from dataclasses).

+1 for a small update.

You are free to propose a PR.

Have a nice day,

>I think the import is implied in the example since the docs page is for
>dataclasses module but adding an explicit import to InventoryItem at
>the top won't hurt too.
Yep, but explicit is better than implicit.

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

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

From report at bugs.python.org  Fri Apr 19 04:39:32 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 19 Apr 2019 08:39:32 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555663172.06.0.0965878451432.issue36661@roundup.psfhosted.org>


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

I think adding "from dataclasses import dataclass" in the first example is fine.

There's a similar import in the sqlite3 documentation, just to pick one at random.

----------

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

From report at bugs.python.org  Fri Apr 19 04:44:14 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 19 Apr 2019 08:44:14 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555663172.06.0.0965878451432.issue36661@roundup.psfhosted.org>
Message-ID: <20190419084410.wg5twjhhjzsm6vn5@xps>


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

Ok, I suggest to add a "first issue" for the sprint days at PyCon US.

----------

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

From report at bugs.python.org  Fri Apr 19 04:45:35 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 19 Apr 2019 08:45:35 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555663535.71.0.0887616004401.issue36661@roundup.psfhosted.org>


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


----------
keywords: +easy

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

From report at bugs.python.org  Fri Apr 19 05:16:23 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 19 Apr 2019 09:16:23 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1555665383.5.0.61304672492.issue36345@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 19 05:16:47 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 19 Apr 2019 09:16:47 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1555665407.46.0.27141296934.issue36345@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 19 20:37:23 2019
From: report at bugs.python.org (Windson Yang)
Date: Sat, 20 Apr 2019 00:37:23 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555720643.51.0.695993057205.issue36661@roundup.psfhosted.org>


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

I can find some example in the docs that didn't `import the correct module` even in the first example. Should we add the `import` statement for all of them?

----------
nosy: +Windson Yang

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

From report at bugs.python.org  Sat Apr 20 05:18:43 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 20 Apr 2019 09:18:43 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555751923.13.0.492597581085.issue36661@roundup.psfhosted.org>


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

I won't discourage anyone from making such changes, but I don't think it's a real problem. I haven't seen that people are confused about needing to import the module being discussed in the documentation. I don't think there's any expectation that the code in the documentation is actually executable as-is. They're not doctests, after all.

----------

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

From report at bugs.python.org  Sat Apr 20 06:43:50 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 20 Apr 2019 10:43:50 +0000
Subject: [docs] [issue36675] Doctest directives and comments not visible or
 missing from code samples
Message-ID: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>


New submission from Steven D'Aprano <steve+python at pearwood.info>:

(Apologies if this is the wrong place for reporting website bugs.)

The website is not rendering doctest directives or comments, either that or the comments have been stripped from the examples.

On the doctest page itself, all the comments are missing:

https://docs.python.org/3/library/doctest.html#directives

The first example says:

    >>> print(list(range(20))) 
    [0,   1,  2,  3,  4,  5,  6,  7,  8,  9,
    10,  11, 12, 13, 14, 15, 16, 17, 18, 19]

but without the directive, the test would fail. Screen shot attached.

Doctest directives are also missing from here:

https://docs.python.org/3/library/ctypes.html



My browser: Firefox 45.1.1

Also checked with text browser "lynx".

----------
assignee: docs at python
components: Documentation
files: missing_directives.png
messages: 340570
nosy: docs at python, steven.daprano
priority: normal
severity: normal
status: open
title: Doctest directives and comments not visible or missing from code samples
type: behavior
Added file: https://bugs.python.org/file48277/missing_directives.png

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

From report at bugs.python.org  Sat Apr 20 06:58:36 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 20 Apr 2019 10:58:36 +0000
Subject: [docs] [issue36675] Doctest directives and comments not visible or
 missing from code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1555757916.63.0.806444980572.issue36675@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Apr 20 09:00:36 2019
From: report at bugs.python.org (Windson Yang)
Date: Sat, 20 Apr 2019 13:00:36 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555765236.26.0.617442480624.issue36661@roundup.psfhosted.org>


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

I agreed most of the documents won't need the change, but some documents like https://docs.python.org/3/library/dataclasses.html#dataclasses.field didn't mention we have to run `from typing import List` and I guess most developers not familiar with this package. I suggest we should add the import statement for the uncommon package.

----------

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

From report at bugs.python.org  Sat Apr 20 11:32:40 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 20 Apr 2019 15:32:40 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555774360.9.0.194438054834.issue36661@roundup.psfhosted.org>


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

I definitely think any missing import from typing should be added.

----------

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

From report at bugs.python.org  Sat Apr 20 12:51:48 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Sat, 20 Apr 2019 16:51:48 +0000
Subject: [docs] [issue36008] [good first issue] Update documentation for 3.8
In-Reply-To: <1550278435.56.0.94881175235.issue36008@roundup.psfhosted.org>
Message-ID: <1555779108.15.0.0166321707662.issue36008@roundup.psfhosted.org>


Change by Utkarsh Gupta <guptautkarsh2102 at gmail.com>:


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

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

From report at bugs.python.org  Sun Apr 21 05:09:18 2019
From: report at bugs.python.org (Christoph Reiter)
Date: Sun, 21 Apr 2019 09:09:18 +0000
Subject: [docs] [issue36689] docs: os.path.commonpath raises ValueError for
 different drives
Message-ID: <1555837758.83.0.507858438764.issue36689@roundup.psfhosted.org>


New submission from Christoph Reiter <reiter.christoph at gmail.com>:

Since I just got bit by this despite reading the docs:

https://docs.python.org/3.8/library/os.path.html#os.path.commonpath

It lists various error cases where ValueError is raised but is missing the case where absolute paths on Windows are on different drives and I forgot to handle that:

  File "C:/building/msys64/mingw64/lib/python3.7\ntpath.py", line 631, in commonpath
    raise ValueError("Paths don't have the same drive")
ValueError: Paths don't have the same drive

----------
assignee: docs at python
components: Documentation
messages: 340604
nosy: docs at python, lazka
priority: normal
severity: normal
status: open
title: docs: os.path.commonpath raises ValueError for different drives
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Sun Apr 21 06:16:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 21 Apr 2019 10:16:07 +0000
Subject: [docs] [issue36689] docs: os.path.commonpath raises ValueError for
 different drives
In-Reply-To: <1555837758.83.0.507858438764.issue36689@roundup.psfhosted.org>
Message-ID: <1555841767.04.0.682723407576.issue36689@roundup.psfhosted.org>


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


----------
keywords: +easy
stage:  -> needs patch
versions: +Python 3.7

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

From report at bugs.python.org  Sun Apr 21 18:14:50 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 21 Apr 2019 22:14:50 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555884890.52.0.213672554411.issue36645@roundup.psfhosted.org>


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


New changeset 5ebfa840a1c9967da299356733da41b532688988 by Berker Peksag (mollison) in branch 'master':
bpo-36645: Fix ambiguous formatting in re.sub() documentation (GH-12879)
https://github.com/python/cpython/commit/5ebfa840a1c9967da299356733da41b532688988


----------
nosy: +berker.peksag

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

From report at bugs.python.org  Sun Apr 21 18:15:10 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 21 Apr 2019 22:15:10 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555884910.1.0.734566964682.issue36645@roundup.psfhosted.org>


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


----------
pull_requests: +12824

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

From report at bugs.python.org  Sun Apr 21 18:20:47 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 21 Apr 2019 22:20:47 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555885247.81.0.371463811537.issue36645@roundup.psfhosted.org>


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


New changeset 71b88827f6ad368eafa17983bd979175d24da888 by Miss Islington (bot) in branch '3.7':
bpo-36645: Fix ambiguous formatting in re.sub() documentation (GH-12879)
https://github.com/python/cpython/commit/71b88827f6ad368eafa17983bd979175d24da888


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

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

From report at bugs.python.org  Sun Apr 21 18:57:32 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 21 Apr 2019 22:57:32 +0000
Subject: [docs] [issue36645] re.sub() library entry does not adequately
 document surprising change in behavior between versions
In-Reply-To: <1555454579.44.0.38794635257.issue36645@roundup.psfhosted.org>
Message-ID: <1555887452.69.0.123137094443.issue36645@roundup.psfhosted.org>


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

Thank you!

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

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

From report at bugs.python.org  Sun Apr 21 21:10:54 2019
From: report at bugs.python.org (Marcin Niemira)
Date: Mon, 22 Apr 2019 01:10:54 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1555895454.1.0.991287949041.issue36523@roundup.psfhosted.org>


Marcin Niemira <marcin.niemira at gmail.com> added the comment:

Hey,
Is there something I can improve in this PR?

----------

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

From report at bugs.python.org  Mon Apr 22 07:14:01 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 22 Apr 2019 11:14:01 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1555931641.4.0.879344031899.issue36523@roundup.psfhosted.org>


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


New changeset ab86521a9d9999731e39bd9056420bb7774fd144 by Inada Naoki (Marcin Niemira) in branch 'master':
bpo-36523: Add docstring to io.IOBase.writelines (GH-12683)
https://github.com/python/cpython/commit/ab86521a9d9999731e39bd9056420bb7774fd144


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

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

From report at bugs.python.org  Mon Apr 22 07:27:12 2019
From: report at bugs.python.org (Marcin Niemira)
Date: Mon, 22 Apr 2019 11:27:12 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1555932432.16.0.121092099299.issue36523@roundup.psfhosted.org>


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


----------
pull_requests: +12832

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

From report at bugs.python.org  Mon Apr 22 08:08:32 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 22 Apr 2019 12:08:32 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1555934912.02.0.937368696505.issue36523@roundup.psfhosted.org>


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


New changeset 1100ae8f3fb1d5a8f6f5638919196bd8fab66de9 by Inada Naoki (Marcin Niemira) in branch '3.7':
bpo-36523: Add docstring to io.IOBase.writelines (GH-12683)
https://github.com/python/cpython/commit/1100ae8f3fb1d5a8f6f5638919196bd8fab66de9


----------

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

From report at bugs.python.org  Mon Apr 22 08:09:08 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 22 Apr 2019 12:09:08 +0000
Subject: [docs] [issue36523] Add docstring to io.IOBase.writelines
In-Reply-To: <1554365037.57.0.454839708261.issue36523@roundup.psfhosted.org>
Message-ID: <1555934948.16.0.567164827388.issue36523@roundup.psfhosted.org>


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

From report at bugs.python.org  Mon Apr 22 14:33:12 2019
From: report at bugs.python.org (Paul Hoffman)
Date: Mon, 22 Apr 2019 18:33:12 +0000
Subject: [docs] [issue36700] base64 has old references that should be updated
Message-ID: <1555957992.77.0.818777064587.issue36700@roundup.psfhosted.org>


New submission from Paul Hoffman <phoffman at proper.com>:

The documentation for base64 library has an RFC that is obsolete.

----------
assignee: docs at python
components: Documentation
messages: 340668
nosy: docs at python, paulehoffman
priority: normal
pull_requests: 12839
severity: normal
status: open
title: base64 has old references that should be updated

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

From report at bugs.python.org  Mon Apr 22 15:13:57 2019
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 22 Apr 2019 19:13:57 +0000
Subject: [docs] [issue36661] Missing dataclass decorator import in
 dataclasses module docs
In-Reply-To: <1555616208.44.0.536731608649.issue36661@roundup.psfhosted.org>
Message-ID: <1555960437.18.0.811659624658.issue36661@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

I also don't think it's critical to make examples within a module's docs work like a doctest. Plus I discourage importing objects directly off of modules anyway and this would actually promote that.

----------
nosy: +brett.cannon

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

From report at bugs.python.org  Tue Apr 23 14:25:23 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 23 Apr 2019 18:25:23 +0000
Subject: [docs] [issue36700] base64 has old references that should be updated
In-Reply-To: <1555957992.77.0.818777064587.issue36700@roundup.psfhosted.org>
Message-ID: <1556043922.99.0.58094619179.issue36700@roundup.psfhosted.org>


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

base64 supports RFC 3548, but not RFC 4648.

=====================================================================
13.  Changes Since RFC 3548

   Added the "base32 extended hex alphabet", needed to preserve sort
   order of encoded data.

   Referenced IMAP for the special Base64 encoding used there.

   Fixed the example copied from RFC 2440.

   Added security consideration about providing a signature for
   cryptoanalysis.

   Added test vectors.

   Fixed typos.
=====================================================================

To support RFC 4648 we need to add support for base 32 encoding with extended hex alphabet (see 16995). Check also that RFC 4648 test vectors are used in the module tests.

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

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

From report at bugs.python.org  Tue Apr 23 14:25:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 23 Apr 2019 18:25:43 +0000
Subject: [docs] [issue36700] base64 has old references that should be updated
In-Reply-To: <1555957992.77.0.818777064587.issue36700@roundup.psfhosted.org>
Message-ID: <1556043943.96.0.102352078683.issue36700@roundup.psfhosted.org>


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

See issue16995.

----------

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

From report at bugs.python.org  Tue Apr 23 15:16:32 2019
From: report at bugs.python.org (Paul Hoffman)
Date: Tue, 23 Apr 2019 19:16:32 +0000
Subject: [docs] [issue36700] base64 has old references that should be updated
In-Reply-To: <1555957992.77.0.818777064587.issue36700@roundup.psfhosted.org>
Message-ID: <1556046992.93.0.470968797178.issue36700@roundup.psfhosted.org>


Paul Hoffman <phoffman at proper.com> added the comment:

We can update the references without supporting every mode given in the new document. It is common for people to support RFC X without supporting every possible option of RFC X.

Having said that, I think adding extended hex makes good sense, if possible.

----------

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

From report at bugs.python.org  Tue Apr 23 22:54:29 2019
From: report at bugs.python.org (Patrick Artman)
Date: Wed, 24 Apr 2019 02:54:29 +0000
Subject: [docs] [issue36689] docs: os.path.commonpath raises ValueError for
 different drives
In-Reply-To: <1555837758.83.0.507858438764.issue36689@roundup.psfhosted.org>
Message-ID: <1556074469.18.0.389746469118.issue36689@roundup.psfhosted.org>


Patrick Artman <pattyshack at protonmail.com> added the comment:

If this isn't taken I'd be happy to give it a go as my first contribution

----------
nosy: +pjartman

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

From report at bugs.python.org  Wed Apr 24 05:01:58 2019
From: report at bugs.python.org (sakamotoaya)
Date: Wed, 24 Apr 2019 09:01:58 +0000
Subject: [docs] [issue36708] can not execute the python + version,
 to launch python under windows.
In-Reply-To: <1556092235.7.0.350859031075.issue36708@roundup.psfhosted.org>
Message-ID: <1556096518.25.0.264930394494.issue36708@roundup.psfhosted.org>


Change by sakamotoaya <aya.sakamoto at outlook.com>:


----------
nosy: +CuriousLearner, docs at python, ncoghlan, ronaldoussoren, serhiy.storchaka, xtreak

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

From report at bugs.python.org  Wed Apr 24 05:16:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 24 Apr 2019 09:16:07 +0000
Subject: [docs] [issue36708] can not execute the python + version,
 to launch python under windows.
In-Reply-To: <1556092235.7.0.350859031075.issue36708@roundup.psfhosted.org>
Message-ID: <1556097367.07.0.45213020006.issue36708@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed Apr 24 11:14:46 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 24 Apr 2019 15:14:46 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1556118886.88.0.304365422226.issue30840@roundup.psfhosted.org>


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


New changeset 70bf713617e15fad390ed953e48b3c65d9bc90ec by Nick Coghlan (Joannah Nanjekye) in branch 'master':
bpo-30840: Document relative imports (#12831)
https://github.com/python/cpython/commit/70bf713617e15fad390ed953e48b3c65d9bc90ec


----------

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

From report at bugs.python.org  Wed Apr 24 11:14:57 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 24 Apr 2019 15:14:57 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1556118897.73.0.819497534459.issue30840@roundup.psfhosted.org>


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


----------
pull_requests: +12862

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

From report at bugs.python.org  Wed Apr 24 11:45:18 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 24 Apr 2019 15:45:18 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1556120718.24.0.774294845707.issue30840@roundup.psfhosted.org>


Change by Nick Coghlan <ncoghlan at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type: behavior -> enhancement
versions: +Python 3.8 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Wed Apr 24 11:44:23 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 24 Apr 2019 15:44:23 +0000
Subject: [docs] [issue30840] Contrary to documentation,
 relative imports cannot pass through the top level
In-Reply-To: <1499109292.04.0.970471813466.issue30840@psf.upfronthosting.co.za>
Message-ID: <1556120663.11.0.824050850582.issue30840@roundup.psfhosted.org>


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


New changeset 4d0233ec656bc7e7814e5f6f484e79a50a0daf91 by Nick Coghlan (Miss Islington (bot)) in branch '3.7':
bpo-30840: Document relative imports (GH-12831) (GH-12938)
https://github.com/python/cpython/commit/4d0233ec656bc7e7814e5f6f484e79a50a0daf91


----------

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

From report at bugs.python.org  Wed Apr 24 13:16:09 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 24 Apr 2019 17:16:09 +0000
Subject: [docs] [issue36708] can not execute the python + version,
 to launch python under windows.
In-Reply-To: <1556092235.7.0.350859031075.issue36708@roundup.psfhosted.org>
Message-ID: <1556126169.24.0.459158580397.issue36708@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

This is by design in the Windows installer. You can check a box to put python3.6 on PATH if you want.

If you want the Python Launcher on UNIX, see https://crates.io/crates/python-launcher.

----------
nosy: +brett.cannon
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed Apr 24 14:22:34 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 24 Apr 2019 18:22:34 +0000
Subject: [docs] [issue36708] can not execute the python + version,
 to launch python under windows.
In-Reply-To: <1556092235.7.0.350859031075.issue36708@roundup.psfhosted.org>
Message-ID: <1556130154.89.0.911176358919.issue36708@roundup.psfhosted.org>


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

More precisely, the default Python install for Windows does not include versioned executables.

If you install Python 3.7 from the Microsoft Store then you will get them, though it's not identical to the full development kit you'll get from python.org.

There may be other distributions that include versioned executables as well. Ours will only put "python.exe" on PATH

----------

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

From report at bugs.python.org  Wed Apr 24 14:16:19 2019
From: report at bugs.python.org (Lisa Roach)
Date: Wed, 24 Apr 2019 18:16:19 +0000
Subject: [docs] [issue36654] Add example to tokenize.tokenize
In-Reply-To: <1555559036.7.0.0522143852215.issue36654@roundup.psfhosted.org>
Message-ID: <1556129779.89.0.615826108394.issue36654@roundup.psfhosted.org>


Lisa Roach <lisaroach14 at gmail.com> added the comment:

This could be added to the examples section of the tokenize doc, would you want to make the PR Windson?

----------
nosy: +lisroach

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

From report at bugs.python.org  Wed Apr 24 16:13:34 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 24 Apr 2019 20:13:34 +0000
Subject: [docs] [issue36715] Dictionary initialization
In-Reply-To: <1556135397.5.0.612221590326.issue36715@roundup.psfhosted.org>
Message-ID: <1556136814.37.0.335903300218.issue36715@roundup.psfhosted.org>


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

This is the same basic problem seen with sequence multiplication, mutable default arguments to a function, etc. It's not going to change though; the documentation says it "Create a new dictionary with keys from iterable and values set to value." "set to value" doesn't allow for implicit copy operations (shallow or deep), and trying to support it would slow fromkeys and violate the normal expectations for functions that reuse an input argument. Essentially, the problem you have is one of expectations; the behavior is correct, but perhaps the documentation could be clearer.

In any event, the general solution to your problem is a dict comprehension (or for dict subclasses, passing a generator expression to the subclass constructor), replacing the incorrect:

    dict.fromkeys(iterable, [])

with the similarly concise/straightforward:

    {k: [] for k in iterable}

or (for general use, where dict can be changed to a dict subclass):

    dict((k, []) for k in iterable)

I've marked this as a documentation bug if someone wants to take a stab at making the behavior more clear.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, josh.r

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

From report at bugs.python.org  Wed Apr 24 21:10:33 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 25 Apr 2019 01:10:33 +0000
Subject: [docs] [issue36715] Dictionary initialization
In-Reply-To: <1556135397.5.0.612221590326.issue36715@roundup.psfhosted.org>
Message-ID: <1556154633.71.0.398645920254.issue36715@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed Apr 24 21:47:38 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 25 Apr 2019 01:47:38 +0000
Subject: [docs] [issue36715] Dictionary initialization
In-Reply-To: <1556135397.5.0.612221590326.issue36715@roundup.psfhosted.org>
Message-ID: <1556156858.57.0.421048785349.issue36715@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Apr 25 00:21:30 2019
From: report at bugs.python.org (Windson Yang)
Date: Thu, 25 Apr 2019 04:21:30 +0000
Subject: [docs] [issue36654] Add example to tokenize.tokenize
In-Reply-To: <1555559036.7.0.0522143852215.issue36654@roundup.psfhosted.org>
Message-ID: <1556166090.76.0.0140118837277.issue36654@roundup.psfhosted.org>


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

Yes, I can make a PR for it.

----------

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

From vadmium+py at gmail.com  Thu Apr 25 00:19:33 2019
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Thu, 25 Apr 2019 04:19:33 -0000
Subject: [docs] Various obvious errors in cookies documentation (issue 11001)
Message-ID: <20190425041933.15842.26062@bugs.ams1.psf.io>


http://bugs.python.org/review/11001/diff/1905/Doc/library/http.cookies.rst
File Doc/library/http.cookies.rst (right):

http://bugs.python.org/review/11001/diff/1905/Doc/library/http.cookies.rst#newcode45
Doc/library/http.cookies.rst:45: and :meth:`value_encode` to use
encoding appropriate for values outside
Suggest clarify what you mean by ?appropriate?. The encoding is not
appropriate if you want to satisfy the Netscape or RFC 6265
specifications for cookies. See <https://bugs.python.org/issue19670>.

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

From report at bugs.python.org  Thu Apr 25 01:20:07 2019
From: report at bugs.python.org (Windson Yang)
Date: Thu, 25 Apr 2019 05:20:07 +0000
Subject: [docs] [issue36654] Add example to tokenize.tokenize
In-Reply-To: <1555559036.7.0.0522143852215.issue36654@roundup.psfhosted.org>
Message-ID: <1556169607.17.0.711883930894.issue36654@roundup.psfhosted.org>


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


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

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

From vadmium+py at gmail.com  Thu Apr 25 03:43:00 2019
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Thu, 25 Apr 2019 07:43:00 -0000
Subject: [docs] Various obvious errors in cookies documentation (issue
 11001)
Message-ID: <20190425074300.15842.18027@bugs.ams1.psf.io>


http://bugs.python.org/review/11001/diff/1905/Doc/library/http.cookies.rst
File Doc/library/http.cookies.rst (right):

http://bugs.python.org/review/11001/diff/1905/Doc/library/http.cookies.rst#newcode45
Doc/library/http.cookies.rst:45: and :meth:`value_encode` to use
encoding appropriate for values outside
On 2019/04/25 06:19:33, Martin Panter wrote:

> Suggest clarify what you mean by ?appropriate?. The encoding is not
appropriate
> if you want to satisfy the Netscape or RFC 6265 specifications for
cookies. See
> <https://bugs.python.org/issue19670>.

[Pasting a reply from Luke, who had trouble posting it]

Given the comments in that ticket, it could read:

  This class derives from :class:`BaseCookie` and overrides
:meth:`value_decode`
  and :meth:`value_encode` to use RFC 2109 quoted-string escaping for
values
  outside the alphanumeric set.

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

From report at bugs.python.org  Thu Apr 25 10:52:18 2019
From: report at bugs.python.org (Michal Kononenko)
Date: Thu, 25 Apr 2019 14:52:18 +0000
Subject: [docs] [issue36720] Correct Should to Must in Definition of
 object.__len__
Message-ID: <1556203938.29.0.467406560077.issue36720@roundup.psfhosted.org>


New submission from Michal Kononenko <michalkononenko at gmail.com>:

The link below defines __len__

https://docs.python.org/3/reference/datamodel.html?highlight=__len__#object.__len__

However, I was reading in the StackOverflow thread below that CPython does some validation to check that the return value of __len__ should be >= 0. Does this mean that len must return a value >= 0, in the RFC 2119 sense of the word?

https://stackoverflow.com/questions/42521449/how-does-python-ensure-the-return-value-of-len-is-an-integer-when-len-is-cal

----------
assignee: docs at python
components: Documentation
messages: 340844
nosy: Michal Kononenko, docs at python
priority: normal
severity: normal
status: open
title: Correct Should to Must in Definition of object.__len__
type: behavior
versions: Python 3.7

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

From report at bugs.python.org  Thu Apr 25 13:53:14 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 25 Apr 2019 17:53:14 +0000
Subject: [docs] [issue36720] Correct Should to Must in Definition of
 object.__len__
In-Reply-To: <1556203938.29.0.467406560077.issue36720@roundup.psfhosted.org>
Message-ID: <1556214794.29.0.248846716456.issue36720@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

There is probably validation code in len(), but the method itself can do whatever it wants if you call it directly. So the documentation is accurate in saying the method _should_ return >= 0 but that there's nothing strictly enforcing that in Python for that specific method when defined and called directly.

----------
nosy: +brett.cannon
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Apr 25 18:47:08 2019
From: report at bugs.python.org (Oliver Too, Eh?)
Date: Thu, 25 Apr 2019 22:47:08 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
Message-ID: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>


New submission from Oliver Too, Eh? <olivertooeh at gmail.com>:

Documentation contents are ordered, and readers familiar with the section numbers/ordering from the Python 2 or Python 3.5 documentation will have an easier time transitioning to Python 3.6 or later if the sections remain numbered.

----------
assignee: docs at python
components: Documentation
messages: 340866
nosy: Oliver Too, Eh?, docs at python
priority: normal
severity: normal
status: open
title: python 3.6+ docs use ul tags instead of ol tags
versions: Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Thu Apr 25 21:11:32 2019
From: report at bugs.python.org (Sebastian Bassi)
Date: Fri, 26 Apr 2019 01:11:32 +0000
Subject: [docs] [issue36730] Change outdated references to macOS
Message-ID: <1556241092.16.0.423050564241.issue36730@roundup.psfhosted.org>


New submission from Sebastian Bassi <sbassi at gmail.com>:

There are multiple occurences in the web page of "Mac OS X", like "Download the latest version for Mac OS X". This OS is called macOS since some years. It may be confusing for a new user.

----------
assignee: docs at python
components: Documentation
messages: 340875
nosy: Sebastian Bassi, docs at python
priority: normal
severity: normal
status: open
title: Change outdated references to macOS
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu Apr 25 22:52:28 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 26 Apr 2019 02:52:28 +0000
Subject: [docs] [issue7951] Should str.format allow negative indexes when
 used for __getitem__ access?
In-Reply-To: <1266450859.13.0.906832569526.issue7951@psf.upfronthosting.co.za>
Message-ID: <1556247148.09.0.402153449733.issue7951@roundup.psfhosted.org>


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

A side question: where is it defined that in `{thing[0]}`, 0 will be parsed as an integer?

The PEP shows `{thing[name]}` and mentions that this is not Python but a smaller mini-language, with `name` always a string, no quotes needed or permitted.

----------

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

From report at bugs.python.org  Thu Apr 25 23:01:37 2019
From: report at bugs.python.org (Windson Yang)
Date: Fri, 26 Apr 2019 03:01:37 +0000
Subject: [docs] [issue36731] Add example to priority queue
Message-ID: <1556247697.17.0.567840188783.issue36731@roundup.psfhosted.org>


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

We don't have the base example for priority queue in https://docs.python.org/3.8/library/heapq.html#priority-queue-implementation-notes, We can add something like:

> q = Q.PriorityQueue()
> q.put(10)
> q.put(1)
> q.put(5)
> while not q.empty():
    print q.get()

We may also need to add Notes about the PriorityQueue will block when we use max size 

> q = Q.PriorityQueue(1)
> q.put(10)
> q.put(1) # will block until the Queue is available again.

----------
assignee: docs at python
components: Documentation
messages: 340878
nosy: Windson Yang, docs at python
priority: normal
severity: normal
status: open
title: Add example to priority queue
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Fri Apr 26 02:23:38 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 26 Apr 2019 06:23:38 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
In-Reply-To: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>
Message-ID: <CAAjsFLT-C4nDuJV0aUNYTxrOBCQi-jp-YEKW2z2-YoQZGFx9dg@mail.gmail.com>


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

issue34717 seems to be related where numbering was turned off. The issue
has a note on reopening it for discussion if numbering is needed at
https://bugs.python.org/issue34717#msg325589 . Would propose closing this.

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

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

From report at bugs.python.org  Fri Apr 26 02:56:04 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 26 Apr 2019 06:56:04 +0000
Subject: [docs] [issue7951] Should str.format allow negative indexes when
 used for __getitem__ access?
In-Reply-To: <1266450859.13.0.906832569526.issue7951@psf.upfronthosting.co.za>
Message-ID: <1556261763.98.0.992167652143.issue7951@roundup.psfhosted.org>


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

I'm not sure where (or if) it's defined in the Python docs, but in PEP 3101 it's in https://www.python.org/dev/peps/pep-3101/#simple-and-compound-field-names: "It should be noted that the use of 'getitem' within a format string is much more limited than its conventional usage. In the above example, the string 'name' really is the literal string 'name', not a variable named 'name'. The rules for parsing an item key are very simple. If it starts with a digit, then it is treated as a number, otherwise it is used as a string.".

----------

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

From report at bugs.python.org  Fri Apr 26 03:43:22 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 26 Apr 2019 07:43:22 +0000
Subject: [docs] [issue36731] Add example to priority queue
In-Reply-To: <1556247697.17.0.567840188783.issue36731@roundup.psfhosted.org>
Message-ID: <1556264602.54.0.143686271458.issue36731@roundup.psfhosted.org>


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

This doesn't make any sense.  None of those operations are defined for the heapq module, nor is there a maxsize.  The heapq usage notes are about the general concept of ways to implement priority queues.  I suspect your suggestion is conflated with queue.PriorityQueue() which does have put(), get(), and maxsize.

As for the queue docs, I don't think more examples are needed. IMO it would just clutter that part of the docs.

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

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

From report at bugs.python.org  Fri Apr 26 07:00:45 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 26 Apr 2019 11:00:45 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
In-Reply-To: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>
Message-ID: <1556276445.79.0.2232522475.issue36727@roundup.psfhosted.org>


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

I notified "Oliver Too, Eh?" by email directly about being dropped from this issue due to the comma in the username. 

xtreak: you seemed to be able to add a message while keeping "Oliver Too, Eh?" on the nosy list: any hints?

----------

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

From report at bugs.python.org  Fri Apr 26 06:49:06 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 26 Apr 2019 10:49:06 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
In-Reply-To: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>
Message-ID: <1556275746.88.0.301574513382.issue36727@roundup.psfhosted.org>


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

Agreed on closing this and discussing it at issue 34717.

(I can't get bpo to accept this because of the comma in "Oliver Too, Eh?", so I'm removing them temporarily. Will try to add back, but might fail.)

----------
nosy: +eric.smith -Oliver Too, Eh?
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Apr 26 07:06:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 26 Apr 2019 11:06:49 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
In-Reply-To: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>
Message-ID: <1556276809.12.0.295416284351.issue36727@roundup.psfhosted.org>


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

> xtreak: you seemed to be able to add a message while keeping "Oliver Too, Eh?" on the nosy list: any hints?

I was also not able to add a comment through bpo so I replied by email which seemed to work. I guess registration should have validated the username to not allow it.

----------
superseder:  -> docs: disable numbered sections for stdlib in html

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

From report at bugs.python.org  Fri Apr 26 07:16:47 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 26 Apr 2019 11:16:47 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
In-Reply-To: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>
Message-ID: <1556277407.79.0.469199283227.issue36727@roundup.psfhosted.org>


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

I created https://github.com/python/bugs.python.org/issues/35 about the comma in the username.

----------

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

From report at bugs.python.org  Fri Apr 26 09:48:13 2019
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 26 Apr 2019 13:48:13 +0000
Subject: [docs] [issue36727] python 3.6+ docs use ul tags instead of ol tags
In-Reply-To: <1556232428.79.0.0883162506271.issue36727@roundup.psfhosted.org>
Message-ID: <1556286493.11.0.979309173814.issue36727@roundup.psfhosted.org>


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


----------
nosy: +Oliver Too, Eh?

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

From report at bugs.python.org  Fri Apr 26 10:19:02 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 26 Apr 2019 14:19:02 +0000
Subject: [docs] [issue25810] Python 3 documentation for eval is incorrect
In-Reply-To: <1449346403.16.0.483198527619.issue25810@psf.upfronthosting.co.za>
Message-ID: <1556288342.91.0.914468074442.issue25810@roundup.psfhosted.org>


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

See also PEP570 and issue 36540.

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

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

From report at bugs.python.org  Fri Apr 26 12:32:25 2019
From: report at bugs.python.org (Oliver Too, Eh?)
Date: Fri, 26 Apr 2019 16:32:25 +0000
Subject: [docs] [issue34717] docs: disable numbered sections for stdlib in
 html
In-Reply-To: <1537218837.12.0.956365154283.issue34717@psf.upfronthosting.co.za>
Message-ID: <1556296345.9.0.204738788959.issue34717@roundup.psfhosted.org>


Oliver Too, Eh? <olivertooeh at gmail.com> added the comment:

As someone who is only now making the transition from Python 2 to Python 3, losing the numbering in the documentation on the Python Standard Library slows down my navigation when looking through the high-level contents.  

Given that the position of sections hasn't drifted much between versions, being able to treat the sections like chapters of a book affords faster access when I can quickly identify my position in the page without having to look at the scrollbar, provided my operating system even displays one when I am not actively scrolling.  Knowing that there are roughly 40 top-level sections in the library means I can find something I know to be in the middle much more quickly from its number (plus or minus version drift) and those of its local surroundings than by its overall position in the page.  Moreover, losing this feature can only be mitigated by search or "find in page" provided I remember modules and their contents by name, correctly spelled.

I appreciate the overall cleaner appearance as sections become heavily nested that is addressed by this enhancement.  I do however respectfully disagree with the choice of doing this at the expense of top level ordering.

----------
nosy: +Oliver Too Eh?

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

From report at bugs.python.org  Fri Apr 26 13:19:46 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 26 Apr 2019 17:19:46 +0000
Subject: [docs] [issue36715] Dictionary initialization
In-Reply-To: <1556135397.5.0.612221590326.issue36715@roundup.psfhosted.org>
Message-ID: <1556299186.22.0.581511718308.issue36715@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 13:26:25 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 17:26:25 +0000
Subject: [docs] [issue14945] Setup & Usage documentation for selected stdlib
 modules
In-Reply-To: <1338256259.22.0.129056676976.issue14945@psf.upfronthosting.co.za>
Message-ID: <1556299585.66.0.821134962279.issue14945@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 13:50:52 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 17:50:52 +0000
Subject: [docs] [issue12957] mmap.resize changes memory address of mmap'd
 region
In-Reply-To: <1315686259.57.0.0304440203891.issue12957@psf.upfronthosting.co.za>
Message-ID: <1556301052.47.0.897870496998.issue12957@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 13:44:59 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 17:44:59 +0000
Subject: [docs] [issue11176] give more meaningful argument names in argparse
 documentation
In-Reply-To: <1297352937.46.0.470038569364.issue11176@psf.upfronthosting.co.za>
Message-ID: <1556300699.68.0.747998828595.issue11176@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 13:28:54 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 17:28:54 +0000
Subject: [docs] [issue12600] Add example of using load_tests to parameterise
 Test Cases
In-Reply-To: <1311226769.48.0.369455670372.issue12600@psf.upfronthosting.co.za>
Message-ID: <1556299734.61.0.683466657931.issue12600@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 13:36:18 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 17:36:18 +0000
Subject: [docs] [issue8350] Document lack of support for keyword arguments
 in C functions
In-Reply-To: <1270764159.26.0.287104770145.issue8350@psf.upfronthosting.co.za>
Message-ID: <1556300178.19.0.00172685481952.issue8350@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:47:14 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:47:14 +0000
Subject: [docs] [issue10048] urllib.request documentation confusing
In-Reply-To: <1286535990.46.0.129844190964.issue10048@psf.upfronthosting.co.za>
Message-ID: <1556308034.42.0.686487593838.issue10048@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:01:47 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:01:47 +0000
Subject: [docs] [issue12217] Cross-link docs for faulthandler,
 traceback and pdb
In-Reply-To: <1306770313.4.0.799430970978.issue12217@psf.upfronthosting.co.za>
Message-ID: <1556305307.69.0.760065484783.issue12217@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:39:01 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:39:01 +0000
Subject: [docs] [issue16663] Poor documentation for METH_KEYWORDS
In-Reply-To: <1355242591.45.0.999993608815.issue16663@psf.upfronthosting.co.za>
Message-ID: <1556307541.13.0.897286212893.issue16663@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:48:28 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:48:28 +0000
Subject: [docs] [issue17924] Deprecate stat.S_IF* integer constants
In-Reply-To: <1367928320.73.0.37418131168.issue17924@psf.upfronthosting.co.za>
Message-ID: <1556308108.28.0.95496036952.issue17924@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:37:31 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:37:31 +0000
Subject: [docs] [issue16242] Pickle and __getattr__
In-Reply-To: <1350324673.62.0.567343854306.issue16242@psf.upfronthosting.co.za>
Message-ID: <1556307451.39.0.234992235731.issue16242@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:16:26 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:16:26 +0000
Subject: [docs] [issue21956] Doc files deleted from repo are not deleted
 from docs.python.org.
In-Reply-To: <1405084031.97.0.312909906567.issue21956@psf.upfronthosting.co.za>
Message-ID: <1556306186.83.0.790677365052.issue21956@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:46:29 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:46:29 +0000
Subject: [docs] [issue14149] argparse: Document how to use argument names
 that are not Python identifiers
In-Reply-To: <1330431835.85.0.549489798388.issue14149@psf.upfronthosting.co.za>
Message-ID: <1556307989.6.0.501326223872.issue14149@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:32:01 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:32:01 +0000
Subject: [docs] [issue14379] Several traceback docs improvements
In-Reply-To: <1332328007.08.0.704590425302.issue14379@psf.upfronthosting.co.za>
Message-ID: <1556307121.02.0.42812856326.issue14379@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:01:03 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:01:03 +0000
Subject: [docs] [issue10175] vs version for win32 compilation of extension
 modules is undocumented.
In-Reply-To: <1287795744.75.0.288699311556.issue10175@psf.upfronthosting.co.za>
Message-ID: <1556305263.55.0.185465220375.issue10175@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:51:09 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:51:09 +0000
Subject: [docs] [issue17243] The changes made for issue 4074 should be
 documented
In-Reply-To: <1361305487.48.0.247163585293.issue17243@psf.upfronthosting.co.za>
Message-ID: <1556308269.54.0.327037187022.issue17243@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:52:49 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:52:49 +0000
Subject: [docs] [issue15629] Add to regrtest the ability to run Lib and Doc
 doctests
In-Reply-To: <1344779660.84.0.741331364071.issue15629@psf.upfronthosting.co.za>
Message-ID: <1556308369.64.0.926672665632.issue15629@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:39:38 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:39:38 +0000
Subject: [docs] [issue10789] Lock.acquire documentation is misleading
In-Reply-To: <1293644478.45.0.40426107256.issue10789@psf.upfronthosting.co.za>
Message-ID: <1556311178.54.0.0130010331201.issue10789@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:06:57 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:06:57 +0000
Subject: [docs] [issue18355] Merge super() guide into documentation
In-Reply-To: <1372901200.41.0.725969821731.issue18355@psf.upfronthosting.co.za>
Message-ID: <1556309217.54.0.522058206953.issue18355@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:43:43 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:43:43 +0000
Subject: [docs] [issue9274] code.InteractiveInterpreter fails to change
 locals when invoked in a function
In-Reply-To: <1279300874.85.0.408315798568.issue9274@psf.upfronthosting.co.za>
Message-ID: <1556311423.17.0.205174577084.issue9274@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 15:38:09 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 19:38:09 +0000
Subject: [docs] [issue16652] socket.getfqdn docs are not explicit enough
 about the algorithm.
In-Reply-To: <1355089481.55.0.645096435972.issue16652@psf.upfronthosting.co.za>
Message-ID: <1556307489.48.0.795455126437.issue16652@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:41:08 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:41:08 +0000
Subject: [docs] [issue18675] Daemon Threads can seg fault
In-Reply-To: <1375867396.76.0.697227657582.issue18675@psf.upfronthosting.co.za>
Message-ID: <1556311268.36.0.380887302083.issue18675@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:01:56 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:01:56 +0000
Subject: [docs] [issue11001] Various obvious errors in cookies documentation
In-Reply-To: <1295908065.55.0.221906287574.issue11001@psf.upfronthosting.co.za>
Message-ID: <1556308916.75.0.351338427924.issue11001@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:41:42 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:41:42 +0000
Subject: [docs] [issue7436] Define 'object with assignable attributes'
In-Reply-To: <1259961781.03.0.33355289278.issue7436@psf.upfronthosting.co.za>
Message-ID: <1556311302.24.0.176614229853.issue7436@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 16:40:25 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Fri, 26 Apr 2019 20:40:25 +0000
Subject: [docs] [issue8041] No documentation for
 Py_TPFLAGS_HAVE_STACKLESS_EXTENSION or Py_TPFLAGS_HAVE_VERSION_TAG.
In-Reply-To: <1267544098.65.0.440493208051.issue8041@psf.upfronthosting.co.za>
Message-ID: <1556311225.63.0.911035394514.issue8041@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Apr 26 18:57:57 2019
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 26 Apr 2019 22:57:57 +0000
Subject: [docs] [issue35181] Doc: Namespace Packages: Inconsistent
 documentation of __loader__ being None
In-Reply-To: <1541543349.68.0.788709270274.issue35181@psf.upfronthosting.co.za>
Message-ID: <1556319477.73.0.552658411071.issue35181@roundup.psfhosted.org>


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


----------
assignee: docs at python -> barry

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

From report at bugs.python.org  Sat Apr 27 00:24:09 2019
From: report at bugs.python.org (Peter Bauer)
Date: Sat, 27 Apr 2019 04:24:09 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
Message-ID: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>


New submission from Peter Bauer <p-bauer-it at t-online.de>:

In the fourth paragraph, the sentence 

"Thus, global variables cannot be directly assigned a value within a function (unless named in a global statement)"

should somehow be extended to mention the nonlocal-statements:

Thus, global variables or variables of enclosing functions cannot be directly assigned a value within a function (unless named in a global statement (for global variables) or named in a nonlocal statement (for variables of enclosing functions)

----------
assignee: docs at python
components: Documentation
messages: 340963
nosy: docs at python, pbhd0815
priority: normal
severity: normal
status: open
title: "4.6. Defining Functions" should mention nonlocal
type: enhancement
versions: Python 3.9

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

From report at bugs.python.org  Fri Apr 26 22:20:56 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Apr 2019 02:20:56 +0000
Subject: [docs] [issue36675] Doctest directives and comments missing from
 code samples
In-Reply-To: <1555757030.56.0.8094269644.issue36675@roundup.psfhosted.org>
Message-ID: <1556331656.0.0.417950311645.issue36675@roundup.psfhosted.org>


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

I verified that the line in Doc/library/doctest.rst has the comment.
"
For example, this test passes::

   >>> print(list(range(20))) # doctest: +NORMALIZE_WHITESPACE
   [0,   1,  2,  3,  4,  5,  6,  7,  8,  9,
   10,  11, 12, 13, 14, 15, 16, 17, 18, 19]
"
However, the comment is omitted from the .html built on Windows by Sphinx 1.8.1.
"
<div class="highlight-python3 notranslate"><div class="highlight"><pre><span></span><span class="gp">&gt;&gt;&gt; </span><span class="nb">print</span><span class="p">(</span><span class="nb">list</span><span class="p">(</span><span class="nb">range</span><span class="p">(</span><span class="mi">20</span><span class="p">)))</span> 
   ***html for comment should be here***
<span class="go">[0,   1,  2,  3,  4,  5,  6,  7,  8,  9,</span>
<span class="go">10,  11, 12, 13, 14, 15, 16, 17, 18, 19]</span>
</pre></div>
</div>
"
To me, this is a bug with building the .html for doctest.rst.  Comments are preserved elsewhere.  For instance, the code example for https://docs.python.org/3/library/functions.html#dir.  The .rst file has
"
   The resulting list is sorted alphabetically.  For example:

      >>> import struct
      >>> dir()   # show the names in the module namespace  # doctest: +SKIP
"
Both use 3-space colon + indents to mean 'example block'.  The only difference is '::' versus ':'.  https://devguide.python.org/documenting/#source-code says :: is required.  idle.rst also has a code example with comments displayed (I just submitted a PR to not suppress color highlighting.)

I leave it to the doc experts to discover why the comments are not included in doctest.html.

----------
nosy: +eric.araujo, ezio.melotti, terry.reedy, willingc
stage:  -> needs patch
title: Doctest directives and comments not visible or missing from code samples -> Doctest directives and comments missing from code samples
versions: +Python 2.7, Python 3.7, Python 3.8

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

From madivad at dav3.net  Mon Apr 22 10:02:10 2019
From: madivad at dav3.net (Dave Matthews)
Date: Tue, 23 Apr 2019 00:02:10 +1000
Subject: [docs] Kindle version
Message-ID: <B298207D-9CAC-473A-BFF0-8BFE5DC1EE89@dav3.net>

Is it possible to create a version nicely viewable for the kindle?

Cheers

Dave

From mw.seo at teeoom.com  Wed Apr 24 03:11:40 2019
From: mw.seo at teeoom.com (=?UTF-8?B?7ISc66qF7JuQ?=)
Date: Wed, 24 Apr 2019 16:11:40 +0900
Subject: [docs] I can't read your pdf file!!!
Message-ID: <CAG6Bo-sSxC9oKTU-8o4MTVw_wsNExLm+6xu3f1zpawnZgtYP1w@mail.gmail.com>

Hi?

I want to download and view a Korean version of pdf file.
When I open it using adobe acrobat on windows 10, English or numbers are
normal, but the part written in Korean is blank.
I think it is a problem with font, I downloaded LM font and installed it on
windows, but it still does not display Korean.

Thank you for your confirmation.

Then, have a good time at work.

-------------------------------------------
??(?) ??? ?????
e-mail : mw.seo at teeoom.com
Tel. : 070-4400-9876
Fax. : 0303-3449-0123
C.P. : 010-6248-1771
Addr. : ????? ??? ??? 174-10, 313? (???, ???????)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190424/020101d3/attachment.html>

From ofjolivares at gmail.com  Wed Apr 24 20:42:58 2019
From: ofjolivares at gmail.com (Omar Francisco Olivares)
Date: Wed, 24 Apr 2019 20:42:58 -0400
Subject: [docs] EPUB and PDF files unavailable
Message-ID: <CANhwGOYTgNAcKOzJU4aauhJS-0zy8KMTXbN2JOv3cWaa3-+N0Q@mail.gmail.com>

Hello

I tried to download the EPUB and PDF files from
https://docs.python.org/dev/download.html  but they're currently
unavailable. How can I download them?

Greetings from Chile
Omar

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

From L.Plant.98 at cantab.net  Thu Apr 25 02:16:22 2019
From: L.Plant.98 at cantab.net (Luke Plant)
Date: Thu, 25 Apr 2019 09:16:22 +0300
Subject: [docs] Various obvious errors in cookies documentation (issue
 11001)
In-Reply-To: <20190425041933.15842.26062@bugs.ams1.psf.io>
References: <20190425041933.15842.26062@bugs.ams1.psf.io>
Message-ID: <76f626bf-7bbd-ca2d-5d4b-ea45fcf87824@cantab.net>

Replying by email because bugs.python.org is throwing me 500 errors when 
I try to reply online.

On 2019/04/25 06:19:33, Martin Panter wrote:

 > Suggest clarify what you mean by ?appropriate?. The encoding is not 
appropriate
 > if you want to satisfy the Netscape or RFC 6265 specifications for 
cookies. See
 > <https://bugs.python.org/issue19670>.

Given the comments in that ticket, it could read:

 ? This class derives from :class:`BaseCookie` and overrides 
:meth:`value_decode`
 ? and :meth:`value_encode` to use RFC 2109 quoted-string escaping for 
values
 ? outside the alphanumeric set.

Luke




On 25/04/2019 07:19, vadmium+py at gmail.com wrote:
> http://bugs.python.org/review/11001/diff/1905/Doc/library/http.cookies.rst
> File Doc/library/http.cookies.rst (right):
>
> http://bugs.python.org/review/11001/diff/1905/Doc/library/http.cookies.rst#newcode45
> Doc/library/http.cookies.rst:45: and :meth:`value_encode` to use
> encoding appropriate for values outside
> Suggest clarify what you mean by ?appropriate?. The encoding is not
> appropriate if you want to satisfy the Netscape or RFC 6265
> specifications for cookies. See <https://bugs.python.org/issue19670>.
>
> http://bugs.python.org/review/11001/



From report at bugs.python.org  Sat Apr 27 00:35:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 27 Apr 2019 04:35:33 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1556339733.96.0.469688678274.issue36739@roundup.psfhosted.org>


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

Thanks for the suggestion.  Would you like to submit a PR?

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

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

From report at bugs.python.org  Sat Apr 27 06:42:32 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sat, 27 Apr 2019 10:42:32 +0000
Subject: [docs] [issue18675] Daemon Threads can seg fault
In-Reply-To: <1375867396.76.0.697227657582.issue18675@psf.upfronthosting.co.za>
Message-ID: <1556361752.59.0.0332717530758.issue18675@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


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

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

From report at bugs.python.org  Sat Apr 27 10:22:57 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Sat, 27 Apr 2019 14:22:57 +0000
Subject: [docs] [issue14149] argparse: Document how to use argument names
 that are not Python identifiers
In-Reply-To: <1330431835.85.0.549489798388.issue14149@psf.upfronthosting.co.za>
Message-ID: <1556374977.62.0.206355739755.issue14149@roundup.psfhosted.org>


Change by Fred L. Drake, Jr. <fdrake at gmail.com>:


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

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

From report at bugs.python.org  Sat Apr 27 09:44:34 2019
From: report at bugs.python.org (Peter Bauer)
Date: Sat, 27 Apr 2019 13:44:34 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1556372674.96.0.239039885199.issue36739@roundup.psfhosted.org>


Change by Peter Bauer <p-bauer-it at t-online.de>:


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

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

From report at bugs.python.org  Sat Apr 27 09:04:22 2019
From: report at bugs.python.org (Peter Bauer)
Date: Sat, 27 Apr 2019 13:04:22 +0000
Subject: [docs] [issue36739] "4.6. Defining Functions" should mention
 nonlocal
In-Reply-To: <1556339049.57.0.959218106285.issue36739@roundup.psfhosted.org>
Message-ID: <1556370262.69.0.81201386012.issue36739@roundup.psfhosted.org>


Peter Bauer <p-bauer-it at t-online.de> added the comment:

ok, will try to create a pull-request for that, although i'm not a natural englishman...

----------

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

From report at bugs.python.org  Sat Apr 27 13:56:43 2019
From: report at bugs.python.org (Jon Dufresne)
Date: Sat, 27 Apr 2019 17:56:43 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
Message-ID: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>


New submission from Jon Dufresne <jon.dufresne at gmail.com>:

Here: https://docs.python.org/3/reference/datamodel.html#object.__get__

The __get__ signature is defined as:

object.__get__(self, instance, owner)

But here: https://docs.python.org/3/howto/descriptor.html#descriptor-protocol

It is defined as:

descr.__get__(self, obj, type=None)

It is not clear to me as a reader if all descriptors should have the owner/type argument default to None or if it should be required. If it should default to None, I think all doc examples should follow this expectation to make it clear to someone implementing a descriptor for the first time. As best I can tell, the owner/type is always passed. So perhaps the =None shouldn't be there.

Grepping the CPython code, I see lots of definitions for both required and optional, adding more confusion for me.

If there is a definitive answer, I'm happy to follow through by updating the docs.

----------
assignee: docs at python
components: Documentation
messages: 341004
nosy: docs at python, jdufresne
priority: normal
severity: normal
status: open
title: Docs: Descript __get__ signature defined differently across the docs
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Sat Apr 27 14:06:22 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 27 Apr 2019 18:06:22 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1556388382.63.0.877232405089.issue36743@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun Apr 28 03:12:09 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 28 Apr 2019 07:12:09 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1556435529.55.0.161108310331.issue36743@roundup.psfhosted.org>


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

Perhaps the datamodel docs can be clarified to note that callers are allowed to omit the third argument (which usually only makes sense when the second argument is not None). FWIW, section 3.3.2.3 already has an example of a direct call to a __get__ descriptor with only the *obj* argument.

----------
assignee: docs at python -> rhettinger
versions:  -Python 2.7, Python 3.5, Python 3.6, Python 3.9

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

From report at bugs.python.org  Sun Apr 28 03:22:49 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 28 Apr 2019 07:22:49 +0000
Subject: [docs] [issue36715] Dictionary initialization
In-Reply-To: <1556135397.5.0.612221590326.issue36715@roundup.psfhosted.org>
Message-ID: <1556436169.76.0.69171114077.issue36715@roundup.psfhosted.org>


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


New changeset da63b321f63b697f75e7ab2f88f55d907f56c187 by Raymond Hettinger in branch 'master':
bpo-36715: Add usage note for dict.fromkeys() (GH-12974)
https://github.com/python/cpython/commit/da63b321f63b697f75e7ab2f88f55d907f56c187


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

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

From report at bugs.python.org  Sun Apr 28 03:23:07 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 28 Apr 2019 07:23:07 +0000
Subject: [docs] [issue36715] Dictionary initialization
In-Reply-To: <1556135397.5.0.612221590326.issue36715@roundup.psfhosted.org>
Message-ID: <1556436187.55.0.908923478441.issue36715@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun Apr 28 04:11:19 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 28 Apr 2019 08:11:19 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1556439079.4.0.77353836921.issue36743@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sun Apr 28 09:07:56 2019
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 28 Apr 2019 13:07:56 +0000
Subject: [docs] =?utf-8?q?=5Bissue23297=5D_Clarify_error_when_=E2=80=98to?=
 =?utf-8?q?kenize=2Edetect=5Fencoding=E2=80=99_receives_text?=
In-Reply-To: <1421901626.89.0.392776519963.issue23297@psf.upfronthosting.co.za>
Message-ID: <1556456876.01.0.873612598293.issue23297@roundup.psfhosted.org>


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

The original problem has already been solved by making tokenize.generate_tokens() public in issue 12486.

However, the same exception can be raised when tokenize.open() is used with tokenize.tokenize(), because it returns a text stream:

    https://github.com/python/cpython/blob/da63b321f63b697f75e7ab2f88f55d907f56c187/Lib/tokenize.py#L396

hello.py
--------

def say_hello():
    print("Hello, World!")

say_hello()


text.py
-------

import tokenize

with tokenize.open('hello.py') as f:
    token_gen = tokenize.tokenize(f.readline)
    for token in token_gen:
        print(token)

When we pass f.readline to tokenize.tokenize(), the second call to detect_encoding() fails, because f.readline() returns str.

In Lib/test/test_tokenize.py, it seems like tokenize.open() is only tested to open a file. Its output isn't passed to tokenize.tokenize(). Most of the tests either pass the readline() method of open(..., 'rb') or io.BytesIO() to tokenize.tokenize().

I will submit a documentation PR that suggests to use tokenize.generate_tokens() with tokenize.open().

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 3.7, Python 3.8 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Sun Apr 28 18:48:30 2019
From: report at bugs.python.org (Ben Finney)
Date: Sun, 28 Apr 2019 22:48:30 +0000
Subject: [docs] =?utf-8?q?=5Bissue23297=5D_Clarify_error_when_=E2=80=98to?=
 =?utf-8?q?kenize=2Edetect=5Fencoding=E2=80=99_receives_text?=
In-Reply-To: <1556456876.01.0.873612598293.issue23297@roundup.psfhosted.org>
Message-ID: <20190428224820.GY26303@benfinney.id.au>


Ben Finney <ben+python at benfinney.id.au> added the comment:

On 28-Apr-2019, Berker Peksag wrote:

> The original problem has already been solved by making
> tokenize.generate_tokens() public in issue 12486.

I don't understand how that would affect the resolution of this issue.

Isn't the correct resolution here going to entail correct
implementation in ?file.readline??

----------

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

From report at bugs.python.org  Mon Apr 29 07:15:50 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Mon, 29 Apr 2019 11:15:50 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556536550.65.0.403555732293.issue35329@roundup.psfhosted.org>


Utkarsh Gupta <guptautkarsh2102 at gmail.com> added the comment:

Hey,

I'd be happy to submit one :)

----------
nosy: +utkarsh2102

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

From report at bugs.python.org  Mon Apr 29 07:20:26 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Mon, 29 Apr 2019 11:20:26 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556536826.9.0.455629210884.issue35329@roundup.psfhosted.org>


Change by Utkarsh Gupta <guptautkarsh2102 at gmail.com>:


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

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

From saichandra1128 at gmail.com  Mon Apr 29 08:50:40 2019
From: saichandra1128 at gmail.com (Sai Chandra Kumar)
Date: Mon, 29 Apr 2019 18:20:40 +0530
Subject: [docs] misbehaving functionality of all() function
Message-ID: <CAAiJ6EWr978chcu6HWs-4tML6rNyZfDAGVVAeYUDQPD_JQv1NQ@mail.gmail.com>

Hello,

I was going through python 3.6 docs and i am finding all function is
behaving differently when working with variables and lists.

The all() function is not iterable for complex numbers. but when I am
passing complex number in list, the all function returns True.
l = [1,2,1+12.1j]


all(l)


I felt happy if you guys reply on top of these.



Thanks&Regards,

V.Saibabu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190429/943902a4/attachment.html>

From report at bugs.python.org  Mon Apr 29 13:53:25 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 29 Apr 2019 17:53:25 +0000
Subject: [docs] [issue36754] Remove smart quotes in pydoc text
Message-ID: <1556560405.97.0.464374588222.issue36754@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

Not all console configurations can correctly render smart quotes in help() text. See the "?" in "superclass's" below.

When building for pydoc-topics, it would be ideal to disable smart quotes. (I'm assuming from issue31793 that this can be done in configuration, though I'm not entirely sure how - it's not clear to me from those PRs)

---

>>> help("BASICMETHODS")
Basic customization
*******************

object.__new__(cls[, ...])
...
   Typical implementations create a new instance of the class by
   invoking the superclass?s "__new__()" method using
   "super().__new__(cls[, ...])" with appropriate arguments and then
   modifying the newly-created instance as necessary before returning
   it.

----------
assignee: docs at python
components: Documentation
messages: 341107
nosy: docs at python, steve.dower
priority: normal
severity: normal
stage: needs patch
status: open
title: Remove smart quotes in pydoc text
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Apr 29 14:14:43 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 29 Apr 2019 18:14:43 +0000
Subject: [docs] [issue36754] Remove smart quotes in pydoc text
In-Reply-To: <1556560405.97.0.464374588222.issue36754@roundup.psfhosted.org>
Message-ID: <20190429181436.GF12773@ando.pearwood.info>


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

> Not all console configurations can correctly render smart quotes in 
> help() text. See the "?" in "superclass's" below.

That suggests to me a mismatch in encodings, rather than inability to 
render curly quotes at all. It's 2019 and surely we don't have to target 
ASCII as the lowest common denominator any more?

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

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

From report at bugs.python.org  Mon Apr 29 14:29:30 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 29 Apr 2019 18:29:30 +0000
Subject: [docs] [issue36754] Remove smart quotes in pydoc text
In-Reply-To: <1556560405.97.0.464374588222.issue36754@roundup.psfhosted.org>
Message-ID: <1556562570.08.0.752769240228.issue36754@roundup.psfhosted.org>


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

> mismatch in encodings

Also likely. I haven't looked into how pydoc does its rendering, but certainly Python 3.7 on Windows should be able to print regular Unicode.

Perhaps it's not going through stdout for some reason?

----------

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

From report at bugs.python.org  Mon Apr 29 22:20:10 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 30 Apr 2019 02:20:10 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556590810.84.0.00918914569405.issue35329@roundup.psfhosted.org>


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


New changeset ee0309f3d83ab9ffa02542bcf45ece84f4fb265e by Benjamin Peterson (Utkarsh Gupta) in branch 'master':
closes bpo-35329: Change 'Package' to 'package' in accordance with PEP8. (GH-13008)
https://github.com/python/cpython/commit/ee0309f3d83ab9ffa02542bcf45ece84f4fb265e


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

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

From report at bugs.python.org  Mon Apr 29 22:20:24 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 30 Apr 2019 02:20:24 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556590824.43.0.997550273061.issue35329@roundup.psfhosted.org>


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


----------
pull_requests: +12941

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

From report at bugs.python.org  Mon Apr 29 22:20:33 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 30 Apr 2019 02:20:33 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556590833.35.0.257374532473.issue35329@roundup.psfhosted.org>


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


----------
pull_requests: +12942

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

From report at bugs.python.org  Mon Apr 29 22:25:44 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 30 Apr 2019 02:25:44 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556591144.23.0.904788849508.issue35329@roundup.psfhosted.org>


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


New changeset 3e5c4a7c804c3ad76a558e5463655c329aee6437 by Miss Islington (bot) in branch '2.7':
closes bpo-35329: Change 'Package' to 'package' in accordance with PEP8. (GH-13008)
https://github.com/python/cpython/commit/3e5c4a7c804c3ad76a558e5463655c329aee6437


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

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

From report at bugs.python.org  Mon Apr 29 22:26:03 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 30 Apr 2019 02:26:03 +0000
Subject: [docs] [issue35329] Documentation - capitalization issue
In-Reply-To: <1543337036.72.0.788709270274.issue35329@psf.upfronthosting.co.za>
Message-ID: <1556591163.14.0.319140695106.issue35329@roundup.psfhosted.org>


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


New changeset 4b5340bb634be2ee2a40242cdf4e3f7a0b6c757a by Miss Islington (bot) in branch '3.7':
closes bpo-35329: Change 'Package' to 'package' in accordance with PEP8. (GH-13008)
https://github.com/python/cpython/commit/4b5340bb634be2ee2a40242cdf4e3f7a0b6c757a


----------

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

From report at bugs.python.org  Tue Apr 30 16:41:36 2019
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 30 Apr 2019 20:41:36 +0000
Subject: [docs] [issue36345] Deprecate Tools/scripts/serve.py in favour of
 python -m http.server -d
In-Reply-To: <1552917459.29.0.295748589939.issue36345@roundup.psfhosted.org>
Message-ID: <1556656896.61.0.989163513034.issue36345@roundup.psfhosted.org>


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

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

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

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

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

The examples in the wsgiref documentation already cover most of the cases. There is no need to add more similar ones.

----------
nosy: +berker.peksag

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

From report at bugs.python.org  Tue Apr 30 17:04:59 2019
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 30 Apr 2019 21:04:59 +0000
Subject: [docs] [issue36329] use the right python "make -C Doc/ serve"
In-Reply-To: <1552849058.57.0.633692372704.issue36329@roundup.psfhosted.org>
Message-ID: <1556658299.65.0.382673742846.issue36329@roundup.psfhosted.org>


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

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

----------
nosy: +berker.peksag

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

From report at bugs.python.org  Tue Apr 30 20:56:01 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 01 May 2019 00:56:01 +0000
Subject: [docs] [issue35181] Doc: Namespace Packages: Inconsistent
 documentation of __loader__ being None
In-Reply-To: <1541543349.68.0.788709270274.issue35181@psf.upfronthosting.co.za>
Message-ID: <1556672160.94.0.370080894186.issue35181@roundup.psfhosted.org>


Barry A. Warsaw <barry at python.org> added the comment:

I've approved both PRs, however I am rather uncomfortable about the code snippet in import.rst.  G?ry's change is a good one AFAICT, and thanks for the contribution!  I would feel much better about the long term correctness of this code snippet if we had a doctest to run over it.  But that's for another time.

----------

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