Summary of messages to the zope-tests list. Period Mon Feb 2 12:00:00 2009 UTC to Tue Feb 3 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=7) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:50:11 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011003.html Subject: FAILED (failures=9) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 2 20:51:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011004.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Feb 2 20:44:08 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010999.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:45:40 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011000.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:47:10 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011001.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:48:40 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011002.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:53:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011005.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 2 20:54:44 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011006.html
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list. Period Mon Feb 2 12:00:00 2009 UTC to Tue Feb 3 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests.
Test failures -------------
Subject: FAILED (failures=7) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:50:11 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011003.html
Subject: FAILED (failures=9) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 2 20:51:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011004.html
It becomes somewhat hard and annoying to keep the old full Zope trunk tree based on externals in sync with the Zope2 buildout and its KGS definition and it seems I failed yesterday. I'd suggest we reorganize the Zope trunk and replace it by the current buildout. As part of that we can move the code that has been moved to its own projects like Acquisition and DateTime out of the main tree. I'd volunteer to do this work if nobody objects. Stefan checked in a new alltests.cfg into the buildout, that lets him run the tests for all direct dependencies of Zope2 in much the same way as we did run all tests for the full package tree before. So we shouldn't loose test coverage of the entire Zope2 release. Hanno
On Tue, Feb 3, 2009 at 13:56, Hanno Schlichting <hannosch@hannosch.eu> wrote:
It becomes somewhat hard and annoying to keep the old full Zope trunk tree based on externals in sync with the Zope2 buildout and its KGS definition and it seems I failed yesterday.
I'd suggest we reorganize the Zope trunk and replace it by the current buildout. As part of that we can move the code that has been moved to its own projects like Acquisition and DateTime out of the main tree.
Would that mean that 2.12 becomes buildout-only? Not that I mind, I use buildouts all the time anyway. Maybe that's the plan anyhow? -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
Lennart Regebro wrote:
On Tue, Feb 3, 2009 at 13:56, Hanno Schlichting <hannosch@hannosch.eu> wrote:
It becomes somewhat hard and annoying to keep the old full Zope trunk tree based on externals in sync with the Zope2 buildout and its KGS definition and it seems I failed yesterday.
I'd suggest we reorganize the Zope trunk and replace it by the current buildout. As part of that we can move the code that has been moved to its own projects like Acquisition and DateTime out of the main tree.
Would that mean that 2.12 becomes buildout-only? Not that I mind, I use buildouts all the time anyway. Maybe that's the plan anyhow?
It would mean buildout becomes a requirement for the development of Zope2 itself. For the devlopment with or on top of Zope2 any system that can deal with normal Python distributions would work. In addition the plan is to release at least for Zope 2.12 an old-style tarball release in the same way all releases up to 2.11 have been handled. Hanno
On Tue, Feb 3, 2009 at 19:44, Hanno Schlichting <hannosch@hannosch.eu> wrote:
It would mean buildout becomes a requirement for the development of Zope2 itself.
Oh, +1 to that.
For the devlopment with or on top of Zope2 any system that can deal with normal Python distributions would work. In addition the plan is to release at least for Zope 2.12 an old-style tarball release in the same way all releases up to 2.11 have been handled.
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 )
-- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
I don't think you faired that badly. ;-) One obvious problem is the removal of the 'defaultSkin' directive, which is still in use by CMFDefault. The rest looks harmless. I am not opposed to ditching the trunk, but I don't think keeping it in sync (if only for a transition period) is impossible either. Stefan On 03.02.2009, at 13:56, Hanno Schlichting wrote:
It becomes somewhat hard and annoying to keep the old full Zope trunk tree based on externals in sync with the Zope2 buildout and its KGS definition and it seems I failed yesterday.
I'd suggest we reorganize the Zope trunk and replace it by the current buildout. As part of that we can move the code that has been moved to its own projects like Acquisition and DateTime out of the main tree.
I'd volunteer to do this work if nobody objects.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03.02.2009 13:56 Uhr, Hanno Schlichting wrote:
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list. Period Mon Feb 2 12:00:00 2009 UTC to Tue Feb 3 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests.
Test failures -------------
Subject: FAILED (failures=7) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Feb 2 20:50:11 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011003.html
Subject: FAILED (failures=9) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 2 20:51:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011004.html
It becomes somewhat hard and annoying to keep the old full Zope trunk tree based on externals in sync with the Zope2 buildout and its KGS definition and it seems I failed yesterday.
I'd suggest we reorganize the Zope trunk and replace it by the current buildout. As part of that we can move the code that has been moved to its own projects like Acquisition and DateTime out of the main tree.
I'd volunteer to do this work if nobody objects.
I am fine with giving up the current Zope 2 SVN branch. Keeping it in sync with the Z3 packages is already hard enough - so a single source of complexity is enough :)
Stefan checked in a new alltests.cfg into the buildout, that lets him run the tests for all direct dependencies of Zope2 in much the same way as we did run all tests for the full package tree before. So we shouldn't loose test coverage of the entire Zope2 release.
Thanks Stefan! Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmJN5YACgkQCJIWIbr9KYxyzgCgrM5NaCX0jzu+JZErUsTYbvHR l6oAoKcAW8v9nPB6zvNDi+zc3JZ4/QpP =paCm -----END PGP SIGNATURE-----
Andreas Jung wrote:
On 03.02.2009 13:56 Uhr, Hanno Schlichting wrote:
It becomes somewhat hard and annoying to keep the old full Zope trunk tree based on externals in sync with the Zope2 buildout and its KGS definition and it seems I failed yesterday.
I'd suggest we reorganize the Zope trunk and replace it by the current buildout. As part of that we can move the code that has been moved to its own projects like Acquisition and DateTime out of the main tree.
I'd volunteer to do this work if nobody objects.
I had time to work on this on our Berlinale Sprint and this is now done! I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same. Hanno
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same.
Out of interest, where can I learn more about Zope 2 from buildout? It's something I'd certainly like to get involved in... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13.02.2009 9:49 Uhr, Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same.
Out of interest, where can I learn more about Zope 2 from buildout?
It's something I'd certainly like to get involved in...
Related recipes: plone.recipe.zope2install plone.recipe.zope2instance Andreas - -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmVOfUACgkQCJIWIbr9KYylqACfZaJR0GuuWUa33Tus8KeMCOhx zSYAoNNPKNyWMNIUxM/a5m/6iKIOC0mi =HJwa -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same.
Out of interest, where can I learn more about Zope 2 from buildout?
It's something I'd certainly like to get involved in...
At this point, the SVN trunk *is* a buildout: $ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk ... $ cd Zope-trunk $ /oath/to/python2.5 bootstrap.py ... $ bin/buildout ... Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJlWqt+gerLs4ltQ4RAo3XAJ9B+VP3j8ePwkKB5pA8WJQPh88KwwCguudD VTpAVraTmY8o36Jw6nhdDv0= =nUw6 -----END PGP SIGNATURE-----
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same. Out of interest, where can I learn more about Zope 2 from buildout?
It's something I'd certainly like to get involved in...
At this point, the SVN trunk *is* a buildout:
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk ... $ cd Zope-trunk $ /oath/to/python2.5 bootstrap.py ... $ bin/buildout
Wow, I didn't know that... I'll definitely have to give it a go. Anyone tried it on Windows? With this model, how would I go about making changes to one of the eggs that make up the buildout and then run all the tests? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code, so we don't confuse people anymore with two locations doing the same. Out of interest, where can I learn more about Zope 2 from buildout?
It's something I'd certainly like to get involved in...
At this point, the SVN trunk *is* a buildout:
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk ... $ cd Zope-trunk $ /oath/to/python2.5 bootstrap.py ... $ bin/buildout
Wow, I didn't know that...
I'll definitely have to give it a go. Anyone tried it on Windows?
With this model, how would I go about making changes to one of the eggs that make up the buildout and then run all the tests?
Same as any other buildout: Check out the egg, make it a 'develop' entry in your buildout.cfg, re-run buildout, then run tests. Lather, rinse, repeat... Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJlWwe+gerLs4ltQ4RAreqAKCBG2TBnu7nY8t/mastoJY6klgfwQCg0Yp5 E3/iKR4c3+/hYKyudc43Yps= =Ppzu -----END PGP SIGNATURE-----
Tres Seaver wrote:
At this point, the SVN trunk *is* a buildout:
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk ... $ cd Zope-trunk $ /oath/to/python2.5 bootstrap.py ... $ bin/buildout
Another question... If I have a project that's Zope 2 based, how do I specify Zope 2 as a dependency? How do I specify a specific version of Zope 2? I guess this equates to "what does a Zope 2 instance look like now that we're buildout-based?" cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Tres Seaver wrote:
At this point, the SVN trunk *is* a buildout:
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk ... $ cd Zope-trunk $ /oath/to/python2.5 bootstrap.py ... $ bin/buildout
Another question...
If I have a project that's Zope 2 based, how do I specify Zope 2 as a dependency? How do I specify a specific version of Zope 2?
I guess this equates to "what does a Zope 2 instance look like now that we're buildout-based?"
install_requires=['Zope2>=2.12dev'], Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJlW7D+gerLs4ltQ4RAgoNAJ9HgcodthVx13Wh/Xvxsz4/Pmif3ACfR84I gb/mU0eU+ETOL7b6AKiJ1c8= =mhS9 -----END PGP SIGNATURE-----
Tres Seaver wrote:
I guess this equates to "what does a Zope 2 instance look like now that we're buildout-based?"
install_requires=['Zope2>=2.12dev'],
Okay, how do I get zopectl and runzope? Where do I put my zope.conf? Where do I put old-school products? What would the following buildout.cfg give me: [buildout] parts = zope2instance versions = versions [version] Zope2 = 2.12dev [zope2instance] recipe = zc.recipe.egg eggs = Zope2 cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Tres Seaver wrote:
I guess this equates to "what does a Zope 2 instance look like now that we're buildout-based?" install_requires=['Zope2>=2.12dev'],
Okay, how do I get zopectl and runzope? Where do I put my zope.conf? Where do I put old-school products?
What would the following buildout.cfg give me:
Dude, run it and find out. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJlXCa+gerLs4ltQ4RAoDRAJwIVpeUbVI3Lv87lfU2Eiuz+Um2rQCgh+qX ijxdMg5iUQc55CZs2RRvBK8= =Kbm4 -----END PGP SIGNATURE-----
For the time being Zope2 must be used as a develop egg. Like e.g. so: http://svn.zope.org/CMF.buildout/trunk/ Stefan On 13.02.2009, at 13:49, Chris Withers wrote:
I guess this equates to "what does a Zope 2 instance look like now that we're buildout-based?"
Hello, On Fri, Feb 13, 2009 at 20:13, Stefan H. Holek <stefan@epy.co.at> wrote:
For the time being Zope2 must be used as a develop egg. Like e.g. so: http://svn.zope.org/CMF.buildout/trunk/
I got it working without development egg: [buildout] parts = instance eggs = some_project zope2 # Reference any eggs you are developing here, one per line # e.g.: develop = src/my.package develop = src/some_project [productdistros] recipe = plone.recipe.distros urls = http://hathawaymix.org/Software/CookieCrumbler/CookieCrumbler-1.2.tar.gz http://www.dieter.handshake.de/pyprojects/zope/ZopeProfiler.tgz nested-packages = version-suffix-packages = [instance] recipe = plone.recipe.zope2instance # That way it looks for mkzopeinstance in the bin directory # That there should be a mkzopeinstance.py is defined in zopepy zope2-location = . zope2-egg = True user = admin:pass http-address = 8080 debug-mode = on verbose-security = on eggs = ${zopepy:eggs} zcml = some_project some_project-overrides products = ${productdistros:location} [zopepy] recipe = zc.recipe.egg eggs = ${buildout:eggs} interpreter = zopepy # This mkzopeinstance=mkzopeinstance.py is a hack. Better would be a patch for zope2instance scripts = zopepy mkzopeinstance=mkzopeinstance.py Best regards, Patrick
participants (8)
-
Andreas Jung -
Chris Withers -
Hanno Schlichting -
Lennart Regebro -
Patrick Gerken -
Stefan H. Holek -
Tres Seaver -
Zope Tests Summarizer