[Python-Dev] Moving the developer docs?

Georg Brandl g.brandl at gmx.net
Thu Sep 23 08:40:21 CEST 2010


That's right.  It is true that it isn't branch-specific information,
and that does cause a little bit of irritation for me too, but neither
is Misc/developers.txt or Misc/maintainers.rst.

Of course, we might consider a separate HG repository (I'm all in favor
of many small repos, instead of a gigantic sandbox one).  The downside
is that I really like the developer docs at docs.python.org, and it
would complicate the build process a bit.

Georg

Am 23.09.2010 06:45, schrieb Brett Cannon:
> A discussion occurred (w/o me) on #python-dev where moving it to Doc/
> would allow it to show up at docs.python.org to perhaps get more
> people involved. It also allows developers to contribute to the docs
> w/o having to get pydotorg commit rights.
> 
> On Wed, Sep 22, 2010 at 21:29, Fred Drake <fdrake at acm.org> wrote:
>> On Wed, Sep 22, 2010 at 10:38 PM, Brett Cannon <brett at python.org> wrote:
>>> the first thing on the agenda is a complete rewrite of the developer
>>> docs and moving them into the Doc/ directory
>>
>> I'd like to know why you think moving the developer docs into the
>> CPython tree makes sense.
>>
>> My own thought here is that they're not specific to the version of
>> Python, though some of the documentation deals with the group of
>> specific branches being maintained.  For me, keeping them in a
>> separate space (like www.python.org/dev/) makes sense.
>>
>>
>>   -Fred
>>
>> --
>> Fred L. Drake, Jr.    <fdrake at acm.org>
>> "A storm broke loose in my mind."  --Albert Einstein
>>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org


-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.



More information about the Python-Dev mailing list