- Zope-Dev - Zope lists

Zope 2 security and SimpleItem
by Florent Guillaume 20 Nov '05

20 Nov '05

I'm in the process of refactoring OFS to use new-style security declarations (about time ;)), and I stumbled on something which may or may not be a bug, I don't know, I'd like some else's opinion: The class SimpleItem has the definition (it's been there since the begining of time when SimpleItem was created): __ac_permissions__=(('View', ()),) The unusual thing here is () instead of ('',). I think the intent here is that it be the object level protection, equivalent to the modern declareObjectProtected('View'). Indeed, if the SimpleItem class had a security = ClassSecurityInfo() (even by itself without further security declaration), then AccessControl/SecurityInfo, which has the code # Empty names list sets access to the class itself, named '' if not len(names): names = ('',) would actually turn the () into a ('',) and the rest of the end of the security setup, in App/class_init.py, would set SimpleItem.__roles__ = PermissionRole('View') and that would be it. However SimpleItem does *not* have this ClassSecurityInfo, which means that the code above is not called, and the final logic in class_init.py does not turn an empty tuple into "protect the object". It means that SimpleItem does not have an object level protection of View (but the default which is that only Manager has access), which is probably as well but not clear from the code. What do you think I should do? - fix to use View? - fix to use nothing? Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

1 1

Heads up: Branch naming scheme
by Philipp von Weitershausen 19 Nov '05

19 Nov '05

Hi there, quick reminder for all of you who have Zope 2.9 branch checkouts: There has been a change (finally!) in the release branch naming scheme. The 2.9 branch was renamed to Zope/branches/2.9 as a result. This will be the naming scheme for all release branches in Zope 2 and 3 from now on. Please switch your Zope 2.9 working copies to the new location with: $ svn switch svn+ssh://USERNAME@svn.zope.org/repos/main/Zope/branches/2.9 Have a good weekend, Philipp

1 0

Zope 2 license
by Philipp von Weitershausen 18 Nov '05

18 Nov '05

Hi there, Zope/doc/LICENSE.txt still is ZPL 2.0 and so are most of the file headers in the Zope 2 source code. Newer files, especially those from Five, are ZPL 2.1, though. I think it's a good time to switch the rest of Zope 2 to ZPL 2.1. That way we only have to supply one license text. Philipp

4 3

Re: branched Zope 2.9
by Florent Guillaume 17 Nov '05

17 Nov '05

Andreas Jung wrote: >> http://www.zope.org/Collectors/Zope/collector_contents?searching=yep&Sear >> chableText=&status%3Alist%3Aignore_empty=Accepted&status%3Alist%3Aignore_ >> empty=Pending&classifications%3Alist%3Aignore_empty=bug&importances%3Alis >> t%3Aignore_empty=critical > > Ups, I got your point. I thought you were talking about 9 critical error > *directly* related to Zope 2.9 e.g. the packaging issue, Five etc..I am > aware of this issues. Issue marked by the issuer as critical might > appear critical to them..so one needs to decide which issues are blockers. Anyway if we want to go further we need to schedule bug days. One per week, or something like that. Otherwise nobody will set aside the time to discuss, investigate and fix the current bugs. BTW I'm for removing the 2.9 branch for now. Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

6 15

Timing the opening of network ports
by Christian Theune 15 Nov '05

15 Nov '05

Hi, a while ago I realized that I liked the initial opening of network ports immediately on server start. After working on a busy site with ZEO in the summer I wished that this feature would be configurable. There are different scenarios that ask for opening the network ports early or late: Situation 1: You are a developer and restart your server frequently. You want the ports to be open as soon as possible, even if the site takes a while to load, because your browser accepts a reload immediately. If you use tabbed browsing this also notifies you when the server is ready and you can read /. while waiting ... Situation 2: You are have a site with only a single application server (w/ or w/o ZEO) and have to restart your server. You want to minimize proxy errors (via Apache) and connection losses experienced by people visiting your site/using your application. So opening the ports early is good here. Situation 3: You are have a site that uses a ZEO cluster. You have to restart the application servers while people are using the site. As you have a load balancer, there are always some application servers around that can answer the queries. Now you want to open the network ports as late as possible. In the ideal case, when the complete server is ready. This avoids that people's connections go onto a still booting server and have to wait for several seconds which results in a even more loaded queue on the booting server ... Does this sound reasonable to make the behaviour of opening the ports configurable? Does anybody have an idea how hard this would be to do? Cheers, Christian -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - ct(a)gocept.com - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development

4 4

Reminder: feature freeze November 1.
by Jim Fulton 14 Nov '05

14 Nov '05

This is a reminder that there will be a feature freeze for the December Zope releases on November 1. No new features for the November releases should be added after October 31. The Zope trunks should be stable and ready for a beta release on November 1. We are committed to time-based releases. This means we need to be very disciplined about deadlines. If a cool new feature isn't quite ready before November 1, then it could be be included in the June release, for which the feature freeze will be May 1. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

8 36

Re: SVN: Zope/trunk/test.py Don't hard-wire forward-slash into sys.path (redux).
by Philipp von Weitershausen 14 Nov '05

14 Nov '05

Tres Seaver wrote: > Log message for revision 40092: > Don't hard-wire forward-slash into sys.path (redux). Please don't forget to merge this and the previous rev to the Zope 2.9 branch. From now on, both the trunk and the 2.9 branch need to be taken care of. Philipp

2 1

buildbot failure in Zope trunk 2.4 Windows 2000 fred-win
by buildbot＠zope.com 14 Nov '05

14 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 fred-win. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1541 Blamelist: philikon BUILD FAILED: failed failed slave lost sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 10 Nov '05

10 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1473 Blamelist: efge,fdrake,jim,rykomats,srichter,tseaver BUILD FAILED: failed test sincerely, -The Buildbot

1 0

'NoneType' has no attribute 'lower'
by Larry Lay 10 Nov '05

10 Nov '05

when sorting using <...tal:repeat subsection python:sequence.sort(subsections,(('title','nocase','asc'),))"> I get the following error: Module DocumentTemplate.sequence.SortEx, line 134 in nocase AttributeError: 'NoneType' has no attribute 'lower' When I switch the 'nocase' to 'cmp' the sort defaults to sorting by order of entry or something. Any help would be greatly appreciated. Thanks.

2 1