[Distutils] How to handle launcher script importability?

Paul Moore p.f.moore at gmail.com
Wed Aug 21 11:46:05 CEST 2013

On 21 August 2013 10:29, Donald Stufft <donald at stufft.io> wrote:

> Can you send me a list (or post them here) of what issues you've hit? The
> biggest one i'm aware of is the scripts problem which is a fundamental
> problem with the 1.0 Wheel (or rather that any library with console entry
> points cannot be universal).

The scripts one is the key one (and yes, that needs to be fixed by updating
the spec to confirm the consensus and then updating the tools to match).

Another one IIRC was that distlib didn't put entry-points.txt in the
.dist-info directory in the wheel (which breaks entry points). I think
that's fixed now (and again, the Wheel spec is silent on what is correct
behaviour here).

I'll try to dig out the others, but they weren't anywhere near as major
(some were also script-related such as inconsistent rewriting of shebang
lines, which are superseded by the current state of play on scripts
anyway). Generally, though, they were all areas where the 1.0 spec is
silent (or just a bit vague) on details, and I was hitting
implementation-defined differences. (For example, I was surprised to find
that nowhere in the Wheel 1.0 spec does it actually state the metadata
version that wheels should contain internally, just that it should be
stored in a file called METADATA and that it should follow PKG-INFO which
sort of implies that it's a 1.X format). Without an implementation that
matches the spec precisely, though, it's often hard to know where to report

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130821/ffc6fcad/attachment.html>

More information about the Distutils-SIG mailing list