Re: [Zope-CMF] [dev] GenericSetup and CMF dependencies
Previously yuppie wrote: Until recently, the Products themselves didn't use setuptools. Revision 85287 (http://svn.zope.org/?rev=85287view=rev) changed that. It is no longer possible to run CMF without setuptools installed. Was that intended when setuptools was added to install_requires? We always tried hard to keep CMF dependencies to a minimum. Will we only support egg releases for CMF 2.2 and later, making setuptools required anyway? The eggified CMF already required setuptools to make sure the Products namespace is setup correctly. Considering that entire python community appears to be moving to egg, Zope2 is going to be distributed in egg form (at least there is a strong move in that direction) I think a dependency on setuptools is not problematic. From a Plone perspective CMF 2.1 will be the last CMF version we use as products. Starting with Plone 4 we will be using the eggified version. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] CMF Tests: 9 OK
Summary of messages to the cmf-tests list. Period Sun Apr 20 11:00:00 2008 UTC to Mon Apr 21 11:00:00 2008 UTC. There were 9 messages: 9 from CMF Tests. Tests passed OK --- Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Tests Date: Sun Apr 20 21:34:46 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008561.html Subject: OK : CMF-1.6 Zope-2.9 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:36:21 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008562.html Subject: OK : CMF-2.0 Zope-2.9 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:37:51 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008563.html Subject: OK : CMF-2.0 Zope-2.10 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:39:21 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008564.html Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:40:51 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008565.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:42:21 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008566.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:43:51 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008567.html Subject: OK : CMF-trunk Zope-2.11 Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:45:21 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008568.html Subject: OK : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Tests Date: Sun Apr 20 21:46:51 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-April/008569.html ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: [dev] GenericSetup and CMF dependencies
yuppie wrote: Wichert Akkerman wrote: Previously yuppie wrote: Until recently, the Products themselves didn't use setuptools. Revision 85287 (http://svn.zope.org/?rev=85287view=rev) changed that. It is no longer possible to run CMF without setuptools installed. For those of you who didn't read the changeset, I used the version number parsing code from setuptools in order to sort the versions inside the upgrade machinery. I didn't want to duplicate the code to parse all those cryptic version numbers like '3.1-rc1-dev-r42' and sort them correctly. My reasoning for reusing the setuptools functions was, that we seem to use them for package versions as well since some time and they seem to be a reasonable standard. Considering that entire python community appears to be moving to egg, Zope2 is going to be distributed in egg form (at least there is a strong move in that direction) I think a dependency on setuptools is not problematic. I guess CMF 2.2 will be released before Zope2 or Python requires setuptools, so at least for now it is a GenericSetup/CMF dependency. http://svn.zope.org/CMF/trunk/ still exists and needs to be maintained (or deleted). Who ever added the setuptools dependency should update INSTALL.txt and friends (if we agree to keep CMF trunk and the dependency). I don't have a strong opinion on CMF/trunk. I don't use it, so I don't have a particular interest in keeping it around. For me the dependencies noted in setup.py are the canonical place and I would delete the DEPENDENCIES.txt files from all packages on trunk and instead make sure the ones in setup.py are current. If we can agree on that, I can do the work and make sure INSTALL.txt is current as well. Hanno ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: [dev] GenericSetup and CMF dependencies
Previously yuppie wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
Until recently, the Products themselves didn't use setuptools. Revision
85287 (http://svn.zope.org/?rev=85287view=rev) changed that. It is no
longer possible to run CMF without setuptools installed.
Was that intended when setuptools was added to install_requires? We
always tried hard to keep CMF dependencies to a minimum. Will we only
support egg releases for CMF 2.2 and later, making setuptools required
anyway?
The eggified CMF already required setuptools to make sure the Products
namespace is setup correctly.
'declare_namespace' is used with a fallback, so setuptools was not
strictly required:
try:
__import__('pkg_resources').declare_namespace(__name__)
except ImportError:
from pkgutil import extend_path
__path__ = extend_path(__path__, __name__)
However without that code the Products.* namespace would probably be
broken and CMF wouldn't work.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: [dev] GenericSetup and CMF dependencies
Hi!
Wichert Akkerman wrote:
Previously yuppie wrote:
Until recently, the Products themselves didn't use setuptools. Revision
85287 (http://svn.zope.org/?rev=85287view=rev) changed that. It is no
longer possible to run CMF without setuptools installed.
Was that intended when setuptools was added to install_requires? We
always tried hard to keep CMF dependencies to a minimum. Will we only
support egg releases for CMF 2.2 and later, making setuptools required
anyway?
The eggified CMF already required setuptools to make sure the Products
namespace is setup correctly.
'declare_namespace' is used with a fallback, so setuptools was not
strictly required:
try:
__import__('pkg_resources').declare_namespace(__name__)
except ImportError:
from pkgutil import extend_path
__path__ = extend_path(__path__, __name__)
Considering that entire python community
appears to be moving to egg, Zope2 is going to be distributed in egg
form (at least there is a strong move in that direction) I think a
dependency on setuptools is not problematic.
I guess CMF 2.2 will be released before Zope2 or Python requires
setuptools, so at least for now it is a GenericSetup/CMF dependency.
http://svn.zope.org/CMF/trunk/ still exists and needs to be maintained
(or deleted). Who ever added the setuptools dependency should update
INSTALL.txt and friends (if we agree to keep CMF trunk and the dependency).
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: [dev] GenericSetup and CMF dependencies
Hi Hanno! Hanno Schlichting wrote: yuppie wrote: I guess CMF 2.2 will be released before Zope2 or Python requires setuptools, so at least for now it is a GenericSetup/CMF dependency. http://svn.zope.org/CMF/trunk/ still exists and needs to be maintained (or deleted). Who ever added the setuptools dependency should update INSTALL.txt and friends (if we agree to keep CMF trunk and the dependency). I don't have a strong opinion on CMF/trunk. I don't use it, so I don't have a particular interest in keeping it around. Maybe it should be replaced by a buildout, but for now I would keep it. For me the dependencies noted in setup.py are the canonical place and I would delete the DEPENDENCIES.txt files from all packages on trunk and instead make sure the ones in setup.py are current. If we can agree on that, I can do the work and make sure INSTALL.txt is current as well. I'm still not 100% convinced that making CMF 2.2 depend on setuptools is necessary. But given that you volunteer to do all the related work, I'm fine with it. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
