| valhallasw added a comment. |
In T144692#2607590, @binbot wrote:I don't know listpages as I always used compat.
Then could you please set up core and test whether listpages solves this use case?
-save/savenew (with flush() after every save) works reliably even for very slow, long search tasks. (I mean up to several days!) Even if there is a crush somewhere, or I have to disconnect my computer from network, the result is there, and I can continue later with -xmlstart from the last saved title (or whatever the script suggested me when I press ctrl c).
I suppose, this is not the case with > (and it still my be operating system dependent).
Why would this not be possible with >?
More to say, if it lasts too long, I can work parallel. When the bot saved 300 titles and still works on the next 3000, I can process the saved titles from another command window. This is much more flexibility than that of > / >>.
stdout can also be flushed.
Saveexc is different, it is created during the work. For using > you should create two output streams (one for console output, one for exceptions), and all data might be lost upon unexpected termination.
We already split output (user output goes to stderr, pipe-able output goes to stdout), so I'm unsure why this would not work, nor why there would be data loss in some cases?
In compat -save works fine for me either with -always or without it.
Never mind, I misread the code. It's indeed saved.
Cc: valhallasw, jayvdb, Xqt, Ninovolador, Ricordisamoa, gerritbot, XZise, Vituzzu, Dvorapa, Thibaut120094, 4nn1l2, Omegat, bzimport, Aklapper, pywikibot-bugs-list, binbot, Mdupont, JJMC89, droid, Jay8g
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
