Re: [Zope3-dev] Re: Tracking eggification of zope.* packages
Baiju M wrote: On 11/5/06, Jim Fulton [EMAIL PROTECTED] wrote: I meant to note that the efforts to eggify many packages is a crucial and much appreciated first step in the effort to get an agg-based Zope 3 (and someday Zope 2) checkout and distribution. Now most of the zope.* packages are eggified, but some packages should be considered broken because it's functional testing are not working. We have to use test layers for functional testing with at least one layer per package based on ZCMLLayer ? Ideally, yes. This should be our goal. Then there will be TestBroserLayer, PublisherLayer etc. or should we create a ZopeAppServerLayer derived from ZCMLLayer and use it for the packages where application server is required to run tests? See Fred's response. Note that an alternative, in the short term is to create a buildout that either includes or uses an existing Zope 3 installation. This will allow the existing functional alyer to be used. It requires specifying the Zope 3 src directory in the extra-paths option of the testrunner section. To eggify zope.app.* packages we should implement this proposal ? : http://wiki.zope.org/zope3/LoadingConfigurationFromTheZopeAppEgg Yes. I have implemented this in my checkout with an ugly hack and tried to eggify one package, can anyone review this ? ftp://ftp.berlios.de/pub/zissue/z3/zope.app.container.tar.bz2 I don't have time to look at this atm. Where do we place zope.app.* individual packages in subversion? If we are placing it in toplevel (under main) there will be about 90+ packages. What about creating a 'zope.app' directory in toplevel and put all zope.app.* packages there ? This is a good question. Several months ago, the same questions was raised wrt Zope 2 Products, which are mostly in the Products package. At the time, we decided to stick with top-level projects because: - That was the subversion standard practice, and - Shallow is better than deep, in general. I wonder, however, if that was the best decision. The list of projects at: http://svn.zope.org/ Is already rather long and unweildy, It is likely to get worse. The fact that most things begin with z makes it even harder to scan. :) Personally, I wouldn't object to organizing things by namespace packages. Of course, zope.app is an odd case because there will be both a zope.app namespace package and a project that we'd be tempted to name zope.app. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Tracking eggification of zope.* packages
Philipp von Weitershausen wrote: Jim Fulton wrote: Baiju M wrote: On 10/24/06, Baiju M [EMAIL PROTECTED] wrote: Hi all, I have created a proposal to _tack eggification_ of zope.* packages, which is already started. http://zope3.zwiki.org/EggificationOfZopePackages May be I should change the status as IsInformational ? Buildout support for individual packages are not included in this proposal. I think it can be another proposal. I have chaged this proposal also to track zc.buildout support for zope.* packages. But I am not sure zc.buildout support is a release goal of Zope 3.4? My plan is to base 3.4 on buildout. I figured as much. Do you have any similar plans for Zope 2.11? Yes, although perhaps not to the same degree. This is all tentative. We need to see if this actually works. :) I'd like to see some experiments take shape as soon as possible. I hope and expect to have some time in late November to begin serious work on a Zope 3 buildout. In the mean time, I'm learning a lot from use of buildout to deploy applications internally at ZC. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Tracking eggification of zope.* packages
I meant to note that the efforts to eggify many packages is a crucial and much appreciated first step in the effort to get an agg-based Zope 3 (and someday Zope 2) checkout and distribution. Jim Jim Fulton wrote: Philipp von Weitershausen wrote: Jim Fulton wrote: Baiju M wrote: On 10/24/06, Baiju M [EMAIL PROTECTED] wrote: Hi all, I have created a proposal to _tack eggification_ of zope.* packages, which is already started. http://zope3.zwiki.org/EggificationOfZopePackages May be I should change the status as IsInformational ? Buildout support for individual packages are not included in this proposal. I think it can be another proposal. I have chaged this proposal also to track zc.buildout support for zope.* packages. But I am not sure zc.buildout support is a release goal of Zope 3.4? My plan is to base 3.4 on buildout. I figured as much. Do you have any similar plans for Zope 2.11? Yes, although perhaps not to the same degree. This is all tentative. We need to see if this actually works. :) I'd like to see some experiments take shape as soon as possible. I hope and expect to have some time in late November to begin serious work on a Zope 3 buildout. In the mean time, I'm learning a lot from use of buildout to deploy applications internally at ZC. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Tracking eggification of zope.* packages
On 11/5/06, Jim Fulton [EMAIL PROTECTED] wrote: I meant to note that the efforts to eggify many packages is a crucial and much appreciated first step in the effort to get an agg-based Zope 3 (and someday Zope 2) checkout and distribution. Now most of the zope.* packages are eggified, but some packages should be considered broken because it's functional testing are not working. We have to use test layers for functional testing with at least one layer per package based on ZCMLLayer ? Then there will be TestBroserLayer, PublisherLayer etc. or should we create a ZopeAppServerLayer derived from ZCMLLayer and use it for the packages where application server is required to run tests? To eggify zope.app.* packages we should implement this proposal ? : http://wiki.zope.org/zope3/LoadingConfigurationFromTheZopeAppEgg I have implemented this in my checkout with an ugly hack and tried to eggify one package, can anyone review this ? ftp://ftp.berlios.de/pub/zissue/z3/zope.app.container.tar.bz2 Where do we place zope.app.* individual packages in subversion? If we are placing it in toplevel (under main) there will be about 90+ packages. What about creating a 'zope.app' directory in toplevel and put all zope.app.* packages there ? Regards, Baiju M P.S: My marriage in on next Sunday, so I won't be doing anymore eggification in coming days. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Tracking eggification of zope.* packages
On 11/6/06, Baiju M [EMAIL PROTECTED] wrote: We have to use test layers for functional testing with at least one layer per package based on ZCMLLayer ? Then there will be TestBroserLayer, PublisherLayer etc. or should we create a ZopeAppServerLayer derived from ZCMLLayer and use it for the packages where application server is required to run tests? Any package that needs to register anything beyond this basic ZopeAppServerLayer will need to define a new layer. Running the tests like that can take time, since the layers take time to build, but isolating the components is worth while, since it makes it easier to re-combine components in different ways, so the only tests that are needed for the integration are those that test the integration itself. Where do we place zope.app.* individual packages in subversion? If we are placing it in toplevel (under main) there will be about 90+ packages. What about creating a 'zope.app' directory in toplevel and put all zope.app.* packages there ? I see no reason to introduce a new convention at this point; there's already a long list of packages at the top level, several more won't make it less convenient. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Tracking eggification of zope.* packages
Jim Fulton wrote: Baiju M wrote: On 10/24/06, Baiju M [EMAIL PROTECTED] wrote: Hi all, I have created a proposal to _tack eggification_ of zope.* packages, which is already started. http://zope3.zwiki.org/EggificationOfZopePackages May be I should change the status as IsInformational ? Buildout support for individual packages are not included in this proposal. I think it can be another proposal. I have chaged this proposal also to track zc.buildout support for zope.* packages. But I am not sure zc.buildout support is a release goal of Zope 3.4? My plan is to base 3.4 on buildout. I figured as much. Do you have any similar plans for Zope 2.11? ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Tracking eggification of zope.* packages
On 10/26/06, Jim Fulton [EMAIL PROTECTED] wrote: Baiju M wrote: But I am not sure zc.buildout support is a release goal of Zope 3.4? My plan is to base 3.4 on buildout. Theune, What about adding this to prospective feature list of Zope 3.4 here: http://wiki.zope.org/zope3/RoadMap Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
