| nichtich added a comment. |
Sure the sources work but I want to release a tool based on pywikibot. My current requirements.txt contains pywikibot but the latest version is 2.0rc5 without SPARQL features. I don't mind which version number but new features must be releases to be usable. Having unreleased features in a developer branch makes sense but these features are deployed at PAWS and documented (?). Without releases it is hard to tell whether and how some feature are available or not.
By the way, I just found out that I can refer to a specific state of code in requirements.txt like this:
git+git://github.com/wikimedia/pywikibot-core.git@COMMITHASH
But which commit is kind of stable (according to https://travis-ci.org/wikimedia/pywikibot-core/builds the code fails since month)? Checkout is also slow this way because each user has to download the full repository instead of a single state.
My current idea to work around the lack of releases is to pin 2.0rc5 in my requirements and copy the missing pieces of code from "current" pywikibot into my project if doable. So in order to use current features of pywikibot in a reliable, distributable way I seem to be forced to include a partial fork of it.
Cc: Framawiki, Magul, Aklapper, pywikibot-bugs-list, nichtich, Tbscho, MayS, Mdupont, JJMC89, jayvdb, Dalba, Masti, Alchimista, Rxy
_______________________________________________ pywikibot-bugs mailing list pywikibot-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
