Zope-Dev February 2010

zope-dev@zope.dev

36 participants
60 discussions

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

zope.dublincore and zope.copypastemove not compatible?
by Michael Howitz 14 Sep '10

14 Sep '10

Hi, I found something strange in metadata when copying a persistent object. My situation is the following: I have a container with some elements inside. I create a copy of this container using zope.copypastemove.ObjectCopier(my_container).copyTo(my_container.__parent__) (Actually I use zope.copypastemove.interfaces.IObjectCopier(my_container) but this calls the adapter mentioned above.) Side note: Is this the right way to copy an persistent object nowadays? This happens tho dublin core metadata then: As zope.dublincore.timeannotators.CreatedAnnotator is subscribed to zope.lifecycleevent.IObjectCreatedEvent it gets called as the ObjectCopiedEvent is a subclass of ObjectCreatedEvent. The copy of the container gets a new creation date set in its metadata. But zope.copypastemove.dispatchToSublocations calls the subscribers for the sublocations using zope.component.subscribers((sub, event), None) So the zope.dublincore.timeannotators.CreatedAnnotator does not get called as it is not registered for (object, event) but only for (event,). This leads to a strange situation: the metadata of the copied container get updated but not the metadata of its contents. This behavior has not changed since version 3.4.0 which was about 2,5 years ago. I think this is a long-standing bug and it should it be fixed in zope.dublincore by registering the subscribers for (object, event)? (Additionally or exclusively, I'm not sure.) Any thoughts? Yours sincerely, -- Michael Howitz · mh(a)gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development

1 3

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

redirect burps on unicode URLs
by Adam GROSZER 01 Mar '10

01 Mar '10

Hello, Looks like zope.publisher burps on unicode URL which contain non-ascii chars. This is from a KGS 3.4 application, but looking at the source it still seems to have the same problems. opinions? ... self.request.response.redirect(url) File "d:\home\.buildout\eggs\zope.publisher-3.4.6-py2.5.egg\zope\publisher\browser.py", line 729, in redirect return super(BrowserResponse, self).redirect(location, status) File "d:\home\.buildout\eggs\zope.publisher-3.4.6-py2.5.egg\zope\publisher\http.py", line 882, in redirect self.setHeader('Location', location) File "d:\home\.buildout\eggs\zope.publisher-3.4.6-py2.5.egg\zope\publisher\http.py", line 676, in setHeader value = str(value) UnicodeEncodeError: 'ascii' codec can't encode character u'\xd6' in position 71: ordinal not in range(128) -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: There is not a heart that but has its moments of longing, yearning for something better. - Henry Ward Beecher

7 19

Adding W3C validating to zope.testbrowser
by Ross Patterson 28 Feb '10

28 Feb '10

I started a branch for doing W3C HTML validation on responses to zope.testbrowser requests: svn://svn.zope.org/repos/main/zope.testbrowser/branches/rossp-validator The idea is to be able to flip a switch and run all my functional zope.testbrowser tests and see validation failures as test failures. The current implementation in that branch just uses a simple environment variable since I wasn't sure what the best way was to support flipping a switch like that. Note that it's possible to use a local installation of the W3C validator (such as is available on Debian based systems in the w3c-markup-validator package) so that the validation doesn't actually slow tests down all that much. I have a couple of questions I'd like to hear any thoughts on. What's the best way to support "flipping the switch" in a global sense so that during the inner testing loop extra time isn't being wasted on repeated validations? Does this belong in zope.testbrowser or in the underlying mechanize package? Other than that, what's the path forward to merging? Ross

5 8

Zope Tests: 6 OK
by Zope Tests Summarizer 28 Feb '10

28 Feb '10

Summary of messages to the zope-tests list. Period Sat Feb 27 12:00:00 2010 UTC to Sun Feb 28 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 Feb 27 20:36:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013647.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Feb 27 20:38:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013648.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 27 20:40:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013649.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 27 20:42:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013650.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 27 20:44:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013651.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 27 20:46:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013652.html

1 0

Developer IRC meeting on#zope next Tuesday at 3pm UTC
by Christian Theune 27 Feb '10

27 Feb '10

Hi everybody, I've been talking to some people in the last weeks trying to figure out how to build upon the good things Martijn brought to the developer community over the last year but also avoiding the troubles he experienced. For starters, I'd like to introduce real-time meetings that we can use to organise ourselves better. I suggest those to happen on IRC. Let's consider this as an experiment without too much overhead, so I'll just start running those meetings through the month of March. I will be on IRC and I'd be happy to talk to people about whatever they think relevant for improving the developer community and/or Zope and I'd be happy if some of you actually show up. I'll also create a summarized report of the meeting and send that out to zope-dev so whatever happens remains visible for the rest who could not attend. Rules ----- Location freenode, #zope Rhythm weekly, every Tuesday in March on 3pm UTC Duration *exactly* 30 minutes, guaranteed Report I will send the IRC log and a summary to zope-dev, maybe publish to wider audience. Moderation I will moderate the meeting (for now) and will walk us through the agenda and keep an eye on the clock. Agenda ------ To keep the meeting constructive and focused I will take the lead on moderating what we discuss. Please send topics you'd like to talk about to me by mail (ct(a)gocept.com) and I will compile an agenda. I'll do some upfront prioritization and give a short period at the beginning of the meeting for attendees to challenge topics they feel I mis-prioritized. Time rules ---------- The meeting will take exactly 30 minutes - after that I *will* wrap up and create the summary. I'd like the meeting itself to focus on organisational issues, not directly solving/discussing technical issues or getting work done. As I want this to spur action, you're free (and welcome!) to stay after the offical part and go into the topics further. Warning ------- I know that I'll fill both a moderator role and have my own stakes in the topics, so please bear with me if I'm struggling balancing that. Cheers, 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

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Zope-Dev February 2010