I think a better spelling of that would be something along the lines of 'abi_version' - listing all the packages your new version of your module breaks... is a long list.On Fri, Aug 14, 2015 at 9:17 AM, Steve Dower <steve.dower@python.org> wrote:
There was discussion about an "incompatible_with" metadata item at one point. Could numpy include {incompatible_with: "scipy<x.y"} in such a release? Or would that not be possible.
circular dependency hell! scipy depends on numpy, not teh other way around -- so it needs to be clear which version of numpy a given version of scipy depends on.
-CHB