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

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

native code compiler? (or, OCaml vs. Python)

• Previous message: [Python-Dev] Re: native code compiler? (or, OCaml vs. Python)
• Next message: [Python-Dev] Re: native code compiler? (or, OCaml vs. Python)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "GvR" == Guido van Rossum <guido@python.org> writes:

  >> But it is useful for to replace modules.  For example, if you
  >> want to debug a module that uses the thread module, you can
  >> replace it's "thread" global with something that hooks
  >> "start_new_thread."  I think that pattern is not uncommon.

  GvR> My proposal is to allow rebinding existing globals, just not to
  GvR> allow binding *new* globals *if* they shadow certain builtins.

Oh!  +1 on that.

just-add-a-future-statement-ly y'rs,
Jeremy

• Previous message: [Python-Dev] Re: native code compiler? (or, OCaml vs. Python)
• Next message: [Python-Dev] Re: native code compiler? (or, OCaml vs. Python)
• 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