[issue22577] local variable changes lost after pdb jump command
Henry Chen added the comment: PEP 558 will fix this issue, which I've verified with the proposed implementation (https://github.com/python/cpython/pull/3640/files). Perhaps this issue can be closed? -- ___ Python tracker <https://bugs.python.org/issue22577> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22577] local variable changes lost after pdb jump command
Change by Henry Chen : -- nosy: +henry ___ Python tracker <https://bugs.python.org/issue22577> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9633] pdb go stack up/down
Change by Henry Chen : -- pull_requests: +10309 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue9633> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35738] Update timeit documentation to reflect default repeat of three
Change by Henry Chen : -- keywords: +patch pull_requests: +11196 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35738> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35738] Update timeit documentation to reflect default repeat of three
Change by Henry Chen : -- keywords: +patch, patch pull_requests: +11196, 11197 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35738> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35738] Update timeit documentation to reflect default repeat of three
Change by Henry Chen : -- keywords: +patch, patch, patch pull_requests: +11196, 11197, 11198 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35738> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35738] Update timeit documentation to reflect default repeat of five
Change by Henry Chen : -- title: Update timeit documentation to reflect default repeat of three -> Update timeit documentation to reflect default repeat of five ___ Python tracker <https://bugs.python.org/issue35738> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34782] Pdb crashes when code is executed in a mapping that does not define `__contains__`
Change by Henry Chen : -- nosy: +scotchka ___ Python tracker <https://bugs.python.org/issue34782> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34782] Pdb crashes when code is executed in a mapping that does not define `__contains__`
Henry Chen added the comment: I agree that this behavior is normal, unless there is a use case for passing a partially implemented mapping object to pdb.run. However I cannot think of such a use case. -- ___ Python tracker <https://bugs.python.org/issue34782> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34782] Pdb crashes when code is executed in a mapping that does not define `__contains__`
Henry Chen added the comment: Hmm, the example works for me (Python 3.6.5): >>> import pdb >>> class FakeContainer: ... def __getitem__(self, key): ... raise KeyError(key) ... >>> pdb.run("eval('1+1',{},FakeContainer())") > (1)() (Pdb) c >>> As for exec/eval accepting an incomplete mapping, that strikes me as a less than thorough checking on the part of exec/eval, perhaps for performance reasons(?) -- ___ Python tracker <https://bugs.python.org/issue34782> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34782] Pdb crashes when code is executed in a mapping that does not define `__contains__`
Henry Chen added the comment: An attempt to clarify the issue in my own mind: def foo(): # import pdb; pdb.set_trace() exec('pass', {}, FakeContainer()) This function runs successfully. But if you uncomment the pdb line and then step thru in the pdb console, there is an Exception. I *think* the underlying principle is that code that runs normally should also run under pdb, which this example violates. However, to adhere to the principle 100% could be a very steep technical cost. Alternatively, I'd argue that the function should NOT run even without pdb, since exec requires a (complete) mapping type according to the documentation. Perhaps the thing to do is to add more stringent type checking to exec and eval? -- ___ Python tracker <https://bugs.python.org/issue34782> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35812] Don't log an exception from the main coroutine in asyncio.run()
Henry Chen added the comment: I'm having trouble reproducing this issue. The main_coro seems to disappear when an exception is raised in it, so that it does not show up in the set of tasks to cancel. I'm probably misunderstanding something basic here. Is it possible to provide a minimal example? -- nosy: +scotchka ___ Python tracker <https://bugs.python.org/issue35812> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36091] clean up async generator from types module
New submission from Henry Chen : the following script: ``` import sys, types def tr(frame, event, arg): print(frame, event, arg) return tr sys.settrace(tr) ``` gives the output: ``` call None exception (, GeneratorExit(), ) return None ``` This is due to Lib/types.py creating an async generator for the sole purpose of getting its type. I'll remove that reference after use to prevent the above message, which is probably benign but perhaps unnerving. -- components: Library (Lib) messages: 336368 nosy: scotchka priority: normal severity: normal status: open title: clean up async generator from types module type: behavior versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue36091> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36091] clean up async generator from types module
Change by Henry Chen : -- keywords: +patch pull_requests: +12021 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36091> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36091] clean up async generator from types module
Henry Chen added the comment: As it happens @cheryl.sabella has created a very useful data set of which files are impacted by open PRs: https://github.com/csabella/pulls and as of 2019-02-18, the only open PR that relates to Lib/types.py is https://github.com/python/cpython/pull/5068 on an unrelated matter -- ___ Python tracker <https://bugs.python.org/issue36091> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36114] test_multiprocessing_spawn changes the execution environment
Henry Chen added the comment: Another example of this, same bot: https://buildbot.python.org/all/#/builders/168/builds/669 -- nosy: +scotchka ___ Python tracker <https://bugs.python.org/issue36114> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36091] clean up async generator from types module
Change by Henry Chen : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue36091> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28956] return list of modes for a multimodal distribution instead of raising a StatisticsError
Henry Chen added the comment: The problem remains that the function can return a number or a list for input that is a list of numbers. This means the user will need to handle both possibilities every time, which is a heavy burden for such a simple function. SciPy's mode function does return the minimum mode when there is a tie, which as far as I can tell is an arbitrary choice. But in that context, since the input is almost always numerical, a minimum is at least well defined, which is not true for an input with a mix of types. For the general use case, the current behavior - raising an exception - in case of tie conveys the most information. -- nosy: +scotchka ___ Python tracker <https://bugs.python.org/issue28956> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28956] return list of modes for a multimodal distribution instead of raising a StatisticsError
Henry Chen added the comment: Yes, the mode function could ALWAYS return a list, but that breaks backward compatibility, as does the currently proposed change. -- ___ Python tracker <https://bugs.python.org/issue28956> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35892] Fix awkwardness of statistics.mode() for multimodal datasets
Change by Henry Chen : -- nosy: +scotchka ___ Python tracker <https://bugs.python.org/issue35892> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com