© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Okay, this is extremely weird. I can see the sys.exit(1) call in buildout sources on that machine, right after the internal error message is printed. Could the logging.shutdown() call in the finally: block somehow clear that exception? Nothing else comes to mind...