[Zope-dev] Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
Hi, the KGS turned from not-having-been-updated to missing. At least regarding to my monitoring. What's happened? Begin forwarded message: Date: Sat, 31 Jan 2009 07:09:44 +0100 (CET) From: nag...@mail.whq.gocept.com (nagios) To: c...@gocept.com Subject: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING ** * Nagios * Notification Type: PROBLEM Service: KGS age Host: Zope Project Services (SVN/Downloads/Mailman/...) Address: download.zope.org State: WARNING Date/Time: Sat Jan 31 07:09:44 CET 2009 Additional Info: HTTP WARNING: HTTP/1.1 404 Not Found -- 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] Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
Darn. The moment I send the mail I realise that Stephan said he'll move the URLs around. I'll update my Nagios. Sorry for the noise. On Sat, 31 Jan 2009 09:17:11 +0100 Christian Theune c...@gocept.com wrote: Hi, the KGS turned from not-having-been-updated to missing. At least regarding to my monitoring. What's happened? Begin forwarded message: Date: Sat, 31 Jan 2009 07:09:44 +0100 (CET) From: nag...@mail.whq.gocept.com (nagios) To: c...@gocept.com Subject: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING ** * Nagios * Notification Type: PROBLEM Service: KGS age Host: Zope Project Services (SVN/Downloads/Mailman/...) Address: download.zope.org State: WARNING Date/Time: Sat Jan 31 07:09:44 CET 2009 Additional Info: HTTP WARNING: HTTP/1.1 404 Not Found -- 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] Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
On Saturday 31 January 2009, Christian Theune wrote: Darn. The moment I send the mail I realise that Stephan said he'll move the URLs around. I also cleared the directory for a short time earlier while upgrading to the new KGS version. I have sym-linked most of the old links though. 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] Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
On Saturday 31 January 2009, Stephan Richter wrote: On Saturday 31 January 2009, Christian Theune wrote: Darn. The moment I send the mail I realise that Stephan said he'll move the URLs around. I also cleared the directory for a short time earlier while upgrading to the new KGS version. I have sym-linked most of the old links though. Mmmh, the symlinks do not seem to work. Could someone from the webadmin team check what's going on there? 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] Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 31, 2009, at 09:49 , Stephan Richter wrote: On Saturday 31 January 2009, Stephan Richter wrote: On Saturday 31 January 2009, Christian Theune wrote: Darn. The moment I send the mail I realise that Stephan said he'll move the URLs around. I also cleared the directory for a short time earlier while upgrading to the new KGS version. I have sym-linked most of the old links though. Mmmh, the symlinks do not seem to work. Could someone from the webadmin team check what's going on there? If you could provide a little bit more context since I have no idea how download.zope.org is managed I could look at it. I need to know what the URLs are that do not work. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmEE1wACgkQRAx5nvEhZLLaLQCeJDybuHGRkbnzFkSLvGIRj5lH //oAn0+hC7f/6WFvv0M3TasvHKfLUIi+ =yQSV -END PGP SIGNATURE- ___ 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] Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens Vagelpohl wrote: On Jan 31, 2009, at 09:49 , Stephan Richter wrote: On Saturday 31 January 2009, Stephan Richter wrote: On Saturday 31 January 2009, Christian Theune wrote: Darn. The moment I send the mail I realise that Stephan said he'll move the URLs around. I also cleared the directory for a short time earlier while upgrading to the new KGS version. I have sym-linked most of the old links though. Mmmh, the symlinks do not seem to work. Could someone from the webadmin team check what's going on there? If you could provide a little bit more context since I have no idea how download.zope.org is managed I could look at it. I need to know what the URLs are that do not work. Probably the virtualhost section for download.zope.org needs to allow following symlinks. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFJhBSM+gerLs4ltQ4RAlj3AJjc2bkZUyMmF1GFMtXjWFQZLXcXAKCd95Oh 3LUb2YzHXzAgDcolQX9lDQ== =CuOE -END PGP SIGNATURE- ___ 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] ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 31, 2009, at 10:06 , Tres Seaver wrote: If you could provide a little bit more context since I have no idea how download.zope.org is managed I could look at it. I need to know what the URLs are that do not work. Probably the virtualhost section for download.zope.org needs to allow following symlinks. Yeah, did that first. I just need to know what to look for to see if it's fixed. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmEG0oACgkQRAx5nvEhZLKjMwCeNkoLNVmJXZ3YpdBviKZ0DwgM /8wAoIZBEKvtyG3SskB6UmCW5Wa9PfH6 =RpdU -END PGP SIGNATURE- ___ 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 3.4.0 Released!
2009/1/31 Stephan Richter srich...@cosmos.phy.tufts.edu: Hi everyone, It is finally here! Thanks goes to everyone who involved! Thank you! BTW, there's some problems with python version requirement in the tarball release. It does not accept python 2.5 while it should as stated in the announcement. -- 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] Zope 3.4.0 Released!
Yay! Thanks for all that work, Stephan! 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] ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
On Sat, 31 Jan 2009 10:35:06 +0100 Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 31, 2009, at 10:06 , Tres Seaver wrote: If you could provide a little bit more context since I have no idea how download.zope.org is managed I could look at it. I need to know what the URLs are that do not work. Probably the virtualhost section for download.zope.org needs to allow following symlinks. Yeah, did that first. I just need to know what to look for to see if it's fixed. My Nagios looks at this URL: http://download.zope.org/zope3.4/pypi-poll-access.lock I'm not sure this is relevant anymore. I guess this might be a better URL now: http://download.zope.org/zope3.4/3.4.0/pypi-poll-access.lock Stephan? -- 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] zope.security changes
Chris Withers wrote at 2009-1-30 18:50 +: Brian Sutherland wrote: zope.configuration.x zope.configuration.y Please don't, having namespace packages that contain files (as zope.configuration already does) breaks setuptools. Then setuptools needs fixing. But not for this purpose: I would find is very unintuitive when configuration were centralized (in subpackages of zope.configuration) rather than modular. Configuration belongs to the application or framework component that depends on this configuration not to any central component. -- Dieter ___ 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] snakebite
Hi there, Recently there was a project called snakebite revealed: http://www.snakebite.org/ http://mail.python.org/pipermail/python-committers/2009-January/000331.html It's basically a whole bunch of machines that open source projects, in particular Python related ones, can make use of for testing. It's essentially a buildbot farm as I understand it. The announcement says: Every CPython, Jython, IronPython and PyPy committer will have access to every development server on the network. I’ve also extended the offer to prominent Python projects like Django and Twisted. I think the Zope project counts as a prominent Python project and we have a lot of interesting code to test, so perhaps they'll let us in. :) Would people be interested in working on making use of this platform? We could use it for testing of a wide range of packages. Perhaps the ZODB would be an interesting package to start with. If so we should approach snakebite to see whether we can get on board. 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] zope.app.keyreference, zope.app.intid and zope.app.catalog
While you guys are moving zope.app.container to zope.container and those cleaning many dependencies, I'd also like to clean intid/catalog related stuff. The whole thing consists of three main packages that can be cleaned: * zope.app.keyreference - it doesn't depend on any ZMI or container stuff, it's just a simple package defining the IKeyReference interface and implementing it for persistent objects. I'd like to rename the package to just zope.keyreference (and making z.a.keyreference depend on it). * zope.app.intid - this one depends on container stuff, because of events and also defines some ZMI views. The events are not a problem anymore, because we have zope.container now, but the ZMI stuff requires zope.app.publisher (though it's not in direct requirements for some reason). I'd like to move all stuff except browser pages to the zope.intid package. * zope.app.catalog - pretty the same story as zope.app.intid, but it also uses zope.app.form's auto-form-directives. I'd like to move the non-ZMI code to plain zope.catalog. However, it's still not clear to me what should we do with old imports and pickled objects (there are over 9000 of them in case of key-references). I'd like to make non-deprecated backward-compatibilty imports in the old places until we have a generic and easy-to-use tool for touching ZODB objects. Suggestions/objections? -- 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] zope.app.keyreference, zope.app.intid and zope.app.catalog
Hi, On Sat, 31 Jan 2009 13:59:52 +0300 Dan Korostelev nad...@gmail.com wrote: While you guys are moving zope.app.container to zope.container and those cleaning many dependencies, I'd also like to clean intid/catalog related stuff. The whole thing consists of three main packages that can be cleaned: * zope.app.keyreference - it doesn't depend on any ZMI or container stuff, it's just a simple package defining the IKeyReference interface and implementing it for persistent objects. I'd like to rename the package to just zope.keyreference (and making z.a.keyreference depend on it). * zope.app.intid - this one depends on container stuff, because of events and also defines some ZMI views. The events are not a problem anymore, because we have zope.container now, but the ZMI stuff requires zope.app.publisher (though it's not in direct requirements for some reason). I'd like to move all stuff except browser pages to the zope.intid package. * zope.app.catalog - pretty the same story as zope.app.intid, but it also uses zope.app.form's auto-form-directives. I'd like to move the non-ZMI code to plain zope.catalog. However, it's still not clear to me what should we do with old imports and pickled objects (there are over 9000 of them in case of key-references). I'd like to make non-deprecated backward-compatibilty imports in the old places until we have a generic and easy-to-use tool for touching ZODB objects. Thanks for picking those up. The suggestions are pretty much like what we've been following: split out the non-ZMI parts from zope.app.* into zope.* packages. WRT the ZODB issues: I've started working on a 'touch' tool for ZODB that analyzes (pickle-based) storages for class references which are missing in your code base and (if all class references exist) can touch all objects that reference classes from indirect imports. Just a note: Martijn and I are currently trying to stabilize the zope.* trunks to get releases out. I think we should try to avoid stepping on each others toes here. 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] zope.security changes
On Jan 30, 2009, at 1:48 PM, Brian Sutherland wrote: Please don't, having namespace packages that contain files (as zope.configuration already does) breaks setuptools. zope.configuration isn't a namespace package. It is simply a package with subpackages. 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 )
Re: [Zope-dev] zope.app.keyreference, zope.app.intid and zope.app.catalog
Hey, [snip plan to clean up more dependencies] Awesome! As Christian said, this is pretty much what we've been doing. You might want to mess around with z3c.recipe.compattest to run compatibility tests after your changes, though it's still a bit finicky and rather slow. But if you try it out, please let the list know about any problems. 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] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Fri Jan 30 12:00:00 2009 UTC to Sat Jan 31 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Jan 30 20:46:02 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010975.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Jan 30 20:47:39 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010976.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Jan 30 20:49:10 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010977.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Jan 30 20:50:40 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010978.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Jan 30 20:52:10 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010979.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Jan 30 20:53:40 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010980.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Jan 30 20:55:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010981.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Jan 30 20:56:52 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010982.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] zope.app.keyreference, zope.app.intid and zope.app.catalog
2009/1/31 Christian Theune c...@gocept.com: WRT the ZODB issues: I've started working on a 'touch' tool for ZODB that analyzes (pickle-based) storages for class references which are missing in your code base and (if all class references exist) can touch all objects that reference classes from indirect imports. Yeah, I saw some commits on that thing. Looking forward for it to be developed! Just a note: Martijn and I are currently trying to stabilize the zope.* trunks to get releases out. I think we should try to avoid stepping on each others toes here. Well, I chose packages that are kind of separated from most of zope the application packages, because there aren't many packages that depend on either zope.app.catalog or zope.app.intid/keyreference. So I think we can do that work at the same time. However, it may be better to wait for zope.container to be released before starting working on intid and catalog? -- 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] Zope 3.4.0 Released!
On Sat, Jan 31, 2009 at 2:33 AM, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: Zope 3.4 requires Python 2.4 or 3.5 to run. /me goes to download Python 3.5. -- Benji York Senior 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] zope.app.keyreference, zope.app.intid and zope.app.catalog
Hi, On Sat, 31 Jan 2009 15:11:44 +0300 Dan Korostelev nad...@gmail.com wrote: 2009/1/31 Christian Theune c...@gocept.com: WRT the ZODB issues: I've started working on a 'touch' tool for ZODB that analyzes (pickle-based) storages for class references which are missing in your code base and (if all class references exist) can touch all objects that reference classes from indirect imports. Yeah, I saw some commits on that thing. Looking forward for it to be developed! Just a note: Martijn and I are currently trying to stabilize the zope.* trunks to get releases out. I think we should try to avoid stepping on each others toes here. Well, I chose packages that are kind of separated from most of zope the application packages, because there aren't many packages that depend on either zope.app.catalog or zope.app.intid/keyreference. So I think we can do that work at the same time. However, it may be better to wait for zope.container to be released before starting working on intid and catalog? I'm just trying to be defensive on the release front. We're trying to get our changes released ASAP and I'd just like to avoid having some packages not in a releasable state at that point. OTOH we're kind of stuck as we're mostly disassembling right now ... grml. Martijn? What do you say? 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] zope.app.keyreference, zope.app.intid and zope.app.catalog
Hey, Dan Korostelev wrote: Well, I chose packages that are kind of separated from most of zope the application packages, because there aren't many packages that depend on either zope.app.catalog or zope.app.intid/keyreference. So I think we can do that work at the same time. However, it may be better to wait for zope.container to be released before starting working on intid and catalog? I think it's fine to start the work, but on a branch if you want to check in, or if you want to check into their trunks, please wait until we let you know we're done (later today). We're going to do a lot of releases today as we touched a lot of packages and without releases many buildouts are currently broken (unless you basically put all the Zope 3 packages on the 'develop' line, which is what z3c.recipe.compattest can do for you, more or less, by creating test runners). Anyway, so please do your work by all means, but it'd be helpful if you could not touch their trunks for the time being. 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.keyreference, zope.app.intid and zope.app.catalog
2009/1/31 Martijn Faassen faas...@startifact.com: Dan Korostelev wrote: Well, I chose packages that are kind of separated from most of zope the application packages, because there aren't many packages that depend on either zope.app.catalog or zope.app.intid/keyreference. So I think we can do that work at the same time. However, it may be better to wait for zope.container to be released before starting working on intid and catalog? I think it's fine to start the work, but on a branch if you want to check in, or if you want to check into their trunks, please wait until we let you know we're done (later today). We're going to do a lot of releases today as we touched a lot of packages and without releases many buildouts are currently broken (unless you basically put all the Zope 3 packages on the 'develop' line, which is what z3c.recipe.compattest can do for you, more or less, by creating test runners). Anyway, so please do your work by all means, but it'd be helpful if you could not touch their trunks for the time being. I already committed a new zope.keyreference package that is very little and it has all its tests pass, so I think it's not a problem. However, I'll stop now, and won't touch original zope.app.keyreference until you get your work done. I'll check out the z3c.recipe.compattest for now:) Good luck with your great work! -- 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 )
[Zope-dev] OSCON 2009 Call For Participation ends Feb 3rd - No Zope proposals yet
Hi folks, The deadline for the O'Reilly Open Source Convention Call For Participation is Tuesday Feb 3rd. OSCON will be held July 20-24 in San Jose, California. As of today, there are no Zope-related proposals, so yours could have a pretty good chance of acceptance. ;-) There have been a lot of exciting developments in the Zope world in the past year, and I for one would really like Zope to get more public exposure. So please, write up your proposals and submit them before the deadline! For more information, see http://conferences.oreilly.com/oscon http://en.oreilly.com/oscon2009/public/cfp/57 Cheers, - Michael Bernstein signature.asc Description: This is a digitally signed message part ___ 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] Zope 3.4.0 Released!
On Sat, Jan 31, 2009 at 08:33, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: Hi everyone, It is finally here! Thanks goes to everyone who involved! Yeah \o/ Thank you Stephan. -- Sebastien Douche sdou...@gmail.com ___ 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.keyreference, zope.app.intid and zope.app.catalog
Hey, I've released our changes in zope.app.intid. We hadn't touched zope.app.catalog and zope.app.keyreference. Anyway, the trunks are yours. 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] Grok cave sprint summary, and future todos
Hi there,
I've just made a lot of releases as the result of our dependency cleanup
sprint. There are more releases to be made, but I think I've released
the most important affected packages now. Christian Theune is going to
follow up and release some more packages that we touched, probably tomorrow.
I'm going to write up a document that describes how we analyzed
dependencies and what approaches we took so that people who want to help
have some idea of what to do.
the most important affected packages are (as far as I can remember):
zope.app.component ('class' ZCML directive moved into zope.security,
site stuff extracted into zope.site)
zope.app.security ('module' directive moved into zope.security, along
with some helper functions)
zope.app.container (most functionality moved into zope.container)
zope.app.folder (base class moved into zope.container, Folder itself
moved into zope.site as its main function was to mix in site management
facilities)
zope.traversing (depends on zope.location now instead of the other way
around)
zope.location (doesn't depend on zope.traversing anymore)
zope.site (a new package extracted from zope.app.component and
zope.app.folder)
zope.container (a new package extracted from zope.app.container and
zope.app.folder)
Another thing we want to do is reduce the test dependencies of packages
to almost nothing (or nothing at all). We think it'd be good if package
only used what they depend on directly for testing purposes; testing
dependencies in general should follow implementation dependencies. This
might allow us to get rid of zope.app.testing at some point. Instead
we'd like to see more (and more consistent!) 'testing' modules in
packages that help with test setup.
We have created a bunch of tools in the process of reducing
dependencies: an extension to the test runner to track imports that
could be modified to be from a better location (though 'grep' is very
useful there too), z3c.recipe.compattest, and Christian Theune is
working on a way to 'touch' the ZODB so that it will update any moved
class to the new location.
Note that we haven't finished going through the codebase changing
imports from zope.app.folder to zope.site where possible - volunteers
are welcome. This should further reduce dependencies in the entire graph
as zope.site pulls in far less than zope.app.folder.
If a bunch of us keep this up we'll that'll allow us to start retiring a
lot of packages that are mostly unused, and have a smaller, easier set
of Zope 3 packages to maintain and understand. Users of the Zope 3
libraries (plain Zope 3, Grok, Zope 2, Repoze, and others) should all
benefit from this.
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] Grok cave sprint summary, and future todos
Hi!
That's a great piece of work you did, thanks!
I've been following package releases and have noticed some mistakes
mainly in changelog formatting:
zope.proxy
=
3.5.0 (unreleased)
* Added support to bootstrap on Jython.
* Use zope.container instead of zope.app.container.
Well, it IS released :) Also it doesn't really use zope.container or
zope.app.container, there's just a comment in the .c file :)
zope.dublincore
=
3.4.2 (unreleased)
3.4.1 (2009-01-26)
Again, it IS released. Also some changelog entry is missing :)
Also, please, check the buildout.cfg of the zope.container, because it
still includes some local developer develop paths and recipes.
2009/1/31 Martijn Faassen faas...@startifact.com:
Hi there,
I've just made a lot of releases as the result of our dependency cleanup
sprint. There are more releases to be made, but I think I've released
the most important affected packages now. Christian Theune is going to
follow up and release some more packages that we touched, probably tomorrow.
I'm going to write up a document that describes how we analyzed
dependencies and what approaches we took so that people who want to help
have some idea of what to do.
the most important affected packages are (as far as I can remember):
zope.app.component ('class' ZCML directive moved into zope.security,
site stuff extracted into zope.site)
zope.app.security ('module' directive moved into zope.security, along
with some helper functions)
zope.app.container (most functionality moved into zope.container)
zope.app.folder (base class moved into zope.container, Folder itself
moved into zope.site as its main function was to mix in site management
facilities)
zope.traversing (depends on zope.location now instead of the other way
around)
zope.location (doesn't depend on zope.traversing anymore)
zope.site (a new package extracted from zope.app.component and
zope.app.folder)
zope.container (a new package extracted from zope.app.container and
zope.app.folder)
Another thing we want to do is reduce the test dependencies of packages
to almost nothing (or nothing at all). We think it'd be good if package
only used what they depend on directly for testing purposes; testing
dependencies in general should follow implementation dependencies. This
might allow us to get rid of zope.app.testing at some point. Instead
we'd like to see more (and more consistent!) 'testing' modules in
packages that help with test setup.
We have created a bunch of tools in the process of reducing
dependencies: an extension to the test runner to track imports that
could be modified to be from a better location (though 'grep' is very
useful there too), z3c.recipe.compattest, and Christian Theune is
working on a way to 'touch' the ZODB so that it will update any moved
class to the new location.
Note that we haven't finished going through the codebase changing
imports from zope.app.folder to zope.site where possible - volunteers
are welcome. This should further reduce dependencies in the entire graph
as zope.site pulls in far less than zope.app.folder.
If a bunch of us keep this up we'll that'll allow us to start retiring a
lot of packages that are mostly unused, and have a smaller, easier set
of Zope 3 packages to maintain and understand. Users of the Zope 3
libraries (plain Zope 3, Grok, Zope 2, Repoze, and others) should all
benefit from this.
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 )
--
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] Grok cave sprint summary, and future todos
Also, there's a bug in zope.traversing:
The getParents function of zope.traversing.api uses the getParents
method of IPhysicallyLocatable, which really is new ILocationInfo, but
this interface doesn't even declare getParents method and the
RootPhysicallyLocatable adapter in zope.traversing doesn't implement
it as well so I got errors. :-/
2009/1/31 Dan Korostelev nad...@gmail.com:
Hi!
That's a great piece of work you did, thanks!
I've been following package releases and have noticed some mistakes
mainly in changelog formatting:
zope.proxy
=
3.5.0 (unreleased)
* Added support to bootstrap on Jython.
* Use zope.container instead of zope.app.container.
Well, it IS released :) Also it doesn't really use zope.container or
zope.app.container, there's just a comment in the .c file :)
zope.dublincore
=
3.4.2 (unreleased)
3.4.1 (2009-01-26)
Again, it IS released. Also some changelog entry is missing :)
Also, please, check the buildout.cfg of the zope.container, because it
still includes some local developer develop paths and recipes.
2009/1/31 Martijn Faassen faas...@startifact.com:
Hi there,
I've just made a lot of releases as the result of our dependency cleanup
sprint. There are more releases to be made, but I think I've released
the most important affected packages now. Christian Theune is going to
follow up and release some more packages that we touched, probably tomorrow.
I'm going to write up a document that describes how we analyzed
dependencies and what approaches we took so that people who want to help
have some idea of what to do.
the most important affected packages are (as far as I can remember):
zope.app.component ('class' ZCML directive moved into zope.security,
site stuff extracted into zope.site)
zope.app.security ('module' directive moved into zope.security, along
with some helper functions)
zope.app.container (most functionality moved into zope.container)
zope.app.folder (base class moved into zope.container, Folder itself
moved into zope.site as its main function was to mix in site management
facilities)
zope.traversing (depends on zope.location now instead of the other way
around)
zope.location (doesn't depend on zope.traversing anymore)
zope.site (a new package extracted from zope.app.component and
zope.app.folder)
zope.container (a new package extracted from zope.app.container and
zope.app.folder)
Another thing we want to do is reduce the test dependencies of packages
to almost nothing (or nothing at all). We think it'd be good if package
only used what they depend on directly for testing purposes; testing
dependencies in general should follow implementation dependencies. This
might allow us to get rid of zope.app.testing at some point. Instead
we'd like to see more (and more consistent!) 'testing' modules in
packages that help with test setup.
We have created a bunch of tools in the process of reducing
dependencies: an extension to the test runner to track imports that
could be modified to be from a better location (though 'grep' is very
useful there too), z3c.recipe.compattest, and Christian Theune is
working on a way to 'touch' the ZODB so that it will update any moved
class to the new location.
Note that we haven't finished going through the codebase changing
imports from zope.app.folder to zope.site where possible - volunteers
are welcome. This should further reduce dependencies in the entire graph
as zope.site pulls in far less than zope.app.folder.
If a bunch of us keep this up we'll that'll allow us to start retiring a
lot of packages that are mostly unused, and have a smaller, easier set
of Zope 3 packages to maintain and understand. Users of the Zope 3
libraries (plain Zope 3, Grok, Zope 2, Repoze, and others) should all
benefit from this.
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 )
--
WBR, Dan Korostelev
--
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] Grok cave sprint summary, and future todos
Hey, Dan Korostelev wrote: That's a great piece of work you did, thanks! I've been following package releases and have noticed some mistakes mainly in changelog formatting: zope.proxy = 3.5.0 (unreleased) * Added support to bootstrap on Jython. * Use zope.container instead of zope.app.container. Well, it IS released :) Also it doesn't really use zope.container or zope.app.container, there's just a comment in the .c file :) Oops, fixed it. zope.dublincore = 3.4.2 (unreleased) 3.4.1 (2009-01-26) Again, it IS released. Also some changelog entry is missing :) Fixed too now. I must've accidentally tagged before I made some more changes in the release notes. Easy to make mistakes when doing so many releases, thanks for catching them! 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] Grok cave sprint summary, and future todos
2009/1/31 Martijn Faassen faas...@startifact.com: Dan Korostelev wrote: Also, there's a bug in zope.traversing: The getParents function of zope.traversing.api uses the getParents method of IPhysicallyLocatable, which really is new ILocationInfo, but this interface doesn't even declare getParents method and the RootPhysicallyLocatable adapter in zope.traversing doesn't implement it as well so I got errors. :-/ Oops, none of the tests caught that somehow, where'd you get the errors? Well, getParents function got used for the root object by z3c.breadcrumb in my application. :) Anyway, Christian Theune should be back online soon to help resolve this one. This case should be added in tests. I think zope.interface.verify.verifyObject will catch errors like that. -- 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 )
[Zope-dev] Progress on zope intid/keyreference.
I just finished working on zope's intid and keyreference packages. The whole key-reference stuff is now moved in zope.keyreference package and the new version of zope.app.keyreference is released that only contains compatibility imports, so it makes no sense to depend on zope.app.keyreference anymore - use zope.keyreference. All functionality of zope.app.intid, except ZMI stuff is moved to the zope.intid package. Old zope.app.intid package now only contains browser pages and add menu item as well as backward-compatiblity imports. So if you are not using ZMI - zope.intid is for you. Next, I'm going to split zope.app.catalog and check other packages for uses of zope.app.intid/zope.app.keyreference (I guess some sqlalchemy-related packages can depend on keyreference stuff). -- 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] Zope 3.4.0 Released!
Stephan Richter wrote: It is finally here! Thanks goes to everyone who involved! January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release. Excellent! I have to say, though, that the download process is quite confusing. Let's say I'm a Pythonista who wants to try out Zope 3. Google sends me here: http://download.zope.org/zope3.4/ After the release overview, the document tells me Zope is now distributed as eggs. I'm familiar with eggs and I like them. Then it talks about the KGS and my buildout. It tells me how to modify my buildout configuration. Wait, what's a buildout and how do I configure it? Hmm, none of the links about the KGS tell me much about this buildout thing. I can already tell it's gonna be hard to learn about Zope... Well, I'll skip over the KGS stuff and see what I can figure out anyway. Ok, I can follow the easy_install directions. I'm really savvy and I'll even use virtualenv to do it, even though the document doesn't mention that. I already have the habit of using virtualenv whenever I use easy_install. So, following the directions, I create a project called HelloWorld. I try to fire it up. Uh-oh... zope.configuration.config.ConfigurationExecutionError: class 'zope.configuration.exceptions.ConfigurationError': Help Topic definition [...]/transaction-1.0a1-py2.5.egg/transaction/README.txt does not exist So it breaks before even starting the server. This is really trying my patience, but I study a lot of web pages and discuss the problem with other developers over a few days. Following a friend's recommendation, I add the following two lines to the [buildout] section of buildout.cfg generated by zopeproject: extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg versions = versions After running bin/buildout again, the server finally starts! Of course, what I see when the server starts is opaque and uninviting, but I'll leave that for another discussion. :-) So, my question is: what should the download page *really* say? Consider that existing developers of Zope 3 don't actually need this page at all since they already use zc.buildout. This page's audience, then, is people who know little about zc.buildout, let alone the KGS. Newbies need straightforward directions to follow. 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 )
Re: [Zope-dev] zope.security changes
On Sat, Jan 31, 2009 at 06:21:27AM -0500, Jim Fulton wrote: On Jan 30, 2009, at 1:48 PM, Brian Sutherland wrote: Please don't, having namespace packages that contain files (as zope.configuration already does) breaks setuptools. zope.configuration isn't a namespace package. It is simply a package with subpackages. I assumed Chris' suggestion was to make zope.configuration a namespace package. Jim -- Jim Fulton Zope Corporation -- Brian Sutherland ___ 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] Progress on zope intid/keyreference.
I also just checked in a hack to make old keyreference objects loadable if zope.app.keyreference is gone because a buildout doesn't depend on it after upgrade: http://mail.zope.org/pipermail/checkins/2009-January/029890.html I wonder if that kind of quick hack is okay to be released for the renamed package like zope.keyreference until we have a tool for upgrading ZODB objects properly. May be there are any side-effects that I don't know of? 2009/2/1 Dan Korostelev nad...@gmail.com: I just finished working on zope's intid and keyreference packages. The whole key-reference stuff is now moved in zope.keyreference package and the new version of zope.app.keyreference is released that only contains compatibility imports, so it makes no sense to depend on zope.app.keyreference anymore - use zope.keyreference. All functionality of zope.app.intid, except ZMI stuff is moved to the zope.intid package. Old zope.app.intid package now only contains browser pages and add menu item as well as backward-compatiblity imports. So if you are not using ZMI - zope.intid is for you. Next, I'm going to split zope.app.catalog and check other packages for uses of zope.app.intid/zope.app.keyreference (I guess some sqlalchemy-related packages can depend on keyreference stuff). -- WBR, Dan Korostelev -- 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] Grok cave sprint summary, and future todos
2009/1/31 Martijn Faassen faas...@startifact.com: Dan Korostelev wrote: Also, there's a bug in zope.traversing: The getParents function of zope.traversing.api uses the getParents method of IPhysicallyLocatable, which really is new ILocationInfo, but this interface doesn't even declare getParents method and the RootPhysicallyLocatable adapter in zope.traversing doesn't implement it as well so I got errors. :-/ Oops, none of the tests caught that somehow, where'd you get the errors? Anyway, Christian Theune should be back online soon to help resolve this one. I checked out the adapters myself and it looks like the RootPhysicallyLocatable works exactly like the default LocationPhysicallyLocatable would work for the IRoot object. So I propose to remove the RootPhysicallyLocatable implementation from zope.traversing.adapters and import LocationPhyscallyLocatable as RootPhysicallyLocatable there and remove its registration from zope.traversing's configure.zcml. And, of course, the getParents method should be added to the ILocationInfo interface and that should be stated in changelog somehow, because that's an extension to API requirements, so third-party components will need to implement that method in their custom implementations, if there are any. -- 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] snakebite
On Saturday 31 January 2009, Martijn Faassen wrote: Would people be interested in working on making use of this platform? We could use it for testing of a wide range of packages. Perhaps the ZODB would be an interesting package to start with. If so we should approach snakebite to see whether we can get on board. I would be interested in testing the various KGS versions on the various Python versions and platforms. 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] ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
On Saturday 31 January 2009, Jens Vagelpohl wrote: On Jan 31, 2009, at 10:06 , Tres Seaver wrote: If you could provide a little bit more context since I have no idea how download.zope.org is managed I could look at it. I need to know what the URLs are that do not work. Probably the virtualhost section for download.zope.org needs to allow following symlinks. Yeah, did that first. I just need to know what to look for to see if it's fixed. Works. See http://download.zope.org/zope3.4/versions-3.4.0c4.cfg which forwards to http://download.zope.org/zope3.4/3.4.0c4/versions.cfg Thanks, 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] ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
On Saturday 31 January 2009, Christian Theune wrote: I'm not sure this is relevant anymore. I guess this might be a better URL now: http://download.zope.org/zope3.4/3.4.0/pypi-poll-access.lock Stephan? Let's use one of these, since they do not depend the specifics of the KGS: http://download.zope.org/zope3.4/index.html http://download.zope.org/zope3.4/3.4.0/versions.cfg http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg 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] Zope 3.4.0 Released!
On Saturday 31 January 2009, Dan Korostelev wrote: BTW, there's some problems with python version requirement in the tarball release. It does not accept python 2.5 while it should as stated in the announcement. Sigh, I only tested by specifying the Python version directly. I am too lazy to fix it now. :-) If someone fixes the configure file and sends me a new TGZ, I'll upload it. On the other hand, I am glad to see that people are testing out the TGZ release and give it a spin. I guess we will have a 3.4.1 release soonish. BTW, would someone like to help out with releases? 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] Planning for Zope 3.5
Hi all, now that we have Zope 3.4.0 finally behind us, let's look forward. As I said in the release notes, I am really willing to switch to a 6 months release cycle again. I think there are three areas that we can work on: - Python 2.6 support. I think this should be straight forward. We have to update packages to not use Python 2.6 keywords and review the AST changes. - Dependency reduction. Well, we are in the middle of this work already. - Improve project setup As Shane pointed out, it is hard to get started. The solution could be a combination of documentation and tools, like zopeproject. I am going to setup a Zope 3.5 development KGS shortly. Jim has already created the directory for me on the server. Thoughts? 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] Zope 3.4.0 Released!
On Saturday 31 January 2009, Shane Hathaway wrote: So, my question is: what should the download page *really* say? Consider that existing developers of Zope 3 don't actually need this page at all since they already use zc.buildout. This page's audience, then, is people who know little about zc.buildout, let alone the KGS. Newbies need straightforward directions to follow. I have purposely skipped a good Getting Started story for the Zope 3.4 release, because of time constraints. It is also one reason, why I am still so committed to the TGZ release. I really, really want to change that for Zoep 3.5, but I'll need help. 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 )
