You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The second example came from a desire that: x < y < z “just work”. In language design we don't always appreciate the consequences of our actions.
Don't all these boil down to the fact that Python is dynamically typed ?
The explanations page mentions that. But there are a lot of cases of cross-type equality: 1 == True, "a" == u"a", 1 == 1.0, etc.
This is the result of python being protocol oriented. But I too think that the __compare__ and __equals__ functions should be implemented consistently throughout the language.
The first arises from loss of precision on conversion to float. The second is operator chaining - the first comparison is True and the second comparison is True. The third (least surprising to me) arises from the fact that tuples aren't equal to lists, even if contents are equal.
As it says, the first isn't all because of loss of precision with float. That's only part of the issue.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.