oops! I did mean decrease :)and yes - it would make sense to not do this with the debug version for the reason you mention.
On Jul 27, 2005, at 1:31 PM, Phillip J. Eby wrote:
At 01:15 PM 7/27/2005 -0400, Mike Taylor wrote:Actually it did load quite a few of libraries - I was adding them to the zip one dir at a time and until I zipped the majority of the directories I was getting one import error after another. The load time of Chandler wasn't the point of the test - the Chandlerpython files are not part of the zip, only the python core library. Myprimary goal for the test was to see if we could speed up the loading of the core python modules. What will increase the load time of Chandler is another change I'll be making to the build - the pre-compiling of all .py files on each platform.I think you mean *decrease* the load time. ;)In any case, the timings you gave are for the case where hardly anything is imported; I suspect that loading Chandler will show more of a speedup from the zipping just because more stdlib modules will have been imported.I suspect that for the debug build we may want to leave the stdlib unzipped, however, so that people using debuggers can step into stdlib source code -- something that can't generally be done with zipped Python code at the moment._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
