[Python-Dev] Moving the developer docs?
fuzzyman at voidspace.org.uk
Thu Sep 23 13:45:04 CEST 2010
On 23/09/2010 11:11, Antoine Pitrou wrote:
> On Thu, 23 Sep 2010 00:29:51 -0400
> 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.
> Many parts of the library docs aren't version-specific either :)
> The dev docs may differ slightly from one version to another, for
> example if a version introduces some new possibilities for tooling, or
> far-reaching implementation changes (think Unladen Swallow).
> The practicality argument of being able to edit those docs without
> having to master a separate (pydotorg) workflow sounds quite strong to
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
More information about the Python-Dev