<div class="gmail_quote">On Thu, Apr 21, 2011 at 9:01 PM, David <span dir="ltr"><<a href="mailto:david@silveregg.co.jp">david@silveregg.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 04/22/2011 06:21 AM, anatoly techtonik wrote:<br>
> On Thu, Apr 21, 2011 at 4:48 AM, Kevin Horn<<a href="mailto:kevin.horn@gmail.com">kevin.horn@gmail.com</a>> wrote:<br>
>><br>
>> cluster****. So he rewrote distutils with an eye on keeping things nice for<br>
>> everyone. Project managers, distro packagers, users installing software,<br>
>> etc. This is distutils2. In Python 3.3 and up it will be called<br>
>> "packaging". Once people start using it, it will make a lot of the current<br>
>> packaging headaches in the Python world go away.<br>
><br>
> Are you sure about that? Where is the list of stories it will solve<br>
> when people start using it, so I can check that my cases are covered<br>
> by distutils2 insurance plan?<br>
<br>
</div>[OT]<br>
You can take a look at bento, which is my own response to the distutils<br>
issues we have in the scipy community (but I would expect twisted and<br>
most big python libraries to have similar issues):<br>
<br>
<a href="http://cournape.github.com/Bento/" target="_blank">http://cournape.github.com/Bento/</a><br>
<br>
It is designed from the ground up with the idea of reliable<br>
customization and complex build supports. It can already build numpy and<br>
scipy with a near 50 % reduction in LOC compared to our setup.py, and<br>
more reliably thanks to using a real build tool in the backend (waf, but<br>
you can add support for a different one if you want).<br>
<br></blockquote><div>That is nice indeed. But why to invent yet another scripting language for</div><div>info files or good old python is not good enough?</div><div>BTW are bento and waf sources included in that 50% reduction?</div>
</div><br clear="all"><br>-- <br>Mikhail Terekhov<br>