Done. Hopefully it wasn’t too anecdotal. I’ve never filed a bug before.

I’ve been playing with tweetyPy for the last day or so, and I’m really kind of enamored. I’m working on a bash-script concoction of watch, screen, and tweetyPy to build a command-line shadow of the variety of GUI Twitter tools. It might be easier to pick up Python, since I’ve been meaning to anyway, but, for the moment, this is it. For those folks who ssh into their boxes and want to use screen with a custom .screenrc which maintains a region with the timelines, and a region for tweeting, I’ll be happy to make it available when I’ve finished.

Yesterday, thinks worked swimmingly, basically. Today, however, it seems that there’s some Unicode business mucking up the timeline. I’m not sure if there’s something that could be changed in the Python, e.g. some headers business, or something else. Here’s the error I’m getting:

Traceback (most recent call last):
File "/home/muraii/utilities/tweetyPy", line 234, in ?
main(sys.argv[1:])
File “/home/muraii/utilities/tweetyPy”, line 228, in main
print result
UnicodeEncodeError: ‘latin-1′ codec can’t encode character u’\u2014′ in position 883: ordinal not in range(256)


Actually, this is a bit different, as it previously was in position 1014. I wager someone used an em-dash in their tweet, and the position change is due to new tweets pushing that offending character around.

Have you had any issues like this?

Thanks for your efforts on this.

Daniel

An improvement could be something like this:

$ ./tweetyPy -t friends_timeline -u user@mail -p
$ Password:

By passing password as a value for an argument, it keeps stored in bash history, that isn’t a good idea…