[Distutils] State of the wheel spec (Was: How to handle launcher script importability?)

Paul Moore p.f.moore at gmail.com
Wed Aug 21 14:15:51 CEST 2013

On 21 August 2013 13:01, Paul Moore <p.f.moore at gmail.com> wrote:

> If you want to say distlib won't support pre-Metadata 2.0 specifications
> of script metadata, then that's your choice - it's not contrary to the
> standards but I'd view it as a quality of implementation choice. I view the
> underspecification in the Wheel 1.0 spec as similarly a quality of detail
> issue, and I'd expect to fix it in either an update to Wheel 1.0, or a
> Wheel 1.1 which does not make the jump to pure Metadata 2.0.

Ignore this (to an extent). I've just seen your comments on the distlib

For those not following along, both wheel and distlib currently process a
pydist.json file in the wheel dist-info directory. The wheel project
doesn't put entry-points.txt data in there yet, but distlib expects to find
script metadata there.

So the incompatibility here is merely one of two implementations being out
of sync - no big deal.

BUT, this means that there is no spec of the current behaviour, and no
implementation of the Wheel 1.0 spec anywhere.

Either there is movement behind the scenes that I'm not aware of, and I'm
jumping the gun in trying to make sense of the current state of play, or
the wheel spec needs a review reasonably soon.

Whichever is the case, I don't think that my current investigations are
adding anything productive here. So I'm going to take a step back from all
of this for a week or two and see what develops.

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

More information about the Distutils-SIG mailing list