Re: [Ganglia-developers] RFC: enabling python modules by default
On Tue, 2008-03-18 at 22:29 -0500, Carlo Marcelo Arenas Belon wrote: On Tue, Mar 18, 2008 at 07:04:10PM -0700, Bernard Li wrote: On 3/18/08, Carlo Marcelo Arenas Belon [EMAIL PROTECTED] wrote: is there any good reason why building the python module wrapper is not enabled by default?, there will always of course the option of disabling it using --disable-python at configure time +1 Committed revision 1082 I suggested this a while back too. any pointers to the discussion? why it was never done then? Maybe Brad will weigh in on this. My guess is because of the additional overhead of including the python wrapper (runtime footprint primarily). It really isn't that much AFAIK but it is something. Of course that's just a guess. I still think it is a good proposal. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] RFC: enabling python modules by default
On Wed, Mar 19, 2008 at 9:13 AM, in message [EMAIL PROTECTED], Matt Ryan [EMAIL PROTECTED] wrote: On Tue, 2008-03-18 at 22:29 -0500, Carlo Marcelo Arenas Belon wrote: On Tue, Mar 18, 2008 at 07:04:10PM -0700, Bernard Li wrote: On 3/18/08, Carlo Marcelo Arenas Belon [EMAIL PROTECTED] wrote: is there any good reason why building the python module wrapper is not enabled by default?, there will always of course the option of disabling it using --disable-python at configure time +1 Committed revision 1082 I suggested this a while back too. any pointers to the discussion? why it was never done then? Maybe Brad will weigh in on this. My guess is because of the additional overhead of including the python wrapper (runtime footprint primarily). It really isn't that much AFAIK but it is something. Of course that's just a guess. I still think it is a good proposal. I am actually good with making python the default. I thought that the discussion before was that mod_python and the python modules were going to be packaged in a separate RPM which was why it was disabled by default. But if we want to make it the default, I think that is a great idea. Brad - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
[Ganglia-developers] RFC: enabling python modules by default
Greetings, is there any good reason why building the python module wrapper is not enabled by default?, there will always of course the option of disabling it using --disable-python at configure time but will had the following advantages compared to the current situation : 1) make dist* will always include them as that target will no longer be dependent of what options were used to configure, making bootstrapping simpler and more consistent. 2) the focus of 3.1 is the modular metrics, so having this enabled by default is more consistent with that goal and funny enough it seems it is enabled in our SPEC and in every other document we have. Carlo - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] RFC: enabling python modules by default
Hi Carlo: On 3/18/08, Carlo Marcelo Arenas Belon [EMAIL PROTECTED] wrote: is there any good reason why building the python module wrapper is not enabled by default?, there will always of course the option of disabling it using --disable-python at configure time but will had the following advantages compared to the current situation : 1) make dist* will always include them as that target will no longer be dependent of what options were used to configure, making bootstrapping simpler and more consistent. 2) the focus of 3.1 is the modular metrics, so having this enabled by default is more consistent with that goal and funny enough it seems it is enabled in our SPEC and in every other document we have. +1 I suggested this a while back too. Cheers, Bernard - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] RFC: enabling python modules by default
On Tue, Mar 18, 2008 at 07:04:10PM -0700, Bernard Li wrote: On 3/18/08, Carlo Marcelo Arenas Belon [EMAIL PROTECTED] wrote: is there any good reason why building the python module wrapper is not enabled by default?, there will always of course the option of disabling it using --disable-python at configure time +1 Committed revision 1082 I suggested this a while back too. any pointers to the discussion? why it was never done then? Carlo - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
