library code cannot tell .testr.conf is missing vs incomplete or whatever
Bug #593322 reported by
Jelmer Vernooij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Testrepository |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
affects testrepository
Right now testrepository will raise a ValueError if there is not
testr.conf file present when attempting to rerun. It would be nice if it
could raise a more specific exception so that callers can have different
behaviour based on the exception type (such as tribunal).
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 593322] [NEW] Raise more specific exception when .testr.conf is missing | #1 |
| Changed in testrepository: | |
| status: | New → Incomplete |
Revision history for this message
| Jelmer Vernooij (jelmer) wrote Re: Raise more specific exception when .testr.conf is missing | #2 |
| Changed in testrepository: | |
| status: | Incomplete → Confirmed |
Revision history for this message
| Robert Collins (lifeless) wrote | #3 |
| Changed in testrepository: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Wishlist |
| summary: |
- Raise more specific exception when .testr.conf is missing + library code cannot tell .testr.conf is missing vs incomplete or + whatever |
To post a comment you must log in.
What sort of behaviour do you have in mind ?
I'd be ok with custom exceptions, but lets put them in the module
raising them generally, I don't want the big pile of exceptions bzr
has, for instance :)
-Rob