py2.6 tests on Travis-CI are now allowed to fail, meaning that we are, actually, supporting only 2.7+. I renew my proposal to *drop* support for py2.6 at all.
On Fri, Aug 8, 2014 at 4:37 AM, Ricordisamoa ricordisamoa@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. ;-)
When we add py 3 support, py 2.6 would drop down to third tier support ...
I renew my proposal to *drop* support for py2.6 at all.
I would like to hear for any users who are forced to use py 2.6 - why? and maybe we can find a solution, or support only the scripts you are using.
Il 07/08/2014 23:48, John Mark Vandenberg ha scritto:
On Fri, Aug 8, 2014 at 4:37 AM, Ricordisamoa ricordisamoa@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.» ;-)
When we add py 3 support, py 2.6 would drop down to third tier support ...
I renew my proposal to *drop* support for py2.6 at all.
I would like to hear for any users who are forced to use py 2.6 - why? and maybe we can find a solution, or support only the scripts you are using.
What about adding the Python version to the User-Agent?
On Fri, Aug 8, 2014 at 5:06 AM, Ricordisamoa ricordisamoa@openmailbox.org wrote:
What about adding the Python version to the User-Agent?
Yes, we discussed that in the last py 2.6 thread, but not in the user-agent thread as I recall.
Now included in a related patch:
https://gerrit.wikimedia.org/r/#/c/152200/
On Fri, Aug 8, 2014 at 5:06 AM, Ricordisamoa ricordisamoa@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@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&a...
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
On Fri, Aug 8, 2014 at 4:58 AM, John Mark Vandenberg jayvdb@gmail.com wrote:
Are they bugs in python that cant be worked around - do we know python issue numbers for them?
Pywikibot bug 1246 (what was listed in the table as unicode bug #3081100) spawned Python bug 10254 http://bugs.python.org/issue10254. I can't be sure what the other one is referring to, but I'm guessing it's Python bug 1054943 http://bugs.python.org/issue1054943.
Hi Ricordisamoa,
Ricordisamoa schreef op 7-8-2014 23:37:
py2.6 tests on Travis-CI are now allowed to fail, meaning that we are, actually, supporting only 2.7+. I renew my proposal to *drop* support for py2.6 at all.
Python2.6.x is still the default version on Redhat Linux. So if you use it in a corporate environment (like I do), you're stuck with that.
Maarten