Ah, maybe. I just saw your "fixes" at my Talk page(s).
----- Ursprüngliche Nachricht -----
Von: Amir Ladsgroup
Gesendet: 26.07.2014 23:22
An: Pywikibot discussion list
Betreff: Re: [Pywikipedia-l] The build is broken
it was another bug that John and Ricordisamoa are talking about.
On 7/27/14, info(a)gno.de <info(a)gno.de> wrote:
> This is not a bug in testing. The test detects a bug for archivebot.py which
> fails for unsigned threads.
> ----- Ursprüngliche Nachricht -----
> Von: John Mark Vandenberg
> Gesendet: 26.07.2014 18:21
> An: Pywikibot discussion list
> Betreff: Re: [Pywikipedia-l] The build is broken
> On Sat, Jul 26, 2014 at 10:39 PM, Ricordisamoa
> <ricordisamoa(a)openmailbox.org> wrote:
>> The build is still broken, but because of this edit, that breaks the
>> timestamp detection of the ArchiveBot.
>> Maybe a fictitious, write-protected talk page should be used?
> That is being tracked on
> An alternative test page would be a good solution.
> Or maybe the unit test could allow unsigned sections to be added to
> the talk page.
> John Vandenberg
> Pywikipedia-l mailing list
Pywikipedia-l mailing list
I found this in the source code of scripts/reflinks.py:
Distributed under the terms of the GPL
This seems to be the single case in the whole repository. Is it
compatible with our license conventions?
It even doesn't have a full GNU-style license header.
Why do we prefer "generator=" to normal query? The disadvantage of
generator is that API might ignore some parameters. For example, we can't
do generator=categories&gclprop=sortkey, while we can do
I'm finishing up the evaluation portion of my API client library
internship project. As a part of that, I'm making sure that
feedback/bug reports/feature requests end up where they should be. I
made several suggestions at the end of the pywikibot-core
evaluation, and have been linking bugzilla issues to some of the
criteria. I also left comments on the documentation RFC  with the
This leaves a handful of larger-scale/general/structural suggestions for change:
* As of 25 July 2014, there are 105 open patches in gerrit. The patch
review process should be streamlined and/or prioritized to reduce the
backlog of unreviewed patches.
* Iterating over a list and calling the API for each item is an
inefficient use of API calls. Pywikibot could be made more efficient
by combining API calls as much as possible (e.g. using generators and
combining resultstitle=title1|title2|...). One option may be a
constructor method that collects Page requests and enables larger,
less frequent API calls.
* The initial installation process features a series of obscure
options and confusing installation documentation. Redesign the initial
installation/configuration process to be lighter-weight, soliciting
and valuing feedback from new or one-time users in the redesign
process. Is it necessary to be logged in before `import pywikibot`
will not cause an error?
* Foster a hospitable attitude on pywikipedia-l, especially to new
and/or inexperienced users. Consider agreeing on community standards
for interaction; the Hacker School social rules may be a useful
Is Bugzilla the best place for these? Would these be useful to discuss
at the pywikibot hackathon at Wikimania? Is there somewhere else these
suggestions ought to go?
from pywikibot gold-standard evaluation
What is the minimum supported mw version for core and compat?
It looks like the lowest family version() are..
core: lockwiki with 1.15.1 (not confirmed as special:version requires
compat: wesolve with 1.5.7, loveto with 1.8.2, and then
wikitravel_shared with 1.10.1 and mozilla with 1.10.2, wikibond with
1.11alpha and twcareer & celtic & botwiki with 1.11.0, wekey &
ubuntutw & openttd with 1.12.0 & krefeldwiki with 1.12alpha
Re wesolve, wordsandmore.org is no longer a wiki.
Re loveto, lovetoknow.com/1911encyclopedia.org/webguru.com are in
various states of 'no longer a wiki'.
wikitravel shared, it is now 1.22 (http://wikitravel.org/shared/Special:Version)
mozilla, it is now 1.19.11
Re wikibond & twcareer & celtic & ubuntutw, they appear to be dead.
botwiki is now 1.17
wekey is now 1.16
openttd is now 1.19.1
krefeldwiki is still 1.12alpha!
So, 1.12alpha is the lowest living mw that we have a family file for.
Currently, the "Version" field of our bugs can only be set to one of
"compat (1.0)", "core (2.0)" or "unspecified".
Why not to create a new "both" option to explicitly indicate that the
bug is valid for both versions?
So, "unspecified" would only mean that the bug has not been tested on
(Ideally, the "version" field should consist of two checkboxes, one for