On 13 Feb 2013 02:50, "PJ Eby" <p...@telecommunity.com> wrote: > > On Tue, Feb 12, 2013 at 3:48 AM, Ronald Oussoren <ronaldousso...@mac.com> wrote: > > The hook could be one or two new header fields in the PKG-INFO > > file, with a PEP that describes those keys and how the builder is invoked and what > > it is supposed to do. Am I understanding this correctly? > > > > Something like: > > > > Extension: pepYYY-builder > > pepYYY-builder/dist: bento (>=1.1) > > pepYYY-builder/build: bento.builder:run > > For simplicity's sake and decoupling/DRY, I'd say the bento project > should be the one who'd include the 'build' field specifying the entry > point. The depending projects should only have to say they're using > bento as a builder. That allows bento to refactor without breaking > depending projects. > > If Vinay's distlib supports entry points and will be in the stdlib, > that'd be even better, since it would avoid having to create Yet > Another Module+Attribute String Parser And Dynamic Importer. ;-) > (Not to mention documenting its spec and teaching it to people.)
Indeed, there is much hand-waving involved in my current "where would I like us to be in a couple of years?" Archiver/Builder/Installer scheme. The immediate focus is on splitting installation out from archiving and building. Splitting archiving from building is going to require more work and isn't especially urgent - I just wanted to be clear on my current position after Marcus raised the topic. Cheers, Nick.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
