[Distutils] Towards a simple and standard sdist format that isn't intertwined with distutils

[Donald Stufft]

On October 7, 2015 at 2:31:03 PM, Oscar Benjamin (oscar.j.benjamin at gmail.com) wrote:
> >
> Your idea of an sdist as something that has fully static build/runtime 
> dependency metadata and a one to one correspondence with binary 
> wheels is not a usable format when releasing the code for e.g. 
> numpy 1.10. It's fine to say that pip/PyPI should work with the 
> source in some other distribution format and numpy could produce 
> that but it means that the standard tarball release needs to be 
> supported some how separately. Numpy should be able to use PyPI 
> in order to host the tarball even if pip ignores the file.
> 
> 
> If numpy released only source wheels then there would be more 
> than one source wheel for each release corresponding to e.g. 
> the different ways that numpy is linked. There still needs to 
> be a way to release a single file representing the code for the 
> release as a whole.
> 

Can you expand on this please? I've never used numpy for anything serious and
I'm trying to figure out why and what parts of what I'm thinking of wouldn't
work for it.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA