[Mailman-Users] reliable python 2.3.3 or 2.3.4 backport?

[John W. Baxter]

On 8/5/2004 5:00, "Jeff Garvas" <jeff at cia.net> wrote:

> On Thu, Aug 05, 2004 at 02:57:14PM +0900 or thereabouts, Stephen J. Turnbull
> wrote:
> 
>> IIRC the lack of definition of Boolean constants is a problem specific
>> to 2.3.2, and all you have to do is define True and False to 1 and 0
>> respectively somewhere in the startup.  I'm not sure if the mm_cfg is
>> early enough.
> 
> This is defined in almost every .py file, but this specific text is from
> Defaults.py: 
> 
> # Some convenient constants
> try:
>   True, False
> except NameError:
>   True = 1
>   False = 0
> 
> Yes = yes = On = on = True
> No = no = Off = off = False
> 
> 
>> This isn't reliable information, OTOH only requires adding two lines
>> and if it works, at least you can get started.
> 
> I had tried adding True = 1 in the last mentioned .py (I'm not a python
> person at all) and it didn't seem to help one bit.


Run python from the command line.

At the prompt, type
print True

On a machine here I tried arbitrarily, Python 2.2.2 responded with
1
and python 2.3.1 responded with
True

But what matters is what happens on the machine on which True is claimed by
Mailman to be undefined.

  --John