Another idea for additional package repositories

[sinoroc]

@steve.dower

I’m not a huge fan of the proposed design as it is.

Of course, there is not much of a design yet. : D

@steve.dower

But the motivation is sound, and I do think it’s worth exploring this space.

Good, that is all I wanted to hear.

@steve.dower

If I were to install scipy from a particular index, it’s going to expect the copy of numpy it was bulit with. If that same index also provides numpy, it’s likely going to be the consistent one
[…]
So if you grab scipy from my index and numpy from PyPI even though there was a numpy on my index, things could break. And if the user is only thinking “I want scipy”, they’re not going to extend their list of packages to specify all dependencies so that they come from the right place - they’re just going to want the right ones.

My gut feeling is to disagree here, but I rarely use the pypackaging-native kind of packages, so my gut feeling might be very wrong. Anyway, from my point of view, the “rules” should be followed strictly. If I configure things to have scipy from a specific index but nothing for numpy, then numpy should come from PyPI. Shouldn’t this kind of issues rather be solved by one of the following?

• What to do about GPUs? (and the built distributions that support them)
• Selecting variant wheels according to a semi-static specification
• Idea: selector packages