##// END OF EJS Templates
help: document weird behavior of uisetup()...
help: document weird behavior of uisetup() While refactoring ui.log() API, it was really annoying that uisetup() is actually an extsetup() the phase 1. Let's document that. I'm planning to add another uisetup() which is called per ui instance, though I can't think of a good name for it.

File last commit:

r37644:0a9c0d34 default
r40633:04d08f17 default
Show More
__init__.py
27 lines | 608 B | text/x-python | PythonLexer
Gregory Szorc
thirdparty: vendor futures 3.2.0...
r37641 # Copyright 2009 Brian Quinlan. All Rights Reserved.
# Licensed to PSF under a Contributor Agreement.
"""Execute computations asynchronously using threads or processes."""
Gregory Szorc
futures: switch to absolute and relative imports...
r37644 from __future__ import absolute_import
Gregory Szorc
thirdparty: vendor futures 3.2.0...
r37641 __author__ = 'Brian Quinlan (brian@sweetapp.com)'
Gregory Szorc
futures: switch to absolute and relative imports...
r37644 from ._base import (
FIRST_COMPLETED,
FIRST_EXCEPTION,
ALL_COMPLETED,
CancelledError,
TimeoutError,
Future,
Executor,
wait,
as_completed,
)
from .thread import ThreadPoolExecutor
Gregory Szorc
thirdparty: vendor futures 3.2.0...
r37641
try:
Gregory Szorc
futures: switch to absolute and relative imports...
r37644 from .process import ProcessPoolExecutor
Gregory Szorc
thirdparty: vendor futures 3.2.0...
r37641 except ImportError:
# some platforms don't have multiprocessing
pass