Comment 2 for bug 1509105
Revision history for this message
| Stanislaw Pitucha (stanislaw-pitucha) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Imagine a situation where bandit missed installing some dependency, or some installed dependency is broken. That may result in ImportError when loading the plugin, rather than some exception at plugin runtime.
Currently, from the tests it looks like that kind of error is not propagated properly. This test failed, because it found 0 errors where 15 were expected, and not explicitly because the plugin failed to initialize.
But silent failures are not good for users or developers. Users should get a clear error that plugins failed to load (likely critical, app-stopping error), while developers should get a fail-fast at the place of a problem to make debugging easier.