[issue12711] Explain tracker components in devguide

[Ezio Melotti]

Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Attached a new patch.
I addressed most of your comments.
AFAICT there are no extension modules in Lib.  All the C modules are in Modules, and if they also have a Python "frontend", that's in Lib.  I think the point of having Extension Modules and Library is to distinguish between C modules and Python modules.

I split the "Tests" component in two different entries:
  1) about our tests, regrtest and test/support.py;
  2) unittest/doctest;
I think the "Tests" component applies to both, and for unittest/doctest it can be used together with "Library".

Listing the paths is both good for people that are submitting ("the error comes from this module"), and for people fixing it ("this component is selected, I should look in that module").

----------
Added file: http://bugs.python.org/file22870/issue12711-2.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12711>
_______________________________________