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-December/018844.html below:

[Python-Dev] nested scopes confusion

[Python-Dev] nested scopes confusion [Python-Dev] nested scopes confusionThomas Heller thomas.heller@ion-tof.com
Tue, 4 Dec 2001 20:58:59 +0100
> Yes, you're out of luck.  Like in all decent languages with nested
> scope, Python binds to the variable, not to its value at the time the
> inner function is defined.

So nested scopes are not really an alternative (at least in this case)
to the 'lambda self, i=i: i' trick.

> 
> > How do I achieve the desired effect? Note that the default argument
> > trick (def mth(i=i): ...) does not work because *args is present.
> 
> Use a class with a __call__ method:

That's what I was trying to avoid, because it is too slow.

Thanks,

Thomas




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