On Fri, Aug 8, 2014 at 5:06 AM, Ricordisamoa
<ricordisamoa(a)openmailbox.org> wrote:
Il 07/08/2014
23:48, John Mark Vandenberg ha scritto:
On Fri, Aug 8, 2014 at 4:37 AM, Ricordisamoa
<ricordisamoa(a)openmailbox.org> wrote:
py2.6 tests on Travis-CI are now allowed to fail, meaning that we are,
actually, supporting only 2.7+.
I would prefer to say that we've made py 2.6 a second tier supported
platform. ;-)
I'd say, «A program that has not been tested does not work.» ;-)
Fair call.
I would use the definitions:
first tier - actively maintained and tested
second tier - accepting bug reports
third tier - accepting patches, which will be rejected if they make
the code ugly or introduce risk for the top two tiers.
Looking at the table on the overview
https://www.mediawiki.org/wiki/Manual:Pywikibot/Overview
which embedded from here
https://www.mediawiki.org/wiki/Manual:Pywikibot/Version_table
It looks like '2.7.2 — 2.7.7' is our only 'first tier' supported
platform version.
And 2.6.5 — 2.7.1 is second tier for pywikibot core.
I am guessing that unicode bug #3081100 and #3443397 was referring to these:
http://sourceforge.net/p/pywikipediabot/bugs/3081100
http://sourceforge.net/p/pywikipediabot/bugs/3443397
which respectively redirect to
http://sourceforge.net/p/pywikipediabot/bugs/1246 - closed-wont-fix
http://sourceforge.net/p/pywikipediabot/bugs/1382 - open
I've updated those:
https://www.mediawiki.org/w/index.php?title=Manual:Pywikibot/Version_table&…
Are those unicode bugs unfixable? I don't like that page saying 'Dont
run these versions on WMF servers - but feel free to screw up your own
wiki'. If they screw up WMF wikis, they will probably screw up other
wikis too. Are they bugs in python that cant be worked around - do we
know python issue numbers for them? It would be nice to either fix
the bugs or isolate the code which doesnt work on those versions so we
can refuse to run the broken scripts, etc. Or, add python version to
the user-agent for compat also, and recommend that the ops team block
bots using those versions.
I am guessing that the Toolserver/Labs 2.7.1 was/is patched, and it is
the ops teams responsibility to manage that, or maybe that version
isnt on those environments any longer??
--
John Vandenberg