Message178486
| Author |
sandro.tosi |
| Recipients |
docs@python, georg.brandl, sandro.tosi, tshepang |
| Date |
2012年12月29日.12:57:52 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAB4XWXz=9e7mgUax7uGLkYRaeGNeJjKyq9jcVVcMPaGV9Y4UnQ@mail.gmail.com> |
| In-reply-to |
<CAA77j2Br3gWzWmd0GWsbt12jqt2jNnX3nh5=iyS_sXddVAgf8Q@mail.gmail.com> |
| Content |
On Sat, Dec 29, 2012 at 4:33 AM, Tshepang Lekhonkhobe
<report@bugs.python.org> wrote:
> It is my preference to be able to build all of CPython with the
> already-installed distro packages, instead of pulling in foreign ones.
IMO, I think with a project as bit as CPython, you should leave you
personal preferences apart and use (as much as possible) the tools the
project has decided to use: having a consistent set of tools to build
doc across everyone/everything (like auto-build doc machines) trying
to generate the doc is the proper way to handle it.
> Any reason why not use later versions?
no-one has done the work of testing, preparation and migration: do you
volunteer? :)
> Can't the docs be written such
> that they can run on various versions of these tools anyway?
Not always, but of course, as Georg said, if for note directive we can
have a syntax working with current and higher versions of
sphinx/docutils, that's ok to do it.
I only think that using a non-standard set of doc-build-tools is to be
discouraged, and sticking to what Makefile will fetch is the proper
way to build the doc and contribute to it.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi |
|