Message166972
| Author |
eli.bendersky |
| Recipients |
Ramchandra Apte, amak, eli.bendersky, eric.araujo, ezio.melotti, georg.brandl, giampaolo.rodola, hynek, ncoghlan, pmoody, python-dev, sandro.tosi, serhiy.storchaka, terry.reedy, tshepang |
| Date |
2012年07月31日.08:00:34 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1343721635.35.0.609235244933.issue14814@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
FWIW I would prefer this HOWTO to be part of the document itself. Splitting a document to two parts and keeping them separated is problematic exactly for the same reasons as external documentation in general - it can be forgotten when things get updated.
HOWTOs are good to discuss concepts that don't pertain to a specific modules, and so there is no other "natural" place to place them. Tutorials that only discuss a single module belong in its doc page together with the reference - I think there are plenty of examples in the stdlib docs where this is the case. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年07月31日 08:00:35 | eli.bendersky | set | recipients:
+ eli.bendersky, georg.brandl, terry.reedy, ncoghlan, giampaolo.rodola, amak, ezio.melotti, eric.araujo, pmoody, sandro.tosi, tshepang, python-dev, Ramchandra Apte, hynek, serhiy.storchaka |
| 2012年07月31日 08:00:35 | eli.bendersky | set | messageid: <1343721635.35.0.609235244933.issue14814@psf.upfronthosting.co.za> |
| 2012年07月31日 08:00:34 | eli.bendersky | link | issue14814 messages |
| 2012年07月31日 08:00:34 | eli.bendersky | create |
|