Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
c420d125
Commit
c420d125
authored
Jul 13, 2013
by
Raymond Hettinger
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Issue #18432: Fix unintended API change in the sched module
parent
f6d89ddd
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
5 additions
and
2 deletions
+5
-2
Lib/sched.py
Lib/sched.py
+1
-1
Lib/test/test_sched.py
Lib/test/test_sched.py
+1
-1
Misc/NEWS
Misc/NEWS
+3
-0
No files found.
Lib/sched.py
View file @
c420d125
...
...
@@ -165,4 +165,4 @@ class scheduler:
# the actual order they would be retrieved.
with
self
.
_lock
:
events
=
self
.
_queue
[:]
return
map
(
heapq
.
heappop
,
[
events
]
*
len
(
events
))
return
list
(
map
(
heapq
.
heappop
,
[
events
]
*
len
(
events
)
))
Lib/test/test_sched.py
View file @
c420d125
...
...
@@ -172,7 +172,7 @@ class TestCase(unittest.TestCase):
e3
=
scheduler
.
enterabs
(
now
+
0.03
,
1
,
fun
)
# queue property is supposed to return an order list of
# 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
):
flag
=
[]
...
...
Misc/NEWS
View file @
c420d125
...
...
@@ -50,6 +50,9 @@ Library
- Issue #18431: The new email header parser now decodes RFC2047 encoded words
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
an
encoded
character
immediately
followed
the
'?'
that
follows
the
CTE
character
,
resulting
in
a
decoding
failure
.
They
are
now
decoded
correctly
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment