On Mar 27, 2013, at 2:04 PM, Vinay Sajip <[email protected]> wrote:
> Donald Stufft <donald <at> stufft.io> writes: > > >> I don't think the packaging formats should dictate the development flow at >> all. > > We might be at cross purposes here. If we posit that packaging metadata is in > JSON format (which I think we both favour), I was addressing Daniel's > objection > to it on the grounds that he doesn't like editing JSON, to suggest an > alternative > for people with that objection. It doesn't follow that they *have* to use any > particular workflow or tool, or that packaging formats are dictating it (other > than the bare fact that they are JSON). > > Regards, > > Vinay Sajip > > _______________________________________________ > Distutils-SIG maillist - [email protected] > http://mail.python.org/mailman/listinfo/distutils-sig Gotcha, yea in my mind the JSON is generated by the archiver tool and added to the various types of dists, wheels, etc. What the users actually edit/use is totally up to the archiver tool. It could be .in files it could be a python file, it could be YAML, it could pull from a SQLite database. Packaging shouldn't care as long as it gets it's sdists bdists, wheels etc in the proper format with the proper metadata files. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
