"Alan McIntyre" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I suppose the "new code" emphasis may make writing a proposal to fix > bugs an exercise in futility. :)
I personally consider anything *you* write to be 'new code'. Let us see what Google thinks. Patches that other people have written would be 'old code', so merely reviewing such, no matter how useful to us, would seem to not meet the criteria. > I'll submit it anyway, Please do. To me, this project would be as useful to Google as many. > Although I didn't state it explicitly, my intention was to push each > item to completion, so that at the end bug+patch is closed with new code > checked into svn. Good intention. One think you can't do is the necessary review of your own patch. Perhaps you could get pre-commitments to review patches for particular bugs. Terry Jan Reedy _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
