April 2009 - Zope-Dev

Re: [Zope-dev] [Checkins] SVN: zope.annotation/trunk/setup.py Whitespace fixes
by Jacob Holm 03 Apr '09

03 Apr '09

Hi Baiju If this whitespace fix is based on the current style guide, I think the guide needs to be fixed. I find the fixed version much less readable. A function that takes this many arguments should have an exception to the PEP 8 rule of no whitespace around the equals sign used for keyword arguments. I *think* a reasonable rule is that if you split the call over multiple lines with one argument per line, you should add single spaces before and after the equals sign. What does anyone else think? - Jacob Baiju M wrote: > Log message for revision 98773: > Whitespace fixes > > > Changed: > U zope.annotation/trunk/setup.py > > -=- > Modified: zope.annotation/trunk/setup.py > =================================================================== > --- zope.annotation/trunk/setup.py 2009-04-01 21:02:33 UTC (rev 98772) > +++ zope.annotation/trunk/setup.py 2009-04-01 21:13:34 UTC (rev 98773) > @@ -23,14 +23,14 @@ > return open(os.path.join(os.path.dirname(__file__), *rnames)).read() > > setup( > - name = 'zope.annotation', > - version = '3.5.0dev', > - url = 'http://pypi.python.org/pypi/zope.annotation', > - license = 'ZPL 2.1', > - description = 'Object annotation mechanism', > - author = 'Zope Corporation and Contributors', > - author_email = 'zope-dev(a)zope.org', > - classifiers = [ > + name='zope.annotation', > + version='3.5.0dev', > + url='http://pypi.python.org/pypi/zope.annotation', > + license='ZPL 2.1', > + description='Object annotation mechanism', > + author='Zope Corporation and Contributors', > + author_email='zope-dev(a)zope.org', > + classifiers=[ > 'Development Status :: 5 - Production/Stable', > 'Intended Audience :: Developers', > 'License :: OSI Approved :: Zope Public License', > @@ -40,23 +40,23 @@ > 'Topic :: Internet :: WWW/HTTP', > 'Topic :: Software Development', > ], > - long_description = \ > + long_description= \ > read('src', 'zope', 'annotation', 'README.txt') > + '\n\n' + > read('CHANGES.txt'), > - packages = find_packages('src'), > - package_dir = {'': 'src'}, > - namespace_packages = ['zope',], > - install_requires = ['setuptools', > - 'zope.interface', > - 'zope.component', > - 'zope.location', > - 'zope.proxy', > - ], > - extras_require = dict( > - test = ['zope.testing', > - 'ZODB3'], > + packages=find_packages('src'), > + package_dir={'': 'src'}, > + namespace_packages=['zope',], > + install_requires=['setuptools', > + 'zope.interface', > + 'zope.component', > + 'zope.location', > + 'zope.proxy', > + ], > + extras_require=dict( > + test=['zope.testing', > + 'ZODB3'], > ), > - include_package_data = True, > - zip_safe = False, > + include_package_data=True, > + zip_safe=False, > ) > > _______________________________________________ > Checkins mailing list > Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/checkins >

7 7

Zope Tests: 5 OK, 2 Failed, 1 Unknown
by Zope Tests Summarizer 03 Apr '09

03 Apr '09

Summary of messages to the zope-tests list. Period Thu Apr 2 12:00:00 2009 UTC to Fri Apr 3 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu Apr 2 20:53:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011375.html Subject: FAILED (failures=3, errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu Apr 2 20:59:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011378.html Unknown ------- Subject: UNKNOWN : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu Apr 2 20:51:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011374.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 2 20:45:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011371.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 2 20:47:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011372.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 2 20:49:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011373.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 2 20:55:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011376.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu Apr 2 20:57:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011377.html

1 0

Dependencies on new packages should require feature releases
by Christian Theune 03 Apr '09

03 Apr '09

Hi, (this message probably just has a reminder function) in one of my apps I had to upgrade many packages to a lot of new versions suddenly when updating zope.publisher. That was caused because zope.publisher started depending on a new (previously non-existing) package within a bugfix release and I was only interested in that bugfix. Reading the Steering Group decisions, I think that's what the last sentence wants to say, but it abruptly ends mid-sentence. @Martijn: You started writing that sentence, you mind finishing whatever you tried to say? (I think it's what I wanted to say with this mail.) :) Christian -- Christian Theune · ct(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

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: > | 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... > > Plenty of people use it without plone. You might want to crawl out of > the vacuum you live in. Yes, and I'm one of them, but I don't think it's fair to try and tempt new users into it... I'm happy to be proven wrong by you writing lots of decent docs, picking up maintenance of zope.org and LocalFS ;-) 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: > | Why does it need to keep living even at old.zope.org? > > Why do you care if it does? Because someone needs to look after the (rather large, ancient and crufty) zope instance in which it lives, and it keeps on tripping up innocent passers-by. I don't think many of these passers by will be put off by the old.zope.org url and we'll still end up with people wondering why LocalFS doesn't work in Zope Classic 4.0 ;-) 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: > | - 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