- Zope-Dev - Zope lists

Zope Tests: 6 OK
by Zope Tests Summarizer 11 Mar '10

11 Mar '10

Summary of messages to the zope-tests list. Period Wed Mar 10 12:00:00 2010 UTC to Thu Mar 11 12:00:00 2010 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: Wed Mar 10 20:37:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013714.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 10 20:39:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013715.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Mar 10 20:41:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013716.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Mar 10 20:43:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013717.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Mar 10 20:45:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013718.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Mar 10 20:47:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013719.html

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 10 Mar '10

10 Mar '10

Summary of messages to the zope-tests list. Period Tue Mar 9 12:00:00 2010 UTC to Wed Mar 10 12:00:00 2010 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: Tue Mar 9 20:36:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013708.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 9 20:38:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013709.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Mar 9 20:40:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013710.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Mar 9 20:42:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013711.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Mar 9 20:44:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013712.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Mar 9 20:46:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013713.html

1 0

Summary of today's developer meeting
by Christian Theune 10 Mar '10

10 Mar '10

Hi, here's the summary of yesterday's meeting. The meeting itself was going more in-depth on the topic we covered so for the next meeting I'll make the agenda even shorter. On the experiment side: while writing up the summary I noticed that yesterday's discussions started going into different directions at the same time and jump around without necessarily having conclusions. That makes it *very* hard to write summaries. I guess I'll try to moderate a bit better next week. I'm not sure what was different this week from last. Any ideas? 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 0 · fax +49 345 1229889 1 Zope and Plone consulting and development

1 0

Agenda for today's IRC meeting (3pm UTC on #zope)
by Christian Theune 10 Mar '10

10 Mar '10

(gmane seems to be stuck, so maybe this ends up being send twice...) Hi, continuing the experiment of weekly meetings, here's the reminder for today's meeting including the proposed agenda. Time and place is, again, 3pm UTC at #zope@freenode. If you'd like to review last week's summary, please check here: https://mail.zope.org/pipermail/zope-dev/attachments/20100302/60a8224d/atta… Agenda ------ These are agenda items compiled from last weeks summary and input from the community: - Test runners / nightly builds (10 minutes) - Volunteer for coordinating automated builds - Towards a list of projects/platforms/etc. we want guaranteed builds for - Access to Windows (2003) build machines for developers (Baiju M.) - Towards a ZTK release (10 minutes) - What is needed for a release? - Who's the release manager? - Can we ensure building Windows binaries? - Bug tracking / working on bugs regularly (5 minutes) - Wrap-up (5 minutes) Horizon ------- These items are currently tracked on the horizon: we won't discuss them at this meeting, but we'll get to them at some point: - How do we deal with proposed API changes and Python 3 compatibility? (Lennart Regebro) - Pondering *some* (re-)structuring of the ZTK to allow for better maintenance/release management/communication/marketing. (Chris McDonough) -- Christian Theune · ct(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

3 2

z3c.form - ComputedErrorViewMessage and crazy adapter behaviour
by Martin Aspeli 09 Mar '10

09 Mar '10

Hi, I posted about this earlier, but the message seems to have gotten lost in the ether. I am trying and struggling to use ComputedErrorViewMessage. So far, I've discovered two problems, one which affects IValue adapters in general. 1. The last discriminator of a ComputedErrorViewMessage (and an ErrorViewMessage) is listed as 'content': ErrorViewMessage = value.StaticValueCreator( discriminators = ('error', 'request', 'widget', 'field', 'form', 'content') ) ComputedErrorViewMessage = value.ComputedValueCreator( discriminators = ('error', 'request', 'widget', 'field', 'form', 'content') ) However, the adapter lookup further down in error.py does: class ErrorViewSnippet(object): ... def update(self): value = zope.component.queryMultiAdapter( (self.context, self.request, self.widget, self.field, self.form, self), interfaces.IValue, name='message') if value is not None: self.message = value.get() else: self.message = self.createMessage() Notice how the last parameter is 'self', i.e. the ErrorViewSnippet. To me, at least, 'content' suggests this refers to the value returned by form.getContent(), most likely form.context. There's no test for this discriminator that I can see, so I'm not sure whether the "bug" is that 'content' is a poor name, or if the last part of that tuple should be self.form.getContent() or self.form.context? 2. The order in which we use ErrorViewMessage or ComputedErrorViewMessage seems to make a difference to its ability to specialise. I really can't figure out what the bug is, though. I've captured and annotated an interpreter session to illustrate the problem: First, some imports: >>> from zope.interface import Interface >>> from zope.component import provideAdapter >>> from zope import schema >>> from zope.schema.interfaces import TooSmall >>> from z3c.form import form, error, field >>> from z3c.form.testing import setupFormDefaults, TestRequest Set up a test environment with two forms. >>> setupFormDefaults() >>> class DummyContext(object): ... pass >>> context = DummyContext() >>> class ISchema(Interface): ... field1 = schema.Int(min=10) >>> class Form1(form.Form): ... fields = field.Fields(ISchema) ... ignoreContext = True >>> class Form2(form.Form): ... fields = field.Fields(ISchema) ... ignoreContext = True Define two error message value adapters. Note that message2 is a specialisation of message1, that also takes the form into account. Also note that message1 (the more general) happens to be created first. >>> message1 = error.ErrorViewMessage(u"Message 1", error=TooSmall, field=ISchema['field1']) >>> message2 = error.ErrorViewMessage(u"Message 2", error=TooSmall, field=ISchema['field1'], form=Form2) Now register these adapters (the order doesn't matter) >>> provideAdapter(message1, name=u"message") >>> provideAdapter(message2, name=u"message") Let's now create an instance of Form1 and try to validate it. >>> form1 = Form1(context, TestRequest(form={'form.widgets.field1': '5'})) >>> form1.update() >>> data, errors = form1.extractData() >>> len(errors) 1 >>> errors[0].message u'Message 1' No surprises there. Now let's try Form2. We'd expect to see message2, since it is registered for the more specific form: >>> form2 = Form2(context, TestRequest(form={'form.widgets.field1': '5'})) >>> form2.update() >>> data, errors = form2.extractData() >>> len(errors) 1 >>> errors[0].message u'Message 1' Ouch. Why is our more specific adapter being ignored? Recall that the ErrorViewSnippet does the IValue adapter lookup like so: value = zope.component.queryMultiAdapter( (self.context, self.request, self.widget, self.field, self.form, self), interfaces.IValue, name='message') The adapted objects are: >>> (errors[0].context, errors[0].request, errors[0].widget, errors[0].field, errors[0].form, errors[0]) (TooSmall(5, 10), <z3c.form.testing.TestRequest instance URL=http://127.0.0.1>, <TextWidget 'form.widgets.field1'>, <zope.schema._bootstrapfields.Int object at 0x1030a1190>, <__main__.Form2 object at 0x1035c0b90>, <ErrorViewSnippet for TooSmall>) Let's look at the interfaces provided by ISchema['field1']: >>> from zope.interface import directlyProvidedBy >>> list(directlyProvidedBy(ISchema['field1']).flattened()) [<InterfaceClass z3c.form.util.IGeneratedForObject_4345958800>, <InterfaceClass z3c.form.util.IGeneratedForObject_4345958800>, <InterfaceClass zope.interface.Interface>] >>> Let's also look at what our adapters are actually adapting: >>> message1.__component_adapts__ (<class 'zope.schema._bootstrapinterfaces.TooSmall'>, None, None, <InterfaceClass z3c.form.util.IGeneratedForObject_4345958800>, None, None) >>> message2.__component_adapts__ (<class 'zope.schema._bootstrapinterfaces.TooSmall'>, None, None, <InterfaceClass z3c.form.util.IGeneratedForObject_4345958800>, <class '__main__.Form2'>, None) Our adapters are both in the registry: >>> from z3c.form.interfaces import IValue >>> from pprint import pprint >>> from zope.component import getSiteManager >>> pprint([r for r in getSiteManager().registeredAdapters() if r.provided == IValue]) [AdapterRegistration(<BaseGlobalComponents base>, [zope.schema._bootstrapinterfaces.TooSmall, Interface, Interface, IGeneratedForObject_4345958800, __main__.Form2, Interface], IValue, u'message', <z3c.form.value.ValueFactory object at 0x1030a1690>, u''), AdapterRegistration(<BaseGlobalComponents base>, [zope.schema._bootstrapinterfaces.TooSmall, Interface, Interface, IGeneratedForObject_4345958800, Interface, Interface], IValue, u'message', <z3c.form.value.ValueFactory object at 0x10268e390>, u'')] Sigh. Let's try again, this time creating the value adapters in the opposite order: >>> from zope.interface import Interface >>> from zope.component import provideAdapter >>> from zope import schema >>> from zope.schema.interfaces import TooSmall >>> from z3c.form import form, error, field >>> from z3c.form.testing import setupFormDefaults, TestRequest Set up a test environment with two forms. >>> setupFormDefaults() >>> class DummyContext(object): ... pass >>> context = DummyContext() >>> class ISchema(Interface): ... field1 = schema.Int(min=10) >>> class Form1(form.Form): ... fields = field.Fields(ISchema) ... ignoreContext = True >>> class Form2(form.Form): ... fields = field.Fields(ISchema) ... ignoreContext = True Define two error message value adapters. Note that message2 is a specialisation of message1, that also takes the form into account. Also note that message2 (the more specific) happens to be created first. >>> message2 = error.ErrorViewMessage(u"Message 2", error=TooSmall, field=ISchema['field1'], form=Form2) >>> message1 = error.ErrorViewMessage(u"Message 1", error=TooSmall, field=ISchema['field1']) Now register these adapters (the order doesn't matter) >>> provideAdapter(message1, name=u"message") >>> provideAdapter(message2, name=u"message") Let's now create an instance of Form1 and try to validate it. >>> form1 = Form1(context, TestRequest(form={'form.widgets.field1': '5'})) >>> form1.update() >>> data, errors = form1.extractData() >>> len(errors) 1 >>> errors[0].message u'Message 1' No surprises there. Now let's try Form2. This time, we get "Message 2" >>> form2 = Form2(context, TestRequest(form={'form.widgets.field1': '5'})) >>> form2.update() >>> data, errors = form2.extractData() >>> len(errors) 1 >>> errors[0].message u'Message 2' Let's also check the registry: >>> (errors[0].context, errors[0].request, errors[0].widget, errors[0].field, errors[0].form, errors[0]) (TooSmall(5, 10), <z3c.form.testing.TestRequest instance URL=http://127.0.0.1>, <TextWidget 'form.widgets.field1'>, <zope.schema._bootstrapfields.Int object at 0x10309b810>, <__main__.Form2 object at 0x10392bd50>, <ErrorViewSnippet for TooSmall>) >>> from zope.interface import directlyProvidedBy >>> list(directlyProvidedBy(ISchema['field1']).flattened()) [<InterfaceClass z3c.form.util.IGeneratedForObject_4345935888>, <InterfaceClass z3c.form.util.IGeneratedForObject_4345935888>, <InterfaceClass zope.interface.Interface>] >>> message1.__component_adapts__ (<class 'zope.schema._bootstrapinterfaces.TooSmall'>, None, None, <InterfaceClass z3c.form.util.IGeneratedForObject_4345935888>, None, None) >>> message2.__component_adapts__ (<class 'zope.schema._bootstrapinterfaces.TooSmall'>, None, None, <InterfaceClass z3c.form.util.IGeneratedForObject_4345935888>, <class '__main__.Form2'>, None) >>> from z3c.form.interfaces import IValue >>> from pprint import pprint >>> from zope.component import getSiteManager >>> pprint([r for r in getSiteManager().registeredAdapters() if r.provided == IValue]) [AdapterRegistration(<BaseGlobalComponents base>, [zope.schema._bootstrapinterfaces.TooSmall, Interface, Interface, IGeneratedForObject_4345935888, Interface, Interface], IValue, u'message', <z3c.form.value.ValueFactory object at 0x10309bd10>, u''), AdapterRegistration(<BaseGlobalComponents base>, [zope.schema._bootstrapinterfaces.TooSmall, Interface, Interface, IGeneratedForObject_4345935888, __main__.Form2, Interface], IValue, u'message', <z3c.form.value.ValueFactory object at 0x10309ba10>, u'')] If there's a difference here, I can't see it. Martin

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 09 Mar '10

09 Mar '10

Summary of messages to the zope-tests list. Period Mon Mar 8 12:00:00 2010 UTC to Tue Mar 9 12:00:00 2010 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: Mon Mar 8 20:36:56 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013702.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Mar 8 20:38:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013703.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Mar 8 20:40:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013704.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Mar 8 20:42:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013705.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Mar 8 20:44:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013706.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Mar 8 20:46:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013707.html

1 0

Agenda for today's IRC meeting (3pm UTC on #zope)
by Christian Theune 09 Mar '10

09 Mar '10

Agenda for today's IRC meeting at 3pm UTC on #zope Hi, continuing the experiment of weekly meetings, here's the reminder for today's meeting including the proposed agenda. Time and place is, again, 3pm UTC at #zope@freenode. If you'd like to review last week's summary, please check here: https://mail.zope.org/pipermail/zope-dev/attachments/20100302/60a8224d/atta… Agenda ------ These are agenda items compiled from last weeks summary and input from the community: - Test runners / nightly builds (10 minutes) - Volunteer for coordinating automated builds - Towards a list of projects/platforms/etc. we want guaranteed builds for - Access to Windows (2003) build machines for developers (Baiju M.) - Towards a ZTK release (10 minutes) - What is needed for a release? - Who's the release manager? - Can we ensure building Windows binaries? - Bug tracking / working on bugs regularly (5 minutes) - Wrap-up (5 minutes) Horizon ------- These items are currently tracked on the horizon: we won't discuss them at this meeting, but we'll get to them at some point: - How do we deal with proposed API changes and Python 3 compatibility? (Lennart Regebro) - Pondering *some* (re-)structuring of the ZTK to allow for better maintenance/release management/communication/marketing. (Chris McDonough) -- Christian Theune · ct(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

1 0

z3c.form - ComputedErrorViewMessage
by Martin Aspeli 09 Mar '10

09 Mar '10

Hi, I'm struggling to get custom ComputedErrorViewMessage adapters to work in z3c.form. I'm still debugging, but I came across this: In error.py: ErrorViewMessage = value.StaticValueCreator( discriminators = ('error', 'request', 'widget', 'field', 'form', 'content') ) ComputedErrorViewMessage = value.ComputedValueCreator( discriminators = ('error', 'request', 'widget', 'field', 'form', 'content') ) class ErrorViewSnippet(object): ... def update(self): value = zope.component.queryMultiAdapter( (self.context, self.request, self.widget, self.field, self.form, self), interfaces.IValue, name='message') if value is not None: self.message = value.get() else: self.message = self.createMessage() ... From what I can tell, self.context is the exception; self.request, self.widget, self.field and self.form are as you'd expect. But the last discriminator, 'content' does not match up with 'self' (i.e. the error view snippet). So, which is right? The discriminator on the value adapter factory, or the multi-adapter lookup? The documentation mentions 'content' as the discriminator, but doesn't define it any further. FWIW, my expection is that 'content' should be the form's context content object. Martin

1 0

vyshakh krishnan wants to chat
by vyshakh krishnan 08 Mar '10

08 Mar '10

----------------------------------------------------------------------- vyshakh krishnan wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-dbd6bff667-b1982e48b6-0879284f0da0a451 You'll need to click this link to be able to chat with vyshakh krishnan. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with vyshakh krishnan, visit: http://mail.google.com/mail/a-dbd6bff667-b1982e48b6-0879284f0da0a451 Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into "conversations" - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages All this, and its yours for free. But wait, there's more! By opening a Gmail account, you also get access to Google Talk, Google's instant messaging service: http://www.google.com/talk/ Google Talk offers: - Web-based chat that you can use anywhere, without a download - A contact list that's synchronized with your Gmail account - Free, high quality PC-to-PC voice calls when you download the Google Talk client We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser).

3 2

Zope Tests: 6 OK
by Zope Tests Summarizer 08 Mar '10

08 Mar '10

Summary of messages to the zope-tests list. Period Sun Mar 7 12:00:00 2010 UTC to Mon Mar 8 12:00:00 2010 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 Mar 7 20:36:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013696.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Mar 7 20:38:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013697.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:40:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013698.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:42:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013699.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:44:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013700.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:46:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013701.html

1 0