<p><br>
On Mar 23, 2012 4:19 PM, "VanL" <<a href="mailto:van.lindberg@gmail.com">van.lindberg@gmail.com</a>> wrote:<br>
><br>
> Three notes. FIrst, distutils.cfg doesn't always work because it is centered around the idea of set paths that are the same each time - which doesn't always work with virtualenvs. </p>
<p>And the virtualenv doesn't contain its own copy of distutils.cfg?</p>
<p>> Second, most installer tools don't follow distutils.cfg. Even if that helps for python setup.py install, the other tools are still broken when you want to specify a layout.</p>
<p>So, we should change Python to fix the broken tools that don't follow documented standards for configuring installation locations?</p>
<p>If the tools are that broken, aren't they going to break even *harder* when you change the paths for Windows?</p>
<p>> And fourth, (because nobody expects the spanish inquisition), isn't the gratuitous difference a (small but) obvious wart? </p>
<p>It's hardly the only wart we keep around for backwards compatibility. If it's going to change, it needs a proper transition period at the least.<br>
</p>