May 2009 - Zope-Dev - Zope lists

ComponentLookupError
by Tim Cook 19 May '09

19 May '09

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* **************************************************************

2 1

Zope Tests: 8 OK
by Zope Tests Summarizer 19 May '09

19 May '09

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

1 0

zope.* package dependencies report
by Chris McDonough 19 May '09

19 May '09

FWIW, this may not be useful to some, but here's a (not-very-detailed) report on all the zope.* packages in Zope's SVN and the number of transitive dependencies they have. They are sorted in the order of most-dependencies-to-fewest. zope.introspectorui/trunk/ OK (96 dependencies) zope.paste/trunk/ OK (73 dependencies) zope.locking/trunk/ OK (72 dependencies) zope.html/trunk/ OK (71 dependencies) zope.psycopgda/trunk/ OK (65 dependencies) zope.testrecorder/trunk/ OK (63 dependencies) zope.formlib/trunk/ OK (62 dependencies) zope.catalog/trunk/ OK (36 dependencies) zope.principalannotation/trunk/ OK (35 dependencies) zope.rdb/trunk/ OK (34 dependencies) zope.intid/trunk/ OK (34 dependencies) zope.fssync/trunk/ OK (34 dependencies) zope.file/trunk/ OK (34 dependencies) zope.site/trunk/ OK (33 dependencies) zope.error/trunk/ OK (33 dependencies) zope.copypastemove/trunk/ OK (33 dependencies) zope.filerepresentation/trunk/ OK (32 dependencies) zope.container/trunk/ OK (32 dependencies) zope.viewlet/trunk/ OK (30 dependencies) zope.session/trunk/ OK (24 dependencies) zope.securitypolicy/trunk/ OK (21 dependencies) zope.introspector/trunk/ OK (20 dependencies) zope.contentprovider/trunk/ OK (20 dependencies) zope.traversing/trunk/ OK (18 dependencies) zope.server/trunk/ OK (18 dependencies) zope.bobo/trunk/ OK (18 dependencies) zope.publisher/trunk/ OK (17 dependencies) zope.principalregistry/trunk/ OK (15 dependencies) zope.sendmail/trunk/ OK (13 dependencies) zope.keyreference/trunk/ OK (13 dependencies) zope.authentication/trunk/ OK (13 dependencies) zope.wfmc/trunk/ OK (12 dependencies) zope.release/trunk/ OK (12 dependencies) zope.security/trunk/ OK (11 dependencies) zope.dublincore/trunk/ OK (11 dependencies) zope.pypisupport/trunk/ OK (10 dependencies) zope.minmax/trunk/ OK (10 dependencies) zope.kgs/trunk/ OK (10 dependencies) zope.index/trunk/ OK (10 dependencies) zope.bforest/trunk/ OK (10 dependencies) zope.annotation/trunk/ OK (09 dependencies) zope.testbrowser/trunk/ OK (08 dependencies) zope.location/trunk/ OK (08 dependencies) zope.mimetype/trunk/ OK (07 dependencies) zope.i18n/trunk/ OK (07 dependencies) zope.modulealias/trunk/ OK (06 dependencies) zope.pagetemplate/trunk/ OK (05 dependencies) zope.configuration/trunk/ OK (05 dependencies) zope.tales/trunk/ OK (04 dependencies) zope.sqlalchemy/trunk/ OK (04 dependencies) zope.schema/trunk/ OK (04 dependencies) zope.lifecycleevent/trunk/ OK (04 dependencies) zope.httpformdate/trunk/ OK (04 dependencies) zope.tal/trunk/ OK (03 dependencies) zope.size/trunk/ OK (03 dependencies) zope.deferredimport/trunk/ OK (03 dependencies) zope.component/trunk/ OK (03 dependencies) zope.testing/trunk/ OK (02 dependencies) zope.proxy/trunk/ OK (02 dependencies) zope.processlifetime/trunk/ OK (02 dependencies) zope.password/trunk/ OK (02 dependencies) zope.httpform/trunk/ OK (02 dependencies) zope.exceptions/trunk/ OK (02 dependencies) zope.documenttemplate/trunk/ OK (02 dependencies) zope.copy/trunk/ OK (02 dependencies) zope.browser/trunk/ OK (02 dependencies) zope.broken/trunk/ OK (02 dependencies) zope.z2release/trunk/ OK (01 dependencies) zope.xmlpickle/trunk/ OK (01 dependencies) zope.thread/trunk/ OK (01 dependencies) zope.structuredtext/trunk/ OK (01 dependencies) zope.sequencesort/trunk/ OK (01 dependencies) zope.interface/trunk/ OK (01 dependencies) zope.i18nmessageid/trunk/ OK (01 dependencies) zope.hookable/trunk/ OK (01 dependencies) zope.globalrequest/trunk/ OK (01 dependencies) zope.fixers/trunk/ OK (01 dependencies) zope.event/trunk/ OK (01 dependencies) zope.dottedname/trunk/ OK (01 dependencies) zope.deprecation/trunk/ OK (01 dependencies) zope.dependencytool/trunk/ OK (01 dependencies) zope.decorator/trunk/ OK (01 dependencies) zope.datetime/trunk/ OK (01 dependencies) zope.contenttype/trunk/ OK (01 dependencies) zope.cachedescriptors/trunk/ OK (01 dependencies) zope.weakset/trunk/ OK (00 dependencies) zope.timestamp/trunk/ OK (00 dependencies) zope.importtool/trunk/ OK (00 dependencies) A lot of nice work since the last time I did this (mid-2007 or so), when a lot of these packages pulled in "the world". - C

2 3

Re: [Zope-dev] SVN: Products.GenericSetup/trunk/Products/GenericSetup/browser/addWithPresettings.pt - don't rely on manage_page_header, manage_form_title and manage_page_footer (in Zope 2.12 they can't be acquired)
by Tres Seaver 18 May '09

18 May '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yvo Schubbe wrote: > Log message for revision 100073: > - don't rely on manage_page_header, manage_form_title and manage_page_footer (in Zope 2.12 they can't be acquired) > What? That can't be right: it will break *tons* of applications. Who did that? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKEYp0+gerLs4ltQ4RAgxsAJsEPXTCJjcg5Pg+UliO8gVDBmnTXgCgtxiu +Jdm+tV5Ij8g2mlOayqWSjI= =QC0l -----END PGP SIGNATURE-----

2 1

Zope Tests: 6 OK
by Zope Tests Summarizer 18 May '09

18 May '09

Summary of messages to the zope-tests list. Period Sun May 17 12:00:00 2009 UTC to Mon May 18 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun May 17 20:45:58 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011731.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun May 17 20:48:02 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011732.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun May 17 20:50:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011733.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun May 17 20:52:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011734.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun May 17 20:54:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011735.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun May 17 20:56:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011736.html

1 0

please release zc.buildout
by Adam GROSZER 18 May '09

18 May '09

Hello zope-dev, Would someone please release a new egg, "close_fds is not supported on Windows platforms" is blocking... -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: There is man for you, blaming on his boots the faults of his feet. - Samuel Beckett

1 0

z3c.form 2.0 release?
by Michael Howitz 18 May '09

18 May '09

Hi, what is still to be done for the z3c.form 2.0 release? Something I can help? Yours sincerely, -- Michael Howitz · mh(a)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

2 1

zc.recipe.cmmi shared builds
by Wolfgang Schnerring 18 May '09

18 May '09

Hello, I'd like to extend zc.recipe.cmmi to support shared build directories. Use case example: we use lxml in a lot of our projects, which currently means having to build libxml and libxslt over and over again, since the buildout needs to be standalone and thus can't depend on them being installed on the system. But while that's a necessity for deployment, it's really annoying for development. Plan of attack: Introduce an option "shared" (defaults to False). If that is set, a) calculate HASH as a hash of the recipe's current options (e. g. configure parameters, environment variables) b) perform the cmmi in ${buildout:download-cache}/cmmi/build/<HASH>, if that directory is not present yet. (Probably needs a little thought about how to differentiate between "present and has a complete build" and "present but we errored out") Any thoughts? Thanks, Wolfgang -- Wolfgang Schnerring · ws(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development

5 7

Mailinglist for Zope 2 bugs!?
by Andreas Jung 17 May '09

17 May '09

On 12.05.09 16:49, Sidnei da Silva wrote: > > > > That's not needed. Since the zope2-dev team is automatically > > subscribed to issues, we only need to set it's contact address. If we > > set that address to zope-dev(a)lists.zope.org, then issues will > > automatically be delivered to it. > > > Based on yesterdays discussion, I propose to setup a new mailman list 'zope2-tracker(a)zope.org' (or propose a better name) that will be added as primary contact address of the Zope 2 team @ Launchpad. So anyone can subscribe to Zope 2 ticket changes without having to be a member of the Zope 2 team. Objections? Andreas

5 8

z3c.form: Problem validating file uploads
by Michael Howitz 17 May '09

17 May '09

Hi, I'm using a trunk version of z3c.form and have the following situation: In my interface I have a zope.schema.Bytes field. z3c.form.converter.FileUploadDataConverter.toFieldValue returns z3c.form.interfaces.NOT_CHANGED when I do not upload a file. z3c.form.validator.SimpleFieldValidator.validate fails later on as the value (z3c.form.interfaces.NOT_CHANGED) is not of type str (which is required by the Bytes field). I created a branch in svn to show the behavior. (z3c.form/branches/ icemac_validate_NOT_CHANGED) I'm not sure how to fix this generally, some possible solutions come to my mind, but each idea has its own problems: 1) Create a special validator for zope.schema.Bytes + z3c.form.interfaces.IFileWidget which knows how to handle NOT_CHANGED. This does not seem to be a really general solution and might have the same problems like the following ideas. 2) When z3c.form.validator.SimpleFieldValidator.validate is called with NOT_CHANGED as value, try to look up the value on the context object. This fails on AddForms as the context there is the parent object. 3) When z3c.form.validator.SimpleFieldValidator.validate is called with NOT_CHANGED as value, do not validate hoping the previous value was valid. This approach fails with AddForms, too, when the Bytes field is required. (The missing-value-error does not get raised.) Anyone having an idea for a possibly working solution? Yours sincerely, -- Michael Howitz · mh(a)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

2 3