Re: [Zope-dev] z3c.form 2.0 release?
2009/5/21 David Glick davidgl...@onenw.org: Won't this cause problems if a z3c.form uses a template which calls a macro from a traditional Zope page template? That is, make it impossible to use z3c.form in a site that isn't using z3c.pt for everything? That was the reason for z3c.ptcompat; it lets you use one import-location to switch between the two implementations. \malthe ___ 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] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Thu May 21 12:00:00 2009 UTC to Fri May 22 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu May 21 21:01:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011761.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu May 21 21:03:42 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011762.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu May 21 21:05:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011763.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu May 21 21:08:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011764.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu May 21 21:10:03 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011765.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu May 21 21:12:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011766.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu May 21 21:14:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011767.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu May 21 21:16:13 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011768.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 )
[Zope-dev] zope.app.component 3.8.2 release
I released a new version of zope.app.component to fix a bug introduced in the recently deprecation of its metadirectives. Packages that were broken by this should use this new version. -- Alex Smith Software Engineer Zope Corporation ___ 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] zope.app.publisher 3.7.0 release
I just released a new version of zope.app.publisher. The changes in this version are largely related to reducing dependencies on zope.app.component and zope.app.container. -- Alex Smith Software Engineer Zope Corporation ___ 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 2.0 release?
On May 21, 2009, at 11:09 PM, Malthe Borch wrote: 2009/5/21 David Glick davidgl...@onenw.org: Won't this cause problems if a z3c.form uses a template which calls a macro from a traditional Zope page template? That is, make it impossible to use z3c.form in a site that isn't using z3c.pt for everything? That was the reason for z3c.ptcompat; it lets you use one import-location to switch between the two implementations. Ah, right...I was remembering incorrectly why we were unable to use z3c.ptcompat from within Plone. The actual reason is that it uses ViewPageTemplateFile from z3c.pt when we need it from five.pt (I think...it's been a while). But we were able to work around that by adjusting the custom form and widget template factories in plone.z3cform David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ 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] zope.app.component 3.8.2 release
Alexander J Smith wrote: I released a new version of zope.app.component to fix a bug introduced in the recently deprecation of its metadirectives. Packages that were broken by this should use this new version. Oops: sorry for the breakage and thanks very much for the fix! 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 )
Re: [Zope-dev] zope.app.publication dependencies (volunteers needed!)
Hey, Chris McDonough wrote: [snip] I tried to go after this today (reversing the dependency setup between zope.formlib and zope.app.form). There are hundreds of changes that need to be made to move interfaces to zope.formlib. I made them (more or less mechanically) but then couldn't get the tests to pass. Since I don't actually use zope.formlib, I don't think it's appropriate that I commit anything. All right, thanks for trying. Hopefully someone else can take a look at it at some point. OTOH, I'm pretty convinced that this action would be a win for packages that depend on formlib. I found these: ./zope.app.component-3.7.0-py2.5.egg/EGG-INFO/requires.txt:zope.formlib ./zope.app.exception-3.5.0-py2.5.egg/EGG-INFO/requires.txt:zope.formlib ./zope.app.zcmlfiles-3.5.3-py2.5.egg/EGG-INFO/requires.txt:zope.formlib With the recent changes zope.app.component is almost devoid of code and packages that relied on zope.app.component now can rely on other packages and entirely avoid the zope.formlib dependency. zope.app.exception only depended on formlib's namedtemplate facility which now resides in zope.app.pagetemplate instead. zope.app.zcmlfiles is a scary package that just pulls in a lot of ZCML that hopefully can vanish entirely over time. 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 )
Re: [Zope-dev] zope.app.publisher 3.7.0 release
Hey, Alexander J Smith wrote: I just released a new version of zope.app.publisher. The changes in this version are largely related to reducing dependencies on zope.app.component and zope.app.container. Thanks very much for doing this work! I could actually remove the (direct) test-dependency on zope.app.component from it as well, though the tests will still obtain it indirectly. 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] package dependency refactoring progress report
Hi there, This is a progress report on the package dependency refactoring work. We've had a lot of people contribute to this process (thanks everybody!), and bit by bit we are able to make a serious impact on dependencies. Yay! Let's take for example zope.app.publisher, which a few weeks ago had a dependency structure like this: http://startifact.com/depgraphs/zope.app.publisher-before.svg (60 dependencies, including zope.app.form and zope.formlib). After a lot of work on a lot of packages, we now have a dependency structure like this: http://startifact.com/depgraphs/zope.app.publisher-after.svg (45 dependencies, no more form related stuff) Still a big graph, but a lot simpler nonetheless, and down 15 packages. So, due to the recent changes we've now managed to cut away zope.app.form and zope.formlib entirely from zope.app.publisher's dependency chain (except for the tests). The main dependency cycles we started out with in the big graph were these: http://startifact.com/depgraphs/zope_app_publisher_cycles.svg After some work we'd gotten it down to this: http://startifact.com/depgraphs/zope_app_publisher_cycles2.svg And by now the main cycles left are these: http://startifact.com/depgraphs/zope_app_publisher_cycles3.svg So, the only dependency cycles left in zope.app.publisher are these: zope.app.publisher -- zope.app.publication -- zope.app.http And also this (familiar) one: zope.container -- zope.filerepresentation I need to do some more analysis to see what other complexities we have in the dependency chain in the ZTK. One obvious set of tasks is to continue evaluating dependencies of things like zope.app.publisher to see whether we cannot take out a few more. Just study the graph and see what can be done by examining the code: http://startifact.com/depgraphs/zope.app.publisher-after.svg For instance, what is zope.app.pagetemplate doing depending on zope.dublincore? What about its direct dependency on zope.container? Another set of tasks is to examine all the test dependencies we have, as those are way more complicated than the main dependencies. Ideally our test dependencies shrink to nothing as well. This will be a hard slog as we rewrite tests, but we can target one dependency at the time, too. 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 )
Re: [Zope-dev] package dependency refactoring progress report
On 5/22/09 1:11 PM, Martijn Faassen wrote: After some work we'd gotten it down to this: http://startifact.com/depgraphs/zope_app_publisher_cycles2.svg And by now the main cycles left are these: http://startifact.com/depgraphs/zope_app_publisher_cycles3.svg So, the only dependency cycles left in zope.app.publisher are these: zope.app.publisher-- zope.app.publication-- zope.app.http In isolation, it sort of looks like we should just collapse zope.app.publication and zope.app.http *into* zope.app.publisher, given that the relationships between the packages are all cyclical. - C ___ 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] zope.mimetype 1.1.2 release
I just released a new version of zope.mimetype. This version no longer depends on zope.app.component directly. -- Alex Smith Software Engineer Zope Corporation ___ 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] package dependency refactoring progress report
Chris McDonough wrote: On 5/22/09 1:11 PM, Martijn Faassen wrote: After some work we'd gotten it down to this: http://startifact.com/depgraphs/zope_app_publisher_cycles2.svg And by now the main cycles left are these: http://startifact.com/depgraphs/zope_app_publisher_cycles3.svg So, the only dependency cycles left in zope.app.publisher are these: zope.app.publisher-- zope.app.publication-- zope.app.http In isolation, it sort of looks like we should just collapse zope.app.publication and zope.app.http *into* zope.app.publisher, given that the relationships between the packages are all cyclical. Well, zope.app.publication and zope.app.publisher are really completely different, despite their similar names. zope.app.publication is a publisher implementation, while zope.app.publisher contains publishable resources. IMHO, zope.app.publisher is more broadly useful than zope.app.publication. So I'm working on removing the dependency from zope.app.publisher to zope.app.publication. It's mostly done, but I'm writing tests for the code I'm moving, since it never had any tests... I'm thinking about also removing the reverse dependency (zope.app.publication - zope.app.publisher). I think the default view name logic might belong in publication, not publisher. Shane ___ 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] Another OFS.Traversable and ZPublisher inconsistency
Hi, So, we determined that OFS.Traversable's unrestrictedTraverse() shouldn't grow support for IPublishTraverse, which is fair enough. We're now using an ITraversable adapter instead (++namespace++). However, we found another inconsistency. In URL traversal, this works: /foo/bar/++namespace++/123 In OFS.Traversable, it doesn't, but this does: /foo/bar/++namespace++blah/123 The reason is that in restrictedTraverse(), we have this check: if name and name[:1] in '@+' and name != '+' and nsParse(name)[1]: ns, nm = nsParse(name) However, nsParse(name)[1] is '' if no name is provided after the namespace. In BaseRequest.traverseName() we have a similar, but more relaxed check: if name and name[:1] in '@+' ns, nm = nsParse(name) if ns: ... This also has the advantage of not calling nsParse() twice. I can't understand why OFS.Traversable would explicitly disallow namespace traversal with an empty string as the name. Is this on purpose, or a bug? 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 )