Skip to content

Commit 744be65

Browse files
erlend-aaslanderlend-aasland
authored
Merge branch 'main' into isolate-elementtree
2 parents b02b18e + b84be8d commit 744be65

File tree

91 files changed

+1957
-950
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

91 files changed

+1957
-950
lines changed

‎Doc/library/asyncio-eventloop.rst‎

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ an event loop:
4848
running event loop.
4949

5050
If there is no running event loop set, the function will return
51-
the result of calling ``get_event_loop_policy().get_event_loop()``.
51+
the result of the ``get_event_loop_policy().get_event_loop()`` call.
5252

5353
Because this function has rather complex behavior (especially
5454
when custom event loop policies are in use), using the
@@ -59,11 +59,9 @@ an event loop:
5959
instead of using these lower level functions to manually create and close an
6060
event loop.
6161

62-
.. note::
63-
In Python versions 3.10.0--3.10.8 and 3.11.0 this function
64-
(and other functions which used it implicitly) emitted a
65-
:exc:`DeprecationWarning` if there was no running event loop, even if
66-
the current loop was set.
62+
.. deprecated:: 3.12
63+
Deprecation warning is emitted if there is no current event loop.
64+
In some future Python release this will become an error.
6765

6866
.. function:: set_event_loop(loop)
6967

‎Doc/library/asyncio-policy.rst‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,9 +116,11 @@ asyncio ships with the following built-in policies:
116116

117117
On Windows, :class:`ProactorEventLoop` is now used by default.
118118

119-
.. versionchanged:: 3.12
120-
:meth:`get_event_loop` now raises a :exc:`RuntimeError` if there is no
121-
current event loop set.
119+
.. deprecated:: 3.12
120+
The :meth:`get_event_loop` method of the default asyncio policy now emits
121+
a :exc:`DeprecationWarning` if there is no current event loop set and it
122+
decides to create one.
123+
In some future Python release this will become an error.
122124

123125

124126
.. class:: WindowsSelectorEventLoopPolicy

‎Doc/library/ctypes.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1656,12 +1656,12 @@ They are instances of a private class:
16561656
passed arguments.
16571657

16581658

1659-
.. audit-event:: ctypes.seh_exception code foreign-functions
1659+
.. audit-event:: ctypes.set_exception code foreign-functions
16601660

16611661
On Windows, when a foreign function call raises a system exception (for
16621662
example, due to an access violation), it will be captured and replaced with
16631663
a suitable Python exception. Further, an auditing event
1664-
``ctypes.seh_exception`` with argument ``code`` will be raised, allowing an
1664+
``ctypes.set_exception`` with argument ``code`` will be raised, allowing an
16651665
audit hook to replace the exception with its own.
16661666

16671667
.. audit-event:: ctypes.call_function func_pointer,arguments foreign-functions

‎Doc/library/datetime.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1351,7 +1351,7 @@ Instance methods:
13511351

13521352
Because naive ``datetime`` objects are treated by many ``datetime`` methods
13531353
as local times, it is preferred to use aware datetimes to represent times
1354-
in UTC; as a result, using ``utcfromtimetuple`` may give misleading
1354+
in UTC; as a result, using :meth:`datetime.utctimetuple` may give misleading
13551355
results. If you have a naive ``datetime`` representing UTC, use
13561356
``datetime.replace(tzinfo=timezone.utc)`` to make it aware, at which point
13571357
you can use :meth:`.datetime.timetuple`.

0 commit comments

Comments
 (0)