May 2009 - Zope-Dev - Zope lists

Zope Tests: 2 OK
by Zope Tests Summarizer 27 May '09

27 May '09

Summary of messages to the zope-tests list. Period Tue May 26 12:00:00 2009 UTC to Wed May 27 12:00:00 2009 UTC. There were 2 messages: 2 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue May 26 20:47:30 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011801.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue May 26 20:49:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011802.html

1 0

Zope 2.12.0 beta 2 released
by Andreas Jung 27 May '09

27 May '09

I just released Zope 2.12.0 beta 2 http://pypi.python.org/pypi/Zope2/2.12.0b2 and created the the official 2.12 release branch: http://svn.zope.org/Zope/branches/2.12/ Please keep the release branch stable from now on. The Zope 2 trunk is now open for new features and other cool stuff. I would like release 2.12.0 final within the next four to six weeks...Objections? Andreas

2 1

Re: [Zope-dev] [Interface-dev] zope.interface 3.5.1 bdist_rpm problem
by Jim Fulton 26 May '09

26 May '09

Thanks. Sorry this didn't make it in. I've added this to my to-do list. :) Jim On May 26, 2009, at 5:52 PM, Armen Babikyan wrote: > Hi, > > I originally submitted this patch for zope.interface 3.4.1 to > interface-dev(a)zope.org about a year ago. This problem still exists in > zope.interface 3.5.1. > > Thanks, > > Armen > > -------- Original Message -------- > Subject: zope.interface 3.4.1 bdist_rpm problem > Date: Tue, 20 May 2008 15:58:29 -0400 > From: Armen Babikyan <armenb(a)ll.mit.edu> > To: interface-dev(a)zope.org <interface-dev(a)zope.org> > > > > Hello, > > There's a small problem when using python distutils' bdist_rpm to > automatically generate RPMs. Some files are referenced in setup.py, > but > not added to a MANIFEST. Here's a patch: > > --- zope.interface-3.4.1/MANIFEST.in 1969-12-31 19:00:00.000000000 > -0500 > +++ zope.interface-3.4.1/MANIFEST.in 2008-05-20 13:23:54.000000000 > -0400 > @@ -0,0 +1,4 @@ > +include CHANGES.txt > +include src/zope/interface/README.txt > +include src/zope/interface/adapter.txt > +include src/zope/interface/human.txt > > This will let "python setup.py build && python setup.py bdist_rpm" > execute without error. > > Thanks, > > Armen > > > -- > Armen Babikyan > MIT Lincoln Laboratory > armenb(a)ll.mit.edu . 781-981-1796 > > _______________________________________________ > Interface-dev mailing list > Interface-dev(a)zope.org > http://mail.zope.org/mailman/listinfo/interface-dev -- Jim Fulton Zope Corporation

1 0

Zope Tests: 5 OK, 3 Unknown
by Zope Tests Summarizer 26 May '09

26 May '09

Summary of messages to the zope-tests list. Period Mon May 25 12:00:00 2009 UTC to Tue May 26 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Unknown ------- Subject: UNKNOWN : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon May 25 21:04:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011798.html Subject: UNKNOWN : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon May 25 21:06:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011799.html Subject: UNKNOWN : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon May 25 21:08:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011800.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 25 20:54:40 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011793.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 25 20:56:44 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011794.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon May 25 20:58:45 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011795.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon May 25 21:00:45 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011796.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon May 25 21:02:45 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011797.html

1 0

Re: [Zope-dev] [Checkins] SVN: z3c.form/trunk/ merged branch icemac_validate_NOT_CHANGED
by Adam GROSZER 26 May '09

26 May '09

Hello Michael, After some simple thinking there are some fears that this wrecks other basic fields validation. Something like the field is required, has a default value but is omitted on input. What will be the result? Accepting the default value instead of raising an error is definitely a problem. Also, values in the system might not be needed to re-validate? Image passing around a 100mb uploaded file. If this is meant only for a file upload field, then I think there should be a special validator registered for those. Would be nice to see some (functional) tests closing out the above fears. Functional, because on the unittest level you can force the widget to a lot of unexpected things, but that might not be inline with what happens when it's really done by the framework. Or better said, revert the changes locally, add those tests, apply the changes back and see whether the tests still pass. Sunday, May 17, 2009, 3:21:19 PM, you wrote: MH> Log message for revision 100028: MH> merged branch icemac_validate_NOT_CHANGED MH> MH> Changed: MH> U z3c.form/trunk/AUTHOR.txt MH> U z3c.form/trunk/CHANGES.txt MH> U z3c.form/trunk/src/z3c/form/validator.py MH> U z3c.form/trunk/src/z3c/form/validator.txt MH> -=- MH> Modified: z3c.form/trunk/AUTHOR.txt MH> =================================================================== MH> --- z3c.form/trunk/AUTHOR.txt 2009-05-17 13:18:11 UTC (rev 100027) MH> +++ z3c.form/trunk/AUTHOR.txt 2009-05-17 13:21:18 UTC (rev 100028) MH> @@ -11,10 +11,11 @@ MH> Daniel Nouri MH> Darryl Cousins MH> Herman Himmelbauer MH> +Jacob Holm MH> Laurent Mignon MH> Malthe Borch MH> Marius Gedminas MH> Martijn Faassen MH> Michael Howitz MH> Michael Kerrin MH> -Paul Carduner MH> +Paul Carduner MH> \ No newline at end of file MH> Modified: z3c.form/trunk/CHANGES.txt MH> =================================================================== MH> --- z3c.form/trunk/CHANGES.txt 2009-05-17 13:18:11 UTC (rev 100027) MH> +++ z3c.form/trunk/CHANGES.txt 2009-05-17 13:21:18 UTC (rev 100028) MH> @@ -150,7 +150,11 @@ MH> MH> - Bug: Don't cause warnings in Python 2.6. MH> MH> +- Bug: `validator.SimpleFieldValidator` is now able to handle MH> + `interfaces.NOT_CHANGED`. This value is set for file uploads when MH> + the user does not choose a file for upload. MH> MH> + MH> Version 1.9.0 (2008-08-26) MH> -------------------------- MH> MH> Modified: z3c.form/trunk/src/z3c/form/validator.py MH> =================================================================== MH> --- z3c.form/trunk/src/z3c/form/validator.py 2009-05-17 13:18:11 UTC (rev 100027) MH> +++ z3c.form/trunk/src/z3c/form/validator.py 2009-05-17 13:21:18 UTC (rev 100028) MH> @@ -42,9 +42,28 @@ MH> MH> def validate(self, value): MH> """See interfaces.IValidator""" MH> + context = self.context MH> field = self.field MH> - if self.context is not None: MH> - field = field.bind(self.context) MH> + widget = self.widget MH> + if context is not None: MH> + field = field.bind(context) MH> + if value is interfaces.NOT_CHANGED: MH> + if (interfaces.IContextAware.providedBy(widget) and MH> + not widget.ignoreContext): MH> + # get value from context MH> + value = zope.component.getMultiAdapter( MH> + (context, field), MH> + interfaces.IDataManager).query() MH> + else: MH> + value = interfaces.NO_VALUE MH> + if value is interfaces.NO_VALUE: MH> + # look up default value MH> + value = field.default MH> + adapter = zope.component.queryMultiAdapter( MH> + (context, self.request, self.view, field, widget), MH> + interfaces.IValue, name='default') MH> + if adapter: MH> + value = adapter.get() MH> return field.validate(value) MH> MH> def __repr__(self): MH> Modified: z3c.form/trunk/src/z3c/form/validator.txt MH> =================================================================== MH> --- z3c.form/trunk/src/z3c/form/validator.txt 2009-05-17 13:18:11 UTC (rev 100027) MH> +++ z3c.form/trunk/src/z3c/form/validator.txt 2009-05-17 13:21:18 UTC (rev 100028) MH> @@ -117,7 +117,6 @@ MH> in the login name: MH> MH> >>> import re MH> - MH> >>> class LoginValidator(validator.SimpleFieldValidator): MH> ... MH> ... def validate(self, value): MH> @@ -182,7 +181,125 @@ MH> ... (None, None, None, IPerson['email'], None), MH> ... interfaces.IValidator) MH> MH> +Widget Validators and File-Uploads MH> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ MH> MH> +File-Uploads behave a bit different than the other form MH> +elements. Whether the user did not choose a file to upload MH> +``interfaces.NOT_CHANGED`` is set as value. But the validator knows MH> +how to handle this. MH> + MH> +The example has two bytes fields where File-Uploads are possible, one MH> +field is required the other one not: MH> + + >>>> class IPhoto(zope.interface.Interface): MH> + ... data = zope.schema.Bytes( MH> + ... title=u'Photo') MH> + ... MH> + ... thumb = zope.schema.Bytes( MH> + ... title=u'Thumbnail', MH> + ... required=False) MH> + MH> +There are several possible cases to differentiate between: MH> + MH> +No widget MH> ++++++++++ MH> + MH> +If there is no widget or the widget does not provide MH> +``interfaces.IContextAware``, no value is looked up from the MH> +context. So the not required field validates successfully but the MH> +required one has an required missing error, as the default value of MH> +the field is looked up on the field: MH> + + >>>> simple_thumb = validator.SimpleFieldValidator( MH> + ... None, None, None, IPhoto['thumb'], None) + >>>> simple_thumb.validate(interfaces.NOT_CHANGED) MH> + + >>>> simple_data = validator.SimpleFieldValidator( MH> + ... None, None, None, IPhoto['data'], None) + >>>> simple_data.validate(interfaces.NOT_CHANGED) MH> + Traceback (most recent call last): MH> + RequiredMissing MH> + MH> +Widget which ignores context MH> +++++++++++++++++++++++++++++ MH> + MH> +If the context is ignored in the widget - as in the add form - the MH> +behavior is the same as if there was no widget: MH> + + >>>> import z3c.form.widget + >>>> widget = z3c.form.widget.Widget(None) + >>>> zope.interface.alsoProvides(widget, interfaces.IContextAware) + >>>> widget.ignoreContext = True + >>>> simple_thumb = validator.SimpleFieldValidator( MH> + ... None, None, None, IPhoto['thumb'], widget) + >>>> simple_thumb.validate(interfaces.NOT_CHANGED) MH> + + >>>> simple_data = validator.SimpleFieldValidator( MH> + ... None, None, None, IPhoto['data'], widget) + >>>> simple_data.validate(interfaces.NOT_CHANGED) MH> + Traceback (most recent call last): MH> + RequiredMissing MH> + MH> +Look up value from default adapter MH> +++++++++++++++++++++++++++++++++++ MH> + MH> +When the value is ``interfaces.NOT_CHANGED`` the validator tries to MH> +look up the default value using a ``interfaces.IValue`` MH> +adapter. Whether the adapter is found, its value is used as default, MH> +so the validation of the required field is successful here: MH> + + >>>> data_default = z3c.form.widget.StaticWidgetAttribute( MH> + ... 'data', context=None, request=None, view=None, MH> + ... field=IPhoto['data'], widget=widget) + >>>> zope.component.provideAdapter(data_default, name='default') + >>>> simple_data.validate(interfaces.NOT_CHANGED) MH> + MH> + MH> +Look up value from context MH> +++++++++++++++++++++++++++ MH> + MH> +If there is a context aware widget which does not ignore its context, MH> +the value is looked up on the context using a data manager: MH> + + >>>> class Photo(object): MH> + ... zope.interface.implements(IPhoto) MH> + ... MH> + ... data = None MH> + ... thumb = None + >>>> photo = Photo() + >>>> widget.ignoreContext = False + >>>> zope.component.provideAdapter(z3c.form.datamanager.AttributeField) MH> + + >>>> simple_thumb = validator.SimpleFieldValidator( MH> + ... photo, None, None, IPhoto['thumb'], widget) + >>>> simple_thumb.validate(interfaces.NOT_CHANGED) MH> + MH> +If the value is not set on the context it is a required missing as MH> +neither context nor input have a valid value: MH> + + >>>> simple_data = validator.SimpleFieldValidator( MH> + ... photo, None, None, IPhoto['data'], widget) + >>>> simple_data.validate(interfaces.NOT_CHANGED) MH> + Traceback (most recent call last): MH> + RequiredMissing MH> + MH> +After setting the value validation is successful: MH> + + >>>> photo.data = 'data' + >>>> simple_data.validate(interfaces.NOT_CHANGED) MH> + MH> + MH> +Clean-up MH> +++++++++ MH> + + >>>> gsm = zope.component.getGlobalSiteManager() + >>>> gsm.unregisterAdapter(z3c.form.datamanager.AttributeField) MH> + True + >>>> gsm.unregisterAdapter(data_default, name='default') MH> + True MH> + MH> + MH> Widget Manager Validators MH> ------------------------- MH> MH> _______________________________________________ MH> Checkins mailing list MH> Checkins(a)zope.org MH> http://mail.zope.org/mailman/listinfo/checkins -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Let him who takes the Plunge remember to return it by Tuesday.

2 1

XML-RPC does not work under the paster process
by Michael Haubenwallner 26 May '09

26 May '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When using paste.httpserver instead of twisted.wsgi server zope.publisher.xmlrpc.XMLRPCRequest.processInputs() hangs when reading 0 Bytes from the request (wsgi.input <socket._fileobject object>). As i found the zope.publisher.http.HTTPInputStream.readlines() signature was changed 3 years ago from readlines(self, hint=None) to readlines(self, hint=0) http://svn.zope.org/Zope3/trunk/src/zope/publisher/http.py?rev=66941&r1=669… Do you think we could revert the change? Bugs reported: zopeproject: https://bugs.launchpad.net/zope3/+bug/283089 grokproject: https://bugs.launchpad.net/grok/+bug/332063 Regards Michael - -- http://blog.d2m.at http://planetzope.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJvRDVl0uAvQJUKVYRAuMZAJ0eZBKjoInmx5CigwgjUf2gDpQyXQCfTBh5 IVbnn5i1v5WAwGPJxUJWCZs= =+cQ+ -----END PGP SIGNATURE-----

3 6

How to include a <style media="print"....> CSS file?
by Hermann Himmelbauer 26 May '09

26 May '09

Hi, I'm currently to make my application printer-friendly, thus I'd like to include a print-CSS file. Currently, I include CSS-files like that: -------------------------------------------------------- <resourceLibrary name="bspskin-lib" layer="zbsp.skin.interfaces.IBSPLayer" > <directory source="lib" include="base.css" /> </resourceLibrary> -------------------------------------------------------- This creates the following code: -------------------------------------------------------- <style type="text/css" media="all">  </style> -------------------------------------------------------- What I'd like to have now is to include some other CSS-file with media="print". The zc.resourcelibrary code seems not to be able to handle this, so I'm curious how to do this: 1) Simply write this directly into my page template 2) Hack zc.resourcelibrary, e.g. add a ZCML-directive "media" 3) Use some other package I'm unaware of Any suggestions? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

3 2

Re: [Zope-dev] SVN: zope.app.pagetemplate/tags/3.7.0/src/zope/app/pagetemplate/tests/test_simpleviewclass.py Coverage.
by Tres Seaver 26 May '09

26 May '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephan Richter wrote: > On Monday 25 May 2009, Tres Seaver wrote: >> Log message for revision 100382: >> Coverage. > > On a tag? My bad: I switched a checkout to the tag to make a release. Note that I then further borked the tag by recopying the trunk there. I have since erased the tag and recopied from the trunk at the original revision. 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 iD8DBQFKG0vw+gerLs4ltQ4RAnW6AJ9cMZNSFU5Aiw5XvKfkcfrF3jUS2ACeOnhT Yg0AnDllgXjc7cA/sE/xLBA= =po29 -----END PGP SIGNATURE-----

1 0

RFC: zope.app.pagetemplate.engine dependencies
by Tres Seaver 26 May '09

26 May '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Resolution #1 ============= Whereas: - - The 'zope.app.pagetemplate.engine' module pulls in nothing from 'zope.app' packages except some antique testing support in doctest; - - that module is potentially useful outside the scope of the Zope3 ZMI; therefore be it resolved: - - that we move the 'engine' module to 'zope.pagetemplate', along with its supporting scaffolding, and clean up the tests. Resolution #2 ============= Whereas: - - The 'evaluateInlineCode' support in the 'engine' module has no tests; - - its comments indicate that it exists to support 'zope.app.pythonpage', which doesn't even import the module; - - third-party consumers of the feature have a recently-released version of the egg which they can continue using indefinitely; therefore be it resolved: - - that we remove the code entirely, documenting the backward incompatibility in a new feature release. Resolution #3 ============= Whereas: - - In Zope2, the 'Products.PageTemplates.Expressions' module depends on the 'zope.app.pagetemplates.engine' module, but only uses its 'ZopeEngine' class; - - Zope2 further supplies its own context class (to avoid using the Zope3 security model); - - one remaining bit of non-overridden functionality is the Zope3- proxified 'getFunctionNamespace' wrapper, which probably won't work at all as intended; - - the other bit is the use of the AdapterNamespaces bit, which feeds into the 'getFunctionNamespace' bit; therefore be it resolved: - - that we forego using the 'ZopeEngine' class completely in Zope2, providing instead a forked / simplified implementation. Debate, anyone? 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 iD8DBQFKGsle+gerLs4ltQ4RAgNKAJwOyvPTdkV40l6YaE7LgXNvts9eagCdHlRF WYPBpVkAXT7nBhX9hSTj9rY= =5xWq -----END PGP SIGNATURE-----

4 6

Zope Tests: 5 OK, 3 Failed
by Zope Tests Summarizer 25 May '09

25 May '09

Summary of messages to the zope-tests list. Period Sun May 24 12:00:00 2009 UTC to Mon May 25 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun May 24 20:57:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011790.html Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun May 24 20:59:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011791.html Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sun May 24 21:01:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011792.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun May 24 20:47:37 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011785.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun May 24 20:49:41 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011786.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun May 24 20:51:45 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011787.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun May 24 20:53:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011788.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun May 24 20:55:52 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011789.html

2 1