Xqt added a comment.
Some ideas for dopping Python 2.7:
- **pwb version issue**
- The next pywikibot release number can be **4.0**:
- 1.0 for compat
- 2.0 for stable release branch of core which has been dropped 2017
- 3.0 for the core master branch
- 4.0 for the new branch supporting Python >= 3.X only
- **Python release issues**
- Python 3.4 reached its end-of-life time in March (PEP 429) and should not
be supported any longer (1) <https://devguide.python.org/devcycle/>
- Python 3.5 reaches its end-of-life time in September 2020 (2)
<https://devguide.python.org/#status-of-python-branches>
- requests library is a base libreary of pwb but requests III needs Python
3.6 (3) <https://2.python-requests.org/projects/3/>
- **Repository issues**
- hard break of core
- we can either have a new repository for the new and set the curren core
repository to be read-only for further use
- use a new branch for the new (as we had it with core "2.0") and merge new
pathes to it. But this can be problematic if we want to change old master with
3.0 and 4.0 with new master at any time.
- **Code issues**
- open patches should be merged as much as possible instead of rebase it to
the new repository/branch
- new features are reserved for the new repository/branch
- code redesing should be done in the new repository/branch
- bugfixes can be done for a longer time if necessary or desirable for the
old repository/branch
see also T221801 <https://phabricator.wikimedia.org/T221801>
TASK DETAIL
https://phabricator.wikimedia.org/T213287
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Xqt
Cc: zhuyifei1999, Dalba, Eatcha, KTC, Lokal_Profil, Dvorapa, Aklapper,
pywikibot-bugs-list, Xqt, Viztor, DannyS712, Wenyi, Tbscho, MayS, Framawiki,
Mdupont, JJMC89, Altostratus, Avicennasis, mys_721tx, jayvdb, Masti,
Alchimista, Rxy
_______________________________________________
pywikibot-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
