- Zope-Dev - Zope lists

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

29 May '09

Summary of messages to the zope-tests list. Period Thu May 28 12:00:00 2009 UTC to Fri May 29 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: Thu May 28 20:50:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011811.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 20:52:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011812.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 20:54:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011813.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu May 28 20:56:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011814.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu May 28 20:58:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011815.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 21:00:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011816.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu May 28 21:02:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011817.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu May 28 21:04:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011818.html

1 0

Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replaced the dependency on zope.deprecation with BBB imports
by Stephan Richter 28 May '09

28 May '09

On Monday 25 May 2009, Shane Hathaway wrote: > +- Replaced the dependency on zope.deprecation with BBB imports As a general question, how will people know that an import location changed? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

6 17

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 28 May '09

28 May '09

Summary of messages to the zope-tests list. Period Wed May 27 12:00:00 2009 UTC to Thu May 28 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (errors=1) : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 21:02:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011808.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 20:51:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011803.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 20:53:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011804.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 20:55:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011805.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed May 27 20:58:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011806.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Wed May 27 21:00:04 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011807.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed May 27 21:04:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011809.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed May 27 21:06:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011810.html

1 0

Test failure in zope.traversing 3.7.0
by Andreas Jung 27 May '09

27 May '09

I get the following failure while running the Zope 2.12 tests: ajung@suxmac2:~/sandboxes/Zope-2.12/2.12 bin/alltests Test-module import failures: Module: zope.traversing.tests.test_vhosting Traceback (most recent call last): File "/Users/ajung/.buildout/eggs/zope.traversing-3.7.0-py2.5.egg/zope/traversing/tests/test_vhosting.py", line 28, in <module> from zope.app.zptpage.zptpage import ZPTPage File "/Users/ajung/.buildout/eggs/zope.app.zptpage-3.5.0-py2.5.egg/zope/app/zptpage/__init__.py", line 18, in <module> from zptpage import ZPTPage File "/Users/ajung/.buildout/eggs/zope.app.zptpage-3.5.0-py2.5.egg/zope/app/zptpage/zptpage.py", line 29, in <module> from zope.app.pagetemplate.engine import AppPT ImportError: No module named engine Andreas

2 2

Zsql and oracle CLOB column
by harshad behere 27 May '09

27 May '09

Dear list, While inserting data into one of the oracle table's CLOB column using zsql via python script, we observed that zope process (running in debug mode) is getting terminated/killed if length of text data >= 4094 with message on command prompt Input string too long, limit 4096 Whereas for text data with length >=4001 and <=4093 - It throws following error OperationalError on <Products.mxODBCZopeDA.ZopeDA.DatabaseConnection "DSN=test_clob_oracle" thread 3672/3672 at 0x3ac3530>: ('HY000', 1704, '[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113) python script details: print context.clob_zsql_test(i_description='A'*4095). return printed zsql details - INSERT INTO CLOB_TEST(description) VALUES(<dtml-sqlvar i_description type="string">) Table/column details : id - number description - clob Where as if we use mxODBCZopeDA execute API with following insert query syntax string_value = 'A'*5000 query = """ INSERT INTO CLOB_TEST(document) VALUES(?) """ result = test_connection.execute(query, string_value) it works fine even with text data having length > 10000 After googling on the same found that execute method uses/support parameters binding (is it similar to oracle bind varibles ? thats may be reason why it works well). Do we have similar support for zsql or is there other workaround ? Configuration/other details are as follows : RDBMS : Oracle Database 10g Release 10.2.0.1.0 ODBC used : Oracle ODBC which shipped with Oracle-Client-10g Python adapter : mxODBC Python ODBC Interface - 2.1 Related Zope Product : mxODBCZopeDA-1.0.10 Zope : Zope 2.11.1-final Python : python 2.4.4 Operating system : win32 ZEO setup : Yes No of ZEO nodes : one Threads per ZEO node : 10 Any kind of pointers/suggestions would be of great help. Thanking you, Harshad.

1 1

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