On 17 Jul 2013 04:19, "Vinay Sajip" <vinay_sa...@yahoo.co.uk> wrote: > > > > >If I were writing a firm proposal, I'd go for something like entry points as metadata > > My extended metadata already covers this, though I use the name "exports" (suggested by PJE) because you can share not just code but data, and "entry points" generally implies code. The current version of distil creates wrappers for both gui and console scripts, and adds the appropriate native executable wrappers (32- or 64-bit, according to the running Python) on Windows.
Yeah, originally we were going to postpone dealing with entry points to a metadata extension (Daniel even had a proto-PEP kicking around in the pre-JSON days). However, I now think it makes more sense to standardise them as an "exports" field in PEP 426. So run with the assumption that something like that will be part of the standard metadata - either derived from entry_points.txt for existing metadata, or specified directly for next generation metadata. Cheers, Nick.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
