report all dependencies that we failed to import or find an acceptable version of, not just the first one #1328

New Issue

tahoe-lafs · 2011-01-16T03:03:20Z

davidsarah commented

2011-01-16 03:03:20 +00:00

This would reduce the number of iterations when several packages need to be installed (for both end-users and buildbot operators).

tahoe-lafs added the

labels 2011-01-16 03:03:20 +00:00

tahoe-lafs added this to the soon milestone 2011-01-16 03:03:20 +00:00

david-sarah@jacaranda.org commented

2011-01-16 03:58:17 +00:00

In [4963/ticket1306]:

src/allmydata/__init__.py: When a requirement fails, print all failures and also the PYTHONPATH and sys.path. refs #1328 (although this is only a partial fix because it doesn't handle failure to import).

In [4963/ticket1306]: ``` src/allmydata/__init__.py: When a requirement fails, print all failures and also the PYTHONPATH and sys.path. refs #1328 (although this is only a partial fix because it doesn't handle failure to import). ```

davidsarah commented

2011-01-27 05:15:29 +00:00

This should have been mostly fixed by changeset:29336a09163cd3d5. It is still possible that pkg_resources can throw an exception (when it is imported) that only has information about one package when there are errors with more than one. However, I don't think there's much we can do about that. This ticket is fixed for the errors that we generate ourselves.