Python for large projects

[Cameron Laird]

In article <mailman.301.1080072433.742.python-list at python.org>,
Dave Brueck <dave at pythonapocrypha.com> wrote:
			.
			.
			.
>> (previously all the programs were written in java)
>> "if one of our programmers changes a method in a class/interface, we
>> immediately will know about it, because the next program-rebuild will
>> simply fail. but if we would use python, we wouldn't find it out".
>
>Say "Bzzt! Wrong!" :) In C++ this is a no brainer because the compiler simply
			.
		[Dave continues with
		his perfectly rendered
		follow-up]
			.
			.
>everybody should avoid. I would ask them to cite a real world example rather
>than hypothetical "what-ifs" because the refactoring of an interface is almost
>always accompanied by a semantic change to the interface, and again the
>compiler can't really help there.
>
>-Dave
>
>

Here's the part that scares me:  I've seen enough to suspect
that, in some shops, this line of reasoning is *not* hypo-
thetical--that is, that the locals truly do conceive of
refactoring as fiddling around with signatures and reacting
to overt compiler messages.  Brutalities are committed in
the name of IT that admit no other explanation.
-- 

Cameron Laird <claird at phaseit.net>
Business:  http://www.Phaseit.net