| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
If the event loop is closed outside of __main__
then it closes the event loop in child processes
for the multiprocessing spawn start method.
Bug: https://bugs.gentoo.org/916142
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce a new exception SignalInterrupt which inherits from
KeyboardInterrupt and adds a 'signum' member. When a signal is received,
raise SignalInterrupt.
At the end of the script, catch KeyboardInterrupt, and look for the
signum member. Reset the signal handler to SIG_DFL, and re-raise the
signal to kill the process.
This ensures that the invoking shell sees that we got killed by a signal
instead of calling exit.
Bug: https://bugs.gentoo.org/887817
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
Closes: https://github.com/gentoo/portage/pull/965
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: John Helmert III <ajak@gentoo.org>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
The switch to using '/usr/bin/env python' shebangs doesn't naively
work with arguments after 'python', so the shebangs were broken. '-b'
is of dubious necessity anyway, so let's just drop it.
Fixes: 41f4f6d25019c4f944b8d9576d96482f92231fda
Signed-off-by: John Helmert III <ajak@gentoo.org>
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: John Helmert III <ajak@gentoo.org>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: John Helmert III <ajak@gentoo.org>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
* We only support Py3 now.
Signed-off-by: Aaron Bauman <bman@gentoo.org>
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
| |
Closes: https://github.com/gentoo/portage/pull/343
|
|
|
|
|
|
|
| |
The default asyncio event loop triggers a resource warning if it
is not explicitly closed, therefore close it when appropriate.
Bug: https://bugs.gentoo.org/654390
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dev-python/pycparser-2.18+ exposes a design flaw in dev-python/ply that
makes it unable to work with -OO code. Given that Gentoo compiles its
Python packages with -OO and both -O and -OO use the same files for
Python < 3.5, using -O in Portage implicitly means -OO for those
implementations.
Remove the optimizations from Portage shebangs to prevent triggering the
issue until we find a proper solution for it.
Bug: https://bugs.gentoo.org/628386
Reviewed-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
|
| |
Modules of installed instance of Portage are now placed in standard location,
which is included in default sys.path.
|
|
|
|
| |
(-bb can trigger errors, depending on Python version and environment.)
|
| |
|
|
|
|
| |
Shouldn't be any functional changes here.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is especially necessary when running in prefix mode, since
sys.path may contain the path for a different version of portage.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The reason for this check, as discussed in bug #166785, is no longer
relevant since emerge does not suggest to run `emaint --check world` in
this case anymore.
|
|
|
|
| |
These go along with commit a715b65f7bd36409c1283e6911265d1f4405ab7a.
|
|
|
|
|
|
|
|
|
|
| |
It makes more sense to use EROOT instead of ROOT for keys in mappings
like portage.db, since it allows for multiple prefixes to exist
simultaneously within the same map without having a key collision.
This affects all portageq commands which take a <root> parameter, since
that parameter now corresponds to EROOT instead of ROOT. None of this
makes any difference for non-prefix users, since EROOT and ROOT are
identical when EPREFIX is empty.
|
| |
|
| |
|
|
|
|
| |
involving EROOT.
|
| |
|
| |
|
|
|
|
|
| |
in the upcoming 2.1.9 branch which will not have sets support but will
still have the code in private and disabled form.
|
|
|
|
|
|
|
|
|
| |
for all of the following cases:
* package is missing repository metadata
* package has repository metadata, but the source repository does not
have a profiles/updates/ directory
* package has repository metadata, but the source repository is not
currently accessible via PORTDIR_OVERLAY
|
|
|
|
| |
most efficient to process all repos at once.
|
|
|
|
|
|
| |
As a backwards-compatibility measure, if a particular repository doesn't
come with an 'updates' directory, fallback to updates from
dbapi.porttree_root.
|
| |
|
|
|
|
|
|
| |
already, and use Atom.cp instead of dep_getkey().
svn path=/main/trunk/; revision=15327
|
|
|
|
|
|
| |
TERM=dumb.
svn path=/main/trunk/; revision=15191
|
|
|
|
| |
svn path=/main/trunk/; revision=14620
|
|
|
|
|
|
| |
compatibility with Python 3.
svn path=/main/trunk/; revision=14421
|
|
|
|
|
|
| |
both python 2.x and 3.x.
svn path=/main/trunk/; revision=14379
|
|
|
|
|
|
|
|
| |
dict.(iterkeys|itervalues|iteritems)() for compatibility with Python 3.
(2to3-3.1 -f dict -nw ${FILES})
svn path=/main/trunk/; revision=14327
|
|
|
|
|
|
|
|
| |
for compatibility with Python 3.
(2to3-3.1 -f itertools -f itertools_imports -nw ${FILES})
svn path=/main/trunk/; revision=14314
|
|
|
|
|
|
| |
(2to3-3.1 -f numliterals -nw ${FILES})
svn path=/main/trunk/; revision=14292
|
|
|
|
| |
svn path=/main/trunk/; revision=14291
|
|
|
|
|
|
| |
(2to3-3.1 -f print -nw ${FILES})
svn path=/main/trunk/; revision=14290
|
|
|
|
|
|
| |
(2to3-3.1 -f except -nw ${FILES})
svn path=/main/trunk/; revision=14289
|
|
|
|
|
|
| |
_unicode_encode() and _unicode_decode() where appropriate.
svn path=/main/trunk/; revision=13993
|
|
|
|
|
|
| |
handling.
svn path=/main/trunk/; revision=13891
|
|
|
|
| |
svn path=/main/trunk/; revision=12072
|
|
|
|
| |
svn path=/main/trunk/; revision=12047
|