PythonLabs Team Moves to ActiveState

[Sheila King]

On Sat, 31 Mar 2001 17:58:49 -0800, "Emile van Sebille" <emile at fenx.com> wrote
in comp.lang.python in article <9a626p$3qrct$1 at ID-11957.news.dfncis.de>:

:I
:think that the "build it and they will come" philosophy has worked nicely so
:far.

I think so, too (for all the newbie that I am). Hey, I already converted a
former Perl script writer to Python in just a week of trying. I think it takes
a while to get the word out, and it isn't a popularity contest, anyhow. Perl
already has an established base, and it is hard to fight that. I think that
adding in curly braces really isn't going to convince people to switch to
Python.

:Some clarification may help.  Perhaps you can reconcile the *optional* curly
:braces and the "from __future__ import" discrepancy.  It may just be my
:misunderstanding, but isn't __future__ designed to allow bleeding-edgers to
:write code for what will become python?  That is, won't all __future__
:thingys become mandatory?  I believe this is how it has been presented so
:far, and makes me think that *optional* curly braces won't be after a short
:transition period.

This thought flit through my mind upon the first reading of the announcement,
also. I hope that that is very wrong. I HATE the curly braces. I sure love
being able to write code without it.

Does this mean, that if curly braces are used to define blocks, that
whitespace will not be significant, then?

Confused,

--
Sheila King
http://www.thinkspot.net/sheila/
http://www.k12groups.org/