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).
Changed in testrepository: | |
status: | New → Incomplete |
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