[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: Éric, thanks for spotting it: removed. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue12409] Moving "Documenting Python" to Devguide

Roundup Robot added the comment: New changeset 7167c04780ed by Sandro Tosi in branch '2.7': Issue: #12409: remove obsolete susp-entries http://hg.python.org/cpython/rev/7167c04780ed New changeset 153e32333aaa by Sandro Tosi in branch '3.2': Issue: #12409: remove obsolete susp-entries http://hg.

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo added the comment: Glad my action plan worked :) There are now obsolete entries in the Doc/tools/sphinxext/susp-ignored.csv file: All lines starting with “documenting” can be removed. -- ___ Python tracker

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: "Documenting Python" has been: - moved to devguide; http://hg.python.org/devguide/rev/5d4a90e568ed - removed from 2.7, 3.2 and default; http://hg.python.org/cpython/rev/8975f7d0fbf7 http://hg.python.org/cpython/rev/70c46599fb0e http://hg.python.org/cpy

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: On Sat, Jan 14, 2012 at 04:36, Éric Araujo wrote: > > Éric Araujo added the comment: > > I just replied to your python-dev email.  I think you can update 2.7 to use > Sphinx 1.0 as soon as you’re down to a handful of warnings. thanks! I've just updated 2.7 to s

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo added the comment: I just replied to your python-dev email. I think you can update 2.7 to use Sphinx 1.0 as soon as you’re down to a handful of warnings. When the migration is done, you can add the documenting doc to the devguide and send a message to pydev to tell people to not

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: Hi Éric, thanks for the review. On Fri, Jan 13, 2012 at 18:13, Éric Araujo wrote: > > Éric Araujo added the comment: > > About the devguide patch: > > a) The part about C roles and directives should probably mention version > specifics (:cmacro: for 2.7, :c:mac

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo added the comment: About the devguide patch: a) The part about C roles and directives should probably mention version specifics (:cmacro: for 2.7, :c:macro: for 3.x) — unless you make this bug dependent on updating Sphinx to 1.0 for 2.7 and then all versions use new-style :c:. b

[issue12409] Moving "Documenting Python" to Devguide

Georg Brandl added the comment: We'll probably have to redirect all /documenting in Apache anyway. -- ___ Python tracker ___ ___ Pyth

[issue12409] Moving "Documenting Python" to Devguide

Changes by Sandro Tosi : Added file: http://bugs.python.org/file24219/doc2devguide-cpython.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: Sure, sorry I didn't make it before; here attached the 2 patches, one against devguide, the other to default cpython repo. -- keywords: +patch Added file: http://bugs.python.org/file24218/doc2devguide-devguide.patch __

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo added the comment: Could you provide a single patch or publish your version somewhere to help reviews? For the CPython docs, I think just removing the whole of Doc/documenting would be okay, or if we expect that people will go to that URI we may leave a placeholder page with only

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: Hi, i'm at last back with some work to show; I've integrated all the "Documenting python" doc into devguide, and the commits are in this sandbox: http://hg.python.org/sandbox/morph-devguide/shortlog/a92d431ef749 (`documenting` branch). I took the files from def

[issue12409] Moving "Documenting Python" to Devguide

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue12409] Moving "Documenting Python" to Devguide

Changes by Adam Woodbeck : -- nosy: +adam.woodbeck ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue12409] Moving "Documenting Python" to Devguide

Georg Brandl added the comment: +1, and as Eric says, we can do it without changing versions of Sphinx used. -- ___ Python tracker ___ __

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo added the comment: My comment was ambiguous, let me rephrase it: I am in favor of moving cpython/Doc/documenting to the devguide. Then, in the devguide, I would like to remove all the doc that’s just duplicating the upstream Sphinx docs, keeping only links and Python-specific par

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: @Fred: thanks about it :) @Éric: I just want to have clear in mind what you mean; my original proposal was to move completely, the whole section "Documenting python" to devguide since it contains building instructions and how's the markup works for python. Is y

[issue12409] Moving "Documenting Python" to Devguide

Changes by Sandro Tosi : Removed file: http://bugs.python.org/file23005/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue12409] Moving "Documenting Python" to Devguide

Brett Cannon added the comment: +1 -- Added file: http://bugs.python.org/file23005/unnamed ___ Python tracker ___+1 ___ Python-bugs-l

[issue12409] Moving "Documenting Python" to Devguide

Ezio Melotti added the comment: +1 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo added the comment: >From IRC: After last being pressed on this, I got to thinking about it more. Back in the day, that's all the doc there was about the tool-chain. With Sphinx standing as a successful independent project, the tool documentation need no longer be part of any o

[issue12409] Moving "Documenting Python" to Devguide

Éric Araujo 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 sph

[issue12409] Moving "Documenting Python" to Devguide

Raymond Hettinger added the comment: I agree with Fred. -- nosy: +rhettinger resolution: -> rejected status: open -> closed ___ Python tracker ___ _

[issue12409] Moving "Documenting Python" to Devguide

Sandro Tosi added the comment: Hi Fred, thanks for your input! Let's see what others think, but I think that at the very least, the "Building the documentation" section (that seams very specific to python) should be moved into the devguide. -- ___

[issue12409] Moving "Documenting Python" to Devguide

Fred L. Drake, Jr. added the comment: -1 > Hi! We have the devguide now, and it should be the place where to look > for references and docs about contributing to Python, that means also > for the documentation. For information specific to the Python documentation itself, but not relevant to us

[issue12409] Moving "Documenting Python" to Devguide

New submission from Sandro Tosi : Hi! We have the devguide now, and it should be the place where to look for references and docs about contributing to Python, that means also for the documentation. In the official Python doc we have a section "Documenting Python" (http://docs.python.org/py3k/