[Python-Dev] What to do with languishing patches?

[Alexander Belopolsky]

On Mon, Jul 19, 2010 at 11:55 PM, Mark Lawrence <breamoreboy at yahoo.co.uk> wrote:
..
> Is this the same login as for the issue tracker or is a new one needed?
>

AFAIK, it is separate.

> I also suspect that subsections for Extension Modules would be extremely
> useful for our C developers, thoughts anybody?

Well, with the current trend of making extensions an optional fast
reimplementation of library modules, the distinction between Lib and
Extension Modules gets blurred.   For example,
http://bugs.python.org/issue1062277, "Pickle breakage with reduction
of recursive structures" is a bug that affects both python and C
implementation of pickle module.  Should this be Lib or Extension
issue or both? (The issue is actually misclassified as "Interpreter
Core".)  I think it is both.  Here is a less clear example.  Suppose
someone reports a bug is time.strptime.  The time module is a C
extension, but strptime is implemented in a "hidden" python module,
_strptime.  How would you classify this issue?  If your head does not
spin yet, consider http://bugs.python.org/issue1677872, "Efficient
reverse line iterator".  When the patch was submitted, io module was
implemented in python, but since then it was reimplemented in C.

If we allow tagging issues with the module name, I would rather not
make distinction between C and python modules.   just make it one flat
list similar to the one in maintainers.txt.