I am not sure whether we need non-API-wiki support anymore. We have the rewrite branch for
fully API support. And trunk release supports both but it fails with getAll method for
some sites. Indeed I am against a mixed stucture who merged to API based site methods and
cuts older methods which means they never works again. As demonstrated in rewrite branch
there could be exists more than one site object. We have BaseSite for basic methods,
APISite for API call methods and DataSite for methods dealing with Wikidata. Why
couldn't we have a site object for non-API wikis? Maybe we do not need non-API support
anymore. Ok, than we should archive the actual framework and remove old code stuff,
perhaps merge from or to rewrite branch and hold only one framework, which would be easier
to support instead of doing the same part twice as it is today.
Greetings
xqt
----- Original Nachricht ----
Von: Amir Ladsgroup <ladsgroup(a)gmail.com>
An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>
Datum: 21.04.2013 22:42
Betreff: [Pywikipedia-l] Stop supporting non-API wikis
Hello all,
API is one of the most important features of MW and it has been used
on WMF wikis since 2009 If I recall correctly
I want to use API on everything remained (in PWB codes) in order to
reduce pressure on servers but this idea of supporting non-API wikis
is really annoying and unreasonable in my opinion
I think we must end supporting non-API wikis, If you're not agree with
me, tell me why not
Best
--
Amir
_______________________________________________
Pywikipedia-l mailing list
Pywikipedia-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l