Carl Zwanzig wrote:
>
>In general, I agree, but I question a language that relies on indent level
>for blocking and don't let you include blank lines for readability. I guess
>it's ok when you get used to it.
The forced indentation is something there will probably never be even
close to univers
On 6/1/06 1:10 PM, "Carl Zwanzig" <[EMAIL PROTECTED]> wrote:
> In general, I agree, but I question a language that relies on indent level
> for blocking and don't let you include blank lines for readability. I guess
> it's ok when you get used to it. But then again, I mostly work in tcl at
> this
In a flurry of recycled electrons, Jim Popovitch wrote:
> I am no Python expert either, but i am a competent perl and C++
> programmer. After about 4 years of tweaking and changing Python code,
> I've learned to appreciate it's power, but also it's simplicity. Python
> is a very well designed
John W. Baxter wrote:
> On 6/1/06 9:30 AM, "Carl Fink" <[EMAIL PROTECTED]> wrote:
>
>> On Thu, Jun 01, 2006 at 11:18:04AM -0500, Brad Knowles wrote:
>>
>>> When the configuration is done in the Python language in a Python
>>> script, you can let Python do all the parsing, and do the equivalent
>>>
Carl Fink wrote:
> On Thu, Jun 01, 2006 at 11:18:04AM -0500, Brad Knowles wrote:
>
>> When the configuration is done in the Python language in a Python
>> script, you can let Python do all the parsing, and do the equivalent
>> of "#include" in order to pull in all your configuration details
On 6/1/06 9:30 AM, "Carl Fink" <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 01, 2006 at 11:18:04AM -0500, Brad Knowles wrote:
>
>> When the configuration is done in the Python language in a Python
>> script, you can let Python do all the parsing, and do the equivalent
>> of "#include" in order to pul
On Thu, Jun 01, 2006 at 11:18:04AM -0500, Brad Knowles wrote:
> When the configuration is done in the Python language in a Python
> script, you can let Python do all the parsing, and do the equivalent
> of "#include" in order to pull in all your configuration details.
Fair enough. Like I
At 12:14 PM -0400 2006-06-01, Carl Fink wrote:
> I actually did restart Mailman, with no errors, and so far it seems to have
> taken my changes. If mm_cfg is just there to be read from, why is it a
> script instead of a text file /etc/mailman?
Because with a text /etc/mailman.cf confi
On Thu, Jun 01, 2006 at 08:30:34AM -0700, Dragon wrote:
> Yeah, that all seems a bit strange but if he can stop and
> successfully restart his qrunners, then the edits are syntactically
> correct and mailman can at least understand what is there. Whether
> those edits are then lexically and log
Mark Sapiro wrote:
>Carl Fink wrote:
> >
> >I'm unable to configure Mailman, because when I edit and run mm_cfg.py
> >("python ./mm_cfg.py") I get this error:
> >
> >Traceback (most recent call last):
> > File "./mm_cfg.py", line 44, in ?
> >from Defaults import *
> >ImportError: No module nam
Carl Fink wrote:
>
>I'm unable to configure Mailman, because when I edit and run mm_cfg.py
>("python ./mm_cfg.py") I get this error:
>
>Traceback (most recent call last):
> File "./mm_cfg.py", line 44, in ?
>from Defaults import *
>ImportError: No module named Defaults
As Christopher said in
On Thu, 1 Jun 2006, Carl Fink wrote:
> I'm unable to configure Mailman, because when I edit and run mm_cfg.py
You don't run mm_cfg.py You just edit it.
It contains values that are then read by the other programs when they run.
==
Chris Ca
Hi.
I'm unable to configure Mailman, because when I edit and run mm_cfg.py
("python ./mm_cfg.py") I get this error:
Traceback (most recent call last):
File "./mm_cfg.py", line 44, in ?
from Defaults import *
ImportError: No module named Defaults
Well, Defaults.py, Defaults.pyo and Default
13 matches
Mail list logo