I finally got around to start testing some of my old apps with Python
2.3. I've had no problems so far, but I did get one intriging
warning. The following is from the Python Command Line:
Python 2.3c1 (#44, Jul 18 2003, 14:32:36) [MSC v.1200 32 bit (Intel)]
on win32
Type "help", "copyright" , "credits" or "license" for more information.[color=blue][color=green][color=darkred]
>>> import win32com.client
>>> ie=win32com.cli ent.DispatchEx( 'InternetExplor er.Application. 1')
>>> ie.Navigate('ht tp://webserver/SomePage.asp')
>>> print ie.ReadyState[/color][/color][/color]
D:\Py23\lib\sit e-packages\win32c om\client\dynam ic.py:446:
FutureWarning:
%u/%o/%x/%X of negative int will return a signed string in Python 2.4
and up
debug_attr_prin t("Getting property Id 0x%x from OLE object" %
retEntry.dispid )
4[color=blue][color=green][color=darkred]
>>>[/color][/color][/color]
The code works well, as can be seen by the returned result. But what
I want to know is what needs to be done to avoid any problems in the
future, with 2.4. Should I submit this to the Win32 extensions
project? Or is it so obvious that it will undoubtedly by resolved and
I shouldn't worry about it?
2.3. I've had no problems so far, but I did get one intriging
warning. The following is from the Python Command Line:
Python 2.3c1 (#44, Jul 18 2003, 14:32:36) [MSC v.1200 32 bit (Intel)]
on win32
Type "help", "copyright" , "credits" or "license" for more information.[color=blue][color=green][color=darkred]
>>> import win32com.client
>>> ie=win32com.cli ent.DispatchEx( 'InternetExplor er.Application. 1')
>>> ie.Navigate('ht tp://webserver/SomePage.asp')
>>> print ie.ReadyState[/color][/color][/color]
D:\Py23\lib\sit e-packages\win32c om\client\dynam ic.py:446:
FutureWarning:
%u/%o/%x/%X of negative int will return a signed string in Python 2.4
and up
debug_attr_prin t("Getting property Id 0x%x from OLE object" %
retEntry.dispid )
4[color=blue][color=green][color=darkred]
>>>[/color][/color][/color]
The code works well, as can be seen by the returned result. But what
I want to know is what needs to be done to avoid any problems in the
future, with 2.4. Should I submit this to the Win32 extensions
project? Or is it so obvious that it will undoubtedly by resolved and
I shouldn't worry about it?