On Mon, 5 Dec 2005, Phillip J. Eby wrote:
At 08:45 PM 12/4/2005 +0000, John J Lee wrote:
After giving this some thought, it seems to me that there might be a better way to conceptualize this. Instead of "choose 1 of N" dependencies, why not allow fallbacks from a requirement? In other words, if you have the
Makes sense to me.
terribly significant for most users, but they're forced to know about it regardless in the current state of affairs.
I'm not sure why; in this particular situation as described it seems to me the way to go would be to just require scipy_core, and treat support for alternative packages as optional. That would inconvenience group #2 only if they have no intention of ever moving to scipy_core, or if for some reason they're unable to build or get it for their platform.
Yes, you're right -- I just didn't like requiring something not really required, but I guess it's no big deal for pure-Python packages (which Scipy isn't, of course).