[pywin32-checkins] pywin32/com/win32com readme.htm,1.15,1.16

[Mark H. <mha...@us...>]

Update of /cvsroot/pywin32/pywin32/com/win32com
In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv25507/com/win32com

Modified Files:
	readme.htm 
Log Message:
Lots of stuff from Roger's work on the py3k branch:

* Lots of string and 64bit enhancements, particularly
  in pythonwin which only accepted plain string objects
  in many cases.  pywintypes and some of the other extension
  code get cleanups in this area too.

* Consolidation of more structure conversions and other helpers
  into pywintypes.

* Additional pythonwin tooltip notification fixes.

* Some '#if (PY_VERSION_HEX < 0x03000000)' blocks have been
  incorporated, but in general, no py3k specific code has
  been merged yet.

* Better error handling in pythonwin; less exceptions should be 
  left lingering, be overridden or simply ignored.

* Drop support for pythoncom.__future_currency__ - the
  decimal module is now always used.  

* A couple of very early interface implementations are upgraded to have 
  unicode passed instead of strings - if you *implement* (not use) any
  of these interfaces, you may need to test to ensure you work when
  args are passed as unicode objects instead of strings.  Affected are
  IErrorLog, IPropertyBag, ICatInformation and IStorage.


Index: readme.htm
===================================================================
RCS file: /cvsroot/pywin32/pywin32/com/win32com/readme.htm,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** readme.htm	31 May 2005 12:36:02 -0000	1.15
--- readme.htm	13 Nov 2008 04:04:51 -0000	1.16
***************
*** 28,41 ****
  </p>
  <p>
! To ease the transition, from pywin32 build 205 a FutureWarning will be issued
! when your code fetches a COM currency object - but a tuple will still be
! returned.  However, if your code sets <code>pythoncom.__future_currency__ = True</code>,
! a warning will not be issued, and a decimal module object will be returned.
! At some undetermined point in the future (but not before build 208) the
! new behaviour will be the default.
! </p>
! <p>
! When supplying a COM currency object, you can supply either a decimal object
! or a tuple.  This issue only applies when pythoncom passes you a currency value
  </p>
  <p>
--- 28,35 ----
  </p>
  <p>
! Up until build 212, code could set <code>pythoncom.__future_currency__ = True</code>
! to force use of the decimal module, with a warning issued otherwise.  In 
! builds 213 and later, the decimal module is unconditionally used when
! pythoncon returns you a currency value.
  </p>
  <p>
***************
*** 55,58 ****
--- 49,59 ----
  
  <h3>Recent Changes</h3>
+ 
+ <h4>Lost of internal changes on the road to py3k</h4>
+ 
+ <h4>win32com.axcontrol and win2con.internet</h4>
+ Many more interfaces for hosting AX controls and the interfaces
+ used by Internet Explorer.
+ 
  <h4>win32com.shell</h4>
  The shell interfaces have undergone a number of enhancements and changes.