<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Mark:</div><div><br class="webkit-block-placeholder"></div><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Aug 25, 2011, at 3:31 AM, Mark McLoughlin wrote:</div></div></div></span></span></div><div><br><blockquote type="cite"><div>I don't know the background to this whole thread, but IMHO:<br><br> * Upstream core devs shouldn't need to worry much about packaging, for<br> any distro. Given the upstream use of virtualenv, the policy for <br> dependencies should be just to use the latest and greatest. For <br> non-python dependencies (e.g. iptables, libvirt, KVM, Xen) there <br> should probably only be versions from a limited set of fast moving<br> distros supported.<br><br></div></blockquote></div><div><br></div><div>My understanding is that virtualenv is really only there as a convenience for developers, so they can run their tests without having to install the packages in their base system. Virtualenv is not intended to be used for deployment. </div><div><br></div><div>In particular, none of the documentation mentions using virtualenv for deployment, and the unit tests run on <a href="https://jenkins.openstack.org/">https://jenkins.openstack.org/</a> do not use virtualenv for testing. (We use the virtualenv for our internal Hudson server, and we occasionally see issues where the virtualenv breaks because of a version bump).</div><div><br></div><div>Lorin</div><div>-</div><div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Lorin Hochstein, Computer Scientist</div><div>USC Information Sciences Institute</div><div>703.812.3710</div><div><a href="http://www.east.isi.edu/~lorin">http://www.east.isi.edu/~lorin</a></div><div><br></div></div></div><br class="Apple-interchange-newline"></div></div></body></html>