| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's more efficient to use global_event_loop than a local EventLoop
instance, so do that when we know it's safe.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
When pruning packages from the merge list, only prune them if the
relevant dependency is not satisfied by an alternative package which
is already installed. This should fix bug #448176, and now there's also
reasons logged for why a particular package is dropped.
|
| |
|
|
|
|
|
| |
This will eventually be used for parallelization of aux_get/regen
processes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
before the patch:
$ repoman full
RepoMan scours the neighborhood...
metadata.missing 1
dev-haskell/qthaskellc/metadata.xml
SRC_URI.mirror 1
dev-haskell/qthaskellc/qthaskellc-1.1.4.ebuild: 'http://download.berlios.de/' found in thirdpartymirrors
after the patch:
$ repoman full
RepoMan scours the neighborhood...
metadata.missing 1
dev-haskell/qthaskellc/metadata.xml
SRC_URI.mirror 1
dev-haskell/qthaskellc/qthaskellc-1.1.4.ebuild: 'http://download.berlios.de/' found in thirdpartymirrors: 'mirror://berlios'
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 83cfc04df383b56592b89f1dc58428c0e8d09925.
This override could be bad if the base class needs to call _async_wait
for some reason.
|
| |
|
| |
|
|
|
|
|
| |
The code has to be in sync in order to prevent erroneous test failures
triggered by new year's day timezone differences.
|
|
|
|
|
| |
If the atom is unsatisfied due to a USE dep that's only visible in the
unevaluated form, then display the unevaluated form.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Avoid blocking for IO if there are any timeout or idle callback events
available to process. This will prevent starvation of the idle
callbacks, which are much more common since commit
a3100be184ba1cac2f672f0a1cadcf01690c6d3f. We don't want these idle
callbacks to be delayed by long periods of IO blocking.
|
|
|
|
|
|
|
|
| |
For cases where _start returns synchronously, this method is a
convenient way to trigger an asynchronous call to self.wait()
(in order to notify exit listeners), avoiding excessive event
loop recursion (or stack overflow) that synchronous calling of
exit listeners can cause.
|
|
|
|
|
|
| |
Isolate ctypes usage in a subprocess, in order to avoid potential
problems with stale cached libraries as described in bug #448858,
comment #14 (also see http://bugs.python.org/issue14597).
|
| |
|
| |
|
| |
|
|
|
|
| |
This helps to minimize ResourceWarning triggered by ^C with python3.
|
| |
|
|
|
|
|
|
| |
The library handle is no longer cached, since commit
9e37cca4f54260bd8c45a3041fcee00938c71649, so skip the LoadLibrary
call and just call find_library instead.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to avoid blocking forever when may_block is True (the
default), callers must be careful to ensure that at least one of the
following conditions is met:
1) An event source or timeout is registered which is guaranteed
to trigger at least on event (a call to an idle function
only counts as an event if it returns a False value which
causes it to be stop being called)
2) Another thread is guaranteed to call one of the thread-safe
methods which notify iteration to stop waiting (such as
idle_add or timeout_add).
These rules ensure that iteration is able to block until an event
arrives, without doing any busy waiting that would waste CPU time.
This will fix busy waiting which would be triggered by
PopenPipeBlockingIOTestCase when waiting for the thread from
PipeReaderBlockingIO to call idle_add.
|
| |
|
| |
|
|
|
|
|
|
| |
This may be useful for using threads to handle blocking IO with Jython,
since Jython lacks the fcntl module which is needed for non-blocking IO
(see http://bugs.jython.org/issue1074).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Trigger a DeprecationWarning even when None is passed in for one of the
deprecated parameters, ensuring that any potentially unsafe usage
triggers the warning.
|