Ezio Melotti added the comment: > Should I write a Makefile patch using the venv/install from pypi approach? > Or could somebody upload new versions to > http://svn.python.org/projects/external/?
I looked at this issue over the past few days and discussed briefly with Georg about it. The 3 main issues are: 1) Sphinx and its dependency have a 2to3-able source that needs to be converted to Python 3 before being used. Should this be done every time or should we provide the already converted source somewhere? 2) If we go for the latter, should it be on externals/ (which still uses SVN) or on a new hg repo? 3) since we don't actually need all the history, should we still just clone these repos or is it better to download the source only? IMHO for 1) it would be better to provide Python3-ready code. For 2) it would also be nice to get rid of the SVN dependency for the docs so if we are going to use a repo it might be better to make a new one on HG. For 3), I'm not sure it makes sense to use repos at all if we don't want the history. If we don't, we would have to put the files somewhere and write some code to download and extract the zip/tarball. OTOH, if we do, we will be able to use hg to clone and update the repo easily, and, if we still decide not to download the history, we can just use the zip/tarballs already provided by hg.python.org. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10224> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
