Reported on-list, see
Installing IPython from source went fine, again using python setup.py install.
At this stage I was at a bit of a loss as to how to test it, my normal ipython
shortcut seemed to still load up my old version 10.1. I found a file
"ipython-qtconsole" in my Python26/Scripts directory but without a suffix or
associated .bat file it wasn't directly executable. This was easily resolved by
creating a bat file iqlab.bat with the contents:
--paging vsplit --pylab inline %*
For the script creation, we can probably add a simple check to see if 'install' is passed on win32, and import setuptools. I think that will ensure the scripts are created. Still, we need to check this, I could be wrong on this one.
Are you sure you want to make setuptools a dependency on windows? I recently removed setuptools dependencies in my own projects. On windows, I did the following in setup.py (see https://github.com/praxes/praxes/blob/master/setup.py), which might work for ipython as well:
scripts = 
# scripts calling multiprocessing must be importable
if ('bdist_wininst' in sys.argv) or ('bdist_msi' in sys.argv):
I guess the extension for ipython-qtconsole should be pyw, so you don't get a dos shell along with the qt console.
I am totally fine with making setuptools a dependency on Windows if getting the executables to work is more than trivial without it.
PR #536 makes setuptools a dependency for install on Windows. Merging that means IPython will not work without setuptools on Windows, because the installed executables in a bdist will also depend on setuptools.
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.