Hi!
There are no deprecation warnings, but Zope2 interfaces are deprecated
for quite a while now. CMF 2.0 and 2.1 should work without using any
Zope2 interfaces in your own code or third party products. The BBB
comments say they will be removed after CMF 2.1.
CMF 2.1 has a branch now, so
Summary of messages to the cmf-tests list.
Period Thu Mar 8 12:00:00 2007 UTC to Fri Mar 9 12:00:00 2007 UTC.
There were 9 messages: 9 from CMF Unit Tests.
Unknown
---
Subject: UNKNOWN : CMF-trunk Zope-trunk Python-2.4.4 : Linux
From: CMF Unit Tests
Date: Thu Mar 8 21:48:57 EST 2007
URL:
Sidnei da Silva wrote:
One possible ill effect is persistent references to interfaces due to
PAS. I've reported that a few days ago, but nobody seems to have
noticed.
Maybe I wasn't clear:
I was talking about oldstyle interfaces using Zope2's Interface package
instead of zope.interface. I
On 3/9/07, yuppie [EMAIL PROTECTED] wrote:
Sidnei da Silva wrote:
One possible ill effect is persistent references to interfaces due to
PAS. I've reported that a few days ago, but nobody seems to have
noticed.
Maybe I wasn't clear:
I was talking about oldstyle interfaces using Zope2's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9 Mar 2007, at 16:17, Sidnei da Silva wrote:
PAS used old-style interfaces at one point, and stored references to
them in __implements__ attributes on persistent objects. I know
because I had to write migration code for an app of mine.
I'm not
On 3/9/07, Jens Vagelpohl [EMAIL PROTECTED] wrote:
I'm not following, are you saying PAS referred to old-style
interfaces defined in the CMF? I wasn't aware of any dependencies there.
Not in CMF sorry, just pointing out a general issue. If people have
any persistent references to interfaces
