Bountysource account link
Trim whitespace on blank lines; #983
Prune unused imports; #983
Reformat Python code for 80 char width; #983
Fix typo in comment; #983
Prune commented-out code; #983
Fix comment typo and tweak None comparison; #983
Preen comments on bountysource/redirect; #983
Trim errant param in docstring; #983
Clean up error handling; #983

In the original pull request (#933), when Bountysource gave us an error
in the querystring to ./associate, we displayed that error message on
the user's profile page. That's not the worst idea in theory, but in
practice we don't have good UI infrastructure in place for that. On the
pattern of lock-fail.html in the other account elsewhere
implementations, this displays the Bountysource error message in a
dedicated ./problem.html page.
Standardize nomenclature: problem -> error; #983
Error -> Failure; #983

This is what is actually used on the page, per lock-fail.html.
Format for 80 chars; #983
Correct a comment re: error handling; #983
Prune unused method; #983

This is a pass-through to the module function of the same name. Afaict,
the method is never called.
Group like functions together; #983

Some of these functions are hooks for the accounts elsewhere
infrastructre, others are helpers specific to this
implementation.
Prune commented-out code; #983
Query by id directly instead of via username; #983

This is in the get_participant_via_access_token function.
Standardize `params' to `user_info'; #983

We use the term user_info in other accounts elsewhere.
Add comment re: ACTIONS; #983

We don't branch on action in Bountysource like we do with other accounts
elsewhere.