I have started seeing this issue too. On Jul 12, 6:05 am, Doza <mcard...@gmail.com> wrote: > Can anybody from Twitter let us know what is going on? Seems like it > is not an isolated issue. > > Thanks, > Mike > > On Jul 11, 10:37 pm, Adam Kent <adam.k...@gmail.com> wrote: > > > > > > > > > I have been seeing this exact 24:00 timestamp issue too for the last > > few days too. > > > Also using tweepy. > > > thanks > > Adam > > > On Jul 10, 10:37 am, Doza <mcard...@gmail.com> wrote: > > > > Hi everybody, > > > > My application queries the search API periodically throughout the > > > day. I'm still working on a solution using the streaming API, but > > > this has been working fairly well for my needs. > > > > About 4 days ago I started getting errors from the Python library that > > > I use to perform the queries (tweepy.) It appears that some results > > > contain what appear to be invalid timestamps. Here is a sample of the > > > times that I see for some tweets: > > > > ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +0000' does not > > > match format '%a, %d %b %Y %H:%M:%S +0000' > > > ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +0000' does not > > > match format '%a, %d %b %Y %H:%M:%S +0000' > > > ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +0000' does not > > > match format '%a, %d %b %Y %H:%M:%S +0000' > > > ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +0000' does not > > > match format '%a, %d %b %Y %H:%M:%S +0000' > > > > These timestamps all have 24 as the hour, which doesn't seem correct. > > > Is anybody else seeing the same thing? > > > > Thanks, > > > Mike
-- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
