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

Closed
opened 2011-01-16 03:03:20 +00:00 by davidsarah · 2 comments
davidsarah commented 2011-01-16 03:03:20 +00:00
Owner

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

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
packaging
major
defect
1.8.1
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
Author
Owner

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
Author
Owner

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.

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.
tahoe-lafs modified the milestone from soon to 1.8.2 2011-01-27 05:15:29 +00:00
tahoe-lafs added the
fixed
label 2011-01-27 05:16:58 +00:00
davidsarah closed this issue 2011-01-27 05:16:58 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1328
No description provided.