I guess I'm one of the few people who use the rewrite branch exclusively then, so I thought I'd chip in and mention that there's at least one user :) As I have next to no experience with the trunk version, I cannot say anything about speed. Most of the stuff I do doesn't require very fast execution, and when I need content I usually have a PreloadingGenerator to fetch page text in batches. As I'm more of a user of Pwb than a developer I have no idea how the two branches should continue further. It would be beneficial for me to know that there's only one branch I have to relate to, though. Cheers, Morten On 20 June 2012 23:34,  <info(a)gno.de> wrote: > I was working on the rewrite branch last week (implementing xmlreader, additional retrieving of special pages, hooking cosmetic_changes with new functionality and some other stuff) > > At least I am a bit frustrated: I guess nobody uses it as I found some blocker in the code and mainly it runs very very slow. The time consumption is more than 10 times of the trunk release. Maybe the cacherequest is still unfinished but I cannot follow the site request since -verbose gives no additional output about that. Is there another switch? > > As I am not able to keep both releases on the same level an merge it vice versa, I would like to ask the next steps and how to proceed in that manner. > > btw I created a matrix for python version / pwb release at http://www.mediawiki.org/wiki/Manual:Pywikipediabot/Overview. Because of the unicode bug (which is triggered by py 2.5/2.6/2.71) it is strictly recommended to use python 2.7.2 or 2.7.2 for the trunk. I guess that bug does not affect the rewrite. But we need 2.6 for some method decorators. > > And at last: thanks Merlijn for the pwb.py shortener. > > Regards > xqt > > _______________________________________________ > Pywikipedia-l mailing list > Pywikipedia-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l