> Testing conditions.
>
All replies - Spot on!
Much appreciated, apology for delay.
Ray.
--
http://mail.python.org/mailman/listinfo/python-list
Ray Gibbon wrote:
Before I resign myself to the inevitable, 'that's the way it is - get used
to it', I'd just like to scratch it once. But, before I try walking on very
thin ice, I want to ask whether there are expectations of some future
changes which address these issues?
I note PEP 3000 is sile
Ray Gibbon wrote:
> This is NOT another request for statements to be accepted as expressions for
> two reasons:-
> 1. I've seen enough arguments on the subject where I've found myself firmly
> on the anti change side.
> 2. I now realise that it might scratch the itch, but it would not cure it.
>
>
"Ray Gibbon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> e.g. 1
> |while new_data = get_more_data(source):
> |process_data(new_data)
>
> is obviously the sort of thing I'm missing, but it is not a general
> solution
> because :-
>
> e.g. 2
> |while new_data, env
On Thu, 10 Feb 2005 05:38:54 +, Ray Gibbon wrote:
> e.g. 2
> |while new_data, environment = get_more_data(source):
> |process_data(new_data, environment)
>
> is something I'm equally likely to want to do, but I can't express it's
> meaning.
I think we'd usually phrase that as
fo
Testing conditions.
Common scenario. Old programmer, new to Python, love it, but still
hankering after some of my old ways.
Of all of it's 'new to me' features, I appear to be enjoying 'no
declarations' and mixing types with abandon. In particular I find myself
writi
