[Python-checkins] python/nondist/peps pep-0003.txt,1.3,1.4

[mwh at users.sourceforge.net]

Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27052

Modified Files:
	pep-0003.txt 
Log Message:
Make this a little bit less hilariously out of date.

Index: pep-0003.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0003.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** pep-0003.txt	30 Sep 2002 01:55:41 -0000	1.3
--- pep-0003.txt	26 May 2004 16:10:30 -0000	1.4
***************
*** 15,18 ****
--- 15,25 ----
      expertise.
  
+     These are guidlines for the developers of Python, not the
+     submitters of bugs.  Those are at 
+ 
+         http://docs.python.org/lib/reporting-bugs.html
+ 
+     (though this hardly seems the best place).
+ 
  
  Guidelines
***************
*** 28,31 ****
--- 35,40 ----
         saying that this is the case (mentioning the PEP explicitly).
  
+        XXX do we prefer the feature request tracker or PEP 42?
+ 
      3. Assign the bug a reasonable priority.  We don't yet have a
         clear sense of what each priority should mean, except than 9 is
***************
*** 34,41 ****
  
      4. If a bug report doesn't have enough information to allow you to
!        reproduce or diagnose it, send email to the original submittor
!        and ask for more information.  If the original report is really
!        thin and your email doesn't get a response after a reasonable
!        waiting period, you can close the bug.
  
      5. If you fix a bug, mark the status as "Fixed" and close it.  In
--- 43,50 ----
  
      4. If a bug report doesn't have enough information to allow you to
!        reproduce or diagnose it, ask the original submitter for more
!        information.  If the original report is really thin and your
!        email doesn't get a response after a reasonable waiting period,
!        you can close the bug.
  
      5. If you fix a bug, mark the status as "Fixed" and close it.  In
***************
*** 45,52 ****
         change.
  
!     6. If you are assigned a bug that you are unable to deal with
!        assign it to someone else.  The guys at PythonLabs get paid to
!        fix these bugs, so pick one of them if there is no other
!        obvious candidate.
  
  
--- 54,60 ----
         change.
  
!     6. If you are assigned a bug that you are unable to deal with,
!        assign it to someone else if you think they will be able to
!        deal with it, otherwise it's probably best to unassign it.