<div>Hi,</div><div class="gmail_quote"><br></div><div class="gmail_quote">2010/12/3 Michael Foord <span dir="ltr"><<a href="mailto:fuzzyman@voidspace.org.uk">fuzzyman@voidspace.org.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":38x">On 02/12/2010 23:01, "Martin v. Löwis" wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[snip...]<br>
</blockquote><div class="im">
I'm just getting tired having to talk to<br>
five projects just to make a single change to the build infrastructure<br>
available to the Python community.<br>
<br>
</div></blockquote>
<br>
The very best hope of resolving that particular problem is distutils2. :-)<br>
<br>
distutils2 is *already* available to the Python community, and whether or not there is a fixed release date it will have betas and then a 1.0 release in the foreseeable future. The team working on it has made an enormous amount of progress. We're much better off as a development community putting our support and energy into distutils2 rather than pining for evolution of distutils.</div>
</blockquote></div><br>Sure. But today (before 3.2b1) we want to merge PEP3149 and PEP384;<div>they change the paths and filenames used by python.<div>Either we modify distutils to comply with the new names,</div><div>or defer these PEPs until distutils2 is ready.<br clear="all">
<br></div><div>-- <br>Amaury Forgeot d'Arc<br>
</div></div>