Issue #21729: Used the "with" statement in the dbm.dumb module to ensure
files closing.  Patch by Claudiu Popa.
Issue #21729: Used the "with" statement in the dbm.dumb module to ensure
files closing.  Patch by Claudiu Popa.
asyncio, Tulip issue 177: Rewite repr() of Future, Task, Handle and TimerHandle

- Uniformize repr() output to format "<Class ...>"
- On Python 3.5+, repr(Task) uses the qualified name instead of the short name
  of the coroutine
(Merge 3.4) asyncio, Tulip issue 177: Rewite repr() of Future, Task, Handle and
TimerHandle

- Uniformize repr() output to format "<Class ...>"
- On Python 3.5+, repr(Task) uses the qualified name instead of the short name
  of the coroutine
Issue #21811: Anticipated fixes to 3.x and 2.7 for OS X 10.10 Yosemite.
Issue #21811: Anticipated fixes to 3.x and 2.7 for OS X 10.10 Yosemite.
Issue #21811: Anticipated fixes to 3.x configure for OS X 10.10 Yosemite.
Issue #21811: Anticipated fixes to 3.x configure for OS X 10.10 Yosemite.
Issue #21163, asyncio: Fix some "Task was destroyed but it is pending!" logs in tests
(Merge 3.4) Issue #21163, asyncio: Fix some "Task was destroyed but it is
pending!" logs in tests
asyncio: sync with Tulip

- Python issue 21163: Fix more "Task was destroyed but it is pending!" logs in
  tests
- Add test to check that run_until_complete() checks the loop of the future
(Merge 3.4) asyncio: sync with Tulip

- Python issue 21163: Fix more "Task was destroyed but it is pending!" logs in
  tests
- Add test to check that run_until_complete() checks the loop of the future
Issue #21163: Fix one more "Task was destroyed but it is pending!" log in tests
(Merge 3.4) Issue #21163: Fix one more "Task was destroyed but it is pending!"
log in tests
asyncio: Handle error handler: enhance formatting of the callback
(Merge 3.4) asyncio: Handle error handler: enhance formatting of the callback
Issue #18592: For idlelib.SearchDialogBase, edit and add docstrings,
move two functions next to the functions that use them.
Merge with 3.4