Philipp von Weitershausen wrote:
That's a bold assumption.
It's a bold assumption based on the fact that I'm pretty sure there's
about 1 person on the planet who's ever used that code. I believe his
name's Andreas. I might be wrong of course, but I don't think it's much
more than that...
Chris Withers wrote:
Philipp von Weitershausen wrote:
That's a bold assumption.
It's a bold assumption based on the fact that I'm pretty sure there's
about 1 person on the planet who's ever used that code. I believe his
name's Andreas. I might be wrong of course, but I don't think it's much
yuppie wrote:
Philipp von Weitershausen wrote:
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
+10
Me too ;-)
1.) WriteLock: Objects are only lockable if their class has
Chris Withers wrote:
yuppie wrote:
Philipp von Weitershausen wrote:
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
+10
Me too ;-)
Great. There don't seem to be
Hi Philipp!
Philipp von Weitershausen wrote:
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
+10
But we can't deprecate z2 interfaces as long as Zope 2 itself uses them
yuppie wrote:
I don't think it will make much sense to keep Zope 2 interfaces around
for more than one year from now. In other words, I'm suggesting to
deprecate them for Zope 2.10.
+10
But we can't deprecate z2 interfaces as long as Zope 2 itself uses them
for other tasks than
Hi Philipp!
Philipp von Weitershausen wrote:
yuppie wrote:
There are a few places in Zope 2 where they are still used for checks
(mostly webdav, OFS, ZCTextIndex).
In detail these are:
1.) WriteLock: Objects are only lockable if their class has
WriteLockInterface in its __implements__ list.
