Issue 49 in twill: upgrade to new mechanize
codesite...@google.com
Owner: nat.williams
CC: the.good.doctor.is.in
Labels: Type-Enhancement Priority-Medium Milestone-Release0.9.2 mechanize
New issue 49 by zerbie: upgrade to new mechanize
http://code.google.com/p/twill/issues/detail?id=49
I realize .1.11 has been dropped in. Could you take a look at _browser.py
and figure out if we still need to wrap everything in
PatchedMechanizeBrowser now that we have a new mechanize?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Comment #1 on issue 49 by nat.williams: upgrade to new mechanize
http://code.google.com/p/twill/issues/detail?id=49
for now, or at least for this release, PatchedMechanizeBrowser should
stay. Pulling
it out causes the refresh and wsgi_intercept tests to fail, so I'm not
going to mess
with it.
codesite...@google.com
Status: Done
Labels: -Type-Enhancement Type-Task
Comment #2 on issue 49 by zerbie: upgrade to new mechanize
http://code.google.com/p/twill/issues/detail?id=49
okay. i'll put something in to take another look for 1.0. thanks!