Martin v. Loewis wrote: > "M.-A. Lemburg" <mal@lemburg.com> writes: > > >>>On the other hand, on my Linux installation, importing a module costs >>>35 system calls if the module is not found, and no PYTHONPATH is set; >>>every directory in PYTHONPATH adds four additional system calls. >> >>Why not address this problem instead ? > > > I'm trying to: every module incorporated in config.c won't be searched > in PYTHONPATH. > >>Note that mxCGIPython can help a lot here: it freeze most of the >>Python std lib into the executable making imports go really fast >>(and that's needed if you're doing a lot of CGI scripting). > > > Indeed, freezing also helps - but is probably only suitable for > special-purpose applications. I think people would be surprised if > they are told that editing the source of a library module won't have > any effect. They shouldn't edit those anyway :-) What ever happened to the ZIP archive import that James C. Ahlstrom was working (I think it was him) ? If startup time for the std lib is considered a problem, then people could be directed to a ZIP archive incorporating the complete pure Python std lib. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH _______________________________________________________________________ eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,... Python Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
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