Mailman 3 March 2017 - docs

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Mariatta Wijaya March 30, 2017

March 30, 2017

Mariatta Wijaya added the comment: New changeset eef6e11f9883f54de491121b8c49fdadd3e3506d by Mariatta in branch '3.5': bpo-29677: DOC: clarify documentation for `round` (GH-877) (GH-893) https://github.com/python/cpython/commit/eef6e11f9883f54de491121b8c49fdadd3… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Mariatta Wijaya March 30, 2017

March 30, 2017

Mariatta Wijaya added the comment: New changeset 2609c9ee78c53d501914a5a90dbe094d9a8c3c97 by Mariatta in branch '3.6': bpo-29677: DOC: clarify documentation for `round` (GH-877) (GH-892) https://github.com/python/cpython/commit/2609c9ee78c53d501914a5a90dbe094d9a… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Mariatta Wijaya March 30, 2017

March 30, 2017

Changes by Mariatta Wijaya <mariatta.wijaya(a)gmail.com>: ---------- pull_requests: +796 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Mariatta Wijaya March 30, 2017

March 30, 2017

Changes by Mariatta Wijaya <mariatta.wijaya(a)gmail.com>: ---------- pull_requests: +795 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Cheryl Sabella March 29, 2017

March 29, 2017

Cheryl Sabella added the comment: Mariatta, Thank you so much for your support and encouragement while I worked on my first PR. You've made this an awesome experience! ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Mariatta Wijaya March 29, 2017

March 29, 2017

Changes by Mariatta Wijaya <mariatta.wijaya(a)gmail.com>: ---------- stage: needs patch -> backport needed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue29677] clarify docs about 'round()' accepting a negative integer for ndigits
by Mariatta Wijaya March 29, 2017

March 29, 2017

Mariatta Wijaya added the comment: New changeset 85deefcf61d3cc192846f41a4ccc6df17da60c98 by Mariatta (csabella) in branch 'master': bpo-29677: DOC: clarify documentation for `round` (GH-877) https://github.com/python/cpython/commit/85deefcf61d3cc192846f41a4ccc6df17d… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29677> _______________________________________

1 0

[issue16011] "in" should be consistent with return value of __contains__
by Neal Parikh March 29, 2017

March 29, 2017

New submission from Neal Parikh: The Python 2.7.3 documentation says the following about defining __contains__: "Called to implement membership test operators. Should return true if item is in self, false otherwise. For mapping objects, this should consider the keys of the mapping rather than the values or the key-item pairs." This suggests that while you should return True/False, you don't need to. Also, the documentation doesn't say that if you return a value other than True or False, it will silently coerce other values to be True or False when you use "in". For example: >>> class Foo(object): ... def __contains__(self, item): return 42 ... >>> foo = Foo() >>> 3 in foo True >>> foo.__contains__(3) 42 When __contains__ is defined, "in" should return whatever __contains__ returns, even if this value is neither True nor False. That would be consistent with, for example, the comparison operators: You can return anything from __lt__ and "x < 4" will correctly pass along that value regardless of what it is. ---------- assignee: docs@python components: Documentation, Interpreter Core messages: 171085 nosy: docs@python, nparikh priority: normal severity: normal status: open title: "in" should be consistent with return value of __contains__ type: behavior versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16011> _______________________________________

10 25

Broken link on distutils doc page
by Ian Fisher March 29, 2017

March 29, 2017

Hello, I am writing to report a bug on the distutils page <https://docs.python.org/3.4/library/distutils.html> of the Python 3.4 documentation. This page contains a broken link to the setuptools page. Currently the link is https://setuptools.pypa.io/en/latest/setuptools.html; the link http://setuptools.readthedocs.io/en/latest/ is probably what was intended. Sincerely, Ian Fisher

1 0

It seems to be a bug in online tutoria
by flavio.bonifacio＠metis-ricerche.it March 29, 2017

March 29, 2017

In the on line tutorial par. 4.6 , in the fib2 function a print is missing >>> def fib2(n): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a, b = 0, 1 ... while a < n: ... result.append(a) # see below ... a, b = b, a+b ... return result ... >>> f100 = fib2(100) # call it >>> f100 # write the result <========> I THINK IT MUST BE print(f100) [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] Flavio Bonifacio --------- Ai sensi e per effetto della Legge sulla tutela della riservatezza personale (D. Lgs. 196/2003) questa e-mail è destinata unicamente agli indirizzi sopra indicati e le informazioni in essa contenute sono da considerarsi strettamente riservate. E' proibito leggere, copiare, usare o diffondere il contenuto della presente e-mail senza autorizzazione. Se avete ricevuto questo messaggio per errore, siete pregati di eliminarlo e darne comunicazione al mittente. Grazie. --------- Metis Ricerche srl via Camerana, 6 10128 Torino Tel +39-011538028

1 0