python-twitter should catch 401 errors about python-twitter HOT 7 OPEN

[deleted comment]

In the bug report, by python-twitter, I mean the tweet program included with 
it. 
Sorry for the confusion.

I could go either way here.  We could either wrap the HTTPError exceptions with 
a
TwitterError, or we could pass them through.  I feel like it is probably more
informative to the caller to get the HTTPError, but I don't feel strongly 
either way.

fwiw I would rather have the httperror

The same issue happens with 403 errors. Twitter is returning error messages 
when you
get these 401 and 403 errors. It should be handled gracefully. Otherwise you are
expecting the consumer of the library to know that 401 and 403 should be caught 
and
also that the contents of the returned page have informative error messages.

Now, if the twitter error message is NOT included in the 401 and 403, then 
throw the
HTTPError instead of the TwitterError

I could pretty easily write the code to catch and wrap the 401 & 403 errors, 
but I'm
waiting on three other patches to be committed at the moment, so I'll hold off 
until
those are dealt with.  I don't want the backlog to grow too big.

The httperror is fine now that oauth authentication is used. Anyway, as a 
newbie, it would have been nice if the documentation told me how to trap it.
try:
    api.GetSomething()
except twitter.TwitterError as err:
    print('%s: %s' % (a,err))