hrafn/apithreads.py

# Python module that handles calls to the twitter API as a separate thread

import re
from threading import Thread

class GetTweets(Thread):
    def __init__(self, api, list_name, pane, num_entries, username):
        Thread.__init__(self)
        self.api = api
        self.list_name = list_name
        self.pane = pane
        self.num_entries = num_entries
        self.username = username


    def run(self):
        print 'debug: GetTweets.run(): start'

        # username/Home entries need to load the appropriate Home feed
        if self.list_name == self.username + '/Home':
            statuses = self.api.GetHomeTimeline(count=self.num_entries)

        # For @username, check if it is one of our usernames, or
        # just needs to be searched on
        elif self.list_name == '@' + self.username:
            statuses = self.api.GetMentions(count=self.num_entries)
        elif re.match('@', self.list_name):
            statuses = results_to_statuses(self.api.Search(self.list_name, rpp=self.num_entries))

        # Direct Messages should match like /Home, above
        elif self.list_name == self.username + '/Direct Messages':
            statuses = dms_to_statuses(self.api.GetDirectMessages())

        # User lookups go straight to the user
        elif re.match(r'user: ', self.list_name):
            statuses = self.api.GetUserTimeline(re.sub(r'^user: ', r'', self.list_name), count=self.num_entries)

        # Lists load the appropriate list from the appropriate account
        elif re.match(r'list: ', self.list_name):
            real_list = re.sub(r'list: .*/(.*)', r'\1', self.list_name)
            statuses = self.api.GetListStatuses(real_list, per_page=self.num_entries)

        # Everything else is a straight search
        else:
            statuses = results_to_statuses(self.api.Search(self.list_name, rpp=self.num_entries))

        self.pane.update_window(statuses)

        print 'debug: GetTweets.run(): finished'


### End class GetTweets



# We use these classes to emulate a Status object when we need
# one to be built out of something else.
class Status():
    def __init__(self):
        self.user = User()
        self.id = None
        self.created_at = None
        self.in_reply_to_screen_name = None
        self.in_reply_to_status_id = None


class User():
    def __init__(self):
        self.screen_name = None
        self.name = None


# To keep things simple elsewhere and improve code reuse
# we'll build a list of home-cooked Status objects out of results.
# Why is this even necessary?
# Why can't we have more consistency out of the Twitter API?
def results_to_statuses(results):
    statuses = []
    for result in results.results:
        status = Status()
        status.id = result.id
        status.user = User()
        status.user.screen_name = result.from_user
        status.user.name = ""
        status.in_reply_to_screen_name = result.to_user
        # The Twitter Search API has different timestamps than the
        # REST API... balls
        # fixme:
        # Gotta be a cleaner way to do this, but I can't think of it
        # right now
        created_at = re.sub(',', '', result.created_at)
        created_split = re.split(' ', created_at)
        status.created_at = created_split[0] + ' ' + created_split[2] + ' ' + created_split[1] + ' ' + created_split[4] + ' ' + created_split[5] + ' ' + created_split[3]
        status.text = result.text
        statuses.append(status)
    return statuses


def dms_to_statuses(direct_messages):
    statuses = []
    for dm in direct_messages:
        status = Status()
        status.id = dm.id
        status.user = User()
        status.user.screen_name = dm.sender_screen_name
        status.user.name = dm.sender.name
        status.created_at = dm.created_at
        status.text = dm.text
        statuses.append(status)
    return statuses