{"action":"closed","issue":{"url":"https://api.github.com/repos/takluyver/pynsist/issues/61","repository_url":"https://api.github.com/repos/takluyver/pynsist","labels_url":"https://api.github.com/repos/takluyver/pynsist/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/takluyver/pynsist/issues/61/comments","events_url":"https://api.github.com/repos/takluyver/pynsist/issues/61/events","html_url":"https://github.com/takluyver/pynsist/issues/61","id":154780943,"number":61,"title":"Install command line launchers","user":{"login":"takluyver","id":327925,"avatar_url":"https://avatars.githubusercontent.com/u/327925?v=3","gravatar_id":"","url":"https://api.github.com/users/takluyver","html_url":"https://github.com/takluyver","followers_url":"https://api.github.com/users/takluyver/followers","following_url":"https://api.github.com/users/takluyver/following{/other_user}","gists_url":"https://api.github.com/users/takluyver/gists{/gist_id}","starred_url":"https://api.github.com/users/takluyver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/takluyver/subscriptions","organizations_url":"https://api.github.com/users/takluyver/orgs","repos_url":"https://api.github.com/users/takluyver/repos","events_url":"https://api.github.com/users/takluyver/events{/privacy}","received_events_url":"https://api.github.com/users/takluyver/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2016-05-13T19:11:30Z","updated_at":"2016-05-19T13:35:57Z","closed_at":"2016-05-19T13:35:57Z","body":"Ping @davvid and @paulproteus who have asked for this feature, and @glyph, who is interested.\r\n\r\n@pfmoore's [notes on making Windows commands](http://paul-moores-notes.readthedocs.io/en/latest/wrappers.html) are pretty clear that making an exe launcher is the only way to offer a command that doesn't have surprising traps lurking. As such, I would use either his [shimmy](https://github.com/pfmoore/shimmy) project, or the [cli launchers](https://github.com/takluyver/win_cli_launchers) pulled out of setuptools - which are less flexible, but more battle tested.\r\n\r\nI envisage an interface something like this:\r\n\r\n```ini\r\n[Command foo]\r\nentry_point=foomod:main\r\n```\r\n\r\nUsing a section per command, rather than `foo=foomod:main`, leaves room for other parameters to be added. With shimmy, we could also support an arbitrary command with `target` and `parameters` options (like shortcuts already allow). With the setuptools cli launchers, we're limited to Python code.\r\n\r\nThe stub exes are a few tens of KB, so installer size shouldn't be a concern. The actual Python code is run as a subprocess, not the main process you start - but for most purposes it doesn't matter, and that's already the case with Python's `console_scripts`  entry points.\r\n\r\nDo we shove the exes somewhere that's already on `%PATH%`, or install them as part of the application and add a directory to `%PATH%`? I'm leaning towards the latter."}}