[Zope3-dev] Re: Zope 3 releases?
Hey, Stephan Richter wrote: [snip] For me z3c.formdemo is a good example of a small Zope 3 application. It is built on top of the Zope 3 Web application server. But in order to get it working, I did not have to install anything special. I just use the libraries. Sure, when I use Grok I just use the libraries too. There's a particular library in my selection called 'grok' that's not there for you, but you're probably using other libraries that are not there for me too. So how does what you do differ from what I do? If it doesn't, I'd be using Zope 3 in the exact same way you do, which isn't true, right? Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3 releases?
Hey, Tres Seaver wrote: [snip] Frozen Releases - A frozen release would consist of: - A single, frozen KGS (index pages cannot change after release). [snip] With Grok we're now using such a versions list with buildout, using the buildout extends mechanism. This has two advantages: * you can just use the cheeseshop. (has the drawback we don't cache releases though, so a cheeseshop release cache (without index page) might be useful in the future to look up missing versions) * you can combine this list with others, which allows you to build frameworks on frameworks. I consider this is an essential use case. In the index page approach you'd have to *copy* the KGS frozen list for a later Grok release, while with the Grok approach I believe we can just point at a URL. If I then have framework X which builds on Grok I'd need to *copy* this list again. If I then want to upgrade to a newer version of Grok, I'd need to do the whole thing again, which means that besides one single big list I'd also need to maintain the smaller list for Grok and my framework X. The buildout extends mechanism seems to offer a way out that's there today. Please don't ignore this working approach for frozen releases? Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Zope 3 releases?
Stephan Richter wrote: On Monday 08 October 2007 15:09, Tres Seaver wrote: Presuming agreement on the known good set (KGS) term, I would think that we have two candidates for what makes up platform releases Frozen Releases I started commenting this section until I saw the one below. I personally do not see much benefit from the frozen release. That said, it would be trivial to create one from the updateable version below. I have already scripts for this, which are checked in as part of Jim's PyPI mirror tool. I don't understand why you believe you couldn't benefit from a frozen release. If you don't have a frozen release, you always run the following risk: * you release your code to someone else (another customer, or another developer) * after this, someone uploads a new bugfix release for an egg which causes your code to break * the customer, or another developer, installs the code, and it breaks, where it used to work when you released it. This risk can never be completely eliminated without frozen releases. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] eggsplosion and tests
Hi there, I just tried something Stephan also tried, but deserves another topic. I just wrote a simple script that takes all the eggs grok uses and tries to run their tests. This is to see whether our pile of eggs isn't broken in some way. I get a ton of errors. Mostly a ton of import errors, but other things as well, probably mostly due to version skew where one release assumes it can do things with APIs in another release that another release doesn't allow yet or not anymore. And then the whole testrunner bails out somewhere in the middle: Traceback (most recent call last): File /home/faassen/buildout/grok-0.10/testbuildout/bin/test, line 115, in ? zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', '-v']) + [ File /home/faassen/buildout-eggs/tmpRHS1Xv/zope.testing-3.4-py2.4.egg/zope/testing/testrunner.py, line 271, in run File /home/faassen/buildout-eggs/tmpRHS1Xv/zope.testing-3.4-py2.4.egg/zope/testing/testrunner.py, line 448, in run_with_options File /home/faassen/buildout-eggs/tmpRHS1Xv/zope.testing-3.4-py2.4.egg/zope/testing/testrunner.py, line 661, in resume_tests zope.testing.testrunner.SubprocessError We'll have a lot of work cut out for us to fix this. This is one point where I can see an evolving index will help. The trouble is we ended up starting with such a messed up state in the first place. :( Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] eggsplosion and tests
On Oct 10, 2007, at 9:45 AM, Martijn Faassen wrote: Hi there, I just tried something Stephan also tried, but deserves another topic. I just wrote a simple script that takes all the eggs grok uses and tries to run their tests. This is to see whether our pile of eggs isn't broken in some way. I get a ton of errors. Mostly a ton of import errors, but other things as well, probably mostly due to version skew where one release assumes it can do things with APIs in another release that another release doesn't allow yet or not anymore. And then the whole testrunner bails out somewhere in the middle: Traceback (most recent call last): File /home/faassen/buildout/grok-0.10/testbuildout/bin/test, line 115, in ? zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', '- v']) + [ File /home/faassen/buildout-eggs/tmpRHS1Xv/zope.testing-3.4- py2.4.egg/zope/testing/testrunner.py, line 271, in run File /home/faassen/buildout-eggs/tmpRHS1Xv/zope.testing-3.4- py2.4.egg/zope/testing/testrunner.py, line 448, in run_with_options File /home/faassen/buildout-eggs/tmpRHS1Xv/zope.testing-3.4- py2.4.egg/zope/testing/testrunner.py, line 661, in resume_tests zope.testing.testrunner.SubprocessError We'll have a lot of work cut out for us to fix this. This is one point where I can see an evolving index will help. The trouble is we ended up starting with such a messed up state in the first place. :( 2 minor notes: - zc.buildout and some recipes tests don't run properly outside of their buildouts. This is because the test setup leverages aspects iof the buildout, especially the presense of the source to build develop eggs needed for the tests. This almost certainly can and should be fixed, but I consider it a low priority in relation to other priorities and limited resources. - ZODB packaging, which is waay too complicated for hysterical reasons, fails to include some files needed for testing. This makes it impossible to run the tests outside of it;s development environment. This too can and should be fixed. I consider this a higher priority but won't have time to deal with it for a while. I think ZODB's setup should be rewritten from scratch. Much of the complexity arises from working around limitations in distutils, some of which have been fixed. Other complexity probably arises from a stubborn desire not to require setuptools for ZODB. Anyway, if someone wants to ehlp with the setup script, it would be appreciated, Otherwise, I'll get to it eventually. In the mean time, I suggest not running the ZODB tests. Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] psycopgda egg
On Wed, Oct 10, 2007 at 11:27:14AM -0300, Sidnei da Silva wrote: Has anyone eggified psycopgda? I can't find mention of an egg for it anywere. I would be pretty surprised that no-one did this so far. psycopg2da comes with the psycopg2 tarball, but I'm not sure if it will be included in a psycopg2 egg. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/jinty%40web.de -- Brian Sutherland ___ 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: Zope 3 releases?
On Mon, Oct 08, 2007 at 06:49:02PM -0400, Stephan Richter wrote: On Monday 08 October 2007 15:09, Tres Seaver wrote: Presuming agreement on the known good set (KGS) term, I would think that we have two candidates for what makes up platform releases Frozen Releases I started commenting this section until I saw the one below. I personally do not see much benefit from the frozen release. That said, it would be trivial to create one from the updateable version below. I have already scripts for this, which are checked in as part of Jim's PyPI mirror tool. A frozen release is very useful for some people (as long as it also gets security updates). -- Brian Sutherland ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] psycopgda egg
Has anyone eggified psycopgda? I can't find mention of an egg for it anywere. I would be pretty surprised that no-one did this so far. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Grok 0.10.1 released!
Hi there, 2007-10-10 - The Grok project is happy to release Grok 0.10.1! Grok 0.10.1 is a bugfix release of Grok, and the first outcome of the Neanderthal Grok sprint that was hosted by GfU Cyrus in Cologne, Germany, last week. The sole aim of this release is to fix Grok's installation story. Releases of Zope 3 components that Grok relied on had the tendency to break Grok. Since Grok now uses a fixed list of versions it relies on, this problem should now be solved. The grokproject tool has also been updated to 0.6, and now automatically uses the version list feature. To update grokproject to 0.6, please type the following: $ easy_install -U grokproject For more information about this release, including instructions on how to update existing buildouts to use the version list feature, see here: http://grok.zope.org/releaseinfo/readme.html What is Grok? - Grok: now even cavemen can use Zope 3 Grok is a web application framework based on Zope 3 technology. Grok aims to make Zope 3 technology more easy to use for beginners and experienced developers alike. More about Grok: http://grok.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: Grok 0.10.1 released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Hi there, 2007-10-10 - The Grok project is happy to release Grok 0.10.1! Grok 0.10.1 is a bugfix release of Grok, and the first outcome of the Neanderthal Grok sprint that was hosted by GfU Cyrus in Cologne, Germany, last week. The sole aim of this release is to fix Grok's installation story. Releases of Zope 3 components that Grok relied on had the tendency to break Grok. Since Grok now uses a fixed list of versions it relies on, this problem should now be solved. The grokproject tool has also been updated to 0.6, and now automatically uses the version list feature. To update grokproject to 0.6, please type the following: $ easy_install -U grokproject For more information about this release, including instructions on how to update existing buildouts to use the version list feature, see here: http://grok.zope.org/releaseinfo/readme.html What is Grok? - Grok: now even cavemen can use Zope 3 Grok is a web application framework based on Zope 3 technology. Grok aims to make Zope 3 technology more easy to use for beginners and experienced developers alike. More about Grok: http://grok.zope.org grokproject appears to be broken:: [/home/tseaver/tmp] $ python VE-trunk/virtualenv.py --no-site-packages gtest New python executable in gtest/bin/python Installing setuptoolsdone. [/home/tseaver/tmp] $ cd gtest/ [/home/tseaver/tmp/gtest] $ bin/easy_install grokproject Searching for grokproject Reading http://pypi.python.org/simple/grokproject/ Reading https://launchpad.net/grok Best match: grokproject 0.6 Downloading http://pypi.python.org/packages/source/g/grokproject/grokproject-0.6.tar.gz#md5=b4901c46bcf1f0682c762506cdc76c47 Processing grokproject-0.6.tar.gz Running grokproject-0.6/setup.py -q bdist_egg --dist-dir /tmp/easy_install-q39YBI/grokproject-0.6/egg-dist-tmp-2DPklW Adding grokproject 0.6 to easy-install.pth file Installing grokproject script to /home/tseaver/tmp/gtest/bin Installed /home/tseaver/tmp/gtest/lib/python2.5/site-packages/grokproject-0.6-py2.5.egg Processing dependencies for grokproject Searching for PasteScript=1.3 Reading http://pypi.python.org/simple/PasteScript/ Reading http://pythonpaste.org/script/ Best match: PasteScript 1.3.6 Downloading http://pypi.python.org/packages/source/P/PasteScript/PasteScript-1.3.6.tar.gz#md5=6a79da14870f0bbe9c1f7d4d12912437 Processing PasteScript-1.3.6.tar.gz Running PasteScript-1.3.6/setup.py -q bdist_egg --dist-dir /tmp/easy_install-TEYY_4/PasteScript-1.3.6/egg-dist-tmp-v8tUrz Adding PasteScript 1.3.6 to easy-install.pth file Installing paster script to /home/tseaver/tmp/gtest/bin Installing paster script to /home/tseaver/tmp/gtest/bin Installed /home/tseaver/tmp/gtest/lib/python2.5/site-packages/PasteScript-1.3.6-py2.5.egg Searching for PasteDeploy Reading http://pypi.python.org/simple/PasteDeploy/ Reading http://pythonpaste.org/deploy/paste-deploy.html Reading http://pythonpaste.org/deploy/ Best match: PasteDeploy 1.3.1 Downloading http://pypi.python.org/packages/source/P/PasteDeploy/PasteDeploy-1.3.1.tar.gz#md5=a14b360b4ddb0d3ca7aa9bad41d6c91c Processing PasteDeploy-1.3.1.tar.gz Running PasteDeploy-1.3.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-Yb3hMF/PasteDeploy-1.3.1/egg-dist-tmp-OyRTGE warning: no files found matching 'docs/*.html' warning: no previously-included files found matching 'docs/rebuild' Adding PasteDeploy 1.3.1 to easy-install.pth file Installed /home/tseaver/tmp/gtest/lib/python2.5/site-packages/PasteDeploy-1.3.1-py2.5.egg Searching for Paste=1.3 Reading http://pypi.python.org/simple/Paste/ Reading http://pythonpaste.org Best match: Paste 1.4.2 Downloading http://pypi.python.org/packages/source/P/Paste/Paste-1.4.2.tar.gz#md5=109bd6b0edd6de3a5ee5feaf42acd6aa Processing Paste-1.4.2.tar.gz Running Paste-1.4.2/setup.py -q bdist_egg --dist-dir /tmp/easy_install-jdPUJu/Paste-1.4.2/egg-dist-tmp-6pbNoK Adding Paste 1.4.2 to easy-install.pth file Installed /home/tseaver/tmp/gtest/lib/python2.5/site-packages/Paste-1.4.2-py2.5.egg Finished processing dependencies for grokproject [/home/tseaver/tmp/gtest] $ bin/grokproject mytest Enter module (Name of a demo Python module placed into the package) ['app.py']: Enter user (Name of an initial administrator user): zope Enter passwd (Password for the initial administrator user): r00ler Enter eggs_dir (Location where zc.buildout will look for and place packages) ['/home/tseaver/buildout-eggs']: Creating directory ./mytest Downloading zc.buildout... Invoking zc.buildout... While: Installing. Getting section app. Initializing section app. Installing recipe zc.zope3recipes=0.5.3. Getting distribution for 'zc.zope3recipes==0.6b1'. Error: Couldn't find a distribution for 'zc.zope3recipes==0.6b1'. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
