Martin Aspeli wrote at 2009-4-12 18:31 +0800:
Finally, there is not total parity between Zope 2 security and Zope 3
security. Zope 2 cannot protect 'property set', for example.
Since Zope 2.8, Zope 2 could in principle -- and until quite recently
I thought, it really can: it only fails
Martin Aspeli wrote at 2009-4-12 18:31 +0800:
...
3) Change the Permission class in AccessControl so that it tries to
look up an IPermission utility and use the title of that utility as the
permission name, falling back on the current behaviour of using the
passed permission name directly.
Chris Withers wrote at 2009-4-13 03:14 +0100:
The context for this is trying to get ParsedXML 1.5 running on Zope 2.12
under Python 2.5 (don't ask why!)
Anyway, ParsedXML has a class:
class ManageableNodeList(ManageableWrapper, DOMProxy.NodeListProxy,
Dieter Maurer wrote:
Martin Aspeli wrote at 2009-4-12 18:31 +0800:
Finally, there is not total parity between Zope 2 security and Zope 3
security. Zope 2 cannot protect 'property set', for example.
Since Zope 2.8, Zope 2 could in principle -- and until quite recently
I thought, it
On Mon, Apr 13, 2009 at 08:14, Dieter Maurer die...@handshake.de wrote:
When upgrading from Zope 2.8 to Zope 2.11, I had to fight for
several hours because Zope 3 interfaces have been changed:
True, you went from Zope 3.0 to 3.3 in one swoop there, and the
changes was significant. But most of
Dieter Maurer wrote:
It does not go wrong with Zope 2.11/Python 2.4, neither.
Maybe, changes done for Python 2.5/2.6 compatibility broke something.
Here is a simpler script to check for problems:
Indeed:
class C:
... l=[1,2,3]
... def __getitem__(self, i):
... return self.l[i]
Chris Withers wrote:
If you try and iterate over an instance of this class, you get an
AttributeError: __iter__. This doesn't make a lot of sense, since you
*don't* get an error like that if you iterate over an instance of:
class X:
def __getitem__(self,i):
return 1
The change
Am Samstag 11 April 2009 15:05:31 schrieb Hanno Schlichting:
Roger Ineichen wrote:
Betreff: [Zope-dev] who wants to maintain Zope 3?
Is anyone interested in maintaining Zope 3?
/me is certainly not
With Zope 3 I mean:
I think we should take a look if we can build a minimal
setup
Martin Aspeli wrote:
I've now implemented 1 and 2 on trunk, since they seem pretty
non-controversial.
1) Use an event handler to ensure that any permission / declared in
ZCML actually creates a valid, Zope 2 permission. I have working code
for this here which we could put in
Hermann Himmelbauer wrote:
-1 from my standpoint. Two of my projects are fully based on the Zope 3
server, and switching to something else would be quite some pain.
FWIW, I think you're absolutely right. We can't just declare it dead
because it is convenient to our goal of having clearer
Summary of messages to the zope-tests list.
Period Sun Apr 12 12:00:00 2009 UTC to Mon Apr 13 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sun Apr 12 20:40:43 EDT 2009
URL:
Hi Martin
-Ursprüngliche Nachricht-
Von: zope-dev-bounces+dev=projekt01...@zope.org
[mailto:zope-dev-bounces+dev=projekt01...@zope.org] Im
Auftrag von Martin Aspeli
Gesendet: Montag, 13. April 2009 13:07
An: zope-dev@zope.org
Betreff: Re: [Zope-dev] who wants to maintain Zope
On Mon, Apr 13, 2009 at 12:49, Hermann Himmelbauer du...@qwer.tk wrote:
I personally find it interesting that people are that fast with turning around
and killing off things. I personally based my decision for Zope 3 on Philipps
book (Web Compontent Development with Zope 3), whereas the latest
Previously Martin Aspeli wrote:
Hermann Himmelbauer wrote:
-1 from my standpoint. Two of my projects are fully based on the Zope 3
server, and switching to something else would be quite some pain.
FWIW, I think you're absolutely right. We can't just declare it dead
because it is
On 4/13/09 10:33 AM, Lennart Regebro wrote:
I understand that people like Zope 2 for historical reasons and Grok for it's
simplicity, but I would really wonder that there's no target audience for
various ideas/patterns in Zope 3 (security model, ZCML...).
There is, but those who prefer ZCML
On Fri, Apr 10, 2009 at 11:33 AM, Martijn Faassen
faas...@startifact.com wrote:
Hi there,
Is anyone interested in maintaining Zope 3?
With Zope 3 I mean:
* the thing with the ZMI - do you care about the ZMI?
* the thing that can be installed as a particular development platform -
do you
Hanno Schlichting wrote:
The change you are interested in is probably:
http://svn.zope.org/Zope/trunk/lib/python/Acquisition/_Acquisition.c?rev=94905r1=92577r2=94905
Acquisition now proxy real iteration via __iter__ correctly (it didn't
do that before). What is missing from that change is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
On Fri, Apr 10, 2009 at 11:33 AM, Martijn Faassen
faas...@startifact.com wrote:
Hi there,
Is anyone interested in maintaining Zope 3?
With Zope 3 I mean:
* the thing with the ZMI - do you care about the ZMI?
* the thing that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
I've not done this yet:
3) Change the Permission class in AccessControl so that it tries to
look up an IPermission utility and use the title of that utility as the
permission name, falling back on the current behaviour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.04.2009 17:58 Uhr, Chris Withers wrote:
Hanno Schlichting wrote:
The change you are interested in is probably:
http://svn.zope.org/Zope/trunk/lib/python/Acquisition/_Acquisition.c?rev=94905r1=92577r2=94905
Acquisition now proxy real
Hi All,
Any ideas what this means or where it's coming from?
Module ZODB.Connection, line 808, in setstate
Module ZODB.Connection, line 876, in _setstate
Module ZODB.serialize, line 604, in setGhostState
Module ZODB.serialize, line 597, in getState
TypeError: ('argument list must be a tuple',
Andreas Jung wrote:
Yes, so this change introduced a bug. Who's the right person to fix it?
What's the right collector to report this in?
Since Acquisition is a core module of Zope: the Zope 2 tracker on Launchpad.
Done:
https://bugs.launchpad.net/zope2/+bug/360761
Now, who knows how to
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
I've not done this yet:
3) Change the Permission class in AccessControl so that it tries to
look up an IPermission utility and use the title of that utility as the
permission name, falling back on
23 matches
Mail list logo
