<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Tarek,<div><br></div><div>For some background on this, see <a href="http://bitbucket.org/srid/modern-package-template/issue/9/distribute_setup-should-not-be-used#comment-139503">http://bitbucket.org/srid/modern-package-template/issue/9/distribute_setup-should-not-be-used#comment-139503</a></div><div><br></div><div>The intent behind calling distribute_setup.use_setuptools (and ez_setup.use_setuptools) is that if the user does not have setuptools installed, running "python setup.py install" will automatically install it for him. </div><div><br></div><div>But if the user already has setuptools, running distribute_setup.use_setuptools upgrades that installation to Distribute. This goes against the original intention, correct?</div><div><br></div><div>Is it reasonable to provide an option to `use_setuptools` that would decide if Distribute must replace the existing setuptools or not?</div><div><br></div><div>-srid</div><div><br></div><div><br></div><div><br></div><meta charset="utf-8"></body></html>