[pywin32-bugs] [ pywin32-Bugs-2488784 ] Unicode exception when using ie.Navigate after dispatch

[SourceForge.net <no...@so...>]

Bugs item #2488784, was opened at 2009-01-06 08:11
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2488784&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: com
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mounir (merrami)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unicode exception when using ie.Navigate after dispatch

Initial Comment:
The situation: When using a IE browser after dispatch and navigating to a particular URL, the exception at the end of this note is observed
Important information: this is from the user of a commercial python program (provided as an executable) called CiteSmart. The error is observed very likely because th user is using a Corean version of Windows XP. This bug couldn't be reproduced on an english plate-form.

> Traceback (most recent call last):
> File "win32com\server\policy.pyo", line 285, in _Invoke_
> File "win32com\server\policy.pyo", line 290, in _invoke_
> File "win32com\server\policy.pyo", line 658, in _invokeex_
> File "win32com\server\policy.pyo", line 653, in
> _transform_args_
> : 'ascii' codec can't encode
> characters in position 0-1: ordinal not in

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2009-01-31 13:36

Message:
Oops - I meant policy.py.  If you check that file, you should find that
core_has_unicode is always True for all supported Python versions - so I
don't quite understand how we could have entered that block.  The next
win32com version will have removed it completely, but that still doesn't
explain how you are hitting this.

----------------------------------------------------------------------

Comment By: Mounir (merrami)
Date: 2009-01-31 12:17

Message:
Mark
thank you for taking time to review this issue.
Yes the line you mention is there in the file policy.py at the lines 652-3
(and not in transform.py).

The python version that was used is 2.5.1 (r251:54863)

If there is anything I can do to help, let me know.

Thank you for your amazing contribution and the excellent tools you
provide us with.


----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2009-01-31 10:22

Message:
This is very strange.  That error seems to be:

            elif not core_has_unicode and arg_type==UnicodeType:
                arg = str(arg)

and 'core_has_unicode' should *always* be True in recent builds.  What
version of Python are you using?  Can you please confirm that line 653 in
your transform.py does point at that code?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2488784&group_id=78018