[issue25532] infinite loop when running inspect.unwrap over unittest.mock.call

Nick Coghlan added the comment: An alternative approach would be to change inspect.unwrap() to use getattr_static() rather than the usual getattr(). The downside of that would be potentially breaking true object proxies, like the 3rd party wrapt module and weakref.proxy. However, what if insp

[issue27487] -m switch regression in Python 3.5.2 (under rare circumstances)

Roundup Robot added the comment: New changeset 43ae044eaccc by Martin Panter in branch '3.5': Issue #27487: Warn if submodule already imported before runpy execution https://hg.python.org/cpython/rev/43ae044eaccc New changeset fccd733aa78b by Martin Panter in branch 'default': Issue #27487: Merg

[issue27820] Possible bug in smtplib when initial_response_ok=False

Changes by R. David Murray : -- components: +email nosy: +barry, r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue27487] -m switch regression in Python 3.5.2 (under rare circumstances)

Nick Coghlan added the comment: Thanks Martin! Closing this as fixed, since the new warning should help nudge folks towards staying within the supported subset of the import system behaviour when it comes to interactions between package.__init__ and package.__main__. -- resolution: -

[issue27782] Multi-phase extension module initialization, inconsistent exceptions and conflicts between code and PEP

Changes by Nick Coghlan : -- assignee: -> ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue27780] memory leaks in pgen build step abort build with address sanitizer enabled

Xiang Zhang added the comment: Valgrind can also complain: valgrind --leak-check=yes --suppressions=Misc/valgrind-python.supp Parser/pgen ./Grammar/Grammar Include/graminit.h Python/graminit.c ==6836== Memcheck, a memory error detector ==6836== Copyright (C) 2002-2015, and GNU GPL'd, by Julian

[issue27782] Multi-phase extension module initialization, inconsistent exceptions and conflicts between code and PEP

Nick Coghlan added the comment: The patch looks good to me, and the relevant contributor licensing is in place, so I'll be applying this shortly :) -- stage: -> commit review ___ Python tracker __

[issue25532] infinite loop when running inspect.unwrap over unittest.mock.call

Hugo Geoffroy added the comment: You are right, the fix would be better suited in `unwrap`. But, still, shouldn't any `__getattr__` implementation take care of not returning, for the `__wrapped__` attribute, a dynamic wrapper that provides the same attribute ? `__wrapped__` is commonly resolv

[issue16764] Make zlib accept keyword-arguments

Martin Panter added the comment: All the interesting keyword arguments seem to work now (checking against my notes from earlier). Is there anything else anyone wants to do, or can we close this now? -- stage: commit review -> resolved ___ Python tra

[issue25532] infinite loop when running inspect.unwrap over unittest.mock.call

Nick Coghlan added the comment: The infinite loop reported here is an inspect.signature bug - it's supposed to prevent infinite loops, but we didn't account for cases where "obj.__wrapped__" implicitly generates a fresh object every time. unittest.mock.Mock is the only case of that in the stan

<    1   2