removed GetPublicTimeline from the docs so as to stop confusing new folks since it was the first example given ... d'oh!

bumped version to 0.8.7
disable the 140 chars counting before posting a tweet

there is a bug where non-English messages are limited to less than 140 characters because unicode characters are counted as more than 1 character.
the simplistic, yet working, solution is to remove the client side restriction for a message to have 140 and send it anyway.
that way longer than 140 characters messages will be rejected by twitter server rather than in the client (which makes sense, the client shouldn't be enforcing server rules at the first place TMHO)
Merge pull request #42 from abloch/noCountChars

disable the 140 chars counting before posting a tweet
PostRetweet function implements retweet API

Added a PostRetweet function which implements the retweet API.

https://dev.twitter.com/docs/api/1/post/statuses/retweet/%3Aid

Also works with Twitter API v1.1.
Merge pull request #46 from sebastianw/retweet

PostRetweet function implements retweet API
Use default python version

Remove specific python version and use /usr/bin/env to determine
executable.
Merge branch 'master' into hashbang
Merge pull request #47 from sebastianw/hashbang

Use default python version
Change API base URL to version 1.1
Update GetSearch to API 1.1

https://dev.twitter.com/docs/api/1.1/get/search/tweets
VIM modeline for two-space indents
Update GetUserTimeline to API 1.1

https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline
Updated twitter_test.py to API 1.1

Updated test URLs to API 1.1 and changed syntax for GetUserTimeline
VIM modeline for two-space indents

VIM modeline for twitter_test.py
Updated Api.Status class to API 1.1

Added new fields from

https://dev.twitter.com/docs/platform-objects/tweets

There are a few older fields which are not documented but still used by
the Twitter API so no fields were removed.
adjusted PostUpdate() for api v1.1
PostRetweet updated for api v1.1
adjust GetUserRetweets for api v1.1
NOTE this technically doesn't exist in the v1.1 api as it's now
a special case of GetUserTimeline -- we may just remove this in
the final push
adjust GetReplies for api v1.1
NOTE we may deprecate this as it is now nothing but a special case
of GetUserTimeline
simple typo fix