Commit c420d125 authored by Raymond Hettinger's avatar Raymond Hettinger

Issue #18432: Fix unintended API change in the sched module

parent f6d89ddd
...@@ -165,4 +165,4 @@ class scheduler: ...@@ -165,4 +165,4 @@ class scheduler:
# the actual order they would be retrieved. # the actual order they would be retrieved.
with self._lock: with self._lock:
events = self._queue[:] events = self._queue[:]
return map(heapq.heappop, [events]*len(events)) return list(map(heapq.heappop, [events]*len(events)))
...@@ -172,7 +172,7 @@ class TestCase(unittest.TestCase): ...@@ -172,7 +172,7 @@ class TestCase(unittest.TestCase):
e3 = scheduler.enterabs(now + 0.03, 1, fun) e3 = scheduler.enterabs(now + 0.03, 1, fun)
# queue property is supposed to return an order list of # queue property is supposed to return an order list of
# upcoming events # upcoming events
self.assertEqual(list(scheduler.queue), [e1, e2, e3, e4, e5]) self.assertEqual(scheduler.queue, [e1, e2, e3, e4, e5])
def test_args_kwargs(self): def test_args_kwargs(self):
flag = [] flag = []
......
...@@ -50,6 +50,9 @@ Library ...@@ -50,6 +50,9 @@ Library
- Issue #18431: The new email header parser now decodes RFC2047 encoded words - Issue #18431: The new email header parser now decodes RFC2047 encoded words
in structured headers. in structured headers.
- Issue #18432: The sched module's queue method was incorrectly returning
an iterator instead of a list.
- Issue #18044: The new email header parser was mis-parsing encoded words where - Issue #18044: The new email header parser was mis-parsing encoded words where
an encoded character immediately followed the '?' that follows the CTE an encoded character immediately followed the '?' that follows the CTE
character, resulting in a decoding failure. They are now decoded correctly. character, resulting in a decoding failure. They are now decoded correctly.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment