[Python-checkins] CVS: python/dist/src/Misc ACKS,1.98.2.1,1.98.2.2 NEWS,1.189.2.5,1.189.2.6
Tim Peters
tim_one@users.sourceforge.net
Wed, 01 Aug 2001 19:40:45 -0700
Update of /cvsroot/python/python/dist/src/Misc
In directory usw-pr-cvs1:/tmp/cvs-serv23606/descr/dist/src/Misc
Modified Files:
Tag: descr-branch
ACKS NEWS
Log Message:
Mrege of trunk tag delta date2001-07-30 to date2001-08-01.
Index: ACKS
===================================================================
RCS file: /cvsroot/python/python/dist/src/Misc/ACKS,v
retrieving revision 1.98.2.1
retrieving revision 1.98.2.2
diff -C2 -d -r1.98.2.1 -r1.98.2.2
*** ACKS 2001/07/28 05:02:59 1.98.2.1
--- ACKS 2001/08/02 02:40:43 1.98.2.2
***************
*** 311,314 ****
--- 311,315 ----
Dan Pierson
François Pinard
+ John Popplewell
Amrit Prem
Paul Prescod
Index: NEWS
===================================================================
RCS file: /cvsroot/python/python/dist/src/Misc/NEWS,v
retrieving revision 1.189.2.5
retrieving revision 1.189.2.6
diff -C2 -d -r1.189.2.5 -r1.189.2.6
*** NEWS 2001/07/30 04:08:14 1.189.2.5
--- NEWS 2001/08/02 02:40:43 1.189.2.6
***************
*** 9,12 ****
--- 9,16 ----
Core
+ - Warnings about a mismatch in the Python API during extension import
+ now use the Python warning framework (which makes it possible to
+ write filters for these warnings).
+
Library
***************
*** 20,23 ****
--- 24,41 ----
C API
+
+ - Two new APIs PyOS_snprintf() and PyOS_vsnprintf() were added
+ which provide a cross-platform implementations for the
+ relatively new snprintf()/vsnprintf() C lib APIs. In contrast to
+ the standard sprintf() and vsprintf() C lib APIs, these versions
+ apply bounds checking on the used buffer which enhances protection
+ against buffer overruns.
+
+ - Unicode APIs now use name mangling to assure that mixing interpreters
+ and extensions using different Unicode widths is rendered next to
+ impossible. Trying to import an incompatible Unicode-aware extension
+ will result in an ImportError. Unicode extensions writers must make
+ sure to check the Unicode width compatibility in their extensions by
+ using at least one of the mangled Unicode APIs in the extension.