This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eli.bendersky
Recipients eli.bendersky, ezio.melotti, loewis, pitrou, python-dev
Date 2013-10-01.14:09:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda_M4ZVCqjWEvQJhzo2KFjrKnmYpPA2ZD_sX9j07C9MpZg@mail.gmail.com>
In-reply-to <1605047839.39400816.1380636013283.JavaMail.root@zimbra10-e2.priv.proxad.net>
Content
On Tue, Oct 1, 2013 at 7:00 AM, Antoine Pitrou <report@bugs.python.org>wrote:

>
> Antoine Pitrou added the comment:
>
> > I'm not sure a separate document is right here because that's one
> > more repository to have. The devguide already contains sections for
> > somewhat more esoteric things like compiler internals guide,
> > coverity scans. Besides, section 18 already has some material about
> > the buildbots.
>
> Well, ideally the more esoteric things wouldn't really be there.
>

I still see the current situation better than the previous one, where this
was scattered around PEPs, Wikis and just random web pages. Having it all
in the same repository is not ideal from a taxonomical point of view,
perhaps, but as a single collection of "everything related to the
development *of* Python" it's not too bad since keeping it in a single
place makes it easier to maintain and review; mostly, there's a somewhat
smaller chance that things will be forgotten and rot.

To put it differently, maintaining the devguide is kind-of a chore for devs
as it is; splitting it into multiple topical repositories will just make
the burden higher so we'll end up not maintaining it at all :)

> Perhaps other people have different opinions?
>
History
Date User Action Args
2013-10-01 14:09:30eli.benderskysetrecipients: + eli.bendersky, loewis, pitrou, ezio.melotti, python-dev
2013-10-01 14:09:30eli.benderskylinkissue19106 messages
2013-10-01 14:09:30eli.benderskycreate