<div dir="ltr"><div class="gmail_extra">On 25 August 2013 23:14, PJ Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com" target="_blank">pje@telecommunity.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb adM"><div class="im">> Unless I'm missing something, I suspect that this over-counts the number of<br>
> people using multi-version, in the sense that many (the majority?) of<br>
> wrapper scripts using multi-version do not actually need to,because the<br>
> users never install more than one version. And quite likely don't even know<br>
> that they could.<br>
<br>
</div></div>That's just it: if you install two programs, one of which needs<br>
CherryPy 2 and the other CherryPy 3, then with easy_install this just<br>
works, without you having any idea that you even have more than one<br>
version installed, unless you for some reason choose to look into it.<br>
<br>
Thus, you don't have to know you have multiple versions installed; it<br>
can trivially happen by way of dependencies you aren't paying<br>
attention to. The more things you install, the more likely it is you<br>
have two versions hanging around.</blockquote></div><br>OK, I see. But I'm not sure if we're agreeing or disagreeing over the result. To me, this is a bad thing on the principle that there is a cost to multiversion support (it's not part of core Python, so you have to do *something* to make it work) and so having people inadvertently pay that cost to use a feature that they don't actually *need* is wrong. An opt-in solution is fine, as in that case the user has to choose to use multiversion, and if they don't want to they can choose an alternative approach that they accept the cost of (for example, running their one CherryPy 2 using application in a virualenv).</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">One other point, just as a matter of curiosity (because it's not relevant to the current discussion): in your explanation above, there doesn't seem to be any step that says the user normally uses CherryPy 3 (so that would be the one they would get automatically at the interactive interpreter). For me, that's really the only use case I'd have for multi-versioning - 99% of the time I use a particular version of a project, but I have one particular application that can't work with the version I prefer.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Paul</div></div>