Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #10770

Re: Early binding as an option

References <CAPTjJmpWN1Tq-46UoHjh_-q9ahkivTWmLJR3_eF9iThHwXQnhA@mail.gmail.com> <j19mbp$985$1@dough.gmane.org> <CAPTjJmr8mjYKTYu9EdKc-QRaFfSwH0rbVdAhnW-ysfvOZujJqQ@mail.gmail.com> <j19t8g$jqa$1@dough.gmane.org>
Date 2011-08-02 23:26 +0100
Subject Re: Early binding as an option
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.1809.1312323964.1164.python-list@python.org> (permalink)

Show all headers | View raw


On Tue, Aug 2, 2011 at 11:21 PM, Gelonida N <gelonida@gmail.com> wrote:
> On the other hand: It might be interesting, that the early binding would
> just take place when python is invoked with -O
>

This could be an excellent safety catch, but on the other hand, it
might destroy all value of the feature - once again, it would be
optimizing in the sole case where the code is probably better
rewritten in C.

Or would this be a sort of "half-way house" - this is where we need
more performance, let's spend two minutes tweaking it in Python rather
than dropping to C - to get some of the performance gains?

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: Early binding as an option Chris Angelico <rosuav@gmail.com> - 2011-08-02 23:26 +0100

csiph-web