Looks good! Don't forget to add your name to AUTHORS.

@tsnoam the travis build is failing on _valid_token. I say we can do without that method, because Telegram will alert the user when the token is invalid anyway, no need for us to do it. Especially as it could incorrectly say a token is invalid like it did now.

@rahiel I added the test for a reason - in case of a not well formatted token, the error from the server will not be a json, but rather an html page (the documentation for the bot API).
Such a webpage will cause a wrong message in the TelegramError exception.
I think that what I'll do instead is fix the unitests to bypass that specific validation, and write new unitests to actually test it.

(and also I'll update the AUTHORS file)

changes with the new PR:

• use functools.wrap for _try_except_req decorator
• added self to AUTHORS
• fixed bug in _valid_token -> thanks to unitests now working
• fix unitests to work with token validator
• gitignore: for files generated by unitests

pushed fix for python3...

Hey, it seems like the unit tests fail for Python 2.6, because there is an assert function missing, that you're not using (there is no regexp in the String you're testing for, so you could just use assertRaises).

All the other changes seem very neat, at a first glance! Thank you very much for your work :)

@jh0ker
following our chat -

• aligned Updater.__init__ prototype to be more consistent
• added unitests to cover the changes as of above
• the accidentally removed str.capitalize() on api_error exceptions is now back

Thank you very much, Noam! :)