Michelle - <br><br>A couple of weeks back I had encountered the same exact problem with the 'latin-1' v. 'utf-8' encoding issue. I posted the issue to the list and I caught Titus @ a bad time since he was @ PyCon. So after some digging (I didn't even see the post from Gabor about how to correct this), I came to the same conclusion as Gabor. At first I had tried to 'monkeypatch' a fix into my twill script like this:
<br><br><start_sample><br>import twill.other_packages.mechanize._html<br><br>def form_parser_args(<br> select_default=False,<br> form_parser_class=None,<br> request_class=None,<br> backwards_compat=False,
<br> encoding="utf-8"<br> ):<br> return get_args(locals())<br> <br>twill.other_packages.mechanize._html.form_parser_args=form_parser_args<br><end_sample><br><br>Unfortunately that didn't work and I was left to editing 'mechanize's' _html.py file which did fix my problem. I guess my remaining questions are:
<br><br>1. Anyone have an idea as to why my 'monkeypatch' doesn't work?<br>2. Is it correct to say that this is more of a 'mechanize' issue than a 'twill' issue? And if so, what can we do to correct the problem?<br><br>