| jayvdb added a comment. |
no I havent explored VisTrails in detail. I will. But as I mentioned on T138140, vendoring does have serious cons on Python. Did you see the bugs I linked to? Yes, there is possibly a project to simplify the vendoring processes on Python correctly, and assist in ongoing maintenance of vendored libraries. I am not a fan of pip at all, and would prefer to have a vendored solution, but it doesnt currently exist. Also it would be outside the scope of Wikimedia Foundation to build that. However the Python Foundation is also part of GSOC, so it might be possible to run a project through them, or jointly with them, but the Python Foundation mostly sponsors projects for improving their own existing code (not anything like pip), and in my experience the key people in the Python community who would need to be on board would also be very opposed to anyone else running such a project.
But that debate and future possibility is not relevant to this GSOC project, as it is core requirement of that project (as described at T129611) to use pip(pypi) where possible, and using OS provided dependencies is an improvement on that as it allows build-only dependencies and build-only steps to be eliminated from the user concerns. e.g. cython to compile packages is not needed if the OS provides pre-compiled versions. And Q.A. and support has been done by the provider (pypi or OS), which reduces the maintenance burden on the pywikibot/pywikibot-catimages teams.
Cc: zhuyifei1999, jayvdb, AbdealiJK, Aklapper, pywikibot-bugs-list, DrTrigon, Zppix, Lethexie, Jay8g
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
