Mailman 3 February 2017 - docs

[issue29580] "Built-in Functions" not being functions
by Stefan Pochmann 20 Feb '17

20 Feb '17

New submission from Stefan Pochmann: About https://docs.python.org/3/library/functions.html: The title "Built-in Functions", the table header "Built-in Functions" and the "functions" in the URL all suggest that what's on this page are functions. But many things on that page don't appear to be functions, like "range" or "dict". They appear to be callable types instead. For example "range": >>> type(range) <class 'type'> >>> import types >>> isinstance(range, types.FunctionType) False >>> isinstance(range, types.BuiltinFunctionType) False Compare with "abs": >>> type(abs) <class 'builtin_function_or_method'> >>> isinstance(abs, types.FunctionType) False >>> isinstance(abs, types.BuiltinFunctionType) True The text between title and table talks about "functions and types", but the title/tableheader/URL disagree. Also, the table is wrong in saying that "abs()" etc are functions. Should say "abs" instead, i.e., remove the "()". Many, like "abs", aren't even allowed to be called like that, as it results in "TypeError: abs() takes exactly one argument (0 given)". ---------- assignee: docs@python components: Documentation messages: 287961 nosy: Stefan Pochmann, docs@python priority: normal severity: normal status: open title: "Built-in Functions" not being functions type: enhancement versions: 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/issue29580> _______________________________________

5 5

[issue28886] Move deprecated abc module decorators to separate section in docs
by Harshul 19 Feb '17

19 Feb '17

Changes by Harshul <harshulrobo(a)gmail.com>: ---------- keywords: +patch Added file: http://bugs.python.org/file46651/bpo-28886_3.7.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28886> _______________________________________

1 0

[issue28886] Move deprecated abc module decorators to separate section in docs
by Harshul 19 Feb '17

19 Feb '17

Changes by Harshul <harshulrobo(a)gmail.com>: ---------- pull_requests: +141 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28886> _______________________________________

1 0

[issue29599] Github organization link is secret and not accessible from core-dev guide
by Sanyam Khurana 19 Feb '17

19 Feb '17

New submission from Sanyam Khurana: On visiting link: https://docs.python.org/devguide/coredev.html#github The first sentence is "You will be added to the Python core team on GitHub." The ``Python core team`` refers to a link to Github which is not accessible to anyone except for those who are part of the organization. I'd like to suggest to either remove the link from the documentation or make the team visible to public. ---------- assignee: docs@python components: Documentation messages: 288131 nosy: CuriousLearner, docs@python, ncoghlan priority: normal severity: normal status: open title: Github organization link is secret and not accessible from core-dev guide type: behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29599> _______________________________________

2 2

[issue10701] Error pickling objects with mutating __getstate__
by Serhiy Storchaka 19 Feb '17

19 Feb '17

Changes by Serhiy Storchaka <storchaka+cpython(a)gmail.com>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python status: open -> pending type: behavior -> enhancement versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10701> _______________________________________

1 0

[issue23890] assertRaises increases reference counter
by Nick Coghlan 19 Feb '17

19 Feb '17

Nick Coghlan added the comment: I've been looking into this further, and a reproducer that's independent of assertRaises() is to just bind the function to a local variable name in an outer function: def outer(): callable_obj = f try: callable_obj() except Exception as exc: return exc That should make it easier to test a basic recursive "clear_all_frames" operation like: def clear_all_frames(exc): cause = exc.__cause__ if cause is not None: clear_all_frames(cause) context = exc.__context__ if context is not None: clear_all_frames(context) traceback.clear_frames(exc.__traceback__) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23890> _______________________________________

1 0

[issue11924] Pickle and copyreg modules doesn't document the interface
by Jesús Cea Avión 19 Feb '17

19 Feb '17

New submission from Jesús Cea Avión <jcea(a)jcea.es>: Python 3.2 here. "copyreg" module documentation says "See the pickle module for more details on the interface expected of function and constructor.", but I don't see any useful "copyreg" reference in pickle documentation. Some examples would be useful here, too. ---------- assignee: docs@python messages: 134416 nosy: docs@python, jcea priority: normal severity: normal status: open title: Pickle and copyreg modules doesn't document the interface versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11924> _______________________________________

5 6

[issue29597] __new__ / __init__ calls during unpickling not documented correctly
by Max 19 Feb '17

19 Feb '17

New submission from Max: According to the [docs](https://docs.python.org/3/library/pickle.html#pickling-class-instance…: > Note: At unpickling time, some methods like `__getattr__()`, `__getattribute__()`, or `__setattr__()` may be called upon the instance. In case those methods rely on some internal invariant being true, the type should implement `__getnewargs__()` or `__getnewargs_ex__()` to establish such an invariant; otherwise, neither `__new__()` nor `__init__()` will be called. It seems, however, that this note is incorrect. First, `__new__` is called even if `__getnewargs__` isn't implemented. Second, `__init__` is not called even if it is (while the note didn't say that `__init__` would be called when `__getnewargs__` is defined, the wording does seem to imply it). class A: def __new__(cls, *args): print('__new__ called with', args) return object.__new__(cls) def __init__(self, *args): print('__init__ called with', args) self.args = args def __getnewargs__(self): print('called') return () a = A(1) s = pickle.dumps(a) a = pickle.loads(s) # __new__ called, not __init__ delattr(A, '__getnewargs__') a = A(1) s = pickle.dumps(a) a = pickle.loads(s) # __new__ called, not __init__ ---------- assignee: docs@python components: Documentation messages: 288088 nosy: docs@python, max priority: normal severity: normal status: open title: __new__ / __init__ calls during unpickling not documented correctly versions: Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29597> _______________________________________

2 1

[issue23890] assertRaises increases reference counter
by Nick Coghlan 18 Feb '17

18 Feb '17

Nick Coghlan added the comment: As Robert noted, this is a straight up error, where the clear_frames() call and deleting the exception traceback from the saved object aren't enough to drop all references to `callable_obj`. The trick is that the cleanup code isn't accounting for __cause__ and __context__: it's only clearing and dropping the traceback for the topmost exception in the chain. In Vjacheslav's example, there are *two* tracebacks to worry about: both the top level one (which is getting cleaned up) and the inner one from exc.__context__ which isn't being touched. We could likely use a "traceback.clear_all_frames()" helper that walks an exception tree clearing *all* the traceback frames, both on the original exception, and on all the __cause__ and __context__ attributes. (We can't just clear __cause__ and __context__, since those can be accessed and tested when using the context manager form and the `exception` attribute) ---------- assignee: docs@python -> components: -Documentation nosy: +ncoghlan type: enhancement -> behavior versions: +Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23890> _______________________________________

1 0

[issue23890] assertRaises increases reference counter
by Subhendu Ghosh 18 Feb '17

18 Feb '17

Changes by Subhendu Ghosh <subho.prp(a)gmail.com>: ---------- nosy: +subho _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23890> _______________________________________

1 0