On Thursday, June 16, 2011 9:02:45 AM UTC-4, Andrew Berg wrote:
> On 2011.06.15 08:57 AM, Zach Dziura wrote:
> > Just repeat this to yourself: Python ISN'T Java.
> class MainClass:
> def public static void main(*args):
> print('Am I doin' it right?')
>
> :P
>
> Or something like that.
On 2011.06.15 08:57 AM, Zach Dziura wrote:
> Just repeat this to yourself: Python ISN'T Java.
class MainClass:
def public static void main(*args):
print('Am I doin' it right?')
:P
Or something like that. I've forgotten almost everything I learned about
Java.
--
http://mail.python.org
Zach Dziura wrote:
> Just repeat this to yourself: Python ISN'T Java
I never had to do anything in Java. But mostly something in Sumatra :D
I'm getting the point that I'll need class very seldom.
Only to understand some more the use of self, whether I'll use a class.
--
goto /dev/null
--
http:
> On Jun 15, 7:57 am, TheSaint wrote:
> Hello
> sorry, I'm bit curious to understand what could be the difference to pack up
> a class for some number of functions in it and a simple module which I just
> import and use the similar functions?
> The only perspective that I think of is that class mi
In article ,
TheSaint wrote:
> Hello
> sorry, I'm bit curious to understand what could be the difference to pack up
> a class for some number of functions in it and a simple module which I just
> import and use the similar functions?
If all you have is a bunch of functions, just sticking them
Hello
sorry, I'm bit curious to understand what could be the difference to pack up
a class for some number of functions in it and a simple module which I just
import and use the similar functions?
The only perspective that I think of is that class might instantiate a
function several time. For m
