>>> On 11/7/2007 at 1:52 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > Currently .pyc files are generated on the fly in > /usr/lib/ganglia/python_modules/ when python modules are enabled. > > I was thinking maybe we should do this as part of the build so that we > can include them in the binary package. > > This way, all these .pyc files are pre-generated ahead of time and the > respective package manager will be able to do its job of managing the > files. > > Thoughts? >
I am not sure that precompiling the .pyc file is necessary. Are you worried about just being able to remove the .pyc's on an uninstall? Because compiling the .py at start up vs. precompiling really has no noticeable difference. I'm also not sure if precompiling the .py's will tie them to a specific python version. If so then the precompiled packaged version might not work if it was precompiled using one version of python and executed using a different version. Brad ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
