A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2001-February/013092.html below:

[Python-Dev] Backwards Incompatibility

[Python-Dev] Backwards IncompatibilityGuido van Rossum guido@digicool.com
Wed, 21 Feb 2001 20:45:10 -0500
> On Wed, Feb 21, 2001 at 05:41:41PM -0500, Andrew Kuchling wrote:
> 
> > Compatibility... ay, there's the rub!
> 
> If you include 'ways of thinking' in 'compatibility', I'll agree. Many
> people are used to being able to use exec/from-foo-import-*, and consider it
> part of Python's wonderful flexibility and straightforwardness (I know I do,
> and all my python-proficient and python-learning colleagues do.)

Actually, I've always considered 'exec' mostly one of those must-have-
because-the-competition-has-it features.  Language theorists love it.
In practice, bare exec not that useful; a more restricted form
(e.g. one that always requires the caller to explicitly pass in an
environment) makes much more sense.

As for import *, we all know that it's an abomination...

--Guido van Rossum (home page: http://www.python.org/~guido/)



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4