On 8 October 2015 at 13:05, Ionel Cristian Mărieș <cont...@ionelmc.ro> wrote: > On Thu, Oct 8, 2015 at 1:18 PM, Oscar Benjamin <oscar.j.benja...@gmail.com> > wrote: >> >> I think this satisfies all of the requirements for static metadata and >> one-to-one correspondence of source wheels and binary wheels. If numpy >> followed this then I imagine that there would be a single source wheel >> on PyPI corresponding to the one configuration that would be used >> consistently there. However numpy still needs to separately release >> the code in a form that is also usable in all of the many other >> contexts that it is already used. > > Can't that configuration just be the build defaults? There would be a single > source but with some preset build configuration. People with different needs > can just override those.
Yeah, I guess so. Maybe I'm just not understanding what the "one-to-one" correspondence is supposed to mean. Earlier in the thread it was said to be important because of wheel caching etc. but if it's possible to configure different builds then it's not really one-to-one. -- Oscar _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
