[Patches] Warnings in pythonrun.c

Barry A. Warsaw bwarsaw@python.org
Wed, 21 Jun 2000 13:59:36 -0400 (EDT)


>>>>> "TP" == Tim Peters <tim_one@email.msn.com> writes:

    TP> + Is there any way to search the patches archive directly

No.
    
    TP> (only way I know is to go to the main python.org search page,
    TP> and check the "SIG archives" box, and that too often turns up
    TP> way too many irrelevant hits from archives other than
    TP> patches)?

Sadly, that's the way to do it.  You could try narrowing it down by
including the word `patches' though.

    TP> + Directed mostly to my PythonLabs co-conspirators: what can
    TP> we do to clean up the patches mess?  I'm scanning the
    TP> archives, and have no idea what has & hasn't been checked in,
    TP> or, when I do <wink>, no idea which of the unchecked-in
    TP> patches should be checked in.  Before Guido's honeymoon there
    TP> was talk of assigning areas of responsibility, and I don't see
    TP> any other way to make progress: someone has to own the
    TP> problems.  Implying we also need to assign an owner to each
    TP> patch that comes in.

    TP> + This mailing list doesn't work.  At least the SourceForge
    TP> patch manager has an "assigned to" slot, a per-patch
    TP> discussion history, and a status classification (open,
    TP> accepted, etc).  I'm sure it sucks in ways I don't know about
    TP> yet (I do know that the interface is s-l-o-w), but better the
    TP> devil you don't know ...

I think we have to start using the patch manager.  If it sucks we'll
either submit requests to the SF folks or expend some effort on
checking out Roundup.

-Barry