-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use API (tracking) #44
Comments
From [email protected] on June 22, 2012 03:02:50 Summary: Use API (tracking) |
From [email protected] on November 09, 2012 02:05:50 Blockedon: wikiteam:26 wikiteam:56 |
From [email protected] on November 09, 2012 02:15:26 There are some libraries which might help: https://www.mediawiki.org/wiki/API:Client_code#Python |
From [email protected] on May 04, 2013 03:18:00 See also specifications for a rewrite at https://meta.wikimedia.org/wiki/WikiTeam/Dumpgenerator_rewrite |
From [email protected] on October 25, 2013 05:46:35 |
From [email protected] on November 05, 2013 09:48:39 Blocking: wikiteam:49 |
From [email protected] on November 11, 2013 22:38:57 Blocking: wikiteam:75 |
From [email protected] on December 16, 2013 04:02:07 Interesting set of PHP scripts which do some things more than dumpgenerator.py for API-enabled wikis (like logs download; interwiki map and usergroups are rarely interesting). https://www.mediawiki.org/wiki/Manual:Grabbers |
From [email protected] on June 08, 2014 06:12:35 As for XML download: jayvdb> Nemo_bis: there is an export=1 and exportnowrap=1 API params, which force the API to provide the same as Special:Export, right down to the bugs in Special:Export Also, his https://gerrit.wikimedia.org/r/136352 should remove any obstacle in using pywikibot. |
Remove xml part of launcher wikidump name
From [email protected] on March 01, 2012 00:41:27
Many bugs request API usage or could (probably) be fixed by using API.
Using API for pages is already many many times more efficient than index; using API everywhere (on wikis which have them) would make the script more robust and faster.
Original issue: http://code.google.com/p/wikiteam/issues/detail?id=44
The text was updated successfully, but these errors were encountered: