Re: [Zope3-dev] Test layers for zope.app.* packages
On Feb 5, 2007, at 11:41 PM, Fred Drake wrote: On 2/5/07, Baiju M <[EMAIL PROTECTED]> wrote: I have created zope.app egg two weeks back (http://svn.zope.org/zope.app/trunk/) I have used setuptools.find_packages function, so setuptools is a dependency. Should we need compatibility with distutils.core ? I suspect it's fine ok for an egg-supporting setup.py to depend on setuptools, though I'm wary of dependencies outside the Python standard library and our own code for basics. Using zc.buildout ensures setuptools is part of a buildout anyway, so I'll get over my own little hangup pretty quickly. Depending on a third-party egg is better than a vendor import (assuming that we don't need to customize it). We don't want to depend on anything with a viral license such as GPL. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Test layers for zope.app.* packages
On Feb 5, 2007, at 11:34 PM, Baiju M wrote: Jim Fulton wrote: On Feb 5, 2007, at 4:40 AM, Baiju M wrote: > We have to add test layer for each packages in zope.app namespace. I think we should. I'm not sure we *need* to. I certainly don't want to do this if it will delay full eggification. As I've mentioned before, I'd be perfectly happy to see a large zope.app egg containing everything we had in previous releases as a start. We could always break packages off later. I have created zope.app egg two weeks back (http://svn.zope.org/ zope.app/trunk/) Cool. I have used setuptools.find_packages function, so setuptools is a dependency. I don't think use of setuptools in the setup file is enough to trigger a dependency, however, you should have used setuptools in the __init__.py file in the app package included in the egg and *that* is enough to triger a depenency. (IOW, if a namespace package is used, then you have to depend on setuptools. I'm uncomfortable wiith the use of find-packages in this context. It is important that the zope.app egg contain *only* packages previously distributed in Zope 3 releases, excluding any packages that have been packages as separate eggs. Should we need compatibility with distutils.core ? No, for 2 reasons: 1. You only use it in the setup file. 2. It is part of the standard library. There is no point listing something that is in the standard library unless it is also distributed separately and we need a later version or need to control the version. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Test layers for zope.app.* packages
On 2/5/07, Baiju M <[EMAIL PROTECTED]> wrote: I have created zope.app egg two weeks back (http://svn.zope.org/zope.app/trunk/) I have used setuptools.find_packages function, so setuptools is a dependency. Should we need compatibility with distutils.core ? I suspect it's fine ok for an egg-supporting setup.py to depend on setuptools, though I'm wary of dependencies outside the Python standard library and our own code for basics. Using zc.buildout ensures setuptools is part of a buildout anyway, so I'll get over my own little hangup pretty quickly. -Fred -- Fred L. Drake, Jr. "Every sin is the result of a collaboration." --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Test layers for zope.app.* packages
Jim Fulton wrote: On Feb 5, 2007, at 4:40 AM, Baiju M wrote: > We have to add test layer for each packages in zope.app namespace. I think we should. I'm not sure we *need* to. I certainly don't want to do this if it will delay full eggification. As I've mentioned before, I'd be perfectly happy to see a large zope.app egg containing everything we had in previous releases as a start. We could always break packages off later. I have created zope.app egg two weeks back (http://svn.zope.org/zope.app/trunk/) I have used setuptools.find_packages function, so setuptools is a dependency. Should we need compatibility with distutils.core ? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Test layers for zope.app.* packages
On Feb 5, 2007, at 4:40 AM, Baiju M wrote: We have to add test layer for each packages in zope.app namespace. I think we should. I'm not sure we *need* to. I certainly don't want to do this if it will delay full eggification. As I've mentioned before, I'd be perfectly happy to see a large zope.app egg containing everything we had in previous releases as a start. We could always break packages off later. I *really* want to be able to have the current Zope 3 application assembled entirely from eggs by the end of PyCon. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
