delta/cpython-git.git/Python/_warnings.c, branch v3.7.13

[3.7] bpo-39831: Fix a reference leak in PyErr_WarnEx(). (GH-18750). (GH-18765)

2020-03-08T16:07:58+00:00

(cherry picked from commit 2d2f85517f8216146a2f888d1ad4d765b3be2339)

[3.7] bpo-39831: Fix a reference leak in PyErr_WarnEx(). (GH-18750). (GH-18760)

2020-03-03T01:13:24+00:00

(cherry picked from commit 2d2f85517f8216146a2f888d1ad4d765b3be2339)

Co-authored-by: Serhiy Storchaka

Fix typo in _warnings.warn_explicit() docstring (GH-16625)

2019-10-08T09:25:56+00:00

(cherry picked from commit 5dfbb4d50333e7a91fc0cd8c03a2f2f2cf56dbd9)

Co-authored-by: Hansraj Das

bpo-35454: Fix miscellaneous minor issues in error handling. (GH-11077)

2018-12-11T07:05:13+00:00

* bpo-35454: Fix miscellaneous minor issues in error handling.

* Fix a null pointer dereference.
(cherry picked from commit 8905fcc85a6fc3ac394bc89b0bbf40897e9497a6)

Co-authored-by: Serhiy Storchaka

bpo-33509: Fix _warnings for module_globals=None (GH-6833)

2018-05-15T20:56:28+00:00

Don't crash on warnings.warn_explicit() if module_globals is not a dict.
(cherry picked from commit b056562860c227bad2e0ba7cd3130e115c007768)

Co-authored-by: Victor Stinner

bpo-32591: fix abort in _PyErr_WarnUnawaitedCoroutine during shutdown (#5337)

2018-01-26T19:28:31+00:00

When an unawaited coroutine is collected very late in shutdown --
like, during the final GC at the end of PyImport_Cleanup -- then it
was triggering an interpreter abort, because we'd try to look up the
"warnings" module and not only was it missing (we were prepared for
that), but the entire module system was missing (which we were not
prepared for).

I've tried to fix this at the source, by making the utility function
get_warnings_attr robust against this in general. Note that it already
has the convention that it can return NULL without setting an error,
which is how it signals that the attribute it was asked to fetch is
missing, and that all callers already check for NULL returns.

There's a similar check for being late in shutdown at the top of
warn_explicit, which might be unnecessary after this fix, but I'm not
sure so I'm going to leave it.

bpo-32571: Avoid raising unneeded AttributeError and silencing it in C code (GH-5222)

2018-01-25T08:49:40+00:00

Add two new private APIs: _PyObject_LookupAttr() and _PyObject_LookupAttrId()

bpo-32591: Fix PyExc_WarnFormat call (follow-up commit) (#5263)

2018-01-22T01:47:04+00:00

The previous version was correct in terms of behaviour, but
checking the return value of PyErr_WarnFormat allows to
avoid calling PyErr_Occurred and silences the coverity alarm.

bpo-32591: Add native coroutine origin tracking (#5250)

2018-01-21T14:44:07+00:00

* Add coro.cr_origin and sys.set_coroutine_origin_tracking_depth
* Use coroutine origin information in the unawaited coroutine warning
* Stop using set_coroutine_wrapper in asyncio debug mode
* In BaseEventLoop.set_debug, enable debugging in the correct thread

bpo-31975 (PEP 565): Show DeprecationWarning in main (GH-4458)

2018-01-08T02:45:02+00:00

- primary change is to add a new default filter entry for
  'default::DeprecationWarning:__main__'
- secondary change is an internal one to cope with plain
  strings in the warning module's internal filter list
  (this avoids the need to create a compiled regex object
  early on during interpreter startup)
- assorted documentation updates, including many more
  examples of configuring the warnings settings
- additional tests to ensure that both the pure Python and
  the C accelerated warnings modules have the expected
  default configuration