[Distutils] PyPI is a sick sick hoarder
robertc at robertcollins.net
Fri May 15 23:06:17 CEST 2015
On 16 May 2015 at 08:46, Justin Cappos <jcappos at nyu.edu> wrote:
>> Example: say I have an ecosystem of 10 packages. A-J. And they do a
>> release every 6 months that is guaranteed to work together, but every
>> time some issue occurs which ends up clamping the group together- e.g.
>> an external release breaks API and so A1s deps are disjoint with A2s,
>> and then the same between A2 and A3. Even though A1's API is
>> compatible with B2's: its not internal bad code, its just taking *one*
>> external dep breaking its API.
>> After 2 releases you have 10^2 combinations, but only 4 are valid at
>> all. Thats 4%. 8 releases gets you 10^8, 8 valid combinations, or
> Yes, so this would not be a situation where "conflicts do not exist (or are
> very rare)" as my post mentioned. Is this rate of conflicts something you
> measured or is it a value you made up?
It's drawn from the concrete example of OpenStack, which has a single
group of co-installable releases that cluster together every 6 months.
I don't have the actual valid/invalid ratio there because I don't have
enough machines to calculate it:).
Robert Collins <rbtcollins at hp.com>
HP Converged Cloud
More information about the Distutils-SIG