You can clone with
We have some hacky, fragile code that installs the top-level scripts for the MSI installer. This code need to be tested, checked, etc. before the release.
Are you referring to ipython_win_post_install.py? Just a comment, I don't think bdist_msi is compatible with post-install scripts. I'd love to be proven wrong, but I've never been able to get it to work, and have had to use bdist_wininst instead.
No, but I think it should be easy enough to add .bat or .exe files to the list of scripts when setup.py is run on windows. Then they would be included in the msi installer.
I think there is some value to having an IPython launcher in the start menu. It makes IPython more accessible to new users on windows: they don't have to modify environment variables to add C:\Python27 and C:\Python27\Scripts to the path.
I just ran python setup.py bdist_wininst on my Win7 VM with current master, and after removing all traces of IPython and running the installer, every script seems to work just fine (I do have C:\Python27 and C:\Python27\Scripts in my PATH).
python setup.py bdist_wininst
I did update the post_install script in #536 to match recent changes, and it appears to work, including Start menu items, as long as setuptools is installed.
Merge branch 'winsetup' (PR #536)
introduces install dependency of setuptools on Windows
This is a temporary fix, and the setuptools dependency should
be removed in 0.12.