On 18 July 2013 23:51, Daniel Holth <dho...@gmail.com> wrote: > On Thu, Jul 18, 2013 at 6:42 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > > I actually now plan to make scripts and exports first class citizens in > PEP > > 426, with pydist-scripts.json and pydist-exports.json as extracted > summary > > files (like the existing pydist-dependencies.json). > > > > They're important enough to include directly. > > > > Cheers, > > Nick. > > Must they be two separate features? One of the reasons I use > entry_points scripts is that I forget that the scripts= command to > setup() exists at all.
This is just the metadata. I would assume that the console-scripts/gui-scripts entry pointdefinitions in setuptools would be extracted and put into the scripts metadata, and any non-script entry points would go into exports. The legacy scripts= arguments would also go into scripts. Nick - How would the 2 methods of specifying scripts (legacy name of a (potentially platform-specific) file, and setuptools module:function style spec requiring wrapper generation) be recorded, under your approach? Paul
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
