Re: python newbie

"Bruno Desthuilliers" wrote:

functions are *not* methods of their module.

Now I am confused - if I write:

result = foo.bar(param)

Then if foo is a class, we probably all agree that bar is
a method of foo.

But the same syntax would work if I had imported some
module as foo.

So what's the difference ? Why can't bar be called a method
of foo, or is it merely a convention that classes have
methods and modules have functions?

Note that I am purposely refraining from mentioning a module
that has a class that has a method.

- Hendrik

.

Relevant Pages

  • Re: Insert with response
    ... FooBar, there's no way and no need to put them in synch. ... column in the foo table to 250 calumns in the bar table. ... set statistics time off ...
    (microsoft.public.sqlserver.programming)
  • Re: Magic function
    ... processing objects created in root at depth 3 ... root obj2 at depth 3 ... processing objects created in foo at depth 2 ... processing objects created in bar at depth 0 ...
    (comp.lang.python)
  • Re: from __future__ import absolute_import ?
    ... foo not in bar ... Unfortunately this is a side effect of using the os's directory structure to represent a python "package" structure. ...
    (comp.lang.python)
  • Re: from __future__ import absolute_import ?
    ... foo not in bar ... A path below the package level is generally a good means to shoot ... to represent a python "package" structure. ...
    (comp.lang.python)
  • Re: how to deserialize variable element/node
    ... string bar; ... In the first deserialization case, bar = "sometimes a simple string is ... Your two XML fragments would have to be represented in an XML schema by ...
    (microsoft.public.dotnet.xml)