Zope-Dev June 2010

zope-dev@zope.dev

33 participants
93 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

Retire zope3-checkins list
by Baiju M 09 Aug '10

09 Aug '10

Hi, What about retiring zope3-checkins list ? Regards, Baiju M

3 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

Bug day report
by Jens Vagelpohl 14 Jul '10

14 Jul '10

2 2

Zope Toolkit - 1.0a1 release
by Hanno Schlichting 11 Jul '10

11 Jul '10

Hi. On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. You can read more about the release at http://docs.zope.org/zopetoolkit/releases/overview-1.0a1.html. The first ZTK release supports all of Python 2.4, 2.5 and 2.6. To use the ZTK release, you can use: [buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg This first release focuses on getting something out and defining the actual technical outcome of a release. Currently the release outcome is tailored to the needs of the three frameworks. Now would be a good time for any direct users of the ZTK to speak up and note anything that would make a ZTK release more useful to them. In a first dev release created earlier last week we tried to create an easy_install friendly index for the release. But there have been questions about the exact contents of the such an index. Furthermore it isn't clear if such an index would be useful at all to any potential ZTK consumer. Since the three frameworks only use buildout and have no use for any other means, we decided to drop the index from the release procedure until it's usefulness and exact definition have become clear. The release team is currently discussing the further roadmap to a 1.0 final release and has some open discussion points to what remains to be done until we can call it a final release and the process for further releases and version upgrades. We post our meeting notes at http://docs.zope.org/zopetoolkit/releaseteam/index.html. Feel free to start discussing with us on this mailing list. All the best, Hanno

7 9

[zope2] Help needed with security checks and add views
by Hanno Schlichting 10 Jul '10

10 Jul '10

Hi there, recently MJ opened a security related bug and disclosed it to the public at https://bugs.launchpad.net/zope2/+bug/578326. In short Zope 2 never supported the permission attribute on ZCML browser:view declarations. It seems some people might have specified this attribute and assumed it would do something. I have added a warning message to Zope 2 (trunk + 2.12 branch) which warns about those cases. This is similar to how we handle other such cases like the unsupported <require set_schema=".." /> and <require set_attributes="..." /> on class directives. But it turns out that Zope 2 itself is using this in one place, that looks like it ought to have a security declaration. The Products.Five.adding.ContentAdding class registered as an add view ("+") has no working security declarations I can see, and only has such a non-functioning permission="zope2.ViewManagementScreens" set. I'm not familiar enough with the add view concept to understand what this is doing. It also looks like both CMF and Plone use similar registrations for their add views. Ideally I'd love to add support for the permission attribute, as clearly people have been using it. But if there's nobody who can figure out how to do that, I'd at least like to clarify the add view case. Any help appreciated, Hanno

3 8

Invitation to bug day in July
by Christian Theune 06 Jul '10

06 Jul '10

Hi everyone, our bug day in July needs scheduling and we'd like you to tell us which day works best for you if you want to participate: http://doodle.com/akd2f59kdadp86r2 Everyone can participate: whether you want to report a bug, discuss a bug or a feature, fix bugs or do anything else to improve Zope software, feel free to step by on #zope@freenode and join us! The last bug day got a lot of work done, see the summarized reports in the wiki: http://wiki.zope.org/ztk/BugDay20100616 Hope to see you during the bug day in July, 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

2 4

Re: [Zope-dev] Zope summit topics
by Hanno Schlichting 06 Jul '10

06 Jul '10

On Mon, Jun 28, 2010 at 6:45 PM, Christian Theune <ct(a)gocept.com> wrote: > So I'd like to open up the floor to everyone who ponders participating > and express their wishes/hopes/expectations for the summit. Don't start > your engines trying to solve any specific issue right now. Try to > abstain from bikeshedding. Think of this as the preliminary > brainstorming to figure out what we want to talk about at the summit. Since nobody else wrote anything, I'll get started - feel free to skip this, as it's gotten long :) - Agree on a process for larger feature changes in "Zope". Things like zope.publisher vs. WSGI, changes to zope.interface semantics, security without proxies, the NoZCML movement, ... - we need to have a way to talk about these in a structured way, document things, create opportunities for feedback from various stakeholders and get a definitive answer on whether we allow it or not. There's different options for how exactly such a process might look like, but I think we definitely need one. - Recognize the weekly Zope-dev IRC meetings as an official voice of the Zope community and declare our support for the decisions we make in these. I think effectively that is what we have today, but it is currently not spoken out. We might want to make sure that certain important decisions do get a mailing list discussion, so that people who cannot attend the meeting have an opportunity to provide their feedback. This needs to be balanced carefully, so we don't get open-ended bikesheds on the mailing lists. - Try to find a way how we can communicate cool new things we do in the various projects. planet.zope.org is currently a bit empty and didn't even mention things like Grok and BB releases. Following the developer mailing lists of each project costs too much time, so it's currently extremely hard to know what others are working on inside the Zope community. I think we share too little knowledge and experience with each other. This could lead to ideas for further improvements and changes to Zope. What lessons have people learned in building RESTful interfaces, Web 2.0 UI's, what strategies on "decomposable UI" like zope.contentprovided / zope.viewlet have actually worked or whatever. The Zope packages have little to offer when it comes to "new" Web technologies but arguably that's one of the main things they are used for. I cannot think of anything else right now. There's always bikeshed topics like Python 3, Subversion vs. DVCS but I don't think talking about those at the current stage has much point. Hanno

4 5

Developer meeting in IRC tomorrow at 15:00 UTC
by Christian Theune 05 Jul '10

05 Jul '10

Hi, I'd like to invite to the next developer meeting on IRC (#zope@freenode) which happens tomorrow at 15:00 UTC. If you have anything you'd like to talk about, please feel free too send a topic suggestion in response to this post: it's really intended to be a platform for anyone of us to get itches scratched, so I want *you* to speak up. :) If nothing else comes up, we'll: - review/wrap up the KGS 3.4.1 release - look forward to the Zope summit As I probably won't make it tomorrow (Charlie, taking over?) I will point out some more details about the Zope summit here: The summit is intended to provide a space for as many of us as possible to meet face to face and look forward to what we want to do next. I'm happy to provide an organizational framework (time, space, infrastructure) at the gocept offices but I do not want to impose or imply anything, really (especially no hidden agendas, only open ones: do cool stuff!) So I'd like to open up the floor to everyone who ponders participating and express their wishes/hopes/expectations for the summit. Don't start your engines trying to solve any specific issue right now. Try to abstain from bikeshedding. Think of this as the preliminary brainstorming to figure out what we want to talk about at the summit. If nothing else, I'd be happy to get a list of ideas what people think would be worthwhile to talk about. 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

2 2

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 June 2010