<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 8/14/2015 16:16, Chris Barker wrote:<br>
<blockquote
cite="mid:CALGmxE+CEgLB-0-R4bojC60GYWTfbb=oDodX+Bj1gVE4SZ9HxQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Aug 14, 2015 at 9:17 AM,
Steve Dower <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:steve.dower@python.org" target="_blank">steve.dower@python.org</a>></span>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
</blockquote>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>-CHB</div>
<br>
</div>
</div>
</div>
</blockquote>
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.<br>
<br>
- Alex W.<br>
</body>
</html>