Change by Francisco Demartino :
--
keywords: +patch
pull_requests: +24904
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26306
___
Python tracker
<https://bugs.python.org/issu
Francisco Demartino added the comment:
Looks like Roger Dahl also noted this on https://bugs.python.org/issue39765:
> Second, set_signal_handler()[sic] silently and implicitly removes
> corresponding handlers set with signal.signal(). [...] I think this should
> be documente
New submission from Francisco Demartino :
Hello,
It looks like when asyncio sets up a signal handler, it forgets about the
previous one (if any).
Here's a patch (was about to create a PR but the default text brought me to
bugs.python.org)
https://github.com/franciscod/cpython/c
Francisco Demartino added the comment:
Serhiy, Chris, thank you for your additional comments. They surely helped me
understand why my solution to this "problem?" isn't that good (also I slept on
it a bit and maybe that helped).
I still ponder for a way to get autoc
Francisco Demartino added the comment:
> There is no way to safely inspect any Python object without triggering some
> dunder functions like __getattr__, __getattribute__ or __dir__.
But somehow inspect.getattr_static can do it?
> Your change is not backwards compatible and m
Francisco Demartino added the comment:
I've updated that branch and made a pull request
(https://github.com/python/cpython/pull/248)
I think this is a good compromise: inspect.getattr_static can tell if it's a
property, and in that case we don't call getattr on it to prevent
Changes by Francisco Demartino :
--
pull_requests: +213
status: pending -> open
___
Python tracker
<http://bugs.python.org/issue29630>
___
___
Python-bugs-lis
Francisco Demartino added the comment:
This branch (working on the PR) fixes it:
https://github.com/franciscod/cpython/tree/bpo-29630
--
___
Python tracker
<http://bugs.python.org/issue29
New submission from Francisco Demartino:
On the REPL, when autocompleting with the TAB key, getattr is called,
potentially triggering code execution.
This took me by surprise. Until you press RETURN, it should be pretty safe to
go around autocompleting with certainty that you won't ru
