RetroSearch Browse

Thu Mar 24 17:16:17 CET 2011 · http://mail.python.org/pipermail/python-dev/2011-March/110010.html

Am 24.03.2011 16:58, schrieb bruce bushby:
>
> My main concern was that a freshly compiled Python attempts to open 168
> non-existent files before starting.
>
> I understand that an interpreted language is probably not the best
> choice for an embedded device (although it's very nice for prototyping)
> , Python really should know what exists after it's just been
> compiled....ie before any corrupting modules or other nonsense has been
> added.
>
> It appears it is hard coded to open these files regardless of any
> "configure" options.
>
> On my desktop pc, when I run the most simple "Hello World" .... 78% of
> the overall execution time is spent opening files....most of which don't
> exist.
>
> Some form of "cache" would help the startup time on the "second go"
> ..... but arguably just a "band aid" covering a deeper problem.

So maybe you should try to come up with a patch, to find out
if the cache helps?

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

Showing content from http://mail.python.org/pipermail/python-dev/2011-March/110010.html below:

[Python-Dev] Embedded Python startup is slow