[issue34899] Possible assertion failure due to int_from_bytes_impl()

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9090 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34899> ___ ___ Py

[issue34910] PyObject_Print() doesn't always return -1 on error

New submission from Zackery Spytz : PyObject_Print() returns 0 if PyUnicode_AsEncodedString() fails. -- components: Interpreter Core messages: 327197 nosy: ZackerySpytz priority: normal severity: normal status: open title: PyObject_Print() doesn't always return -1 on error

[issue34910] PyObject_Print() doesn't always return -1 on error

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9119 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34910> ___ ___ Py

[issue34899] Possible assertion failure due to int_from_bytes_impl()

Change by Zackery Spytz : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue34940] Possible assertion failure due to _check_for_legacy_statements()

New submission from Zackery Spytz : The PyUnicode_Tailmatch() and PyUnicode_FromString() calls in _check_for_legacy_statements() are not properly checked for failure. -- components: Interpreter Core messages: 327379 nosy: ZackerySpytz priority: normal severity: normal status: open

[issue34940] Possible assertion failure due to _check_for_legacy_statements()

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9151 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34940> ___ ___ Py

[issue34987] A possible null pointer dereference in _pickle.c's save_reduce()

New submission from Zackery Spytz : The get_class() call in save_reduce() is not checked for failure. -- components: Extension Modules messages: 327732 nosy: ZackerySpytz priority: normal severity: normal status: open title: A possible null pointer dereference in _pickle.c&#

[issue34987] A possible null pointer dereference in _pickle.c's save_reduce()

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9249 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34987> ___ ___ Py

[issue34987] A possible null pointer dereference in _pickle.c's save_reduce()

Zackery Spytz added the comment: It is not properly checked: Py_DECREF() is always called on the result of get_class(), but get_class() can return NULL. -- ___ Python tracker <https://bugs.python.org/issue34

[issue16965] 2to3 should rewrite execfile() to open in 'rb' mode

Change by Zackery Spytz : -- pull_requests: +9253 ___ Python tracker <https://bugs.python.org/issue16965> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35068] [2.7] Possible crashes due to incorrect error handling in pyexpat.c

Change by Zackery Spytz : -- components: Extension Modules nosy: ZackerySpytz priority: normal severity: normal status: open title: [2.7] Possible crashes due to incorrect error handling in pyexpat.c type: crash versions: Python 2.7 ___ Python

[issue35068] [2.7] Possible crashes due to incorrect error handling in pyexpat.c

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9432 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35068> ___ ___ Py

[issue35068] [2.7] Possible crashes due to incorrect error handling in pyexpat.c

New submission from Zackery Spytz : The attached PR fixes several error handling bugs in pyexpat.c. -- ___ Python tracker <https://bugs.python.org/issue35

[issue25451] tkinter: PhotoImage transparency methods

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9690 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue25451] tkinter: PhotoImage transparency methods

Zackery Spytz added the comment: I've created a PR for this issue. -- nosy: +ZackerySpytz versions: +Python 3.8 -Python 3.6 ___ Python tracker <https://bugs.python.org/is

[issue35269] A possible segfault involving a newly-created coroutine

New submission from Zackery Spytz : If compute_cr_origin() fails in PyCoro_New(), coro->cr_origin won't be initialized. This will cause a crash during the coroutine's deallocation. I'll create a PR for this issue. -- components: Interpreter Core, asyncio mes

[issue35269] A possible segfault involving a newly-created coroutine

Change by Zackery Spytz : -- keywords: +patch pull_requests: +9829 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35269> ___ ___ Py

<    3   4   5   6   7   8