homepage

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 lemburg
Recipients brett.cannon, ezio.melotti, lemburg, ncoghlan, orsenthil, pitrou, r.david.murray, tshepang
Date 2013年09月13日.20:44:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5233793C.4080604@egenix.com>
In-reply-to <1379103802.7.0.904269766856.issue18967@psf.upfronthosting.co.za>
Content
On 13.09.2013 22:23, R. David Murray wrote:
> 
> R. David Murray added the comment:
> 
> Just to be clear: the reason I am opposed is that the audience for Misc/NEWS is different from the audience for commit messages, and I would prefer that the text reflect that. Mine do :)
I'm with David and -1 on auto-generating documentation that
is meant for Python users. Here's my take on the intentions
behind the various forms of documentation we have:
 * Commit messages only provide a very terse hint at what a
 particular patch set was meant for. The target audience
 is other core developers.
 * News entries explain these patches (there may be more than one
 for a particular issue or project) to Python programmers who
 need to know what to watch out for when upgrading to a new
 version.
 * The "What's New" document explains the reasoning and effects
 of major changes and gives a high level overview of what
 to expect in a new version.
 * Finally, the Python documentation, with it's "Version added"
 markers, provides details to application programmers who need
 to know how the new techniques work and when they were added
 (in order to determine which APIs they can use if they want to
 support multiple Python versions).
History
Date User Action Args
2013年09月13日 20:44:51lemburgsetrecipients: + lemburg, brett.cannon, ncoghlan, orsenthil, pitrou, ezio.melotti, r.david.murray, tshepang
2013年09月13日 20:44:51lemburglinkissue18967 messages
2013年09月13日 20:44:51lemburgcreate

AltStyle によって変換されたページ (->オリジナル) /