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 r.david.murray
Recipients Ludovic.Gasc, asvetlov, docs@python, r.david.murray
Date 2014-11-17.03:31:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1416195103.83.0.626052853135.issue22882@psf.upfronthosting.co.za>
In-reply-to
Content
The fact that it cost you a lot of time buttresses my point.  Any documentation we write is likely to get stale; it is only the downstream that knows when these things change and could maintain such a document.  And the easy answer is as Andrew indicated, which is maintained by downstream.  That said, if the various downstreams are using a unified set of names, then the equation would change.  The fact that you had separate sections for separate distributions argues that that is not (yet?) the case, though.

The build instructions in the devguide are more likely to be kept up to date, which is why I suggested we should cross link to them from the main build documentation.
History
Date User Action Args
2014-11-17 03:31:43r.david.murraysetrecipients: + r.david.murray, asvetlov, docs@python, Ludovic.Gasc
2014-11-17 03:31:43r.david.murraysetmessageid: <1416195103.83.0.626052853135.issue22882@psf.upfronthosting.co.za>
2014-11-17 03:31:43r.david.murraylinkissue22882 messages
2014-11-17 03:31:43r.david.murraycreate