[Python-checkins] CVS: python/dist/src/Lib/test/output test_unicode,1.4,1.5

Wed, 5 Apr 2000 16:11:51 -0400 (EDT)

Update of /projects/cvsroot/python/dist/src/Lib/test/output
In directory eric:/home/guido/hp/mal/py-patched/Lib/test/output
Modified Files:
	test_unicode 
Log Message:
Marc-Andre's third try at this bulk patch seems to work (except that
his copy of test_contains.py seems to be broken -- the lines he
deleted were already absent). Checkin messages:
New Unicode support for int(), float(), complex() and long().
- new APIs PyInt_FromUnicode() and PyLong_FromUnicode()
- added support for Unicode to PyFloat_FromString()
- new encoding API PyUnicode_EncodeDecimal() which converts
 Unicode to a decimal char* string (used in the above new
 APIs)
- shortcuts for calls like int(<int object>) and float(<float obj>)
- tests for all of the above
Unicode compares and contains checks:
- comparing Unicode and non-string types now works; TypeErrors
 are masked, all other errors such as ValueError during
 Unicode coercion are passed through (note that PyUnicode_Compare
 does not implement the masking -- PyObject_Compare does this)
- contains now works for non-string types too; TypeErrors are
 masked and 0 returned; all other errors are passed through
Better testing support for the standard codecs.
Misc minor enhancements, such as an alias dbcs for the mbcs codec.
Changes:
- PyLong_FromString() now applies the same error checks as
 does PyInt_FromString(): trailing garbage is reported
 as error and not longer silently ignored. The only characters
 which may be trailing the digits are 'L' and 'l' -- these
 are still silently ignored.
- string.ato?() now directly interface to int(), long() and
 float(). The error strings are now a little different, but
 the type still remains the same. These functions are now
 ready to get declared obsolete ;-)
- PyNumber_Int() now also does a check for embedded NULL chars
 in the input string; PyNumber_Long() already did this (and
 still does)
Followed by:
Looks like I've gone a step too far there... (and test_contains.py
seem to have a bug too).
I've changed back to reporting all errors in PyUnicode_Contains()
and added a few more test cases to test_contains.py (plus corrected
the join() NameError).
Index: test_unicode
===================================================================
RCS file: /projects/cvsroot/python/dist/src/Lib/test/output/test_unicode,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** test_unicode	2000年03月28日 20:29:56	1.4
--- test_unicode	2000年04月05日 20:11:19	1.5
***************
*** 4,5 ****
--- 4,6 ----
 Testing Unicode formatting strings... done.
 Testing builtin codecs... done.
+ Testing standard mapping codecs... 0-127... 128-255... done.