- Zope-Dev - Zope lists

Re: [Zope-dev] [Zope] Zope 4.0, maybe not such a bad idea...
by Chris Withers 02 Apr '09

02 Apr '09

Andrew Milton wrote: > | - mature > | - stable > | - maybe not the best choice for new development. > ^ for you Indeed, but "classic" doesn't have any "bad" connotations as far as I'm concerned, and it'll need to keep living as long as Plone relies on it, which will be forever... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Re: [Zope-dev] [Zope] Zope 4.0, maybe not such a bad idea...
by Chris Withers 02 Apr '09

02 Apr '09

Andrew Milton wrote: > +-------[ Chris Withers ]---------------------- > | Remember this: > > | Seriously, how do people feel about this? > > You can do anything you want with your time... who are we to judge? d8) Well, if there were no complaints I might do just that... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Two small convenience suggestions for zope.interface and zope.component
by Martin Aspeli 02 Apr '09

02 Apr '09

Hi, I'd like to add support for the following: 1) Provider decorator: @provider(IFoo) def some_function(context) pass This is an alternative to doing a separate alsoProvides() on the function. 2) An interfaceProvides directive: class IFoo(Interface): interfaceProvides(ISomeMarker) This is alternative to doing alsoProvides() on the interface. The reason for this is that currently, you have to put those alsoProvides() lines after the function or interface. This makes them difficult to find if the bodies of the functions or interfaces are long, and goes against the convention of having the "what is this" information at the top of the entity. I can probably help implement this. Any thoughts? Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

8 10

Re: [Zope-dev] WSGI access log user info howto?
by Roger Ineichen 02 Apr '09

02 Apr '09

Hi Alex > Betreff: Re: WSGI access log user info howto? > > A branch containing this refactoring named > 'achapman__username_logging now exists in the zope.app.wsgi > directory. I'll be merging it today and tagging a release if > it appears acceptable. This looks good to me. Can you add a test for the new logging part? Or let me know if I can do it for you. Regards Roger Ineichen > - Alex Chapman > > > On Tue, Mar 31, 2009 at 10:00 PM, Alex Chapman > <achap5dk(a)gmail.com> wrote: > > > This would work great for my own needs if its acceptable with > everyone else. > > Thanks for the help on this. In the future I'll do work > on a branch and > request a review from all those on the owner list > before merging, > tagging, and releasing. > > -Alex Chapman > > On Wed, 2009-04-01 at 03:30 +0200, Roger Ineichen wrote: > > Hi all > > > > Shane, > > any idea about the following which whould also > > affect the zope.pipeline or the zope.publisher refactoring? > > > > I need some advice for the access log topic in wsgi. > > > > > > The zope http server logs access in zope.publisher.http > > like: > > > > def setPrincipal(self, principal): > > 'See IPublicationRequest' > > super(HTTPRequest, self).setPrincipal(principal) > > logging_info = ILoggingInfo(principal, None) > > if logging_info is None: > > message = '-' > > else: > > message = logging_info.getLogMessage() > > self.response.authUser = message > > > > This means there is a ILoggingInfo adapter which returns > > a simple string. ASCII and no space are preffered because > > the standard access log format uses space aas delimiter. > > And access lgo fiels are not unicode. > > > > Of corse the ILoggingInfo adapter is responsible for > > choose the right format for each project. A default > > is configured in zope.publisher.principallogging > > PrincipalLogging > > > > Now to the question. > > > > In the latest checkins there was a access log part > > implemented. It doesn't use the ILoggingInfo adapter and > > is exposing the user login which is a part of the security > > credential. This get already released. (not good) > > > > Is there a standard how WSGI apps will log user info in > > access logs? I guess not, right? > > > > Does someone have a good idea how we should implement > > user access info for access logs in zope.app.wasg? > > > > If not, I propose the following: > > > > logging_info = ILoggingInfo(request.principal, None) > > if logging_info is None: > > message = '-' > > else: > > message = logging_info.getLogMessage() > > environ['wsgi.logging_info'] = message > > > > > > - this will set a ``wsgi.logging_info`` environ > > variable (or is there already a standard name)? > > > > - it uses the ILoggingInfo adapter which let us use > > different kind of access log info strategies in > > custom projects. By default we should use the > > PrincipalLogging adapter form > zope.publisher.principallogging. > > > > Does anybody have a better idea how we can make the user > > info available for the access log? > > > > Alex whould this fit for you? > > > > > > Regards > > Roger Ineichen > > _____________________________ > > END OF MESSAGE > > > > > >

1 0

Zope and Cygwin
by Cesar Canassa 01 Apr '09

01 Apr '09

Hi all, I am trying to run Zope using cygwin and Windows XP. I started by downloading the Python 2.4.6 sources and compiling it with: ./configure make && make install After that I downloaded the Zope-2.11.2-final sources and compiled it with: ./configure --with-python=/usr/local/bin/python make && make install The compilation went smoothly so I created a instance and started the server with the runzope script. The script returned this error: $ ./runzope Traceback (most recent call last): File "/opt/Zope-2.11/lib/python/Zope2/Startup/run.py", line 56, in ? run() File "/opt/Zope-2.11/lib/python/Zope2/Startup/run.py", line 21, in run starter.prepare() File "/opt/Zope-2.11/lib/python/Zope2/Startup/__init__.py", line 109, in prepare self.startZope() File "/opt/Zope-2.11/lib/python/Zope2/Startup/__init__.py", line 300, in startZope Zope2.startup() File "/opt/Zope-2.11/lib/python/Zope2/__init__.py", line 47, in startup _startup() File "/opt/Zope-2.11/lib/python/Zope2/App/startup.py", line 105, in startup Globals.VersionNameName) File "/opt/Zope-2.11/lib/python/App/ZApplication.py", line 32, in __init__ if not root.has_key(name): File "/opt/Zope-2.11/lib/python/ZODB/Connection.py", line 811, in setstate self._setstate(obj) File "/opt/Zope-2.11/lib/python/ZODB/Connection.py", line 870, in _setstate self._reader.setGhostState(obj, p) File "/opt/Zope-2.11/lib/python/ZODB/serialize.py", line 604, in setGhostState state = self.getState(pickle) File "/opt/Zope-2.11/lib/python/ZODB/serialize.py", line 597, in getState return unpickler.load() File "/opt/Zope-2.11/lib/python/ZODB/serialize.py", line 471, in _persistent_load return self.load_oid(reference) File "/opt/Zope-2.11/lib/python/ZODB/serialize.py", line 537, in load_oid return self._conn.get(oid) File "/opt/Zope-2.11/lib/python/ZODB/Connection.py", line 245, in get obj = self._reader.getGhost(p) File "/opt/Zope-2.11/lib/python/ZODB/serialize.py", line 591, in getGhost return klass.__new__(klass, *args) TypeError: Acquirer.__new__(Application) is not safe, use Persistence.Persistent.__new__() Am I doing something wrong? Does anyone knows if it's possible to compile Zope with Cygwin? Thanks, Cesar Canassa

3 6

WSGI access log user info howto?
by Roger Ineichen 01 Apr '09

01 Apr '09

Hi all Shane, any idea about the following which whould also affect the zope.pipeline or the zope.publisher refactoring? I need some advice for the access log topic in wsgi. The zope http server logs access in zope.publisher.http like: def setPrincipal(self, principal): 'See IPublicationRequest' super(HTTPRequest, self).setPrincipal(principal) logging_info = ILoggingInfo(principal, None) if logging_info is None: message = '-' else: message = logging_info.getLogMessage() self.response.authUser = message This means there is a ILoggingInfo adapter which returns a simple string. ASCII and no space are preffered because the standard access log format uses space aas delimiter. And access lgo fiels are not unicode. Of corse the ILoggingInfo adapter is responsible for choose the right format for each project. A default is configured in zope.publisher.principallogging PrincipalLogging Now to the question. In the latest checkins there was a access log part implemented. It doesn't use the ILoggingInfo adapter and is exposing the user login which is a part of the security credential. This get already released. (not good) Is there a standard how WSGI apps will log user info in access logs? I guess not, right? Does someone have a good idea how we should implement user access info for access logs in zope.app.wasg? If not, I propose the following: logging_info = ILoggingInfo(request.principal, None) if logging_info is None: message = '-' else: message = logging_info.getLogMessage() environ['wsgi.logging_info'] = message - this will set a ``wsgi.logging_info`` environ variable (or is there already a standard name)? - it uses the ILoggingInfo adapter which let us use different kind of access log info strategies in custom projects. By default we should use the PrincipalLogging adapter form zope.publisher.principallogging. Does anybody have a better idea how we can make the user info available for the access log? Alex whould this fit for you? Regards Roger Ineichen _____________________________ END OF MESSAGE

1 0

trying out the buildout-based Zope 2.12...
by Chris Withers 31 Mar '09

31 Mar '09

Hey All, I'm trying to get Zope 2.12 working with buildout, in the absence of docs, I thought I'd try: [buildout] parts = zopetest [zopetest] recipe = zc.recipe.egg interpreter = py eggs = zope2 ...and was rewarded with: Got zope.principalregistry 3.7.0. While: Installing zopetest. Error: There is a version conflict. We already have: zope.component 3.5.1 but zope.app.security 3.7.0 requires 'zope.component>=3.6.0'. wtf? Chris

8 39

snakebite
by Martijn Faassen 30 Mar '09

30 Mar '09

Hi there, Recently there was a project called snakebite revealed: http://www.snakebite.org/ http://mail.python.org/pipermail/python-committers/2009-January/000331.html It's basically a whole bunch of machines that open source projects, in particular Python related ones, can make use of for testing. It's essentially a buildbot farm as I understand it. The announcement says: "Every CPython, Jython, IronPython and PyPy committer will have access to every development server on the network. I’ve also extended the offer to prominent Python projects like Django and Twisted." I think the Zope project counts as a "prominent Python project" and we have a lot of interesting code to test, so perhaps they'll let us in. :) Would people be interested in working on making use of this platform? We could use it for testing of a wide range of packages. Perhaps the ZODB would be an interesting package to start with. If so we should approach snakebite to see whether we can get on board. Regards, Martijn

6 7

Buildbot for Zope 3
by Sebastien Douche 30 Mar '09

30 Mar '09

Hi, sad time for zope 3: http://zope.buildbot.securactive.org/waterfall Tell me if you other things (I want repoze, python and Tarek's distutils). -- Sebastien Douche <sdouche(a)gmail.com>

1 0

progress on Zope 2.12.0a1 from buildout with no funky recipes ; -)
by Chris Withers 30 Mar '09

30 Mar '09

Hey All, I've made some progress on this, here's the buildout: [buildout] parts = zopeinstance extends = versions2.cfg [zopeinstance] recipe = zc.recipe.egg eggs = zope2 entry-points= runzope=Zope2.Startup.run:run zopectl=Zope2.Startup.zopectl:main scripts = runzope zopectl initialization = import sys sys.argv[1:1] = ['-C','${buildout:directory}/etc/zope.conf'] There are 3 other files you need: - versions2.cfg, which is a static copy of: http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg (and changed to extend versions3.cfg instead of versions-zope3.cfg) - versions3.cfg, which is a static copy of: http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope3.cfg - zope.conf, which is a minimal zope.conf So, with this, the following will work: - bin/runzope - bin/zopectl fg However, bin/zopectl (start|stop) doesn't work because line 131 of zopectl.py sets zdrun to a hard coded path. I guess we need to generate a script for zdrun that has all the eggs present. Any ideas on the "right" way to do this? I guess we may need to do something similar with zeoctl? cheers, Chris

1 1