| Lokal_Profil added a comment. |
In T106121#2802405, @Magul wrote:I Your case if You don't want to maintain Your code, You can pin to particular version/pypi release of library, and if You want to use new features You can just use virtualenvs to execute particular code with particular library's version. I believe You're aware of this possibilities. It will require a little more work from Your side as library user, but it will add significant change in development velocity for library maintainers (and as You know there are over 700 issues in backlog, where the oldest one live in it for more than 2 years).
While we have only infrequent releases of the library using the pypi version is in my opinion not really a realistic solution. 2.0 is currently 1990 commits behind master and I know of at least some of them which fix breaking upstream changes, but the lag means it is getting painful to try to port them.
While we don't have some type of frequent versioned releases I would say it is difficult to get rid of the deprecated code. Now if we get (semantic) versioned releases rolling then it should be possible to set some general rules for on which version changes it is ok to drop deprecated code (or after a certain number of changes of that type).
Cc: Magul, TerraCodes, Legoktm, Luke081515, hashar, Jay8g, Dalba, Lokal_Profil, StudiesWorld, Multichill, valhallasw, jayvdb, XZise, Ricordisamoa, Aklapper, Xqt, pywikibot-bugs-list, MayS, Mdupont, JJMC89, fbstj, Masti, Alchimista, Rxy
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
