> On May 2, 4:14 am, Sebastian Wiesner wrote:
>> >
>> > In either case, I think you're picking a nit so small that it isn't
>> > actually there. All objects are instances (in Python), and all
>> > instances are objects.
>>
>> Exactly, so strictly seen, "Request object" could possibly refer to th
On May 2, 4:14 am, Sebastian Wiesner wrote:
> > I don't understand your objection. Is it that the
> documentation calls it
> > Request instead of urllib2.Request? Or that it calls it an object instead
> > of an instance?
>
> I guess the latter ...
>
> > In either case, I think you're picking a ni
In message , grocery_stocker wrote:
> req is clearly an instance of urllib2.Request and not a Request object.
"Object" is a term commonly used to mean "instance of a class". In Python,
classes are also objects, but if classes were meant rather than instances, I
imagine it would say so.
--
http
> I don't understand your objection. Is it that the documentation calls it
> Request instead of urllib2.Request? Or that it calls it an object instead
> of an instance?
I guess the latter ...
> In either case, I think you're picking a nit so small that it isn't
> actually there. All objects are i
On Fri, 01 May 2009 13:02:59 -0700, grocery_stocker wrote:
> I don't get how urllib2.urlopen() can take a Request object. When I do
> the following
>
> [cdal...@localhost ~]$ python
> Python 2.4.3 (#1, Oct 1 2006, 18:00:19) [GCC 4.1.1 20060928 (Red Hat
> 4.1.1-28)] on linux2 Type "help", "co
On 5/1/2009 1:02 PM grocery_stocker said...
At the following url...
http://docs.python.org/library/urllib2.html
They have the following...
"urllib2.urlopen(url[, data][, timeout])
Open the URL url, which can be either a string or a Request
object"
I don't get how urllib2.urlopen() can ta
