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

Showing content from https://mail.python.org/pipermail/python-dev/2003-March/034277.html below:

[Python-Dev] Fast access to __builtins__

• Previous message: [Python-Dev] Fast access to __builtins__
• Next message: [Python-Dev] Fast access to __builtins__
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, 2003-03-28 at 08:30, Skip Montanaro wrote:

> Like a compiler flag to disable the run-time optimization so your debugging
> open() would be seen everywhere?

Sure, that would work.  I'm still thinking about "from __builtins__
import open".  Part of the issue there is that you might not be sure
/which/ open is causing the problems.  But I agree that this is not a
common case; I don't even think it would be common programming practice
(i.e. my use case is primarily debugging).

-Barry

P.S. I don't actually poke _() into builtins :)

• Previous message: [Python-Dev] Fast access to __builtins__
• Next message: [Python-Dev] Fast access to __builtins__
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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