Announcement

Handling duplicate filename properly in BTQueue

Long time ago, I used BTQueue for massively downloading large amount of files automatically by crawling trackers periodically. Then I got a problem due to duplicate filename, e.g., AVSEQ01.DAT or MUSIC01.DAT. This problem was caused by users who didn’t rename filename to what it should be. In addition, BTQueue have never asked destination directory, filename, or directory name because I designed it for fully automatic downloading. Interactive actions must not be used here at all. At that time, I solved this problem by automatically renaming that files to somewhat unique. However, this feature disappeared since BTQueue 0.1.0. Now, it’s time to solve it again.

GWT Hello World in Python

Eventually, pyjamas has reached the first milestone to write Hello World example in Python and then translate them to JavaScript and HTML. Note that it also supports event handling. Let’s see how it looks like in action.

from ui import Button, RootPanel  

pyjamas: GWT clone in Python

Since  has been  for a week, Google was  its new version yesterday. GWT is now so popular. Anyway, I don’t like to program in Java. Now, there is a serious effort to reverse engineer GWT to make a clone in Python for Python fans like me. In beginning, it named as py-gwt but now it has been changed to pyjamas and it’s alive. Let’s see how it looks like at the real code in subversion repository.

Peer backs with verbose log

Since BTQueue has been moved its core back to BitTorrent, "peer" command was malfunction. Now, it backs again. You can see peers which the tracker responses by just as below.

peer [id]

In addition, you might want to see what is going on at current time. "last_message" also has been re-enabled. Anyway, there is only one message to indicate announce URL.

BTQueue 0.1.2 454

I’m very proud to announce the release of BTQueue 0.1.2 454. This release is mainly targeted to handling incorrect data sent from some private trackers gracefully. Actually, I was inspired by a post in forum. It turned out that BTQueue can’t talk to some private trackers and raised error message like: bad data from tracker - invalid bencoded value (data after valid prefix). Million thanks to dodgy, I managed to find the problem. Let me give you some example. Assuming that a tracker returns below data after receiving an announce message.

d8:intervali1800e5:peers6:B__}__ee