<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    i would very strongly suggest to completely avoid distutils as base
    for a new tool<br>
    being based on distutils is one of the main reasons why setuptools
    is so painful to develop/maintain, <br>
    its always a huge mental cost and pain to work into that huge pile
    of historic spaghetti<br>
    <br>
    and its even more pain to come up with useful tests<br>
    <br>
    -- Ronny<br>
    <br>
    <div class="moz-cite-prefix">On 10/21/2015 09:05 PM, Chris Barker
      wrote:<br>
    </div>
    <blockquote
cite="mid:CALGmxE+=GTVMbnaNyo8f0n0CbzDL8E_8ZYAN0=Xmi+-i4+W8dA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Wed, Oct 21, 2015 at 10:03 AM,
            Ronny Pfannschmidt <span dir="ltr"><<a
                moz-do-not-send="true"
                href="mailto:opensource@ronnypfannschmidt.de"
                target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:opensource@ronnypfannschmidt.de">opensource@ronnypfannschmidt.de</a></a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> why does that have
                to be in setuptools ?!<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>it doesn't have to be in setuptools at all -- I suppose
              I should have defined more clearly what I meant:</div>
            <div><br>
            </div>
            <div>setuptools_lite would be a package that does all things
              that setuptools does that we currently think it *should*
              do -- and nothing else.</div>
            <div><br>
            </div>
            <div>whether it's in setuptools as a special mode, forked
              from setuptools, or written from scratch is all
              implementation detail.</div>
            <div><br>
            </div>
            <div>perhaps it would be better with a different name --
              maybe "buildtools"?</div>
            <div><br>
            </div>
            <div>But I thought for acceptance by the community, maybe
              saying: </div>
            <div><br>
            </div>
            <div>replace all your "import setuptools" with "import
              setuptool_lite" would be clear what the intent was -- i.e.
              not YET ANOTHER brand new build system...</div>
            <div><br>
            </div>
            <div>Oh and it would use the same API for the parts that it
              still supported. Given all that, if I were to do it, and
              I'm not sure I can... I would probably start with
              setuptools and rip stuff out rather than start from
              scratch.</div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">and both distutils
                and setuptools are very very sub-par </div>
            </blockquote>
            <div><br>
            </div>
            <div>well, see the other discussion about the role /
              necessity of distutils... but yes, it's certainly possible
              to make a new build system completely independent of
              distutils.</div>
            <div><br>
            </div>
            <div>-CHB</div>
            <div> </div>
          </div>
          <div><br>
          </div>
          -- <br>
          <div class="gmail_signature"><br>
            Christopher Barker, Ph.D.<br>
            Oceanographer<br>
            <br>
            Emergency Response Division<br>
            NOAA/NOS/OR&R            (206) 526-6959   voice<br>
            7600 Sand Point Way NE   (206) 526-6329   fax<br>
            Seattle, WA  98115       (206) 526-6317   main reception<br>
            <br>
            <a moz-do-not-send="true"
              href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>