January 2010 - Zope-Dev

Manuel Beta
by Benji York 14 Jan '11

14 Jan '11

I've just released the first beta of Manuel, my next-generation doctest project. Being that zope-dev has some of the most well-informed users of doctest (and some of the most well-informed non-users of doctest), I'd like to gather feedback from this group before making an announcement to the wider world. Manuel is available from PyPI (http://pypi.python.org/pypi/manuel) with docs, details, and examples at http://packages.python.org/manuel/. I'm interested in any feedback and/or questions you may have be it technical, documentation, or "marketing" (i.e., how do I describe what Manuel does and what benefits it has). -- Benji York Senior Software Engineer Zope Corporation

5 12

vocabularies missing wihtout zope.app.schema
by Roger 22 Jul '10

22 Jul '10

Hi all I'm not happy with the current vocabulary registry concept. Some zope.* packages provide vocabularies as zope.schema.interfaces.IVocabularyFactory utilities. The current zope.schema vocabulary registry without the patch located in zope.app.schema can't lookup such vocabulary factory utilities. Which concept should the ZTK use? The plain vocabulary from zope.schema.vocabulary or the enhanced component lookupbased concept defined in zope.app.schema.vocabulary? Any hints how we should improve that? Regards Roger Ineichen _____________________________ END OF MESSAGE

6 7

zope.app.authentication
by Souheil CHELFOUH 02 Jul '10

02 Jul '10

Hello guys, I'm coding some stuff, using zope.app.authentication and this package appears to do too many things, in my opinion. Would it be wise to cut off some of the functionalities ? The pure PAU components could go in a dedicated package, like zope.pluggableauthservice The whole handling of principals, groups and folder makes it a bit hard to read and introduces a lot of redundancy if we wish to roll our own things. What do you guys think ? Cheers - Souheil

5 13

Possible DateTime timezone-related regression in Zope 2.12
by Martin Aspeli 05 Mar '10

05 Mar '10

Hi, We have a failing test in plone.app.dexterity 1.0a7. This is simply trying to compare two dates: >>> from DateTime import DateTime >>> DateTime() > DateTime(md.CreationDate()) True At least here in Australia, the second test fails. Right now, the following expressions are: DateTime(): DateTime('2010/01/10 11:20:24.718203 GMT+8') md.CreationDate(): '2010-01-10 11:19:57' DateTime(md.CreationDate()): DateTime('2010/01/10 11:19:57 GMT+0') On Zope 2.10, it's a different story: DateTime(): DateTime('2010/01/10 11:34:01.508 GMT+8') md.CreationDate(): '2010-01-10 11:24:42' DateTime(md.CreationDate()): DateTime('2010/01/10 11:24:42 GMT+8') Andi Zeidler looked into it briefly, and said the following: imho, this is due a bug in `DateTime` 2.12.0. the newer version behaves differently when it's initialized via a string representation of a date — it interprets the given date to be GMT while before it was taken to be from your local time zone: $ cd ~/plone/coredev/branches $ cat foo.py from DateTime import DateTime print DateTime('2010-01-09 00:34:37') $ 3.3/bin/zopepy foo.py 2010/01/09 00:34:37 GMT+1 $ 4.0/bin/zopepy foo.py 2010/01/09 00:34:37 GMT+0 so in your test, `DateTime(md.CreationDate())` will always be the current time, but with an implicitly added 'GMT+0' while `DateTime()` will be the current time in your local time zone. so if i'm not mistaken, on plone 4.0 the test with fail for you an me (in 'GMT+x' time zones) and pass in the u.s. fun! :) Does anyone know if this change was deliberate, or what may have happened? Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 3

Re: [Zope-dev] Possible DateTime timezone-related regression in Zope 2.12
by Laurence Rowe 05 Mar '10

05 Mar '10

2010/1/10 <zopyxfilter(a)gmail.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Martin Aspeli wrote: >> Wichert Akkerman wrote: >>> On 2010-1-10 04:36, Martin Aspeli wrote: >>>> so in your test, `DateTime(md.CreationDate())` will always be >>>> the current time, but with an implicitly added 'GMT+0' while >>>> `DateTime()` will be the current time in your local time zone. >>>> so if i'm not mistaken, on plone 4.0 the test with fail for you >>>> an me (in 'GMT+x' time zones) and pass in the u.s. fun! :) >>>> >>>> Does anyone know if this change was deliberate, or what may >>>> have happened? >>> Have you looked at >>> http://zope3.pov.lt/trac/log/Zope/trunk/lib/python/DateTime?rev=95999 >>> >>> > for hints? >> >> Yes, there are various timezone related changes, e.g. >> >> http://zope3.pov.lt/trac/changeset/81213/Zope/trunk/lib/python/DateTime >> >> > http://zope3.pov.lt/trac/changeset/85830/Zope/trunk/lib/python/DateTime >> >> It's hard to know whether this was an intended change or not, and >> if so, how to deal with the breakage in a way that's compatible >> with 2.10 and 2.12. >> >> I blame Laurence. :-p > Better blame DateTime :-) > Fixing one issue in DateTime is likely to trigger another new bug. > The DateTime is just fragile. I believe the current behaviour is intentional to preserve backwards compatibility. See the discussion starting here: https://mail.zope.org/pipermail/zope-dev/2007-October/030042.html Maybe it was 'fixed' on 2.10 branch some time later. Laurence

3 4

z3c.password and "failedAttempts" and SessionCredentialsPlugin
by Jan-Wijbrand Kolman 04 Feb '10

04 Feb '10

Hi, I'm looking into integrating z3c.password into an application that also uses the PAU with the principal folder, InternalPrincipals and the SessionCredentialsPlugin. One of the features of z3c.password that I'd like to use is locking out an user account after a number of failed login attempts. z3c.password provides such a feature. However, it seems this feature does not play well with the SessionCredentialsPlugin: The SessionCredentials will store the login and password that were submitted through the login form in a session. This login/password combination then is checked against the internal principal stored in the principal folder. If the password is correct then (obviously) everything is fine. When the password is incorrect, the user is directed back to the login form as authentication failed. If the page with the login form retrieves resources (like images or css of javascript files) and since the zopepublication will _try_ to authenticate every request, the wrongful login/password combination is checked multiple times for that page and its resources against the internal principal object. The internal principal mixin of z3c.password will count the number of failed checks. If you tell it to lock out an user after, say, three failed attempts, you have a problem, as the number of login page resources (thus requests) will quite easily outnumber the maximum number of attempts. Questions: is anyone using this feature of z3c.password in combination with the SessionCredentialsPlugin? If this is working for you, do you have any idea what I am doing wrong here? What type of authentication are the authors of z3c.password using? Thanks for any insight here. regards, jw

4 9

Zope Tests: 6 OK
by Zope Tests Summarizer 31 Jan '10

31 Jan '10

Summary of messages to the zope-tests list. Period Sat Jan 30 12:00:00 2010 UTC to Sun Jan 31 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: Sat Jan 30 20:44:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013479.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jan 30 20:46:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013480.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 30 20:48:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013481.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 30 20:50:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013482.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 30 20:52:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013483.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 30 20:54:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013484.html

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 30 Jan '10

30 Jan '10

Summary of messages to the zope-tests list. Period Fri Jan 29 12:00:00 2010 UTC to Sat Jan 30 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: Fri Jan 29 20:47:18 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013473.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Jan 29 20:49:18 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013474.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 29 20:51:18 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013475.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 29 20:53:18 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013476.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 29 20:55:18 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013477.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 29 20:57:18 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013478.html

1 0

bugfix release for zope.app.wsgi, pypi rights
by Jan-Wijbrand Kolman 29 Jan '10

29 Jan '10

Hi, I'd like to make a 3.6.1 bugfix release for zope.app.wsgi. On the trunk there's support for picking up "product configuration" that has not been released yet (however, it had been released in a bugfix release in the 3.4 line). Could I ask someone to grant me pypi rights for this package? regards, jw

2 2

Zope Tests: 6 OK
by Zope Tests Summarizer 29 Jan '10

29 Jan '10

Summary of messages to the zope-tests list. Period Thu Jan 28 12:00:00 2010 UTC to Fri Jan 29 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: Thu Jan 28 20:39:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013467.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jan 28 20:41:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013468.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 28 20:43:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013469.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 28 20:45:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013470.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 28 20:47:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013471.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 28 20:49:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013472.html

1 0