25 Nov
2005
25 Nov
'05
9:37 a.m.
Lennart Regebro wrote:
It depends on what you mena with deprecated. It *is* deprecated from the point of view, that if you start developing something new now, then don't use it.
Really? What should we be using instead then?
It is not deprecated in the way that "this will go away in the future", though. It must stay for backwards compatibility reasons, but if it can be fixed, than this would be a Good Thing.
I honestly think it _should_ go away, just with plenty of notice... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk