AW: [Checkins] SVN: z3c.zrtresource/trunk/src/z3c/zrtresource/zrtresource.pyz3c.zrtresource is made to work in Zope2. A docstring wasadded as the zope2 publisher won't publish otherwise. Added aconditional import on Five's FileResource. Only oneconditiona

[Wichert Akkerman]

Previously Nikolay Kim wrote:
> 
> > > Probably this is not much important enough for that
> > > *import* usecase, but if we start with that, can you tell
> > > me wheres the border with mixin code into Zope3 packages
> > > and what is Ok and where do we stop?
> > 
> > I agree it should rarely be used, but it was just one import so then
> > I thought it was ok.
> 
> Conditional import are ugly and many of us doesn't use zope2 at all.

And many of us do use Zope2 and want to be able to use all the nice
Zope3 technology. A single conditional import is an extremely small
price to pay to give a large group of people access to new technology.

I thought the componentized Zope 3 was all about making it easier to
reuse modules. Did that change?

Wichert.

-- 
Wichert Akkerman <wichert at wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.