delta/cpython-git.git/Python/traceback.c, branch v3.7.13 github.com: python/cpython.git bpo-33029: Fix signatures of getter and setter functions. (GH-10746) 2018-11-27T17:58:07+00:00 Miss Islington (bot) 31488909+miss-islington@users.noreply.github.com 2018-11-27T17:58:07+00:00 5ceb7018dc63fab96f81d05e62bbe704e9f10cb9 Fix also return type for few other functions (clear, releasebuffer). (cherry picked from commit d4f9cf5545d6d8844e0726552ef2e366f5cc3abd) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com> 
Fix also return type for few other functions (clear, releasebuffer).
(cherry picked from commit d4f9cf5545d6d8844e0726552ef2e366f5cc3abd)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
 bpo-34588: Fix an off-by-one error in traceback formatting. (GH-9077) 2018-09-10T16:00:08+00:00 Miss Islington (bot) 31488909+miss-islington@users.noreply.github.com 2018-09-10T16:00:08+00:00 49020174305ca3dc90a811b03a05f44873297c61 The recursive frame pruning code always undercounted the number of elided frames by one. That is, in the "[Previous line repeated N more times]" message, N would always be one too few. Near the recursive pruning cutoff, one frame could be silently dropped. That situation is demonstrated in the OP of the bug report. The fix is to start the identical frame counter at 1. (cherry picked from commit d545869d084e70d4838310e79b52a25a72a1ca56) Co-authored-by: Benjamin Peterson <benjamin@python.org> 
The recursive frame pruning code always undercounted the number of elided frames
by one. That is, in the "[Previous line repeated N more times]" message, N would
always be one too few. Near the recursive pruning cutoff, one frame could be
silently dropped. That situation is demonstrated in the OP of the bug report.

The fix is to start the identical frame counter at 1.
(cherry picked from commit d545869d084e70d4838310e79b52a25a72a1ca56)

Co-authored-by: Benjamin Peterson <benjamin@python.org>
 bpo-30579: Allow TracebackType creation and tb_next mutation from Python (GH-4793) 2018-01-07T13:30:18+00:00 Nathaniel J. Smith njs@pobox.com 2018-01-07T13:30:18+00:00 e46a8af450210ee5c7f0459ad6beddbc626ae60f Third party projects may wish to hide their own internal machinery in order to present more comprehensible tracebacks to end users (e.g. Jinja2 and Trio both do this). Previously such projects have had to rely on ctypes to do so: https://github.com/pallets/jinja/blob/fe3dadacdf4cf411d0a5b6bbd4d5234697a28af2/jinja2/debug.py#L345 https://github.com/python-trio/trio/blob/1e86b1aee8c0c759f6f239ae53a05d0d3963c629/trio/_core/_multierror.py#L296 This provides a Python level API for creating and modifying real Traceback objects, allowing tracebacks to be edited at runtime. Patch by Nathaniel Smith. 
Third party projects may wish to hide their own internal machinery in
order to present more comprehensible tracebacks to end users
(e.g. Jinja2 and Trio both do this).

Previously such projects have had to rely on ctypes to do so:

  https://github.com/pallets/jinja/blob/fe3dadacdf4cf411d0a5b6bbd4d5234697a28af2/jinja2/debug.py#L345
  https://github.com/python-trio/trio/blob/1e86b1aee8c0c759f6f239ae53a05d0d3963c629/trio/_core/_multierror.py#L296

This provides a Python level API for creating and modifying real
Traceback objects, allowing tracebacks to be edited at runtime.

Patch by Nathaniel Smith.
 bpo-31949: Fixed several issues in printing tracebacks (PyTraceBack_Print()). (#4289) 2017-11-15T15:38:52+00:00 Serhiy Storchaka storchaka@gmail.com 2017-11-15T15:38:52+00:00 edad8eebeee3c99e324a7f1ac5073167c2b0b54d * Setting sys.tracebacklimit to 0 or less now suppresses printing tracebacks. * Setting sys.tracebacklimit to None now causes using the default limit. * Setting sys.tracebacklimit to an integer larger than LONG_MAX now means using the limit LONG_MAX rather than the default limit. * Fixed integer overflows in the case of more than 2**31 traceback items on Windows. * Fixed output errors handling. 
* Setting sys.tracebacklimit to 0 or less now suppresses printing tracebacks.
* Setting sys.tracebacklimit to None now causes using the default limit.
* Setting sys.tracebacklimit to an integer larger than LONG_MAX now means using
  the limit LONG_MAX rather than the default limit.
* Fixed integer overflows in the case of more than 2**31 traceback items on
  Windows.
* Fixed output errors handling.
bpo-25658: Implement PEP 539 for Thread Specific Storage (TSS) API (GH-1362) 2017-10-06T10:41:34+00:00 Masayuki Yamamoto ma3yuki.8mamo10@gmail.com 2017-10-06T10:41:34+00:00 731e18901484c75b60167a06a0ba0719a6d4827d See PEP 539 for details. Highlights of changes: - Add Thread Specific Storage (TSS) API - Document the Thread Local Storage (TLS) API as deprecated - Update code that used TLS API to use TSS API 
See PEP 539 for details.

Highlights of changes:

- Add Thread Specific Storage (TSS) API
- Document the Thread Local Storage (TLS) API as deprecated
- Update code that used TLS API to use TSS API
 bpo-30860: Consolidate stateful runtime globals. (#3397) 2017-09-08T05:51:28+00:00 Eric Snow ericsnowcurrently@gmail.com 2017-09-08T05:51:28+00:00 2ebc5ce42a8a9e047e790aefbf9a94811569b2b6 * group the (stateful) runtime globals into various topical structs * consolidate the topical structs under a single top-level _PyRuntimeState struct * add a check-c-globals.py script that helps identify runtime globals Other globals are excluded (see globals.txt and check-c-globals.py). 
* group the (stateful) runtime globals into various topical structs
* consolidate the topical structs under a single top-level _PyRuntimeState struct
* add a check-c-globals.py script that helps identify runtime globals

Other globals are excluded (see globals.txt and check-c-globals.py).
 bpo-31370: Remove support for threads-less builds (#3385) 2017-09-07T16:56:24+00:00 Antoine Pitrou pitrou@free.fr 2017-09-07T16:56:24+00:00 a6a4dc816d68df04a7d592e0b6af8c7ecc4d4344 * Remove Setup.config * Always define WITH_THREAD for compatibility. 
* Remove Setup.config
* Always define WITH_THREAD for compatibility.
bpo-6532: Make the thread id an unsigned integer. (#781) 2017-03-23T13:48:39+00:00 Serhiy Storchaka storchaka@gmail.com 2017-03-23T13:48:39+00:00 aefa7ebf0ff0f73feee7ab24f4cdcb2014d83ee5 * bpo-6532: Make the thread id an unsigned integer. From C API side the type of results of PyThread_start_new_thread() and PyThread_get_thread_ident(), the id parameter of PyThreadState_SetAsyncExc(), and the thread_id field of PyThreadState changed from "long" to "unsigned long". * Restore a check in thread_get_ident(). 
* bpo-6532: Make the thread id an unsigned integer.

From C API side the type of results of PyThread_start_new_thread() and
PyThread_get_thread_ident(), the id parameter of
PyThreadState_SetAsyncExc(), and the thread_id field of PyThreadState
changed from "long" to "unsigned long".

* Restore a check in thread_get_ident().
Issue #23782: Fixed possible memory leak in _PyTraceback_Add() and exception 2016-10-18T10:26:25+00:00 Serhiy Storchaka storchaka@gmail.com 2016-10-18T10:26:25+00:00 df0fd74ae8fa204aab51c35e10870fd99101e99c loss in PyTraceBack_Here(). 
loss in PyTraceBack_Here().
Issue #23782: Fixed possible memory leak in _PyTraceback_Add() and exception 2016-10-18T10:23:18+00:00 Serhiy Storchaka storchaka@gmail.com 2016-10-18T10:23:18+00:00 04eb7772794a11bdb7ed7cd132adebb2ae527191 loss in PyTraceBack_Here(). 
loss in PyTraceBack_Here().