[Grok-dev] dependencies missing needed for Grok 1.1 backwards compatibility

[Martijn Faassen]

Jan-Wijbrand Kolman wrote:
> -0 on putting lots of work in backwards compatibility packages - we 
> just do not have the developer-bandwidth for this.

I'm only talking about dependencies, so I think discussions of developer 
bandwidth are not very relevant. Specifically, I'm talking about a 
package that has a setup.py that includes those packages that we've 
dropped from Grok in 1.1.

So that'd be zope.app.catalog.

What else? I don't know.

Do we need to know? yes.

Is it easier to test whether our list is complete using a package with a 
setup.py than with upgrade notes? Yes.

Is it more work than maintaining upgrade notes? No, I don't think so.

We can generate such a list by looking at what packages Grok 1.0 pulls 
in and looking at what packages Grok 1.1 pulls in (actually pulled in, 
not just listed in a setup.py) and seeing what's been dropped.

Regards,

Martijn