[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Mon Apr 21 11:00:00 2008 UTC to Tue Apr 22 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Mon Apr 21 20:58:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009440.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 21 21:00:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009441.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 21 21:01:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009442.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 21 21:03:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009443.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 21 21:04:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009444.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 )
[Zope-dev] paver: buildout is utterly doomed
Hi there, I just found out about this site: http://www.blueskyonmars.com/projects/paver/ I know that the author has used buildout in the past. He apparently decided to roll his own. I have no idea what the technical qualities of paver are. To get your attention, let me spell out a strongly worded and opinionated message nonetheless: zc.buildout is toast. It's on the way out now. Paver is going to compete it away and buildout is doomed to be a niche project only used by weird zope people. That's strongly worded. I'll admit it's drastically overstated. It's based on virtually no technical information! But that's exactly how many programmers will judge the projects: on community aspects, and not primarily technical. Paver has this in its favor: * Paver actually has a nice website that speaks to Python programmers of simplicity. zc.buildout has cheeseshop page with a lot of doctest documentation people have said was hard to understand. (including the author of paver!) * the author is well connected in the Python community. I'd say TurboGears and Pylons people are likely to go for Paver. * it's *already* showing up on programmer's sites like programming.reddit.com, where I just found it. Nobody bothers to link to buildout, as there's no easily digestable message about it available. So, I fear very much that this, or some other alternative, will wash away the undoubtedly more feature-rich and technically robust zc.buildout, if buildout doesn't present itself better. Without better presentation, fast, buildout is doomed to be a Zope-specific thing forever. You Can Save Buildout! So, who is up to make a nice clean looking website and a few tutorials for buildout? It needs a website. Buildout has been around for a few years without a proper website already, Paver for 5 minutes and it's got one. I'm not going to do it, but someone should. Just to be sure, I certainly *won't* be doing this. Jim won't either, and I don't expect it from him. Let him write great code, not make websites. So don't sit back and hope someone else will do it, as they won't. If nobody else can bother to step up, Paver probably deserves to win. If you're intereested, I think we already have a nice buildout for deploying grok.zope.org that can probably be adapted. The repoze people have a nice site too, so you could go ask there. Alternatively we start to figure out how to convert our buildouts to Paver. :) 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] paver: buildout is utterly doomed
From Kevin's blog http://www.blueskyonmars.com/2008/04/22/paver-and-the-building-distribution-deployment-etc-of-python-projects/ (http://tinyurl.com/68sz6u) The idea is to use zc.buildout's machinery, not reinvent it. On Tue, Apr 22, 2008 at 8:44 AM, Martijn Faassen [EMAIL PROTECTED] wrote: Hi there, I just found out about this site: http://www.blueskyonmars.com/projects/paver/ I know that the author has used buildout in the past. He apparently decided to roll his own. I have no idea what the technical qualities of paver are. To get your attention, let me spell out a strongly worded and opinionated message nonetheless: zc.buildout is toast. It's on the way out now. Paver is going to compete it away and buildout is doomed to be a niche project only used by weird zope people. That's strongly worded. I'll admit it's drastically overstated. It's based on virtually no technical information! But that's exactly how many programmers will judge the projects: on community aspects, and not primarily technical. Paver has this in its favor: * Paver actually has a nice website that speaks to Python programmers of simplicity. zc.buildout has cheeseshop page with a lot of doctest documentation people have said was hard to understand. (including the author of paver!) * the author is well connected in the Python community. I'd say TurboGears and Pylons people are likely to go for Paver. * it's *already* showing up on programmer's sites like programming.reddit.com, where I just found it. Nobody bothers to link to buildout, as there's no easily digestable message about it available. So, I fear very much that this, or some other alternative, will wash away the undoubtedly more feature-rich and technically robust zc.buildout, if buildout doesn't present itself better. Without better presentation, fast, buildout is doomed to be a Zope-specific thing forever. You Can Save Buildout! So, who is up to make a nice clean looking website and a few tutorials for buildout? It needs a website. Buildout has been around for a few years without a proper website already, Paver for 5 minutes and it's got one. I'm not going to do it, but someone should. Just to be sure, I certainly *won't* be doing this. Jim won't either, and I don't expect it from him. Let him write great code, not make websites. So don't sit back and hope someone else will do it, as they won't. If nobody else can bother to step up, Paver probably deserves to win. If you're intereested, I think we already have a nice buildout for deploying grok.zope.org that can probably be adapted. The repoze people have a nice site too, so you could go ask there. Alternatively we start to figure out how to convert our buildouts to Paver. :) 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 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] Re: Proposal: Merge philikon-aq branch into Zope trunk
Hi. Hanno Schlichting wrote: I'd like to propose to merge the philikon-aq branch into Zope trunk aka Zope 2.12. [...] Timeline: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Just as a note for those interested: I'm working on this now, but ran into some merge problems which took more time to figure out than I had this weekend. I'll continue ASAP. Stay tuned ;) 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 )
[Zope-dev] ZConfig 2.5.1 test failures
I'm getting a Traceback when running `python setup.py test` for ZConfig-2.5.1 as per the changelog. Attached is the output, let me know how I can help. I'm not a proficient python programmer; however, I'm more than willing to learn more. --Tim _ / They collapsed ... like nuns in the street ... they had no teen \ \ appeal! / - \ \ \ \ /\ ( ) .( o ). running test running egg_info writing ZConfig.egg-info/PKG-INFO writing top-level names to ZConfig.egg-info/top_level.txt writing dependency_links to ZConfig.egg-info/dependency_links.txt reading manifest file 'ZConfig.egg-info/SOURCES.txt' writing manifest file 'ZConfig.egg-info/SOURCES.txt' running build_ext test_derived_dict (ZConfig.components.basic.tests.test_mapping.BasicSectionTypeTestCase) ... ok test_simple_dict (ZConfig.components.basic.tests.test_mapping.BasicSectionTypeTestCase) ... ok test_simple_empty_dict (ZConfig.components.basic.tests.test_mapping.BasicSectionTypeTestCase) ... ok test_config_without_handlers (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_config_without_logger (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_custom_formatter (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_http_method (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_logging_level (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_syslog_facility (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_email_notifier (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_http_logger_localhost (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_http_logger_remote_host (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_logfile (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_rotating_logfile (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_stderr (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_stdout (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_with_syslog (ZConfig.components.logger.tests.test_logger.TestConfig) ... ok test_filehandler_reopen (ZConfig.components.logger.tests.test_logger.TestReopeningLogfiles) ... ok test_logfile_reopening (ZConfig.components.logger.tests.test_logger.TestReopeningLogfiles) ... ok test_filehandler_reopen (ZConfig.components.logger.tests.test_logger.TestReopeningRotatingLogfiles) ... ok test_logfile_reopening (ZConfig.components.logger.tests.test_logger.TestReopeningRotatingLogfiles) ... ok test_missing_import (ZConfig.tests.test_cfgimports.TestImportFromConfiguration) ... ok test_repeated_import (ZConfig.tests.test_cfgimports.TestImportFromConfiguration) ... ok test_simple_import (ZConfig.tests.test_cfgimports.TestImportFromConfiguration) ... ok test_bad_datatype (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_loading (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_named_sections (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_reading_config (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_section_contents (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_too_many_keys (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_unknown_key (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_without_clopts (ZConfig.tests.test_cmdline.CommandLineTest) ... ok test_define (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_define_errors (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_fragment_ident_disallowed (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_include (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_includes_with_defines (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_load_from_abspath (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_load_from_fileobj (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_load_from_relpath (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_simple_gets (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_simple_sections (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_type_errors (ZConfig.tests.test_config.ConfigurationTestCase) ... ok test_rewriting_key_names (ZConfig.tests.test_cookbook.CookbookTestCase) ... ok test_byte_size (ZConfig.tests.test_datatypes.DatatypeTestCase) ... ok test_datatype_basickey (ZConfig.tests.test_datatypes.DatatypeTestCase) ... ok test_datatype_boolean (ZConfig.tests.test_datatypes.DatatypeTestCase) ... ok test_datatype_dotted_name (ZConfig.tests.test_datatypes.DatatypeTestCase) ... ok test_datatype_dotted_suffix (ZConfig.tests.test_datatypes.DatatypeTestCase) ... ok test_datatype_float
Re: [Zope-dev] paver: buildout is utterly doomed
Kent Tenney wrote: From Kevin's blog http://www.blueskyonmars.com/2008/04/22/paver-and-the-building-distribution-deployment-etc-of-python-projects/ (http://tinyurl.com/68sz6u) The idea is to use zc.buildout's machinery, not reinvent it. I agree, it sounds like Kevin wants to take the best parts of zc.buildout and make something more complete. Assuming Paver matures, why not switch Zope to use Paver when it's ready? 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 )
[Zope-dev] Re: paver: buildout is utterly doomed
Martijn Faassen wrote: You Can Save Buildout! So, who is up to make a nice clean looking website and a few tutorials for buildout? It needs a website. Buildout has been around for a few years without a proper website already, Paver for 5 minutes and it's got one. I'm not going to do it, but someone should. IMHO, we could feasibly fit this into http://zode01.lovelysystems.com/projects if someone wants to own the content and the Zope Foundation doesn't mind. If people prefer it to be separate, that'd be fine of course. I think it'd take: - a quick overview - an install guide - a couple of deeper examples - a few pages of documentation Just to be sure, I certainly *won't* be doing this. Jim won't either, and I don't expect it from him. Let him write great code, not make websites. So don't sit back and hope someone else will do it, as they won't. This is all too true and goes for the zope.org revitilisation efforts too. I've promised to help shepherd and provide infrastructure, but we need people to write content now. :) If nobody else can bother to step up, Paver probably deserves to win. If you're intereested, I think we already have a nice buildout for deploying grok.zope.org that can probably be adapted. The repoze people have a nice site too, so you could go ask there. The Paver site seems based on the doc generation thing that the new docs on python.org use. Alternatively we start to figure out how to convert our buildouts to Paver. :) I'd argue that the build system isn't quite as important as all that. We should ensure our packages work properly any setuptools-capable environment. Building and deployment will always be project-specific to a certain extent. However, I think we (including Plone) have a lot vested in zc.buildout and I think it is worth presenting it in the proper way. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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] ZConfig 2.5.1 test failures
On Tue, Apr 22, 2008 at 6:49 PM, Timothy Selivanow [EMAIL PROTECTED] wrote: I'm getting a Traceback when running `python setup.py test` for ZConfig-2.5.1 as per the changelog. Attached is the output, let me know how I can help. I'm not a proficient python programmer; however, I'm more than willing to learn more. Can you provide the traceback? I'm getting this: Traceback (most recent call last): File setup.py, line 1, in ? from setuptools import find_packages, setup ImportError: No module named setuptools This is because someone (Tres, IIRC) changed things to assume that setuptools is always available. If you're using zc.buildout, it pretty much is, but probably isn't part of your Python installation (it'll certainly not be part of mine). If that's the problem you're seeing, I'm inclined to fix things so that setuptools is supported if found (required for python setup.py test, since test is from setuptools, not distutils), but otherwise remains optional. -Fred -- Fred L. Drake, Jr. fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ 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] ZConfig 2.5.1 test failures
On Tue, 2008-04-22 at 19:44 -0400, Fred Drake wrote: Can you provide the traceback? It's in the attached file at the bottom. I didn't put it in the body of the email 'cause the total output is ~14kB and includes *all* the output from running the tests (so it also shows the last good test that it ran, and everything that led up to it). Here's the Traceback in case someone is interested in just it (I don't think it's useful because it's the unittest module that raises the error...but that's just me ;) Traceback (most recent call last): File setup.py, line 47, in module 'zope.testing', File /usr/lib64/python2.5/distutils/core.py, line 151, in setup dist.run_commands() File /usr/lib64/python2.5/distutils/dist.py, line 974, in run_commands self.run_command(cmd) File /usr/lib64/python2.5/distutils/dist.py, line 994, in run_command cmd_obj.run() File /usr/lib/python2.5/site-packages/setuptools/command/test.py, line 119, in run self.with_project_on_sys_path(self.run_tests) File /usr/lib/python2.5/site-packages/setuptools/command/test.py, line 101, in with_project_on_sys_path func() File /usr/lib/python2.5/site-packages/setuptools/command/test.py, line 130, in run_tests testLoader = loader_class() File /usr/lib64/python2.5/unittest.py, line 768, in __init__ self.runTests() File /usr/lib64/python2.5/unittest.py, line 805, in runTests result = self.testRunner.run(self.test) File /usr/lib64/python2.5/unittest.py, line 705, in run test(result) File /usr/lib64/python2.5/unittest.py, line 437, in __call__ return self.run(*args, **kwds) File /usr/lib64/python2.5/unittest.py, line 433, in run test(result) File /usr/lib64/python2.5/unittest.py, line 437, in __call__ return self.run(*args, **kwds) File /usr/lib64/python2.5/unittest.py, line 433, in run test(result) File /usr/lib64/python2.5/unittest.py, line 281, in __call__ return self.run(*args, **kwds) File /usr/lib64/python2.5/unittest.py, line 247, in run result.startTest(self) File /usr/lib64/python2.5/unittest.py, line 649, in startTest self.stream.write(self.getDescription(test)) File /usr/lib64/python2.5/unittest.py, line 642, in getDescription return test.shortDescription() or str(test) File /usr/lib64/python2.5/unittest.py, line 232, in shortDescription doc = self._testMethodDoc AttributeError: 'StartUpFailure' object has no attribute '_testMethodDoc' --Tim ___ / Try to relax and enjoy the crisis.\ \ -- Ashleigh Brilliant / --- \ \ \ \ /\ ( ) .( o ). ___ 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] Re: ZConfig 2.5.1 test failures
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred Drake wrote:
On Tue, Apr 22, 2008 at 6:49 PM, Timothy Selivanow
[EMAIL PROTECTED] wrote:
I'm getting a Traceback when running `python setup.py test` for
ZConfig-2.5.1 as per the changelog. Attached is the output, let me know
how I can help. I'm not a proficient python programmer; however, I'm
more than willing to learn more.
Can you provide the traceback? I'm getting this:
Traceback (most recent call last):
File setup.py, line 1, in ?
from setuptools import find_packages, setup
ImportError: No module named setuptools
This is because someone (Tres, IIRC) changed things to assume that
setuptools is always available. If you're using zc.buildout, it
pretty much is, but probably isn't part of your Python installation
(it'll certainly not be part of mine).
Not it. ;)
$ svn blame svn+ssh://svn.zope.org/repos/main/ZConfig/trunk/setup.py\
| grep setuptools
79390 fdrake from setuptools import find_packages, setup
My changes were to add support for running tests using 'setup.py test'.
See output from:
$ svn diff svn+ssh://svn.zope.org/repos/main/ZConfig/tags/2.5{,.1}
If that's the problem you're seeing, I'm inclined to fix things so
that setuptools is supported if found (required for python setup.py
test, since test is from setuptools, not distutils), but otherwise
remains optional.
- -1. In fact, the setuptools dependency has been there since the initial
checkin to a satellite direcotry (#72182):
$ svn blame -r 76917 \
svn+ssh://svn.zope.org/repos/main/ZConfig/trunk/setup.py \
| grep setuptools
72182jim from setuptools import setup
FWIW, using a python which does have setuptools installed, I get:
$ /path/to/python-with-setuptools setup.py test
running test
Checking .pth file support in \
/home/tseaver/bin/python2.4 -E -c pass
Searching for zope.testing
Reading http://pypi.python.org/simple/zope.testing/
Reading http://svn.zope.org/zope.testing
Best match: zope.testing 3.5.1
Downloading \
http://pypi.python.org/packages/source/z/zope.testing/zope.testing-3.5.1.tar.gz#md5=8f843c98ac3baf678db3e9fba42657f8
Processing zope.testing-3.5.1.tar.gz
Running zope.testing-3.5.1/setup.py -q bdist_egg --dist-dir \
/tmp/easy_install-1s54Lg/zope.testing-3.5.1/egg-dist-tmp-2bnzUH
Installed /home/tseaver/tmp/ZConfig-2.5.1/zope.testing-3.5.1-py2.4.egg
running egg_info
creating ZConfig.egg-info
writing ZConfig.egg-info/PKG-INFO
writing top-level names to ZConfig.egg-info/top_level.txt
writing dependency_links to ZConfig.egg-info/dependency_links.txt
writing manifest file 'ZConfig.egg-info/SOURCES.txt'
writing manifest file 'ZConfig.egg-info/SOURCES.txt'
running build_ext
test_derived_dict \
(ZConfig.components.basic.tests.test_mapping.BasicSectionTypeTestCase)\
... ok
test_undefined_names (ZConfig.tests.test_subst.SubstitutionTestCase)\
... ok
--
Ran 155 tests in 1.005s
OK
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
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
iD8DBQFIDn3r+gerLs4ltQ4RApsxAKCf6+c/jaPzKC/YYiheIZyrtX3yAACeOaNK
RPZ5ysJEqt57tuaqxbuRsWE=
=fo/G
-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] Re: paver: buildout is utterly doomed
The Paver site seems based on the doc generation thing that the new docs on python.org use. Sphinx is the doc generation thing, it's really nice, takes ReST files and creates TOC, indexes, provides search, all from an attractive front page. If a tiny bit of markup was added to the existing ReST files in zc.buildout and massaged by Sphinx, the result would be useful and accessable doc. Alternatively we start to figure out how to convert our buildouts to Paver. :) I'd argue that the build system isn't quite as important as all that. We should ensure our packages work properly any setuptools-capable environment. Building and deployment will always be project-specific to a certain extent. However, I think we (including Plone) have a lot vested in zc.buildout and I think it is worth presenting it in the proper way. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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 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] ZConfig 2.5.1 test failures
On Tue, Apr 22, 2008 at 7:57 PM, Timothy Selivanow [EMAIL PROTECTED] wrote: Here's the Traceback in case someone is interested in just it (I don't think it's useful because it's the unittest module that raises the error...but that's just me ;) What's odd is that there's nothing from ZConfig or it's tests in here. I can't reproduce this, using either Python 2.4.4 or 2.5.2; in both cases I'm using setuptools 0.6c8. I don't think this is a ZConfig problem, but am willing to be enlightened. -Fred -- Fred L. Drake, Jr. fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ 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] paver: buildout is utterly doomed
--On 22. April 2008 17:14:49 -0600 Shane Hathaway [EMAIL PROTECTED] wrote: Kent Tenney wrote: From Kevin's blog http://www.blueskyonmars.com/2008/04/22/paver-and-the-building-distribut ion-deployment-etc-of-python-projects/ (http://tinyurl.com/68sz6u) The idea is to use zc.buildout's machinery, not reinvent it. I agree, it sounds like Kevin wants to take the best parts of zc.buildout and make something more complete. Assuming Paver matures, why not switch Zope to use Paver when it's ready? You don't have to jump on any train just because it passes by. Competition is a good thing and having several alternatives for a particular problem is not bad by design. The basic problem within the Python community is the inflation of alternatives - I would call it also unnecessary inflation of alternatives). Unnecessary alternatives means: bad designed, bad implemented. Some examples: every week new tiny Python ORMs pop up (we have strong implementations like SQLALchemy, Storm, SQLObject), we have an inflation of zc.buildout recipes doing nearly the same (svn checkouts, executing command line commands). Andreas pgpmpV4ntJezN.pgp Description: 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 )
