[issue11105] Compiling recursive Python ASTs crash the interpreter
Change by ppperry : -- nosy: -ppperry ___ Python tracker <https://bugs.python.org/issue11105> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42849] pool worker can't be terminated
ppperry added the comment: duplicate of issue22393? -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue42849> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30953] Fatal python error when jumping into except clause
Change by ppperry : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue30953> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33065] IDLE debugger: failure stepping through module loading
Change by ppperry : -- nosy: -ppperry ___ Python tracker <https://bugs.python.org/issue33065> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40241] [C API] Make PyGC_Head structure opaque, or even move it to the internal C API
Change by ppperry : -- title: [C API] Make PyGC_Head structure opaque, or even more it to the internal C API -> [C API] Make PyGC_Head structure opaque, or even move it to the internal C API ___ Python tracker <https://bugs.python.org/issue40241> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39665] Cryptic error message when creating types that don't include themselves in their MRO
Change by ppperry : -- components: -Build versions: +Python 3.9 ___ Python tracker <https://bugs.python.org/issue39665> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39382] abstract_issubclass() doesn't take bases tuple item ref
ppperry added the comment: I posted a test on the PR -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue39382> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39665] Cryptic error message when creating types that don't include themselves in their MRO
New submission from ppperry : I was trying to create a class that didn't have any references to itself to test issue39382 and ran the following code: class Meta(type): def mro(cls): return type.mro(cls)[1:] class X(metaclass=Meta): pass This produced an extremely cryptic error message: Traceback (most recent call last): File "", line 1, in class X(metaclass=Meta): TypeError: super(type, obj): obj must be an instance or subtype of type While what I am trying to do may well not be supported, the error message referencing the `super` function, which I didn't use, is not helpful. -- components: Build, Interpreter Core messages: 362152 nosy: ppperry priority: normal severity: normal status: open title: Cryptic error message when creating types that don't include themselves in their MRO type: behavior versions: Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue39665> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39585] Delete a pending item in _warning.c
ppperry added the comment: What if a warning has a metaclass with a custom __getattribute__ method? -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue39585> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32615] Inconsistent behavior if globals is a dict subclass
ppperry added the comment: I was not attempting to run untrusted Python code when I filed this bug report. -- ___ Python tracker <https://bugs.python.org/issue32615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39344] ImportError: DLL load failed while importing _ssl: The specified module could not be found."
Change by ppperry : -- title: Getting error while importing ssl " import _ssl # if we can't import it, let the error propagate ImportError: DLL load failed while importing _ssl: The specified module could not be found." -> ImportError: DLL load failed while importing _ssl: The specified module could not be found." ___ Python tracker <https://bugs.python.org/issue39344> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11105] Compiling evil ast crashes interpreter
ppperry added the comment: What about indirect cycles like below: >>> e = ast.UnaryOp(op=ast.Not(), lineno=0, col_offset=0) >>> f = ast.UnaryOp(op=ast.Not(), lineno=0, col_offset=0) >>> e.operand = f >>> f.operand = e >>> compile(ast.Expression(e), "", "eval") (I tested, this also crashes) -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue11105> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36220] LOAD_NAME and LOAD_GLOBAL, STORE_GLOBAL handle dict subclasses for globals() differently
ppperry added the comment: Duplicate of issue32615 -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue36220> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters
Change by ppperry : -- type: compile error -> behavior ___ Python tracker <https://bugs.python.org/issue38262> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38229] ClientConnectionError exception doesn't serialize propertly
ppperry added the comment: This seems more likely to be a bug in aiohttp than in python. -- nosy: +ppperry type: crash -> behavior ___ Python tracker <https://bugs.python.org/issue38229> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38084] multiprocessing cannot recover from crashed worker
ppperry added the comment: Is this not a duplicate of issue22393? -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue38084> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37863] Speed up hash(fractions.Fraction)
Change by ppperry : -- title: Speed hash(fractions.Fraction) -> Speed up hash(fractions.Fraction) ___ Python tracker <https://bugs.python.org/issue37863> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37830] continue in finally with return in try results with segfault
ppperry added the comment: Unfortunately, there's a similar bug for `break` in a finally inside two nested loops, so just re-banning `continue` won't fix the crash. The code below segfaults: ``` def simple(): for number in range(2): for number in range(2): try: return number finally: break simple() ``` -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue37830> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35753] Importing call from unittest.mock directly causes ValueError
Change by ppperry : -- nosy: -ppperry ___ Python tracker <https://bugs.python.org/issue35753> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35753] Importing call from unittest.mock directly causes ValueError
ppperry added the comment: Indeed, you are right that this should be reopened. -- ___ Python tracker <https://bugs.python.org/issue35753> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1402289] Allow mappings as globals (was: Fix dictionary subclass ...)
ppperry added the comment: See also issue32615 -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue1402289> ___ ___ 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__`
ppperry added the comment: You have to step into the eval for the error to be raised. -- ___ 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
[issue35753] Importing call from unittest.mock directly causes ValueError
ppperry added the comment: Sorry, looks like I was wrong about it being a duplicate. The actual bug appears to be "doctest can't run on a module that contains un-unwrappable objects", which there probably is an issue for but I don't know what it is. -- ___ Python tracker <https://bugs.python.org/issue35753> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35753] Importing call from unittest.mock directly causes ValueError
ppperry added the comment: According to the error message, this is a duplicate of https://bugs.python.org/issue25532 -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue35753> ___ ___ 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__`
ppperry added the comment:
The thing is, though, that the same error occurs if a larger code being
debugged calls `exec` or `eval` with such a mapping
(`pdb.run("eval('1+1',{},FakeContainer())" also crashes with the same error),
and the test suite contains code that evals other code in an incomplete mapping
(test_var_annot_custom_maps in test_grammar)
--
___
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
[issue19675] Pool dies with excessive workers, but does not cleanup
Change by ppperry : -- nosy: -ppperry ___ Python tracker <https://bugs.python.org/issue19675> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35098] Deleting __new__ does not restore previous behavior
ppperry added the comment: This is a duplicate of issue25731 -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue35098> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33065] IDLE debugger: failure stepping through module loading
ppperry added the comment: Line 59 isn't actually executed; the error comes from the trace event that gets fired before line 59, which is the first `line` event in the frame containing the uninitialized _ModuleLock. -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue33065> ___ ___ 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 ppperry : -- type: -> behavior ___ 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__`
New submission from ppperry :
class FakeContainer:
def __getitem__(self, key)
raise KeyError(key)
pdb.run("pass",{},FakeContainer())
Traceback (most recent call last):
File "", line 1, in
pdb.run("pass",{},FakeContainer())
File "C:\Program Files\Python37\lib\pdb.py", line 1590, in run
Pdb().run(statement, globals, locals)
File "C:\Program Files\Python37\lib\bdb.py", line 585, in run
exec(cmd, globals, locals)
File "", line 1, in
File "", line 1, in
File "C:\Program Files\Python37\lib\bdb.py", line 88, in trace_dispatch
return self.dispatch_line(frame)
File "C:\Program Files\Python37\lib\bdb.py", line 112, in dispatch_line
self.user_line(frame)
File "C:\Program Files\Python37\lib\pdb.py", line 261, in user_line
self.interaction(frame, None)
File "C:\Program Files\Python37\lib\pdb.py", line 351, in interaction
self.print_stack_entry(self.stack[self.curindex])
File "C:\Program Files\Python37\lib\pdb.py", line 1453, in print_stack_entry
self.format_stack_entry(frame_lineno, prompt_prefix))
File "C:\Program Files\Python37\lib\bdb.py", line 549, in format_stack_entry
if '__args__' in frame.f_locals:
File "", line 3, in __getitem__
raise KeyError
KeyError: 0
Obviously, the debugger shouldn't crash in this case (running code outside of
the debugger works as expected, producing a NameError on variable reads and a
TypeError whenever a name is assigned).
--
components: Library (Lib)
messages: 326186
nosy: ppperry
priority: normal
severity: normal
status: open
title: Pdb crashes when code is executed in a mapping that does not define
`__contains__`
versions: Python 3.7, Python 3.8
___
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
[issue34779] IDLE internals show up in tracebacks when returning objects that cannot be `repr`ed
New submission from ppperry : >>> class NoRepr: def __repr__(self): raise ValueError >>> NoRepr() Traceback (most recent call last): File "", line 1, in NoRepr() File "C:\Program Files\Python37\lib\idlelib\rpc.py", line 617, in displayhook text = repr(value) File "", line 3, in __repr__ raise ValueError ValueError What should happen in this case isn't exactly clear, but the current traceback is wrong in multiple ways. -- assignee: terry.reedy components: IDLE messages: 326172 nosy: ppperry, terry.reedy priority: normal severity: normal status: open title: IDLE internals show up in tracebacks when returning objects that cannot be `repr`ed versions: Python 3.6, Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue34779> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33065] IDLE debugger crashes when `repr` raises an exception
Change by ppperry : -- title: IDLE debugger: problem importing user created module -> IDLE debugger crashes when `repr` raises an exception ___ Python tracker <https://bugs.python.org/issue33065> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33065] IDLE debugger: problem importing user created module
Change by ppperry : -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue33065> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34609] Importing certain modules while debugging raises an exception
ppperry added the comment: The Pdb bug and the IDLE bug are unrelated to each other: Pdb fails because it is attempting to import the readline module every time its `trace_dispatch` is called, and the import implementation is not reentrant in that way. IDLE is crashing because the uninitialized _ModuleLock instance raised an error when `repr` is called, and the IDLE debugger lacks code to catch that exception. -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue34609> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14905] zipimport needs to support namespace packages when no 'directory' entry exists
Change by ppperry : -- title: zipimport.c needs to support namespace packages when no 'directory' entry exists -> zipimport needs to support namespace packages when no 'directory' entry exists ___ Python tracker <https://bugs.python.org/issue14905> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on non-instaniable objects
ppperry added the comment: Also happens for some objects in the `_tkinter` module: >>> _tkinter.TkttType.__new__(_tkinter.TkttType) Traceback (most recent call last): File "", line 1, in _tkinter.TkttType.__new__(_tkinter.TkttType) TypeError: object.__new__(_tkinter.tktimertoken) is not safe, use _tkinter.tktimertoken.__new__() >>> _tkinter.Tcl_Obj.__new__(_tkinter.Tcl_Obj) Traceback (most recent call last): File "", line 1, in _tkinter.Tcl_Obj.__new__(_tkinter.Tcl_Obj) TypeError: object.__new__(_tkinter.Tcl_Obj) is not safe, use _tkinter.Tcl_Obj.__new__() >>> _tkinter.TkappType.__new__(_tkinter.TkappType) Traceback (most recent call last): File "", line 1, in _tkinter.TkappType.__new__(_tkinter.TkappType) TypeError: object.__new__(_tkinter.tkapp) is not safe, use _tkinter.tkapp.__new__() -- ___ Python tracker <https://bugs.python.org/issue34284> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34467] No mechanism to abort created coroutine or suppress not-awaited warning
ppperry added the comment: Does calling `coro.close()` not work? -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue34467> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1529353] Squeezer - squeeze large output in IDLE
Change by ppperry : -- title: Squeezer - squeeze large output in the interpreter -> Squeezer - squeeze large output in IDLE ___ Python tracker <https://bugs.python.org/issue1529353> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19050] [Windows] fflush called on pointer to potentially closed file
Change by ppperry : -- title: [Python 2, Windows] fflush called on pointer to potentially closed file -> [Windows] fflush called on pointer to potentially closed file ___ Python tracker <https://bugs.python.org/issue19050> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5322] object.__new__ argument calling autodetection faulty
Change by ppperry : -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue5322> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34362] User-created types with wrong __new__ can be instantiated
ppperry added the comment: issue5322, despite its confusing title, mentions this exact bug in one of the comments below. It looks like there is one bug in the logic for assigning `__new__`, which causes `__new__` and `tp_new` to point to different things, confusing the error-handling logic in `object.__new__` as well as causing creation of a type by calling it to work in cases where direct calls to __new__ fail. There's no one bug report about that, however issue5322, issue25731 and some cases of issue34284 are all symptoms of the same root issue. -- ___ Python tracker <https://bugs.python.org/issue34362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5322] object.__new__ argument calling autodetection faulty
Change by ppperry : -- title: Python 2.6 object.__new__ argument calling autodetection faulty -> object.__new__ argument calling autodetection faulty ___ Python tracker <https://bugs.python.org/issue5322> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34362] User-created types with wrong __new__ can be instantiated
ppperry added the comment: Whoops, realized this is a duplicate of issue5322. -- ___ Python tracker <https://bugs.python.org/issue34362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34362] User-created types with wrong __new__ can be instantiated
New submission from ppperry : If you have a class that defines __new__ to the __new__ of another builtin type that it isn't a subclass of: >>> class X: ...__new__ = tuple.__new__ Instantiating this class should produce an error because `tuple.__new__` can't handle non-tuples, but instead it succeeds: >>> X() <__main__.X object at 0x032C3F98> (related: issue34284) -- components: Interpreter Core messages: 323297 nosy: Vadim Pushtaev, ncoghlan, ppperry, serhiy.storchaka priority: normal severity: normal status: open title: User-created types with wrong __new__ can be instantiated type: behavior versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue34362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33954] float.__format__('n') fails with _PyUnicode_CheckConsistency assertion error for locales with non-ascii thousands separator
Change by ppperry :
--
title: float.__format__('n') fails with _PyUnicode_CheckConsistency assertion
error -> float.__format__('n') fails with _PyUnicode_CheckConsistency assertion
error for locales with non-ascii thousands separator
___
Python tracker
<https://bugs.python.org/issue33954>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on non-instaniable objects
ppperry added the comment: The problem doesn't just happen with `sys.flags`, though. It happens with all types that can't be created directly by python. Ex: frame objects, generators, cells, etc. The bug is that in types whose c-level tp_new is null, the python-level __new__ is inherited from the superclass (and since object defines a `__new__`, such a function always exists), instead of being defined to always raise an error, like calling the type directly does. -- ___ Python tracker <https://bugs.python.org/issue34284> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34331] Incorrectly pluralized abstract class error message
ppperry added the comment: No, this isn't causing me an actual problem, however the related issue34127 was accepted, and this one should be no harder to fix. -- ___ Python tracker <https://bugs.python.org/issue34331> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34331] Incorrectly pluralized abstract class error message
New submission from ppperry : >>> class abstract(abc.ABC): ... @abc.abstractmethod ... def meth(): ... pass ... >>> x() Traceback (most recent call last): File "", line 1, in TypeError: Can't instantiate abstract class x with abstract methods meth Error should be "Can't instantiate abstract class abstract with abstract method meth" in the singular, because there is only one abstract method. -- components: Interpreter Core, Library (Lib) messages: 323059 nosy: Anjali Bansal, ppperry, rhettinger, serhiy.storchaka, terry.reedy, xtreak priority: normal severity: normal status: open title: Incorrectly pluralized abstract class error message versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue34331> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34327] test_subprocess fails
Change by ppperry : -- components: +Tests -Build title: CPython make test crash -> test_subprocess fails type: crash -> behavior ___ Python tracker <https://bugs.python.org/issue34327> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX
Change by ppperry : -- title: setup.py: _ctypes won't getbuilt when system ffi is only in $PREFIX -> setup.py: _ctypes won't get built when system ffi is only in $PREFIX ___ Python tracker <https://bugs.python.org/issue31710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34279] RFC: issue a warning in regrtest when no tests have been executed?
Change by ppperry : -- title: RFC: issue a warning in regrtest when no test have been executed? -> RFC: issue a warning in regrtest when no tests have been executed? ___ Python tracker <https://bugs.python.org/issue34279> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29502] Should PyObject_Call() call the profiler on C functions, use C_TRACE() macro?
ppperry added the comment: issue30990 is related -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue29502> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on non-instaniable objects
ppperry added the comment: Thus, I think the bug is that "type(sys.flags).__new__" is an alias for "tuple.__new__" and is not in the code for __new__ calls that your PR touches. -- ___ Python tracker <https://bugs.python.org/issue34284> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on non-instaniable objects
ppperry added the comment:
The error I'm expecting here is "cannot create sys.flags objects". Anything
else violates the fact that type(*args) is sugar for:
result = type.__new__(type, *args)
if isinstance(result, type):
result.__init__(*args)
("type" in the above snippet is a variable name, not the actual builtin "type")
--
title: Nonsensical exception message when calling `__new__` on some sys objects
-> Nonsensical exception message when calling `__new__` on non-instaniable
objects
___
Python tracker
<https://bugs.python.org/issue34284>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on non-instaniable object
ppperry added the comment: Same thing happens for other objects, like `type(sys._getframe(0)).__new__(type(sys._getframe_))`, and presumably any object that one cannot instantiate by calling -- title: Nonsensical exception message when calling `__new__` on some sys objects -> Nonsensical exception message when calling `__new__` on non-instaniable object ___ Python tracker <https://bugs.python.org/issue34284> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on some sys objects
ppperry added the comment: Your PR is not an improvement: 1. In this case, this will produce the error "tuple.__new__(sys.flags) is not safe". But I didn't call "tuple.__new__", I called sys.flags.__new__, and type(X).__new__(type(X)) should always be safe 2. The change in error message for namedtuples (A) isn't related and (B) isn't correct. `tuple.__new__(NamedTuple)` works, and produces a namedtuple object, so tuple.__new__ is what the error should point to. -- ___ Python tracker <https://bugs.python.org/issue34284> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34284] Nonsensical exception message when calling `__new__` on some sys objects
New submission from ppperry : > type(sys.flags).__new__(type(sys.flags)) Traceback (most recent call last): File "", line 1, in type(sys.flags).__new__(type(sys.flags)) TypeError: tuple.__new__(sys.flags) is not safe, use sys.flags.__new__() Ignoring the confusion caused by both the type and the instance being called "sys.flags", this error doesn't make sense. I am using "sys.flags" (the type).__new__, so why is it complaining? "type(sys.flags)()" produces the standard "non-instantiable type" error. The same behavior also happens for "sys.version_info", but strangely not for any of the other sys constants. -- components: Interpreter Core, Library (Lib) messages: 322688 nosy: ppperry priority: normal severity: normal status: open title: Nonsensical exception message when calling `__new__` on some sys objects type: behavior versions: Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue34284> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34266] Bad behavior with "restart \" or "restart "" in pdb
ppperry added the comment: Both of those work and don't produce an error -- ___ Python tracker <https://bugs.python.org/issue34266> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34266] Bad behavior with "restart \" or "restart "" in pdb
ppperry added the comment: `restart "` also crashes with the same tb -- title: Bad behavior with "restart \" in pdb -> Bad behavior with "restart \" or "restart "" in pdb ___ Python tracker <https://bugs.python.org/issue34266> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34266] Bad behavior with "restart \" in pdb
ppperry added the comment: Just to be clear, even though the traceback is python 3.6, the same bug occurs in 3.7 with an identical traceback except for some changes in line number -- ___ Python tracker <https://bugs.python.org/issue34266> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34266] Bad behavior with "restart \" in pdb
New submission from ppperry :
(Pdb) restart \
Traceback (most recent call last):
File "C:\Program Files\Python36\lib\pdb.py", line 1667, in main
pdb._runscript(mainpyfile)
File "C:\Program Files\Python36\lib\pdb.py", line 1548, in _runscript
self.run(statement)
File "C:\Program Files\Python36\lib\bdb.py", line 431, in run
exec(cmd, globals, locals)
File "", line 1, in
File "C:\Program Files\Python36\lib\bdb.py", line 48, in trace_dispatch
return self.dispatch_line(frame)
File "C:\Program Files\Python36\lib\bdb.py", line 66, in dispatch_line
self.user_line(frame)
File "C:\Program Files\Python36\lib\pdb.py", line 261, in user_line
self.interaction(frame, None)
File "C:\Program Files\Python36\lib\pdb.py", line 352, in interaction
self._cmdloop()
File "C:\Program Files\Python36\lib\pdb.py", line 321, in _cmdloop
self.cmdloop()
File "C:\Program Files\Python36\lib\cmd.py", line 138, in cmdloop
stop = self.onecmd(line)
File "C:\Program Files\Python36\lib\pdb.py", line 418, in onecmd
return cmd.Cmd.onecmd(self, line)
File "C:\Program Files\Python36\lib\cmd.py", line 217, in onecmd
return func(arg)
File "C:\Program Files\Python36\lib\pdb.py", line 1025, in do_run
sys.argv = shlex.split(arg)
File "C:\Program Files\Python36\lib\shlex.py", line 305, in split
return list(lex)
File "C:\Program Files\Python36\lib\shlex.py", line 295, in __next__
token = self.get_token()
File "C:\Program Files\Python36\lib\shlex.py", line 105, in get_token
raw = self.read_token()
File "C:\Program Files\Python36\lib\shlex.py", line 206, in read_token
raise ValueError("No escaped character")
--
components: Library (Lib)
messages: 322595
nosy: ppperry
priority: normal
severity: normal
status: open
title: Bad behavior with "restart \" in pdb
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issue34266>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34193] Fix pluralization in TypeError messages in getargs.c
Change by ppperry : -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue34193> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34188] Allow dict choices to "transform" values in argpagse
Change by ppperry : -- title: Use dicts to "transform" argparse arguments to values -> Allow dict choices to "transform" values in argpagse ___ Python tracker <https://bugs.python.org/issue34188> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21600] mock.patch.stopall doesn't work with patch.dict
Change by ppperry : -- title: mock.patch.stopall doesn't work with patch.dict to sys.modules -> mock.patch.stopall doesn't work with patch.dict ___ Python tracker <https://bugs.python.org/issue21600> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34127] Gramatically incorrect error message for some calls with wrong number of arguments
ppperry added the comment: Another test case: >> classmethod() Traceback (most recent call last): File "", line 2, in check TypeError: classmethod expected 1 arguments, got 0 -- title: Gramatically incorrect error message for some descriptor calls with wrong number of arguments -> Gramatically incorrect error message for some calls with wrong number of arguments ___ Python tracker <https://bugs.python.org/issue34127> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34128] Release GIL periodically in _pickle module
Change by ppperry : -- nosy: -ppperry ___ Python tracker <https://bugs.python.org/issue34128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34128] Release GIL periodically in _pickle module
Change by ppperry : -- components: +Library (Lib) title: Do not block threads when pickle/unpickle -> Release GIL periodically in _pickle module ___ Python tracker <https://bugs.python.org/issue34128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34126] Profiling certain invalid calls crashes Python
Change by ppperry : -- title: Profiling certain invalid calls crash Python -> Profiling certain invalid calls crashes Python ___ Python tracker <https://bugs.python.org/issue34126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34128] Do not block threads when pickle/unpickle
ppperry added the comment: um, something doesn't make sense about this. the python implementation of pickle never released the GIL (it can't, by definition -- it's written in python). The C implementation releasing the GIL wouldn't make sense, as the pickle api involves calls into python everywhere (for example, `__reduce__`) -- nosy: +ppperry ___ Python tracker <https://bugs.python.org/issue34128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34126] Profiling certain invalid calls crash Python
Change by ppperry : -- type: -> crash ___ Python tracker <https://bugs.python.org/issue34126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34127] Gramatically incorrect error message for some descriptor calls with wrong number of arguments
New submission from ppperry :
`{}.get()`
Traceback (most recent call last):
File "", line 1, in
TypeError: get expected at least 1 arguments, got 0
Shouldn't that be "TypeError: get expected at least 1 argument, got 0" instead?
--
components: Interpreter Core
messages: 321752
nosy: ppperry
priority: normal
severity: normal
status: open
title: Gramatically incorrect error message for some descriptor calls with
wrong number of arguments
versions: Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue34127>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33120] infinite loop in inspect.unwrap(unittest.mock.call)
Change by ppperry : -- type: crash -> behavior ___ Python tracker <https://bugs.python.org/issue33120> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29199] test_regrtest fails if PCBuild directory doesn't exist
ppperry added the comment: To be precise, fixed as part of issue33352 -- ___ Python tracker <https://bugs.python.org/issue29199> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29199] test_regrtest fails if PCBuild directory doesn't exist
ppperry added the comment: This issue seems to have been fixed in 3.7 -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue29199> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33460] "..." is used to confusingly indicate many different things in chapter 3
Change by ppperry : -- title: ... used to indicate many different things in chapter 3, some are confusing -> "..." is used to confusingly indicate many different things in chapter 3 ___ Python tracker <https://bugs.python.org/issue33460> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33120] infinite loop in inspect.unwrap(unittest.mock.call)
ppperry <maprea...@olum.org> added the comment: This is a dupe of https://bugs.python.org/issue25532 -- nosy: +ppperry ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33120> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33093] Fatal error on SSL transport
Change by ppperry <maprea...@olum.org>: -- type: -> behavior ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33093> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30953] Fatal python error when jumping into except clause
ppperry <maprea...@olum.org> added the comment: ... with a bad error message, because there are no finally blocks in the code -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue30953> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32926] Add public TestCase method/property to get result of current test
Change by ppperry <maprea...@olum.org>: -- versions: +Python 3.8 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32926> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32926] Add public TestCase method/property to get result of current test
Change by ppperry <maprea...@olum.org>: -- components: +Library (Lib) ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32926> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32911] Doc strings no longer stored in body of AST
Change by ppperry <maprea...@olum.org>: -- title: Doc strings omitted from AST -> Doc strings no longer stored in body of AST ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32911> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32900] Teach pdb to step through asyncio et al.
Change by ppperry <maprea...@olum.org>: -- versions: +Python 3.8 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32900> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32900] Teach pdb to step through asyncio et al.
ppperry <maprea...@olum.org> added the comment: Just to be clear, I'm not opposing having the default value for `skip` be something other than the empty set, but it should be overridable, and the default should include some other things this patch omits, like `importlib._bootstrap(_external)?` -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32900> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32900] Teach pdb to step through asyncio et al.
ppperry <maprea...@olum.org> added the comment:
This feature already exists and doesn't need to be reimplemented; use
`pdb.Pdb(skip={"trio", "contextlib", ...}).run(...)`, and in any case should be
disableable. I don't use asyncio, but happen to have a habit of running pdb
through the standard library for no reason and don't want to have that option
taken away.
--
nosy: +ppperry
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32900>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32895] Make general function sum() use Numpy's sum when obviously possible
Change by ppperry <maprea...@olum.org>: -- type: performance -> enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32895> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32895] Make general function sum() use Numpy's sum when obviously possible
Change by ppperry <maprea...@olum.org>: -- type: enhancement -> performance ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32895> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32895] Make general function sum() use Numpy's sum when obviously possible
Change by ppperry <maprea...@olum.org>: -- components: +Library (Lib) -2to3 (2.x to 3.x conversion tool) ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32895> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8525] Display exceptions' subclasses in help()
Change by ppperry <maprea...@olum.org>: -- title: Display exception's subclasses in help() -> Display exceptions' subclasses in help() ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue8525> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28685] Optimizing list.sort() by performing safety checks in advance
ppperry <maprea...@olum.org> added the comment: ... and I'm still trying to come up with even more pathological mutating cases -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue28685> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14010] deeply nested itertools objects segfault
Change by ppperry <maprea...@olum.org>: -- title: deeply nested filter segfaults -> deeply nested itertools objects segfault ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue14010> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17852] Built-in module _io can lose data from buffered files in reference cycles
Change by ppperry <maprea...@olum.org>: -- title: Built-in module _io can lose data from buffered files at exit -> Built-in module _io can lose data from buffered files in reference cycles ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue17852> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32621] Problem of consistency in collection.abc documentation
Change by ppperry <maprea...@olum.org>: -- title: Problem of consistence in collection.abc documentation -> Problem of consistency in collection.abc documentation ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32621> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32615] Inconsistent behavior if globals is a dict subclass
ppperry <maprea...@olum.org> added the comment: Uh, I'm not undertsanding the relevance of whether the code is run at module-level or not. It can't possibly be a feature that * some code * uses the overrides and *other code* doesn't. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32615] Inconsistent behavior if globals is a dict subclass
Change by ppperry <maprea...@olum.org>: -- type: -> behavior ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32615] Inconsistent behavior if globals is a dict subclass
New submission from ppperry <maprea...@olum.org>:
Take the following code:
import builtins
class K(dict):
def __getitem__(self, k):
if k not in builtins.__dict__:
print("get %s" % k)
return dict.__getitem__(self, k)
def __setitem__(self, k, v):
print("set %s" % k)
dict.__setitem__(self, k, v)
exec("""
foo = "bar"
foo
try:
qyz
except NameError:
pass
class K:
baz = foo
def f(ggg=foo): pass
def g(ggg=foo):
global f
f = 87
f
g()
""",K())
This should consitently either call or not call the overridden methods on the
dictionary, producing either no output or:
set foo
get foo
get qyz
get foo
get foo
set K
get foo
set g
get g
set f
get f
Instead, only sometime the override gets called, producing
set foo
get foo
get qyz
set K
get foo
set g
get g
get f
meaning that
(a) modifications of global variables via global statements
(b) code at class-level
ignore overridden methods, whereas everything else follows them
--
components: Interpreter Core
messages: 310388
nosy: ppperry
priority: normal
severity: normal
status: open
title: Inconsistent behavior if globals is a dict subclass
versions: Python 3.6
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32615>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32140] IDLE debugger fails with non-trivial __new__ super call
ppperry <maprea...@olum.org> added the comment: Simplified reproducer for same bug without any imports: class BadRepr: def __repr__(self): 1/0 def broken(): x=BadRepr() x=x #filler line for debugger In this case, the problematic BadRepr object in the "broken" function explictly has a broken __repr__, but the uninitialized Fraction object in the "__new__" function of the Fraction class has a similarly broken __repr__ -- nosy: +ppperry ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32140> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31925] test_socket creates too many locks
Change by ppperry <maprea...@olum.org>: -- title: test_socket creates too much locks -> test_socket creates too many locks ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31925> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30990] Calls to C functions using `.__call__` don't get sent to profiler.
New submission from ppperry: If you create a file called `inputtest.py` with the contents `input.__call__()`, and run the built-in profile module on it, it doesn't notice the call to `input`, and produces a report not including that call. 4 function calls in 0.000 seconds Ordered by: standard name ncalls tottime percall cumtime percall filename:lineno(function) 10.0000.0000.0000.000 :0(exec) 10.0000.0000.0000.000 :0(setprofile) 10.0000.0000.0000.000 inputtest.py:1() 10.0000.0000.0000.000 profile:0( at 0x029880C0, file "inputtest.py", line 1>) 00.000 0.000 profile:0(profiler) -- components: Interpreter Core, Library (Lib) messages: 298847 nosy: ppperry priority: normal severity: normal status: open title: Calls to C functions using `.__call__` don't get sent to profiler. type: behavior versions: Python 2.7, Python 3.7 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30990> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30958] Scripts folder is empty
Changes by ppperry <maprea...@olum.org>: -- type: performance -> behavior ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30958> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30953] Fatal python error when jumping into except clause
New submission from ppperry: trying to execute the following code: import sys def trace(frame, event, arg): if event == "line" and frame.f_lineno > 12: frame.f_lineno = 12 return None return trace sys.settrace(trace) def error(): try: pass except: pass pass pass error() Produces a fatal error: Fatal Python error: XXX block stack underflow Current thread 0x0af4 (most recent call first): File "jumpintoexception.py", line 12 in error File "jumpintoexception.py", line 15 in -- components: Interpreter Core, Library (Lib) messages: 298556 nosy: ppperry priority: normal severity: normal status: open title: Fatal python error when jumping into except clause type: crash versions: Python 3.7 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30953> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
