On Sun, 13 Nov 2005, Beni Cherniavsky wrote: > Date: Sun, 13 Nov 2005 11:18:11 +0200 > From: Beni Cherniavsky <[EMAIL PROTECTED]> > To: guy keren <[EMAIL PROTECTED]> > Cc: Beni Cherniavsky <[EMAIL PROTECTED]>, [email protected] > Subject: Re: updated python material - start of python reference > > On Sun, 2005-11-13 at 09:14 +0200, guy keren wrote: > > On Sun, 13 Nov 2005, Beni Cherniavsky wrote: > > > > > * I'm introducing modules quite early - I had to, to allow them to > > > write the small games you mentioned.Should we perhaps say > > > something general about them before they are casually used? > > > > modules? i didn't say anything about modules. the plan sais nothing about > > modules. i don't want them to write modules at all. > > > > all the programs to be written this year will be in a singlefile, no > > 'module'. > > > > the only thing we need to teach them is 'import', since they are required > > to use 'sys', 'time' and perhaps a few others... > > > That's what I meant - I'm introducing ``import`` briefly in order for > them to access random.randrange() and time.sleep().My question was, > should I explain the ``import`` statement not so in-passing?
you're writing a reference - not a user manual. as such, you should emphasize on syntax and usage examples - not on explaining how commands work. i'll consider this issue when writing the slides of the first lecture that deals with import. i do not intend to delve into the issue of modules too deeply... -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy
