I'm sorry I haven't been able to reply topython tutor, I was wondering couldyou
guys send me some beginner issuesthat get straight to basic problems.
Beginners have when starting pythonand using it as a scripting language. And
nothing else because I'm thinking thats the only way to use it when game
designing.please reply
> From: tutor-requ...@python.org
> Subject: Tutor Digest, Vol 69, Issue 73
> To: tutor@python.org
> Date: Mon, 16 Nov 2009 13:39:38 +0100
>
> Send Tutor mailing list submissions to
> tutor@python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.python.org/mailman/listinfo/tutor
> or, via email, send a message with subject or body 'help' to
> tutor-requ...@python.org
>
> You can reach the person managing the list at
> tutor-ow...@python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tutor digest..."
>
>
> Today's Topics:
>
>1. Re: GzipFile has no attribute '__exit__' (Sander Sweers)
>2. Re: Writing code while tired, counterproductive?
> (Albert-Jan Roskam)
>3. Re: I love python / you guys :) (Luke Paireepinart)
>4. Re: GzipFile has no attribute '__exit__' (Kent Johnson)
>
>
> --
>
> Message: 1
> Date: Mon, 16 Nov 2009 13:15:32 +0100
> From: Sander Sweers
> To: Dave Angel
> Cc: Python Tutor mailing list
> Subject: Re: [Tutor] GzipFile has no attribute '__exit__'
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
> 2009/11/16 Dave Angel :
> > Alternatively, you could subclass it, and write your own. ?At a minimum, the
> > __exit__() method should close() the stream.
>
> This triggered my to dig into this a bit. This is not fixed untill
> python 3.1 but seems easilly added to the ZipFile class. My attempt to
> backport this from python 3.1's gzip.py below seems to work.
>
> Greets
> Sander
>
> import gzip
>
> class myGzipFile(gzip.GzipFile):
> def __enter__(self):
> if self.fileobj is None:
> raise ValueError("I/O operation on closed GzipFile object")
> return self
>
> def __exit__(self, *args):
> self.close()
>
> zfilepath = r'C:\test.gz'
> s = 'This is a test'
>
> with myGzipFile(zfilepath,'w') as output:
> output.write(s)
>
>
> --
>
> Message: 2
> Date: Mon, 16 Nov 2009 04:17:51 -0800 (PST)
> From: Albert-Jan Roskam
> To: OkaMthembo , Luke Paireepinart
>
> Cc: tutor@python.org
> Subject: Re: [Tutor] Writing code while tired, counterproductive?
> Message-ID: <940960.30630...@web110706.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I find that switching to a completely different approach or strategy becomes
> more difficult when tired. Depending on the context, that could be called
> persistence of perseverence (begin good or bad, respectively).?However, in my
> opinion, not being able to view things from a different angle is usually
> counterproductive.
>
> Cheers!!
> Albert-Jan
>
> ~~
> In the face of ambiguity, refuse the temptation to guess.
> ~~
>
> --- On Mon, 11/16/09, Luke Paireepinart wrote:
>
>
> From: Luke Paireepinart
> Subject: Re: [Tutor] Writing code while tired, counterproductive?
> To: "OkaMthembo"
> Cc: tutor@python.org
> Date: Monday, November 16, 2009, 9:56 AM
>
>
> I hate to be the odd one out here, but I actually find that I am extremely
> productive when I'm tired.? It's easier for me to commit completely to the
> code, when I'm well-rested I dream about running through fields of sunflowers
> and such, get distracted more easily.? The code I write when I'm tired is
> usually of marginally worse quality, but it's usually easy to audit it when
> I'm rested and fix any problems.? Although if I'm trying to solve something
> particularly difficult, especially something I've never done before,
> sometimes I won't be able to do it until I wake up a bit.? Note that this is
> for being tired, not exhausted.? If I'm exhausted I write a whole lot of
> awful code that I have to completely rewrite when I wake up.
>
>
> On Mon, Nov 16, 2009 at 12:57 AM, OkaMthembo wrote:
>
> >From first-hand experience, i would concur :)
>
> A refreshed mind will perform much better than an over-exerted one.
>
>
>
>
>
> On Sat, Nov 14, 2009 at 8:57 PM, Alan Gauld wrote:
>
>
> "Modulok" wrote
>
>
> Does anyone else find, writing code while tired to be counterproductive?
>
> Yes. Doing anything that is mentally taxing is usually a bad idea when tired!
>
> Alan G
>
> ___
> Tutor maillist ?- ?tu...@python.org
> To unsubscribe or change subscription options:
> http://mail.python.org/mailman/listinfo/tutor
>
>
>
> --
> Regards,
> Lloyd