On Sat, Jul 12, 2008 at 9:47 AM, Paul Melvin
<[EMAIL PROTECTED]> wrote:
> And how can i go about testing that i get appropriate values during the
> testing/building phase (generally speaking), is it lots of print/return
> statements and then remove them?
Take a look at the doctest and unittest mo
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Alan Gauld
> Sent: 12 July 2008 18:08
> To: tutor@python.org
> Subject: Re: [Tutor] Classes v2, thoughts/suggestions please
>
>
> "Paul Melvin" <[EMAIL PROTECT
"Paul Melvin" <[EMAIL PROTECTED]> wrote
i have come up with a working class for a square,
Well done. It might not be the most elegant solution on the
inside but it isn't too bad from the users point of view and thats
what you should aim for IMHO.
I was thinking about using *args to get may
Thanks to Alans insights i have come up with a working class for a square,
overcomplicated probably but it lays the groundwork for my polygon class
which will iterate over something to generate an n-sided polygon.
If anyone is interested in actually running/testing this you need to get
hold of pgyl
