当我尝试使用.open时,Python Mechanize一直给我"response_seek_wrapper" [英] Python Mechanize keeps giving me 'response_seek_wrapper' when I try to use .open

查看:72
本文介绍了当我尝试使用.open时,Python Mechanize一直给我"response_seek_wrapper"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我不确定发生了什么,因为脚本曾经起作用(在我在系统上弄乱python之前……)

I'm not sure what's going on, as the script used to work (before I messed around with my python on my system...)

但是当我尝试类似的方法

But when I try something along the lines of

import mechanize
browser = mechanize.Browser()
browser.open("http://google.com")

我得到类似

<response_seek_wrapper at 0x10123fd88 whose wrapped object = <closeable_response at 0x101232170 whose fp = <socket._fileobject object at 0x1010bf5f0>>>

有人知道这是为什么吗?解决方法是什么?

Does anyone know why this is and what the fix is?

谢谢!

推荐答案

这也不例外,是吗?
没发生任何错误,您只得到了一个返回值,该值本质上是一个响应对象,等效于br.response().

it's not an exception, is it?
nothing wrong is happening, you just got a return value, which is esentially a response object, equivalent to br.response().

请参见

>>> r = browser.open("http://google.com")
>>> r
<response_seek_wrapper at 0x9bb116c whose wrapped object = <closeable_response at 0x9bb426c whose fp = <socket._fileobject object at 0x9ba306c>>>
>>> r.info().headers
# see the response headers

vs

>>> browser.open("http://google.com")
>>> browser.response()
<response_seek_wrapper at 0x9c229cc whose wrapped object = <closeable_response at 0x9bb426c whose fp = <socket._fileobject object at 0x9ba306c>>>
>>> browser.response().info().headers
# see the response headers

这篇关于当我尝试使用.open时,Python Mechanize一直给我"response_seek_wrapper"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆