Re: [Zope-CMF] [dev] GenericSetup and CMF dependencies
Previously Charlie Clark wrote: Am 21.04.2008 um 08:59 schrieb Wichert Akkerman: 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. -1 Lemmings and cliff spring to mind when you mention inevitability. I think there is a significant difference between supporting eggs and requiring them. I never said 'require eggs'. I said 'requiring setuptools is not problematic'. 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
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] [dev] GenericSetup and CMF dependencies
Hi! Each Product has two lists of dependencies: One in DEPENDENCIES.txt and one in setup.py. They are not in sync. The setup.py files contain only 'setuptools' and 'five.localsitemanager' dependencies: Products.GenericSetup/setup.py: install_requires=[ setuptools, five.localsitemanager = 0.2, # 'Zope = 2.10', ], Products.CMFCore/setup.py: install_requires=[ 'setuptools', 'five.localsitemanager=0.3', ], all other setup.py files: install_requires=[ 'setuptools', ], 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? I'm just asking. If there are good reasons, I'm fine with adding the setuptools dependency. As soon as we have a decision, the relevant files should be updated. Can we get rid of the DEPENDENCIES.txt files and specify *all* dependencies in the setup.py files? Any feedback is welcome. 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
