Re: [Zope-dev] Grok cave sprint summary, and future todos

2009-01-31 Thread Dan Korostelev
Hi! That's a great piece of work you did, thanks! I've been following package releases and have noticed some mistakes mainly in changelog formatting: zope.proxy = 3.5.0 (unreleased) * Added support to bootstrap on Jython. * Use zope.container instead of

Re: [Zope-dev] Grok cave sprint summary, and future todos

2009-01-31 Thread Dan Korostelev
Also, there's a bug in zope.traversing: The getParents function of zope.traversing.api uses the getParents method of IPhysicallyLocatable, which really is new ILocationInfo, but this interface doesn't even declare getParents method and the RootPhysicallyLocatable adapter in zope.traversing

Re: [Zope-dev] Grok cave sprint summary, and future todos

2009-01-31 Thread Martijn Faassen
Hey, Dan Korostelev wrote: That's a great piece of work you did, thanks! I've been following package releases and have noticed some mistakes mainly in changelog formatting: zope.proxy = 3.5.0 (unreleased) * Added support to bootstrap on Jython. * Use zope.container

Re: [Zope-dev] Grok cave sprint summary, and future todos

2009-01-31 Thread Dan Korostelev
2009/1/31 Martijn Faassen faas...@startifact.com: Dan Korostelev wrote: Also, there's a bug in zope.traversing: The getParents function of zope.traversing.api uses the getParents method of IPhysicallyLocatable, which really is new ILocationInfo, but this interface doesn't even declare

Re: [Zope-dev] Grok cave sprint summary, and future todos

2009-01-31 Thread Dan Korostelev
2009/1/31 Martijn Faassen faas...@startifact.com: Dan Korostelev wrote: Also, there's a bug in zope.traversing: The getParents function of zope.traversing.api uses the getParents method of IPhysicallyLocatable, which really is new ILocationInfo, but this interface doesn't even declare