for tracking purposes, the profile output and an error for the streaming API when it goes boom
For tracking purposes for chris's bennifit, here's the output log file from a python -m profile main.pyw execution over a 24 hour period. I'm also including an error from error.log that shows what happens when streaming takes a shit, maybe we can kill two birds with one stone. Here's the error. Tue Nov 29, 2011 00:56:26 core.buffers.updating ERROR: twitmonger_dev: Error during update process in buffer buffer Sent Traceback (most recent call last): File "core\sessions\buffers\buffers\updating.py", line 85, in update new = self.retrieve_update(update_type=update_type) File "session\twitter\buffers\sent.py", line 35, in retrieve_update tweets = self.paged_update(update_function_name='user_timeline', since_id=self.get_max_sent_item_id(), include_rts=True) File "session\twitter\buffers\api_count.py", line 28, in paged_update new_data = self.session.api_call(update_function_name, report_success=False, report_failure=False, args, *kwargs) File "session\twitter\twitter.py", line 338, in api_call raise e TweepError: Failed to send request: [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond This happens in all streaming buffers.