Chris Withers wrote at 2005-5-12 20:45 +0100:
Jens Vagelpohl wrote:
I suppose it could be argued that custom_zodb.py should simply not be
read in any longer, or throw big fat warnings.
[DM]
I agree with you, Jens.
[CW]
Why wouldn't it still work fine, apart from some minor Control Panel
Jens Vagelpohl wrote:
I suppose it could be argued that custom_zodb.py should simply not be
read in any longer, or throw big fat warnings.
Why wouldn't it still work fine, apart from some minor Control Panel
barfage?
Chris
--
Simplistix - Content Management, Zope Python Consulting
-
On May 12, 2005, at 21:45, Chris Withers wrote:
Jens Vagelpohl wrote:
I suppose it could be argued that custom_zodb.py should simply not
be read in any longer, or throw big fat warnings.
Why wouldn't it still work fine, apart from some minor Control
Panel barfage?
You will agree that it is
v2.7.4 running on Linux - I'm trying to use this (custom_zodb.py in
INSTANCE_HOME)
custom_zodb.py is no longer used for Zope 2.7.x. You define
databases in zope.conf.
Ah, OK thanks.
Is it for the collector that, aside from messing up the ZMI a bit, the
custom_zodb.py approach is
On May 2, 2005, at 14:49, Jim Abramson wrote:
v2.7.4 running on Linux - I'm trying to use this (custom_zodb.py in
INSTANCE_HOME)
custom_zodb.py is no longer used for Zope 2.7.x. You define
databases in zope.conf.
Ah, OK thanks.
Is it for the collector that, aside from messing up the ZMI a bit,
On Apr 29, 2005, at 20:32, Jim Abramson wrote:
v2.7.4 running on Linux - I'm trying to use this (custom_zodb.py in
INSTANCE_HOME)
custom_zodb.py is no longer used for Zope 2.7.x. You define databases
in zope.conf.
jens
___
Zope maillist -
