>
>
> So downstream distributors can download an sdist - or even a tarball of a
> VCS tag, if they're being strict about it - build wheels from that using
> the config in this proposal, and then transform the wheels into their own
> package format.
>
this has wheel itself being the interoperability standard.
the going idea is that there would be a metadata artifact ("pydist.json" in
PEP426), that provides the standard across different formats.
> Longer term, I think the answer is sdist 2.0 which has proper metadata
> inside of it (name, version, dependencies, etc) but which also includes a
> hook like this PEP has to specify the build system
>
> I hadn't heard of this before - is it something that's being worked on?
>
I haven't seen any PEP's for it yet.
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
