A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Backwards Incompatibility

[Python-Dev] Backwards Incompatibility [Python-Dev] Backwards IncompatibilityAndrew Kuchling akuchlin@mems-exchange.org
Wed, 21 Feb 2001 17:41:41 -0500
On Wed, Feb 21, 2001 at 11:33:34PM +0100, Thomas Wouters wrote:
>Besides from any real problems we'll see, the added wartiness (which is what
>the hypothetical howls are all about) does really matter. What are we trying
>to solve with nested scopes ? Anything other than the default-argument hack
>wart ? Aren't we adding more warts to fix that one wart ?

I wouldn't consider either nested scopes or the additional
restrictions really warts.  'from...import *' is already somewhat
frowned upon, and often people use exec in situations where something
else would be a better solution (storing variable names in a
dictionary instead of exec'ing 'varname=expr').  If we were starting
from a clean slate, I'd say accepting nested scopes would be a
no-brainer.  Compatibility... ay, there's the rub!

--amk




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