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/2013-October/129122.html below:

[Python-Dev] cpython: Use cached builtins.

[Python-Dev] cpython: Use cached builtins. [Python-Dev] cpython: Use cached builtins.Serhiy Storchaka storchaka at gmail.com
Wed Oct 2 21:11:20 CEST 2013
02.10.13 20:31, Antoine Pitrou написав(ла):
> On Wed,  2 Oct 2013 18:16:48 +0200 (CEST)
> serhiy.storchaka <python-checkins at python.org> wrote:
>> http://hg.python.org/cpython/rev/d48ac94e365f
>> changeset:   85931:d48ac94e365f
>> user:        Serhiy Storchaka <storchaka at gmail.com>
>> date:        Wed Oct 02 19:15:54 2013 +0300
>> summary:
>>    Use cached builtins.
>
> What's the point? I don't think it's a good idea to uglify the code if
> there isn't a clear benefit.

These builtins already were cached. I only change recently added code to 
use cached values.

The point was perhaps that the access to module globals is a little 
faster than to builtins. Fred Drake was introduced this in changeset 
261a70c0aa79.

You can open a separate issue for removing this caching or for adding 
new builtins to this set.


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