[interpid] [bitesize] bugnumbers crashed with ValueError in main()

Do you know which specific version on Hardy failed more gracefully? I saw the following:

Setting up bughelper (0.2.14) ...
bdmurray@superman:~$ bugnumbers -p bughelper --status new
Traceback (most recent call last):
  File "/usr/bin/bugnumbers", line 324, in <module>
    main()
  File "/usr/bin/bugnumbers", line 210, in main
    raise ValueError, "unknown status: %s" %x
ValueError: unknown status: set(['new'])

This is also kind of addressed in bug 197037

Some time ago bughelper/numbers etc. did not have any validation of the value given as status and importance option, so no error was raised if there was an unknown value.

But making this option case-insensitive should not be that hard, working on it

Markus

I think I fixed it with the attached patch (against revno 220 of the main branch),

$ ./bugnumbers -p bughelper --status "new, incOMplete,wOn'T fIx, confirmed" --importance "unDecided, WISHLIST"
226483 (New, Undecided) - bughelper crashed with NotBranchError in find_format()
129341 (New, Wishlist) - bughelper would benefit from the ability to inherit clues from a clue file not named after a package
88102 (Confirmed, Undecided) - sort report by issue type rather than bug number
239007 (Confirmed, Undecided) - clue file for bugs without a package

But for unknown status there is still a ValueError raised:
$ ./bugnumbers -p bughelper --status "booo"
Traceback (most recent call last):
  File "./bugnumbers", line 383, in <module>
    main()
  File "./bugnumbers", line 259, in main
    raise ValueError, "unknown status: %s" %x
ValueError: unknown status: set(['Booo'])

Please test and review the attached patch,
Markus

The patch ends up modifying searches for "Incomplete w/" and "Incomplete w/o" to "Incomplete W/" and "Incomplete W/o" which then fails. I've attached a patch that deals with those particular statuses, or we could modify python-launchpad-bugs itself to include an alias for these statuses.

Brian, your last patch is looking good to me.

Resolved in revision 223 of the bzr branch of bughelper.

This bug was fixed in the package bughelper - 0.2.16

---------------
bughelper (0.2.16) intrepid; urgency=low

  * resolved bughelper issue were it would not write results to a file anymore
    (LP: #272655)
  * resolved issues where bugnumbers / bughelper crashes when unknown statuses
    are used - thanks Markus Korn (LP: #271155)

 -- Brian Murray <email address hidden> Wed, 24 Sep 2008 13:30:51 -0700