Mailman 3 December 2016 - docs

[issue29024] Add Kivy entry to Graphic User Interface FAQ
by Alexander Taylor Dec. 20, 2016

Dec. 20, 2016

Changes by Alexander Taylor <alexanderjohntaylor(a)gmail.com>: ---------- type: enhancement -> _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29024> _______________________________________

1 0

[issue29024] Add Kivy entry to Graphic User Interface FAQ
by Alexander Taylor Dec. 20, 2016

Dec. 20, 2016

Changes by Alexander Taylor <alexanderjohntaylor(a)gmail.com>: ---------- assignee: docs@python components: Documentation files: gui_faq_kivy.patch keywords: patch nosy: docs@python, inclement priority: normal severity: normal status: open title: Add Kivy entry to Graphic User Interface FAQ type: enhancement versions: Python 3.7 Added file: http://bugs.python.org/file45975/gui_faq_kivy.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29024> _______________________________________

1 0

[issue29010] Incorrect description about scope related with inheritance
by woo yoo Dec. 20, 2016

Dec. 20, 2016

woo yoo added the comment: I agree with you ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29010> _______________________________________

1 0

[issue29010] Incorrect description about scope related with inheritance
by woo yoo Dec. 20, 2016

Dec. 20, 2016

woo yoo added the comment: If i was wrong about this issue, please tell me. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29010> _______________________________________

2 1

[issue29010] Incorrect description about scope related with inheritance
by woo yoo Dec. 19, 2016

Dec. 19, 2016

woo yoo added the comment: The previous description about scope classify it into 3 types explicitly, which means the scope containing the current module's global names is not same as the scope containing built-in names. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29010> _______________________________________

1 0

[issue29010] Incorrect description about scope related with inheritance
by R. David Murray Dec. 19, 2016

Dec. 19, 2016

R. David Murray added the comment: It is part of the global scope, which contains all other scopes. (I'm not 100% sure I'm comfortable with that language, but it doesn't seem obviously wrong.) ---------- nosy: +r.david.murray _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29010> _______________________________________

1 0

[issue29010] Incorrect description about scope related with inheritance
by woo yoo Dec. 19, 2016

Dec. 19, 2016

woo yoo added the comment: Code: >class A(object): pass 'object' is not in the same scope as 'A' ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29010> _______________________________________

1 0

[issue28383] __hash__ documentation recommends naive XOR to combine but this is suboptimal
by Kevin Norris Dec. 19, 2016

Dec. 19, 2016

New submission from Kevin Norris: The documentation for __hash__ contains this text: "The only required property is that objects which compare equal have the same hash value; it is advised to somehow mix together (e.g. using exclusive or) the hash values for the components of the object that also play a part in comparison of objects." The recommendation of "using exclusive or" is likely to result in programmers naively doing this: def __hash__(self): return hash(self.thing1) ^ hash(self.thing2) ^ hash(self.thing3) In the event that (say) self.thing1 and self.thing2 have almost or exactly the same hash (with "almost" referring to bitwise differences rather than integral distance), this wipes out most or all of the entropy from both values and greatly increases the likelihood of hash collisions. Indeed, Python's own tuple type does not do this (while it does use XOR, it also does some other math to ensure the bits are as mixed up as is practical).[1] Because the correct algorithm is both nontrivial to implement and already exists in the tuple type's __hash__, I propose that the documentation be updated to recommend something like the following: def __hash__(self): return hash((self.thing1, self.thing2, self.thing3)) One possible wording: "The only required property is that objects which compare equal have the same hash value; it is advised to mix together the hash values of the components of the object that also play a part in comparison of objects by packing them into a tuple and hashing the tuple: [code example]" [1]: https://hg.python.org/cpython/file/fca5c4a63251/Objects/tupleobject.c#l348 ---------- assignee: docs@python components: Documentation messages: 278229 nosy: Kevin.Norris, docs@python priority: normal severity: normal status: open title: __hash__ documentation recommends naive XOR to combine but this is suboptimal type: performance versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28383> _______________________________________

7 9

[issue29009] Outdated part in the doc of PyUnicode_RichCompare
by Xiang Zhang Dec. 19, 2016

Dec. 19, 2016

New submission from Xiang Zhang: The sentence: "Note that Py_EQ and Py_NE comparisons can cause a UnicodeWarning in case the conversion of the arguments to Unicode fails with a UnicodeDecodeError." in the doc of PyUnicode_RichCompare is not true in 3.x. Proposed patch simply deletes it. ---------- assignee: docs@python components: Documentation files: doc-of-PyUnicode_RichCompare.patch keywords: patch messages: 283578 nosy: docs@python, haypo, xiang.zhang priority: normal severity: normal stage: patch review status: open title: Outdated part in the doc of PyUnicode_RichCompare versions: Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file45960/doc-of-PyUnicode_RichCompare.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29009> _______________________________________

4 6

[issue29010] Incorrect description about scope related with inheritance
by Brendan Donegan Dec. 19, 2016

Dec. 19, 2016

Brendan Donegan added the comment: Hi. Can you please provide a small code snippet illustrating where this diverges from the actual behaviour? ---------- nosy: +brendan-donegan _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29010> _______________________________________

1 0