<div dir="ltr">On 16 July 2013 19:18, Vinay Sajip <span dir="ltr"><<a href="mailto:vinay_sajip@yahoo.co.uk" target="_blank">vinay_sajip@yahoo.co.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
>If I were writing a firm proposal, I'd go for something like entry points as metadata<br>
<br>
</div>My extended metadata already covers this, though I use the name "exports" (suggested by PJE) because you can share not just code but data, and "entry points" generally implies code. The current version of distil creates wrappers for both gui and console scripts, and adds the appropriate native executable wrappers (32- or 64-bit, according to the running Python) on Windows.</blockquote>
<div><br></div><div>Nice. So we could say that wheel installers should create exe wrappers based on the 'scripts' key of the 'exports' metadata. Then we process the 'scripts' directory unaltered for backward compatibility.</div>
<div><br></div><div>The only other part of the equation is to ensure that wheel *builders* do not put setuptools-generated entry point wrappers into the scripts directory. Before I embarrass myself again (:-)) is this also something you already have implemented in distlib? :-)</div>
<div><br></div><div>When you're finished with Guido's time machine, make sure you put the keys back :-)</div><div>Paul</div></div></div></div>