[Interface-dev] Separate zope.interface package
hazmat at objectrealms.net
Thu Jul 1 02:59:31 EDT 2004
On Jun 14, 2004, at 10:02 AM, Fred Drake wrote:
> On Monday 14 June 2004 10:38 am, Jim Fulton wrote:
>>> What, specifically, do you feel was a mistake? Using the ZopeX3
>>> sharing the version number, both,
> That makes it clear; thanks!
>> That was not my intent. One of the main points of the repository work
> I presume you mean the packaging effort.
>> was to decouple repository layout and release management. Of course,
>> the "standard" subversion layout strategy tends to couple repository
>> layout and releases. :( I need to ponder this.
> I don't think this is a function of the standard Subversion project
> layout at
> all. I do think some of the current issues here are tightly related
> to a
> couple of things:
> - Python's difficulty in dealing with packages that are split across
> locations (where len(__path__) > 1); the pkgutil bug should be seen as
> serious, I think, but there have been no followups other than my own:
> - your expectation that dependencies will be part of the checkout
> instead of
> separate packages that need to be installed.
another option, at least for zope.interface would be to explore the use
of the svn:externals on the zope package itself to pull in
zope.interface from whatever repository location it lives. this isn't
without some caveats, but its useful.
More information about the Interface-dev