[Python-checkins] python/dist/src/Misc NEWS,1.654,1.655

[gvanrossum@users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Misc
In directory sc8-pr-cvs1:/tmp/cvs-serv24803

Modified Files:
	NEWS 
Log Message:
Issue a warning when int('0...', 0) returns an int with the sign
folded; this will change in Python 2.4.  On a 32-bit machine, this
happens for 0x80000000 through 0xffffffff, and for octal constants in
the same value range.  No warning is issued if an explicit base is
given, *or* if the string contains a sign (since in those cases no
sign folding ever happens).


Index: NEWS
===================================================================
RCS file: /cvsroot/python/python/dist/src/Misc/NEWS,v
retrieving revision 1.654
retrieving revision 1.655
diff -C2 -d -r1.654 -r1.655
*** NEWS	12 Feb 2003 17:05:26 -0000	1.654
--- NEWS	12 Feb 2003 20:48:22 -0000	1.655
***************
*** 11,15 ****
  
  Core and builtins
! -----------------
  
  - Through a bytecode optimizer bug (and I bet you didn't even know
--- 11,15 ----
  
  Core and builtins
! ----------------
  
  - Through a bytecode optimizer bug (and I bet you didn't even know
***************
*** 24,27 ****
--- 24,34 ----
    value, but according to PEP 237 it really needs to be 1 now.  This
    will be backported to Python 2.2.3 a well.  (SF #660455)
+ 
+ - int(s, base) sometimes sign-folds hex and oct constants; it only
+   does this when base is 0 and s.strip() starts with a '0'.  When the
+   sign is actually folded, as in int("0xffffffff", 0) on a 32-bit
+   machine, which returns -1, a FutureWarning is now issued; in Python
+   2.4, this will return 4294967295L, as do int("+0xffffffff", 0) and
+   int("0xffffffff", 16) right now.  (PEP 347)
  
  - super(X, x): x may now be a proxy for an X instance, i.e.