| bd808 | |
| Mar 30 2020, 8:09 PM |
| F31815603: mail.txt | |
| May 13 2020, 9:49 AM |
Pywikibot is actively deprecating Python2 support (T213287: Drop support of Python 2.7). The documentation at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Pywikibot is still python2 focused.
Someone needs to help the pywikibot Toolforge community understand how to run their bots under python3 and direct them to T242120: Python 2 to 3 support request for additional support at needed.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Xover | T265640 phe-tools: Match&Split bot is not running because of python2 deprecation in pywikibot | |||
| Resolved | Xqt | T213287 Drop support of Python 2.7 | |||
| Resolved | Xqt | T248914 Information campaign and tech support needed to get Toolforge pywikibot use moved from py2 to py3 |
We sent first e-mail in January or February I guess and it should've been delivered to Toolforge mailing list as well? @Urbanecm ?
Another e-mail could follow the 2.7.18 release of Python right before final deprecation works begin.
Looks good but I think we should speak from last/next stable version because master is starting to go to Python 3.5+ immediately after that deployment (and will become a new stable release 4.0 few weeks later). Maybe you can refer the to the version table at MW.
Should we have fix EOL date then. 13th of June is one month from now.
Okay, so you suggest exact date(s), is that right?
Yes. It easier to communicate a fixed date than saying "soon" or "in one month" or so.
Sorry, I'm completely busy. Could cca June 1st be the last py2 version and cca July 1st the first py3-only? Or do we need two versions before (June 1st and July 1st) and then August 1st py3-only version?
I would say the next release will be on 1st June which is the last py3 but https://gerrit.wikimedia.org/r/#/c/pywikibot/core/+/594106/ should be merged first. The first py3-only version can be published on 1st July but I would't brake the master branch before 26th June. So bot owners have 4 weeks from now for stable as well as master branch.
This was the last question I had. I'll improve the message for mailinglists and prepare Tech news in the next 7 days and then perhaps we could send them together with or right before 3.0.2020060x
I changed my mind. If we wait with changing the master until 26th June we also can publish another python2 branch then. So let's have a new branch on Monday 1st June and the last py2 4 weeks later e.g. 30th June as you suggested. That still gives bot owners 4 weeks from now. The master changes after 1st July and the first py3 release can come few weeks later
@Urbanecm sent a nice announcement to the cloud-announce list that will hopefully reach some Toolforge tool maintainers. Thank you very much Martin. :)
After this announcement reaches Pywikibot mailing list, I'll also send a note to Tech news, again with the link to the e-mail announcement.