projects / portage.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0620388) | patch
Instead of calling sys.exit when a ParseError occurs in the config
authorZac Medico <zmedico@gentoo.org>
Tue, 11 Dec 2007 23:46:11 +0000 (23:46 -0000)
committerZac Medico <zmedico@gentoo.org>
Tue, 11 Dec 2007 23:46:11 +0000 (23:46 -0000)
commitdee48ce8f7febb304cf4f56251ad7b3316ffaa67
tree639c6b16a77e499915f41cde6dec0755175a3290tree | snapshot
parent06203883b252d39c335f5ef2118f43aa093334b8commit | diff
Instead of calling sys.exit when a ParseError occurs in the config
constructor, raise a ParseError and make emerge and portageq handle
the error. This way consumers of the portage api can handle the
ParseError rather than have their application exit. Thanks to lxnay
for reporting. (trunk r8884)

svn path=/main/branches/2.1.2/; revision=8886
bin/emerge diff | blob | history
bin/portageq diff | blob | history
pym/portage.py diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.