[Python-checkins] CVS: python/nondist/peps pep-0230.txt,1.4,1.5

Guido van Rossum python-dev@python.org
Mon, 11 Dec 2000 08:50:13 -0800


Update of /cvsroot/python/python/nondist/peps
In directory slayer.i.sourceforge.net:/tmp/cvs-serv17521

Modified Files:
	pep-0230.txt 
Log Message:
Add responses to Barry's and Fred's concerns.  Message matching is now
case insensitive.


Index: pep-0230.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0230.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** pep-0230.txt	2000/12/11 16:34:34	1.4
--- pep-0230.txt	2000/12/11 16:50:11	1.5
***************
*** 181,185 ****
  
      - message is a compiled regular expression that the warning
!       message must match
  
      - module is a compiled regular expression that the module name
--- 181,185 ----
  
      - message is a compiled regular expression that the warning
!       message must match (the match is case-insensitive)
  
      - module is a compiled regular expression that the module name
***************
*** 265,269 ****
      - 'message' is a message string; matches warnings whose message
        text is an initial substring of 'message' (matching is
!       case-sensitive)
  
      - 'category' is an abbreviation of a standard warning category
--- 265,269 ----
      - 'message' is a message string; matches warnings whose message
        text is an initial substring of 'message' (matching is
!       case-insensitive)
  
      - 'category' is an abbreviation of a standard warning category
***************
*** 344,350 ****
  Rejected Concerns
  
!     Paul Prescod has brought up several additional concerns that I
!     feel aren't critical.  I address them here (the concerns are
!     paraphrased, not necessarily exactly Paul's words).
  
      - Paul: warn() should be a built-in or a statement to make it easily
--- 344,350 ----
  Rejected Concerns
  
!     Paul Prescod, Barry Warsaw and Fred Drake have brought up several
!     additional concerns that I feel aren't critical.  I address them
!     here (the concerns are paraphrased, not exactly their words):
  
      - Paul: warn() should be a built-in or a statement to make it easily
***************
*** 369,372 ****
--- 369,391 ----
  
        Response: I don't.
+ 
+     - Barry: It would be nice if lineno can be a range specification.
+ 
+       Response: Too much complexity already.
+ 
+     - Barry: I'd like to add my own warning action.  Maybe if `action'
+       could be a callable as well as a string.  Then in my IDE, I
+       could set that to "mygui.popupWarningsDialog".
+ 
+       Response: For that purpose you would override
+       warnings.showwarning().
+ 
+     - Fred: why do the Warning category classes have to be in
+       __builtin__?
+ 
+       Response: that's the simplest implementation, given that the
+       warning categories must be available in C before the first
+       PyErr_Warn() call, which imports the warnings module.  I see no
+       problem with making them available as built-ins.