>>> Dieter Maurer wrote
> Currently, there is a heated debate in c.l.p about PEP 308, an
> "if-then-else" expression for Python.
> Some vote should decide its fate.
>
> I think, we want an "if-then-else" expression for Zope, as it would
> make decisions in TALES expressions much clearer and more
Thanks for giving me a push in the right direction. I already knew from
the message that it
was the CComMember zclass. The problem was that I had deleted all
instances of that zclass
when I deleted the LoginManager based acl_users. I then deleted the zclass
from the Products
folder of the Con
Currently, there is a heated debate in c.l.p about PEP 308, an
"if-then-else" expression for Python.
Some vote should decide its fate.
I think, we want an "if-then-else" expression for Zope, as it would
make decisions in TALES expressions much clearer and more
robust than with the "... and ... or"
This is a repost from the [EMAIL PROTECTED] mailing list, as I got no
responses there.
For a number of reasons, I find myself wanting to persist instances of
PIL.Image in the ZODB.
Ideally, such a subclass of PIL.Image and Persistent would also be
API-compatible with OFS.Image, but I'd be willing
Andy McKay wrote:
3. I've found at least two companies that run many, many zope servers on
remote boxes all over the place and would like one ui to see the status
of them all, I'm trying to see if i can get some $ out of them for the
development :)
If it's about monitoring, let me just mention
On Sunday 09 February 2003 11:16 am, Adrian van den Dries wrote:
> > Your idea of does have merit IMHO. Should the ZMI really
> > assume existence of anything other than "id" for objects?
>
> Definitely not.
Its worse than that ;-) The management interface currently assumes that
objects do not
On February 7, Jim Washington wrote:
> Or, you could assure that your objects all have titles (at least ="") if
> you want them managed through the ZMI.
It seems you have missed the author's point: the ZMI should be robust
enough to deal with this sort of thing, otherwise it is not very
useful a
Hi,
I got these warnings building zope (you might be interested in fixing some/all
of them):
BTrees/BucketTemplate.c:214: warning: `bucket_append' defined but not used
BTrees/BucketTemplate.c:214: warning: `bucket_append' defined but not used
BTrees/BucketTemplate.c:214: warning: `bucket_append' d
Hi,
to let the 'find' in stupid_clean remove even file names with spaces you may
replace it with:
find . -name '*.o' -o -name '*.so' -o -name '*.py[co]' -o -name 'core*' |
while read file
do rm -f "$file"
done
It's not clear to me why you put that command in a separa
