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

Jack Jansen jackjansen@users.sourceforge.net
Fri, 15 Mar 2002 16:35:38 -0800


Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv23866

Modified Files:
	pep-0278.txt 
Log Message:
One more "t" replaced by "U".
Unicode is confirmed "newline-safe".


Index: pep-0278.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0278.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** pep-0278.txt	14 Mar 2002 22:47:31 -0000	1.4
--- pep-0278.txt	16 Mar 2002 00:35:36 -0000	1.5
***************
*** 111,120 ****
      I think there are no special issues with unicode. utf-16 shouldn't
      pose any new problems, as such files need to be opened in binary
!     mode anyway. Interaction with utf-8 I am not 100% sure about: is it
!     possible for a 0x0a or 0x0d byte to occur as part of a multibyte
!     escape without the stadnard meaning of CR or LF? I assume not,
!     because if such bytes are allowed it would mean that readline() on
!     Unix would terminate the read on a 0x0d (and on MacOS on a 0x0a)
!     without a full line being read.
  
      Universal newline files should work fine with iterators and
--- 111,116 ----
      I think there are no special issues with unicode. utf-16 shouldn't
      pose any new problems, as such files need to be opened in binary
!     mode anyway. Interaction with utf-8 is fine too: values 0x0a and 0x0d
!     cannot occur as part of a multibyte sequence.
  
      Universal newline files should work fine with iterators and
***************
*** 125,129 ****
      While universal newlines are automatically enabled for import they
      are not for opening, where you have to specifically say open(...,
!     "t"). This is open to debate, but here are a few reasons for this
      design:
  
--- 121,125 ----
      While universal newlines are automatically enabled for import they
      are not for opening, where you have to specifically say open(...,
!     "U"). This is open to debate, but here are a few reasons for this
      design: