Message148273
| Author |
eric.araujo |
| Recipients |
brett.cannon, eli.bendersky, eric.araujo, ezio.melotti, ncoghlan, petri.lehtinen, pitrou, terry.reedy |
| Date |
2011年11月24日.16:22:41 |
| SpamBayes Score |
4.5513832e-05 |
| Marked as misclassified |
No |
| Message-id |
<1322151762.12.0.912835582666.issue13455@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> [...] The devguide is *already* too big. [...]
> The devguide was supposed to be something that you read quickly and easily, not an exhaustive
> reference of how development works. Or at least there should be a clear separation between the
> two (the guide part, and the reference part). [...]
> The devguide is *not* primarily for core developers. It's for new contributors who want to get
> set up, so that they don't give up in the absence of clear indications. [...]
Thanks Antoine, I was not aware of that or I had forgotten it. The old python.org/dev pages contained information for new and experienced core devs too, so I thought the devguide was intended to contain the same info. I’ll support a clearer separation between the guide and the reference, to make the devguide less overwhelming for new contributors but still complete for core devs. |
|