[Zope-Checkins] SVN: Zope/trunk/lib/python/ZopeUndo/ Revert -r95019 as it conflicts with the external.
Log message for revision 95213: Revert -r95019 as it conflicts with the external. Changed: D Zope/trunk/lib/python/ZopeUndo/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] zope.globalrequest?
Roger Ineichen wrote: I see your point. I'm not saying that this is bad in general. Probably when used in moderation is the right concept for this package ;-) and it wasn't written with anything else in mind -- merely for the odd case when you need a request object, but none has been passed around. imho, it makes more sense to use a defined API in those cases instead of relying on knowledge about the current implementation. i mean, sometimes it's not possible to adjust the design and change all of the involved code (at least not timely), in which case people may resolve to simply fetch the request from anywhere they know it's accessible. a common API does help here, especially when it comes to changing things. but like i said, that's not supposed to mean `zope.globalrequest` was to promote a new pattern for zope development. cheers, andi -- zeidler it consulting - http://zitc.de/ - i...@zitc.de friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.1.5.1 released! -- http://plone.org/products/plone/ ___ 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] can these wrong DEPENDENCIES.cfg files be removed?
We are working on zope.app.renderer and I see that there is a file named DEPENDENCIES.cfg that lists: docutils zope.app zope.component zope.configuration zope.interface zope.schema zope.structuredtext zope.testing while the actual package has a different list of dependencies: setuptools docutils zope.component zope.configuration zope.i18nmessageid zope.interface zope.publisher zope.schema zope.structuredtext [test] zope.app.testing What is the DEPENDENCIES.cfg file for, and why are the dependencies listed different than the current ones in setup.py? Can I just remove the redundant information in DEPENDENCIES.cfg and have the information in just one place instead? -- Brandon Craig Rhodes bran...@rhodesmill.org http://rhodesmill.org/brandon ___ 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] can these wrong DEPENDENCIES.cfg files be removed?
AFAIK, these files are for (pre-egg, no-longer-used) zpkg tool. They are removed in zope.app.renderer's trunk, BTW. 2009/1/27 Brandon Craig Rhodes bran...@rhodesmill.org: We are working on zope.app.renderer and I see that there is a file named DEPENDENCIES.cfg that lists: docutils zope.app zope.component zope.configuration zope.interface zope.schema zope.structuredtext zope.testing while the actual package has a different list of dependencies: setuptools docutils zope.component zope.configuration zope.i18nmessageid zope.interface zope.publisher zope.schema zope.structuredtext [test] zope.app.testing What is the DEPENDENCIES.cfg file for, and why are the dependencies listed different than the current ones in setup.py? Can I just remove the redundant information in DEPENDENCIES.cfg and have the information in just one place instead? -- Brandon Craig Rhodes bran...@rhodesmill.org http://rhodesmill.org/brandon ___ 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 ) -- WBR, Dan Korostelev ___ 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] Plans for Zope 2.12
Dieter Maurer wrote: Chris Withers wrote at 2009-1-22 09:38 +: ... One thing that myself and Shane talked briefly about on this list was re-implementing the AST manipulation as dissallow-by-default filter rather than a straight manipulation. That way, unexpected stuff should be allowed by default. The terms do not seem to match: disallow-by-default would mean that unexpected stuff would be disallowed by default. Sorry, you're correct, I meant unexpected stuff should be disallowed by default... cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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: 6 OK, 2 Failed
Summary of messages to the zope-tests list. Period Mon Jan 26 12:00:00 2009 UTC to Tue Jan 27 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (failures=1, errors=29) : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Jan 26 20:56:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010949.html Subject: FAILED (failures=1, errors=29) : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Jan 26 20:57:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010950.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Jan 26 20:47:11 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010943.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Mon Jan 26 20:48:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010944.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Mon Jan 26 20:50:11 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010945.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Mon Jan 26 20:51:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010946.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Jan 26 20:53:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010947.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Jan 26 20:54:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010948.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] Plans for Zope 2.12
Shane Hathaway wrote: Chris Withers wrote: I don't think this is such a huge change, it's a change in the style of what RP does already, not a complete re-implementation... OTOH, with Python 3 now released, it seems unlikely that we'll see any new syntax added to Python 2.x. So RP doesn't really need any sort of overhaul until we start switching to Python 3. I'm still curious as to how hard a job this will be, part of me hopes this will be a lot easier than expected ;-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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] can these wrong DEPENDENCIES.cfg files be removed?
On Tuesday 27 January 2009, Fred Drake wrote: On Tue, Jan 27, 2009 at 6:01 AM, Dan Korostelev nad...@gmail.com wrote: AFAIK, these files are for (pre-egg, no-longer-used) zpkg tool. They are removed in zope.app.renderer's trunk, BTW. I certainly hope no one is relying on that old tools! I care about those files in Zope3/ and ZODB3/, since they are used to create the Zope 3 tar ball. Remember, Zope 3.4 will be the *first* release where we officially introduce eggs. And I have heard from a lot of people that would like to see a couple more TAR ball releases. I have a script to update the Zope3/ tree, so it is fairly easy for me to fulfill that request. 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] can these wrong DEPENDENCIES.cfg files be removed?
On Tuesday 27 January 2009, Dan Korostelev wrote: Isn't it possible to rewrite the tarball builder to use egg requires instead of those files? I don't know much about the tarball releasing process though... Sure, if you are willing to do the work. And it would still be quiet a different release. I will not delay the release of Zope 3.4 waiting for this to happen. 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 )
[Zope-dev] Attention Zope 3 KGS consumers: zope.kgs changes
Hi everyone, as you probably saw from the checkins last night, Paul and I finished all outstanding coding tasks that were blocking a Zope 3.4 release based on a KGS. In particular, we can generate a skinable Web site for a KGS and the release process is now very much automated. With these extensions comes also a change in URLs. All files/directories related to a particular version are now located within a directory named after the version. For the Zope 3 KGS, this will have the following impact: http://download.zope.org/zope3.4/versions-3.4.0c4.cfg - http://download.zope.org/zope3.4/3.4.0c4/versions.cfg http://download.zope.org/zope3.4/controlled-packages-3.4.0c4.cfg - http://download.zope.org/zope3.4/3.4.0c4/controlled-packages.cfg I will retroactively change the locations for all zope3.4 KGS releases. Thus, I am very interested to hear from the consuming communities: How painful is that for you? I am particularly interested to hear from Grok, Zope 2 and Plone, but also from individuals using the KGS. Thanks! Regards, Stepan -- 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] can these wrong DEPENDENCIES.cfg files be removed?
On Tue, 27 Jan 2009 09:51:49 -0800 Stephan Richter srich...@cosmos.phy.tufts.edu wrote: On Tuesday 27 January 2009, Dan Korostelev wrote: Isn't it possible to rewrite the tarball builder to use egg requires instead of those files? I don't know much about the tarball releasing process though... Sure, if you are willing to do the work. And it would still be quiet a different release. I will not delay the release of Zope 3.4 waiting for this to happen. The interesting part of the first post was that it indicated that the DEPENDENCIES.cfg are old and incorrect already. Why exactly don't you just take everything thats in the Zope3 tree checkout and ignore those DEPENDENCY.cfg files? Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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] Attention Zope 3 KGS consumers: zope.kgs changes
Stephan Richter wrote: [snip] I will retroactively change the locations for all zope3.4 KGS releases. Thus, I am very interested to hear from the consuming communities: How painful is that for you? I am particularly interested to hear from Grok, Zope 2 and Plone, but also from individuals using the KGS. Shouldn't make a difference for Grok, as we really maintain our own list but synch with KGS's list once every while. 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] can these wrong DEPENDENCIES.cfg files be removed?
On Jan 27, 2009, at 12:36 PM, Stephan Richter wrote: On Tuesday 27 January 2009, Fred Drake wrote: On Tue, Jan 27, 2009 at 6:01 AM, Dan Korostelev nad...@gmail.com wrote: AFAIK, these files are for (pre-egg, no-longer-used) zpkg tool. They are removed in zope.app.renderer's trunk, BTW. I certainly hope no one is relying on that old tools! I care about those files in Zope3/ and ZODB3/, since they are used to create the Zope 3 tar ball. Remember, Zope 3.4 will be the *first* release where we officially introduce eggs. And I have heard from a lot of people that would like to see a couple more TAR ball releases. I have a script to update the Zope3/ tree, so it is fairly easy for me to fulfill that request. What do people want from a tar release. Wouldn't their needs be adequately met by a source release made with zc.sourcerelease? Jim -- Jim Fulton 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] extracting things out of zope.app.component
Hi there, We're working (at a small Grok sprint) on refactoring bits of Zope to reduce the insane dependency relations that exist between some packages. The goal is a nice layered dependency structure for Zope 3 packages. To that purpose Brandon Rhodes and myself started extracting things from zope.app.component. zope.app.component was a rather confusing package; it had a README.txt that was lying about the existence of 2 out of 3 other txt files. It takes care of registering some ZCML directives (class), it offers local site management facilities, and it has some ZMI to deal with that. As a first step we've extracted zope.site out of zope.app.component. It only cares about site management, not about introducing ZCML directives or about a UI. We've left backwards compatibility imports in the old package (not deprecation warnings because of a conclusion reached that appeared to have been reached about not using those in a recent discussion). Right now it doesn't reduce dependencies yet. It's a step however, as we're going to go through the existing packages and change imports. We're also going to extract the ZCML directive registrations from zope.app.component into its own package. What will be left in zope.app.component will be backwards compatibility code and ZMI stuff. 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] can these wrong DEPENDENCIES.cfg files be removed?
2009/1/27 Stephan Richter srich...@cosmos.phy.tufts.edu: On Tuesday 27 January 2009, Fred Drake wrote: On Tue, Jan 27, 2009 at 6:01 AM, Dan Korostelev nad...@gmail.com wrote: AFAIK, these files are for (pre-egg, no-longer-used) zpkg tool. They are removed in zope.app.renderer's trunk, BTW. I certainly hope no one is relying on that old tools! I care about those files in Zope3/ and ZODB3/, since they are used to create the Zope 3 tar ball. Remember, Zope 3.4 will be the *first* release where we officially introduce eggs. And I have heard from a lot of people that would like to see a couple more TAR ball releases. I have a script to update the Zope3/ tree, so it is fairly easy for me to fulfill that request. Isn't it possible to rewrite the tarball builder to use egg requires instead of those files? I don't know much about the tarball releasing process though... -- WBR, Dan Korostelev ___ 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] Attention Zope 3 KGS consumers: zope.kgs changes
Stephan Richter wrote: I will retroactively change the locations for all zope3.4 KGS releases. Thus, I am very interested to hear from the consuming communities: How painful is that for you? I am particularly interested to hear from Grok, Zope 2 and Plone, but also from individuals using the KGS. Plone doesn't use the Zope 3.4 KGS in any way. Our most current version stable version Plone 3.2 has moved to an egg-based install, with the exception of Zope2 and everything it includes. Thus we still rely on the Zope2 old-style full tarball release. For current Plone 4.0 / trunk we are aiming at Zope 2.12 /trunk whose eggification is almost complete. This is based on the version set specified in the Zope 3.4 KGS. The technical means by which it does that, is however having a local copy of the versions.cfg from http://download.zope.org/zope3.4/versions.cfg. So changing URL's doesn't cause any problems for us. I think I can speak for both the Plone and Zope2 project here. Hanno ___ 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] Attention Zope 3 KGS consumers: zope.kgs changes
On Tuesday 27 January 2009, Hanno Schlichting wrote: For current Plone 4.0 / trunk we are aiming at Zope 2.12 /trunk whose eggification is almost complete. This is based on the version set specified in the Zope 3.4 KGS. The technical means by which it does that, is however having a local copy of the versions.cfg from http://download.zope.org/zope3.4/versions.cfg. So changing URL's doesn't cause any problems for us. I think I can speak for both the Plone and Zope2 project here. Great. Thanks. 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] extracting things out of zope.app.component
Martijn Faassen wrote: We're working (at a small Grok sprint) on refactoring bits of Zope to reduce the insane dependency relations that exist between some packages. The goal is a nice layered dependency structure for Zope 3 packages. This is awesome news :) I maintain dependency graphs for all zope packages included in Zope2 trunk at http://hannosch.eu/dependencies/zope/. Those should be correct covering the state from yesterday before your release-marathon. But I think the depdendencies didn't change for any of the packages I cover. If you want to generate those yourself, to get an easy graphical way of understanding the mess, then the following steps should get you there: easy_install tl.eggdeps Thanks Thomas! This parses the requires.txt in the egg_info folders. So make sure they are updated after you edit any setup.py files. Run: eggdeps -x -d zope.foo -i setuptools zope.foo-full.dot [-x ignores extras, -d specifies a dot file as output, -i ignores setuptools] In order to make the graphs more readable you can remove the transitive dependency edges from the graph: tred zope.foo-full.dot zope.foo.dot And finally produce a nice visual graph: dot -Tjpeg zope.foo.dot zope.foo.jpeg [-Tsvg or -Tpng should work as well] tred and dot are part of graphviz. If you happen to run Mac OS and use MacPorts you need to install graphviz-devel instead of the graphviz port for tred to work. In the latest stable graphviz port tred is broken. Hanno ___ 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] Attention Zope 3 KGS consumers: zope.kgs changes
On Tuesday 27 January 2009, Martijn Faassen wrote: Shouldn't make a difference for Grok, as we really maintain our own list but synch with KGS's list once every while. Great. So I think I will switch the KGS tonight, so that you all can see the results of the work we did. 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] extracting things out of zope.app.component
Hi, On Tue, 27 Jan 2009 19:49:16 +0100 Hanno Schlichting hanno...@hannosch.eu wrote: [... nice eggdeps and graphviz info ...] tred and dot are part of graphviz. If you happen to run Mac OS and use MacPorts you need to install graphviz-devel instead of the graphviz port for tred to work. In the latest stable graphviz port tred is broken. We're doing that already, but thanks for the pointer. One thing we found is that tred makes the graphs way to nice and doesn't hint you at the problematic points. We manually isolated packages that we find sufficiently 'nice' and ignore those manually (like zope.interface). After that the graph only contains the messy parts but becomes a bit more readable. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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] extracting things out of zope.app.component
Christian Theune wrote: On Tue, 27 Jan 2009 19:49:16 +0100 Hanno Schlichting hanno...@hannosch.eu wrote: [... nice eggdeps and graphviz info ...] tred and dot are part of graphviz. If you happen to run Mac OS and use MacPorts you need to install graphviz-devel instead of the graphviz port for tred to work. In the latest stable graphviz port tred is broken. We're doing that already, but thanks for the pointer. One thing we found is that tred makes the graphs way to nice and doesn't hint you at the problematic points. We manually isolated packages that we find sufficiently 'nice' and ignore those manually (like zope.interface). After that the graph only contains the messy parts but becomes a bit more readable. Sure. That's a good approach. I found looking at the full dot files or grepping through them to work quite well for certain tasks. The reduced graphs gives you an easy way of seeing which packages can already be declared nice. For the actual dependency analysis of the messy ones, you need to dig deeper :) Hanno ___ 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] extracting things out of zope.app.component
Hey, Hanno Schlichting wrote: Martijn Faassen wrote: We're working (at a small Grok sprint) on refactoring bits of Zope to reduce the insane dependency relations that exist between some packages. The goal is a nice layered dependency structure for Zope 3 packages. This is awesome news :) I maintain dependency graphs for all zope packages included in Zope2 trunk at http://hannosch.eu/dependencies/zope/. Those should be correct covering the state from yesterday before your release-marathon. But I think the depdendencies didn't change for any of the packages I cover. Yeah, zope.site isn't completed yet, as currently zope.app.component relies on zope.site and vice versa. The vice versa needs to go away and that can be done by extracting more from zope.app.component (the implemnentation of various ZCML directives) into another package. [snip explanation] Thanks for the explanation. We are using tl.eggdeps and dot as well already, though. In order to make the graphs more readable you can remove the transitive dependency edges from the graph: tred zope.foo-full.dot zope.foo.dot This also takes some information about dependencies we'd like to remove from the graph, so instead we've created the full messy graph but removing nodes that are already have no dependencies, or have clear layering (such as zope.interface, zope.component). The remaining graph then gives us clues about what we should focus on. 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] declarePublic function
I would like to upgrade my site from Zope 2.7.x to Zope 2.10.x When I try to run my site under Zope 2.10.x, I get this exception: class JMZPTMacros: File /home/orl/Zope/Products/JMZPTMacros/JMZPTMacros.py, line 28, in JMZPTMacros security.declarePublic() TypeError: declarePublic() takes at least 2 arguments (1 given) I need to use JMZPTMacros. It is an old product that seems to require a patch to line 28. I can see that Zope 2.7.x defines declarePublic() as: def declarePublic(self, *names): and that Zope 2.10.x defines declarePublic() as: def declarePublic(self, name, *names): therefore I understand that one parameter is obligatory. But I cannot guess what parameter it should be for JMZPTMacros. I tried to look how declarePublic is used inside Zope but it gave me no clue. Please help. -- Milos Prudek ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] declarePublic function
On Tue, Jan 27, 2009 at 14:06, Milos Prudek pru...@bvx.cz wrote:
I would like to upgrade my site from Zope 2.7.x to Zope 2.10.x
When I try to run my site under Zope 2.10.x, I get this exception:
class JMZPTMacros:
File /home/orl/Zope/Products/JMZPTMacros/JMZPTMacros.py, line 28, in
JMZPTMacros
security.declarePublic()
TypeError: declarePublic() takes at least 2 arguments (1 given)
I need to use JMZPTMacros. It is an old product that seems to require a patch
to line 28. I can see that Zope 2.7.x defines declarePublic() as:
def declarePublic(self, *names):
and that Zope 2.10.x defines declarePublic() as:
def declarePublic(self, name, *names):
therefore I understand that one parameter is obligatory. But I cannot guess
what parameter it should be for JMZPTMacros. I tried to look how
declarePublic is used inside Zope but it gave me no clue.
declarePublic was never meant to be called without any names, hence
the signature change. Calling it without names is a bug in
JMZPTMacros. Most likely, the author meant to protect the method right
below that line.
To illustrate, the code probably looks something like:
security.declarePublic()
def someMethod(self, REQUEST):
Whatever
You put the name of that method in a string:
security.declarePublic('someMethod')
It could also be that the author assumed that not putting in a method
name meant that *all* methods on the class would be public. In that
case, you'll need to use declareObjectPublic() instead.
--
Martijn Pieters
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] declarePublic function
JMZPTMacros. Most likely, the author meant to protect the method right
below that line.
To illustrate, the code probably looks something like:
security.declarePublic()
def someMethod(self, REQUEST):
Actually, it does not look like that. It is not followed by method definition.
Here is all the context:
class JMZPTMacros:
#All the ZPT Objects will be loaded as attributes of my
#JMZPTMacros class
security=ClassSecurityInfo()
security.declarePublic()
#Loads my generic manage_add form macros
security.declarePublic('generic_add')
generic_add=PageTemplateFile('zpt/generic_add',globals())
generic_add._owner=None
#Loads my generic manage_edit form macros
security.declarePublic('generic_edit')
generic_edit=PageTemplateFile('zpt/generic_edit',globals())
generic_edit._owner=None
#Loads my generic manage_view form macros
security.declarePublic('generic_view')
generic_view=PageTemplateFile('zpt/generic_view',globals())
generic_view._owner=None
#Loads my generic macros
security.declarePublic('generic')
generic=PageTemplateFile('zpt/generic',globals())
generic._owner=None
So, since there are many correct calls of declarePublic(), what does the
incorrect (paremeter-less) call near the top of the class do?
--
Milos Prudek
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] declarePublic function
On Tue, Jan 27, 2009 at 16:31, Milos Prudek pru...@bvx.cz wrote: Actually, it does not look like that. It is not followed by method definition. Here is all the context: class JMZPTMacros: #All the ZPT Objects will be loaded as attributes of my #JMZPTMacros class security=ClassSecurityInfo() security.declarePublic() snip So, since there are many correct calls of declarePublic(), what does the incorrect (paremeter-less) call near the top of the class do? As the bottom of my email stated, use declareObjectPublic() in this case. The rest of the security calls are then somewhat redundant, probably put in because the first declarePublic didn't do what the author expected of it.. -- Martijn Pieters ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
