Is there any reason or advantage for putting the page in asyncron mode while I am using
replace.py manually? I guess this should be changed to normal put and put operation in
-always mode maybe done asyncroneously to save time for searching and processing the next
pages like interwiki.py does it with -async option.
Greetings
xqt
----- Original Nachricht ----
Von: Merlijn van Deen <valhallasw(a)arctus.nl>
An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>
Datum: 23.10.2010 15:08
Betreff: Re: [Pywikipedia-l] Replace.py should save -- please comment
On 23 October 2010 12:13, Bináris
<wikiposta(a)gmail.com> wrote:
quitting with "q". Not applicable with
ctrl C. Here is a little bug, the
counter cannot check if put_async _will_ be successful.
It can.
def put_async(self, newtext,
comment=None, watchArticle=None, minorEdit=True,
force=False,
callback=None):
(...)
callback: a callable object that will be called after the page put
operation; this object must take two arguments:
(1) a Page object, and (2) an exception instance, which
will be None if the page was saved successfully.
Just make sure you know how to do multithreading, or this will come back to
bite you. (No, incrementing a global variable is not the right way.)
Best regards,
Merlijn
--------------------------------
_______________________________________________
Pywikipedia-l mailing list
Pywikipedia-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l