Restricting import file lookup for pyd, dll, ...
3dbernard at gmail.com
Fri Oct 20 04:19:32 CEST 2006
I'm affraid this step has already been done. I was not being pedantic
when I said "locations that don't make sense", I *really* meant it.
You would have to see the Filemon log!
Anyway, then is there a way to tell Python not to look for pyd/dll and
others in certain locations? In locations were you expect not to have
such files for example?
On 10/19/06, Gabriel Genellina <gagsl-py at yahoo.com.ar> wrote:
> At Thursday 19/10/2006 22:38, Bernard Lebel wrote:
> >That's because I'm using Python through another application, via the
> >pywin32 extensions. When that other application starts, it performs
> >several thousands of file requests (we're talking 4,500, roughly) in
> >the Python installation, locations where there are Python files, and
> >in some other locations that don't make sense. This adds considerable
> >time to the startup time of the application, we're talking between 2
> >and 9 seconds.
> >This a problem with the application, not Python. But I'm looking for
> >ways to minimize this overhead so the users of this application waste
> >less time waiting after the startup.
> Try to shorten the PYTHONPATH to the really required directories
> (deleting those locations "that don't make sense").
> Gabriel Genellina
> Softlab SRL
> Correo Yahoo!
> Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
> ¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar
More information about the Python-list