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/2011-January/107196.html below:

[Python-Dev] Possible optimization for LOAD_FAST ?

[Python-Dev] Possible optimization for LOAD_FAST ? [Python-Dev] Possible optimization for LOAD_FAST ?Guido van Rossum guido at python.org
Tue Jan 4 16:58:46 CET 2011
On Tue, Jan 4, 2011 at 2:49 AM, Michael Foord <fuzzyman at voidspace.org.uk> wrote:
> I think someone else pointed this out, but replacing builtins externally to
> a module is actually common for testing. In particular replacing the open
> function, but also other builtins, is often done temporarily to replace it
> with a mock. It seems like this optimisation would break those tests.

Hm, I already suggested to make an exception for open, (and one should
be added for __import__) but if this is done for other builtins that
is indeed a problem. Can you point to example code doing this?

-- 
--Guido van Rossum (python.org/~guido)
More information about the Python-Dev mailing list

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