Éric Araujo <mer...@netwok.org> added the comment: I don’t understand Fred’s replies.
> The scope of this document is much larger than Python's documentation, > but extends to all projects written in Python that use Sphinx as their > documentation tool. Really? docs.python.org/documenting is much smaller that sphinx.pocoo.org, and only seems to cover documenting Python, not any Python project. > With that, it makes sense to keep it as part of the documentation for > users of Python. I don’t follow. You’re saying that since the document also covers other projects than Python, it makes sense to include it in the Python docs? IMO, the criterion for the devguide is to have version-independent documents in one place instead of needlessly including them with CPython and having to sync across versions. For the Documenting Python docs, if they contain version-specific instructions, or if they contain instructions needed in a CPython tarball, then they’re in the right place, otherwise they could move to the devguide. ---------- nosy: +eric.araujo _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12409> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
