[Zope-dev] Zope Tests: 4 OK, 1 Unknown
Summary of messages to the zope-tests list. Period Tue Aug 26 11:00:00 2008 UTC to Wed Aug 27 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Tue Aug 26 20:38:20 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010070.html Tests passed OK --- Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 26 20:39:50 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010071.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 26 20:41:20 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010072.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 26 20:42:50 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010073.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 26 20:44:20 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010074.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] [Checkins] SVN: zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt as it seems impossible to upload umlauts in long_description to pypi using distutils, so I had to replace t
This looks like a bad idea. You are weakening the test by removing non-ascii chars here. A better approach would have been to rewrite the non-ascii chars using \N (or \u or \U) escapes. Regards - Jacob Michael Howitz wrote: Log message for revision 90434: as it seems impossible to upload umlauts in long_description to pypi using distutils, so I had to replace the umlauts Changed: U zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt -=- Modified: zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt === --- zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt 2008-08-27 11:44:57 UTC (rev 90433) +++ zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt 2008-08-27 11:49:47 UTC (rev 90434) @@ -18,8 +18,8 @@ === zc.sourcefactory.browser.token.fromUnicode( - ... u'somestring with umlauts öäü') - '45dadc304e0d6ae7f4864368bad74951' + ... u'somestring with strange chars #*_;)') + 'f33b8a6b56403c9d560e2ef772336798' Integer === ___ Checkins mailing list [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/checkins ___ 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] Problems with schema Date field - year is truncated
Hi, I'm somehow stuck on the following problem: I defined a Date() schema field in one of my interfaces. I currently have a de-AT locale, so I'd like to enter the value of my date as e.g. dd.MM., e.g. 01.02.1980 in my z3c.form based form. What happens is, that the locale silently assumes a format of dd.MM.yy, which means, that the YY / 80 is truncated and 01.02.19 is stored in my database, when updating. So, I'd like to know if: - It is possible to change the format to dd.MM., which is a lot more appropriate for my application (a birth date) - Make the application more strict, meaning that no data is truncated in any case. I tried to stick my nose into i18n.locales but was somehow overwhelmed by what I found. However, the following somehow seems to explain it: /dateFormatLength dateFormatLength type=medium dateFormat patterndd.MM./pattern /dateFormat /dateFormatLength dateFormatLength type=short dateFormat patterndd.MM.yy/pattern /dateFormat /dateFormatLength Nevertheless I don't know if there's a way to select a specific dateFormat, e.g. medium in my case. Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ 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] weird release of transaction module
Hi there, I just looked at the PyPI page of 'transaction': http://pypi.python.org/pypi/transaction And I see some weirdnesses: * it's called 'transaction 1.0a1' * the 'changes' claim however: 1.0 (unreleased) What's up? Clearly something went wrong during the releasing of this package, at least documentation-wise. Should be fixed. Note that zope.sqlalchemy pulls in this package as a dependency, even though I don't think ZODB 3.8 comes with that version of transaction... 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] z3c.form - extraction from sequence widget
Hi, In z3c.form.widget.SequenceWidget, we have: def extract(self, default=interfaces.NOVALUE): See z3c.form.interfaces.IWidget. if (self.name not in self.request and self.name+'-empty-marker' in self.request): return [] value = self.request.get(self.name, default) if value != default: for token in value: if token == self.noValueToken: continue try: self.terms.getTermByToken(token) except LookupError: return default return value This means that if the request contains the empty-marker only (no selection was made) for a checkbox widget (say), then the return value is [], rather than default (NOVALUE). Is that a bug? I have a custom checkbox widget derived from the standard checkbox widget, (z3c.formwidget.query, in fact), and I never get any required missing exceptions, even when I untick all the checkboxes and click OK. Am I missing something? Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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] z3c.form - extraction from sequence widget
On Wednesday 27 August 2008, Martin Aspeli wrote: This means that if the request contains the empty-marker only (no selection was made) for a checkbox widget (say), then the return value is [], rather than default (NOVALUE). Is that a bug? I have a custom checkbox widget derived from the standard checkbox widget, (z3c.formwidget.query, in fact), and I never get any required missing exceptions, even when I untick all the checkboxes and click OK. Am I missing something? I think you have a point. Have you tried changing the behavior to return default and see what tests fail? If no major failures come out of this, I would say change it. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training 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] z3c.form - extraction from sequence widget
On Wed, Aug 27, 2008 at 05:15:48PM -0700, Stephan Richter wrote: On Wednesday 27 August 2008, Martin Aspeli wrote: This means that if the request contains the empty-marker only (no selection was made) for a checkbox widget (say), then the return value is [], rather than default (NOVALUE). Is that a bug? I have a custom checkbox widget derived from the standard checkbox widget, (z3c.formwidget.query, in fact), and I never get any required missing exceptions, even when I untick all the checkboxes and click OK. Am I missing something? I think you have a point. Have you tried changing the behavior to return default and see what tests fail? If no major failures come out of this, I would say change it. Wait a second, maybe I'm misunderstanding this, but I certainly oppose any change that would make an unchecked checkbox an error during form validation. A required Bool field can have two values: True or False. One is represented by a checked checkbox, the other by an unchecked checkbox. An unchecked checkbox is not missing input and should not trigger required missing errors. Marius Gedminas -- As easy as 3.14159265358979323846264338327950288419716 signature.asc Description: Digital signature ___ 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 )
