<html>

 <head>

  <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">

 </head>

 <body bgcolor="#FFFFFF" text="#000000">

  On 6/21/12 11:55 PM, David Cournapeau wrote:

  <blockquote

cite="mid:CAGY4rcX2RE_jP901_uPwPewoZ77OVWHYA877y77B3G+y5Uz4Tg@mail.gmail.com"

   type="cite">

   <div class="gmail_quote">

    <div><br>

    </div>

    <div>I think there is a misunderstanding of what bento is: bento

     is not a compiler or anything like that. It is a set of

     libraries that work together to configure, build and install a

     python project.</div>

    <div><br>

    </div>

    <div>Concretely, in bento, there is</div>

    <div> - a part that build a packager description

     (Distribution-like in distutils-parlance) from a <a

      moz-do-not-send="true" href="http://bento.info"

      target="_blank">bento.info</a> (a bite like setup.cfg)</div>

    <div> - a set of tools of commands around this package

     description. </div>

    <div> - a set of "backends" to e.g. use waf to build C

     extension with full and automatic dependency analysis (rebuild

     this if this other thing is out of date), parallel builds and

     configuration. Bento scripts build numpy more efficiently and

     reliable while being 50 % shorter than our setup.py.</div>

    <div> - a small library to build a distutils-compatible

     Distribution so that you can write a 3 lines setup.py that

     takes all its info from <a moz-do-not-send="true"

      href="http://bento.info">bento.info</a> and allow for pip to

     work.</div>

    <div><br>

    </div>

    <div>Now, you could produce a similar package description from

     the setup.cfg to be fed to bento, but I don't really see the

     point since AFAIK, <a moz-do-not-send="true"

      href="http://bento.info">bento.info</a> is strictly more

     powerful as a format than setup.cfg.</div>

   </div>

   <br>

  </blockquote>

  <br>

  So that means that *today*, Bento can consume Distutils2 project and

  compiles them, just by reading their setup.cfg, right ?<br>

  <br>

  And the code you have to convert setup.cfg into bento.info is what I

  was talking about.<br>

  <br>

  It means that I can create a project without a setup.py file, and

  just setup.cfg, and have it working with distutils2 *or* bento<br>

  <br>

  That's *exactly* what I was talking about. the setup.cfg is the

  *common* standard, and is planned to be published at PyPI

  statically.<br>

  <br>

  Let people out there use their tool of their choice to install a

  project defined by a setup.cfg<br>

  <br>

  so 2 questions:<br>

  <br>

  1/ does Bento install things following PEP 376 ?<br>

  <br>

  2/ how does the setup.cfg hooks work wrt Bento ?<br>

  <br>

  and last one proposal: how a PEP that defines a setup.cfg standard

  that is Bento-friendly, but still distutils2-friendly would sound ?<br>

  <br>

 </body>

</html>