Re: [Zope-dev] movedaddedremoved branches of zope.container and zope.lifecycleevent
Chris McDonough wrote: On 5/18/09 6:42 AM, Martijn Faassen wrote: Chris McDonough wrote: I don't currently have access to publish zope.intid, but I think it's probably ready for a release too, BTW. I just gave you access to this package. Stephan has a script by the way that can give you access to a wide range of packages, might be a good idea if he ran it. :) Thanks. zope.intid 3.7.1 (which depends on zope.lifecycleevent=3.5.2 and zope.location=3.5.4) has been released. Thanks. But: why is this not zope.intid 3.8? It's clearly not a bugfix release. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.* package dependencies report
Chris McDonough wrote: In SVN, as a result of changes to zope.container, zope.lifecycleevent, zope.location, and zope.intid: zope.intid/trunk/ OK (20 dependencies) (delta -14 dependencies) zope.container/trunk/ OK (30 dependencies) (delta -2 dependencies) zope.location/trunk/ OK (08 dependencies) (delta -0 dependencies) zope.lifecycleevent/trunk/ OK (04 dependencies) (delta -0 dependencies) zope.formlib/trunk/ OK (61 dependencies) (delta -1 dependencies) zope.catalog/trunk/ OK (35 dependencies) (delta -1 dependencies) Cool, the decrease in dependencies for zope.intid is really impressive. Looks like we still have some work to do concerning zope.formlib's dependencies, though. :) Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Mon May 18 12:00:00 2009 UTC to Tue May 19 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: Mon May 18 20:56:58 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011737.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 18 20:59:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011738.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon May 18 21:01:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011739.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon May 18 21:03:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011740.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon May 18 21:05:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011741.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon May 18 21:07:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011742.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon May 18 21:09:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011743.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon May 18 21:11:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011744.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.publication dependencies (volunteersneeded!)
Michael Howitz wrote: Am 15.05.2009 um 13:30 schrieb Martijn Faassen: [...] Cool. It would seem to make sense that the named template mechanism is bundled along with the page template library anyway (instead of the form library). zope.formlib currently depends on zope.app.pagetemplate too so we could easily leave a backwards compatibility import in place. Done. Moved namedtemplate to zope.app.pagetemplate and made new releases of zope.app.pagetemplate zope.formlib Also cut the dependency of zope.app.publication on zope.app.exception by moving ISystemErrorView to zope.browser. Released: zope.browser zope.app.exception zope.app.publication Very cool, thanks very much for doing this work! Looking at the new dependency cycle graphs again. This is the before: http://startifact.com/depgraphs/zope_app_publisher_cycles.svg And this is the after: http://startifact.com/depgraphs/zope_app_publisher_cycles2.svg zope.app.exception is now taken from the graph (good!) Somehow a direct cyclical dependency between zope.app.publication and zope.app.publication now exists where there wasn't any before. zope.app.publication now depends on zope.app.publisher and it didn't do so in the past. Ah, it looks like this was actually a missing dependency which got added about 6 weeks ago. We need to get rid of it... Let's continue with the other refactoring: It looks like we still need to lose the dependency of zope.app.publisher on zope.app.component, or alternatively (or in addition) lose the dependency on zope.app.component on zope.formlib and zope.app.security. The zope.app.security dependency turns out to be only a test dependency, so I just made it such. zope.app.component is starting to look pretty empty. I can see three things still going on in it: * some browser views in zope.app.component.browser. These are to support the ZMI and can stay where they are. * the registration of the zope:view and zope:resource directives. I'm not sure what these are for, as we have browser:view and browser:resource. Perhaps these can be safely lifted into zope.app.publisher, which defines the browser:* varieties * the code in zope.app.component vocabularies. This is support code to create vocabularies for utilities. It depends on zope.interface, zope.component and zope.schema, and zope.app.interface. It might be sensible to move this vocabulary stuff (along with the one in zope.app.interface that we depend on) into a package called zope.componentvocabulary. We can jettison zope.app.component then. zope.componentvocabulary would depend on zope.schema, zope.component, zope.interface and zope.security only. We can then make zope.app.publisher depend on zope.componentvocabulary and lose the zope.formlib dependency, along with the zope.app.security dependency. Anyone wants to work on zope.componentvocabulary? It'd contain zope.app.component.vocabulary + surrounding tests, and zope.app.interface's vocabulary that it depends on. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.publication dependencies (volunteersneeded!)
On Tuesday 19 May 2009, Martijn Faassen wrote: * the registration of the zope:view and zope:resource directives. I'm not sure what these are for, as we have browser:view and browser:resource. Perhaps these can be safely lifted into zope.app.publisher, which defines the browser:* varieties Yes. The zope:* variants are used to allow registration of non-browser views and resources. I am pretty sure it is still used, so we should keep them, but the move to zope.app.publisher makes sense. * the code in zope.app.component vocabularies. This is support code to create vocabularies for utilities. It depends on zope.interface, zope.component and zope.schema, and zope.app.interface. It might be sensible to move this vocabulary stuff (along with the one in zope.app.interface that we depend on) into a package called zope.componentvocabulary. We can jettison zope.app.component then. zope.componentvocabulary would depend on zope.schema, zope.component, zope.interface and zope.security only. We can then make zope.app.publisher depend on zope.componentvocabulary and lose the zope.formlib dependency, along with the zope.app.security dependency. I agree. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] movedaddedremoved branches of zope.container and zope.lifecycleevent
On 5/19/09 6:49 AM, Martijn Faassen wrote: Chris McDonough wrote: On 5/18/09 6:42 AM, Martijn Faassen wrote: Chris McDonough wrote: I don't currently have access to publish zope.intid, but I think it's probably ready for a release too, BTW. I just gave you access to this package. Stephan has a script by the way that can give you access to a wide range of packages, might be a good idea if he ran it. :) Thanks. zope.intid 3.7.1 (which depends on zope.lifecycleevent=3.5.2 and zope.location=3.5.4) has been released. Thanks. But: why is this not zope.intid 3.8? It's clearly not a bugfix release. Er, it actually isn't a major release. None of *its* interfaces moved. I thought we were defining major release as API change. - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] ComponentLookupError
I'm getting this traceback: == serving on http://127.0.0.1:8080 2009-05-17 11:56:42,332 ERROR [SiteError] http://localhost:8080 Traceback (most recent call last): File /home/tim/.buildout/eggs/zope.publisher-3.7.0-py2.5.egg/zope/publisher/publish.py, line 127, in publish publication.beforeTraversal(request) File /home/tim/.buildout/eggs/zope.app.publication-3.5.3-py2.5.egg/zope/app/publication/zopepublication.py, line 85, in beforeTraversal principal = auth.authenticate(request) File /home/tim/.buildout/eggs/zope.principalregistry-3.7.0-py2.5.egg/zope/principalregistry/principalregistry.py, line 58, in authenticate if p.validate(password): File /home/tim/.buildout/eggs/zope.principalregistry-3.7.0-py2.5.egg/zope/principalregistry/principalregistry.py, line 190, in validate pwManager = self.__getPasswordManager() File /home/tim/.buildout/eggs/zope.principalregistry-3.7.0-py2.5.egg/zope/principalregistry/principalregistry.py, line 184, in __getPasswordManager return getUtility(IPasswordManager, self.__pwManagerName) File /home/tim/.buildout/eggs/zope.component-3.6.0-py2.5.egg/zope/component/_api.py, line 171, in getUtility raise ComponentLookupError(interface, name) ComponentLookupError: (InterfaceClass zope.password.interfaces.IPasswordManager, u'SHA1') Though everything seems to me to be okay. This was originally a grokproject based application and uses grok 1.0a3 but I have been incrementally/painfully changing the versions of components to get it to run with ZODB3.9.0b1 The server starts but when I try to access http://localhost:8080 I get the above error. The principal in site.zcml looks like this: principal id=zope.manager title=Manager login=admin password=17e15cddd033e22ae348aeb5660fc2140aec35850c4da997 description=OSHIP Developer password_manager=SHA1 / Any ideas where to start on this? Thanks, Tim -- Timothy Cook, MSc Health Informatics Research Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] movedaddedremoved branches of zope.container and zope.lifecycleevent
Chris McDonough wrote: [snip] Er, it actually isn't a major release. None of *its* interfaces moved. I thought we were defining major release as API change. Hm, a dependency change isn't a bugfix either. It's an edge case, and one where I think we should err on the side of caution. It's a change in behavior that could have more consequences than the normally bugfix, though less consequences than API change. It could be argued that a change in dependencies *is* a feature change. Less might be registered. People might depend on implicit dependencies being present (even though they shouldn't). Less might be monkey-patched... It was recorded here previously: http://docs.zope.org/zopetoolkit/steeringgroup/decisions.html Moving code around as part of dependency refactoring is worth a feature release (x.y as opposed to x.y.z version number) for the affected packages. Changing an import to make use of a new package that came out of such refactoring is also worth a feature release. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ComponentLookupError
Am 19.05.2009 um 16:53 schrieb Tim Cook: [...] /home/tim/.buildout/eggs/zope.component-3.6.0-py2.5.egg/zope/ component/_api.py, line 171, in getUtility raise ComponentLookupError(interface, name) ComponentLookupError: (InterfaceClass zope.password.interfaces.IPasswordManager, u'SHA1') Did you include zope.password's configure.zcml? This is where the password manager utilities are defined. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] movedaddedremoved branches of zope.container and zope.lifecycleevent
On 5/19/09 11:06 AM, Martijn Faassen wrote: Chris McDonough wrote: [snip] Er, it actually isn't a major release. None of *its* interfaces moved. I thought we were defining major release as API change. Hm, a dependency change isn't a bugfix either. It's an edge case, and one where I think we should err on the side of caution. It's a change in behavior that could have more consequences than the normally bugfix, though less consequences than API change. It could be argued that a change in dependencies *is* a feature change. Less might be registered. People might depend on implicit dependencies being present (even though they shouldn't). Less might be monkey-patched... It was recorded here previously: http://docs.zope.org/zopetoolkit/steeringgroup/decisions.html Moving code around as part of dependency refactoring is worth a feature release (x.y as opposed to x.y.z version number) for the affected packages. Changing an import to make use of a new package that came out of such refactoring is also worth a feature release. OK, noted. Thanks, - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Why does restrictedTraverse() in Zope 2 not respect IPublishTraverse adapters?
Some days ago I ran into the same problem, and have been pointed to this
thread. Maybe you are interested in my solution. It's ugly, but I needed it
for a test-case, where I wanted to access
@@plone_context_state/is_view_template:
from ZPublisher.HTTPRequest import HTTPRequest
from ZPublisher.HTTPResponse import HTTPResponse
from Products.PloneTestCase import PloneTestCase
import base64
user_id = PloneTestCase.default_user
password = PloneTestCase.default_password
encoded = base64.encodestring( '%s:%s' % ( user_id, password ) )
auth_header = 'basic %s' % encoded
resp = HTTPResponse()
env={'SERVER_URL':'http://nohost/plone',
... 'URL':'http://nohost/plone',
... 'HTTP_AUTHORIZATION': auth_header,
... 'REQUEST_METHOD': 'GET',
... 'steps': [],
... '_hacked_path': 0,
... '_test_counter': 0,
... }
request = HTTPRequest(stdin=None, environ=env, response=resp)
request['PARENTS'] = [self.getPortal()]
contextState = request.traverse(weblog/issue193/
... @@plone_context_state)
request['ACTUAL_URL'] = 'http://nohost/weblog/issue193'
contextState.is_view_template()
True
request.close()
Grüße
Jan Hackel
Martin Aspeli wrote:
There's currently a funny inconsistency in Zope's Traversable class. If
you have a URL like http://localhost:8080/path/to/@@aview/foo, and
@@aview implements IPublishTraverse (and, I presume, if there's a custom
IPublishTraverse adapter for any other path component), URL traversal
will work fine, but calling to.restrictedTraverse('@@aview/foo') or some
variant thereof will fail, because (un)restrictedTraverse() does not
respect custom IPublishTraverse adapters.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.publication dependencies (volunteersneeded!)
Hi there, I started working on zope.componentvocabulary. It exists now and zope.app.interface and zope.app.component both depend on it, along with zope.app.publisher. We're not entirely rid of zope.app.component yet though: Martijn Faassen wrote: [snip] * the registration of the zope:view and zope:resource directives. I'm not sure what these are for, as we have browser:view and browser:resource. Perhaps these can be safely lifted into zope.app.publisher, which defines the browser:* varieties I need to do some analysis to see where the zope:view and zope:resource directives are in use. I don't want to accidentally introduce *more* dependencies as packages that use these directives would now have to depend on zope.app.publisher instead of zope.app.component, and zope.app.publisher carries around a load of dependencies. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.publication dependencies (volunteersneeded!)
Hey, I need to do some analysis to see where the zope:view and zope:resource directives are in use. I don't want to accidentally introduce *more* dependencies as packages that use these directives would now have to depend on zope.app.publisher instead of zope.app.component, and zope.app.publisher carries around a load of dependencies. I wrote a quick script that uses lxml to parse a whole lot of *.zcml files. I find that these directives are in use in the following places: zope.app.preference/src/zope/app/preference/configure.zcml zope.app.apidoc/src/zope/app/apidoc/codemodule/browser/introspector.zcml zope.app.apidoc/src/zope/app/apidoc/enabled.zcml zope.app.apidoc/src/zope/app/apidoc/disabled.zcml zope.app.publisher/src/zope/app/publisher/xmlrpc/configure.zcml zope.traversing/src/zope/traversing/browser/configure.zcml zope.html/src/zope/html/configure.zcml zope.app.form/src/zope/app/form/browser/tests/widgetDirectives.zcml zope.app.securitypolicy/src/zope/app/securitypolicy/browser/configure.zcml zope.app.http/src/zope/app/http/exception/configure.zcml zope.app.http/src/zope/app/http/configure.zcml zope.app.onlinehelp/src/zope/app/onlinehelp/configure.zcml zope.app.ftp/src/zope/app/ftp/configure.zcml zope.app.dav/src/zope/app/dav/configure.zcml zope.mimetype/src/zope/mimetype/configure.zcml The zope.traversing dependency is a problem today, as I don't think zope.app.component is currently a dependency of this package. It sets up various IAbsoluteURL views. It might actually be the best to move these ZCML directives *down* into zope.component. That won't affect the dependencies of zope.component at all in fact; the [zcml] dependencies of zope.component already need all the dependencies that zope.app.component's view and resource directives implement. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
