Chris Withers simplistix.co.uk> writes:
>
> Martin Aspeli wrote:
> > That's 2.10, grep lib/python/zope/interface on your own instance in case
> > it's changed. However, IFoo.providedBy(obj) and
> > IFoo.implementedBy(obj.__class__) should be the same.
>
> They are, but when is isImplementedBy
Philipp von Weitershausen weitershausen.de> writes:
> We should remove it from the trunk.
OK
> For backward compatibility, I suggest we redefine
> zope.app.introspector.Introspect to zope.app.apidoc.UseAPIDoc via
> meta:redefinePermission.
Good point. I did not know this directive.
Here is t
I see that zope.app.introspector "Will be gone in 3.3." [sic].
To help on this, I would like to commit a patch on `trunk` to remove dependency
of API doc on this deprecated package; see below.
If someone want to keep backward compatibility on this permission, I can do
something more complex. If
Philipp von Weitershausen weitershausen.de> writes:
> Over the last couple of days we've been discussing Zope's new release
> cycle and the release management. I would like to sum up what seems to
> be the gist of those discussions:
I agree with the overall policy to improve the release machin
Benji York zope.com> writes:
>
> Florent Xicluna wrote:
> > I am working on a 'light' version of Zope
>
> You may want to contribute toward "eggifying" Zope 3 for the next
> release. Once Z3 is sufficiently broken into individual components,
>
Florent wrote:
> I propose to patch the 'trunk' in order to allow removing of these packages.
> Here are the proposed changes:
> - catch 'ImportError' when we make use of zope.app.skins
> - introduce ZCML feature 'deprecatedlayers' which is 'on' by default
> and can be disabled
> - add a 'zcml:
Hello,
I am working on a 'light' version of Zope, where all deprecated things are
removed (and maybe other less useful things). Although this is probably not
convenient for the main part of Zope developers, this has some benefits for our
internal project, and probably for other people:
- easier to
