##// END OF EJS Templates
Moving extensions to either quarantine or deathrow....
Moving extensions to either quarantine or deathrow. When a module is moved to quarantine, it means that while we intend to keep it, it is currently broken or sufficiently untested that it can't be in the main IPython codebase. To be moved back into the main IPython codebase a module must: 1. Work fully. 2. Have a test suite. 3. Be a proper IPython extension and tie into the official APIs. 3. Have members of the IPython dev team who are willing to maintain it. When a module is moved to deathrow, it means that the code is either broken and not worth repairing, deprecated, replaced by newer functionality, or code that should be developed and maintained by a third party.

File last commit:

r2119:2c8c96be
r2267:928c921b
Show More
setupegg.py
12 lines | 297 B | text/x-python | PythonLexer
vivainio
Separate eggsetup.py that handles scripts installation in the egg...
r138 #!/usr/bin/env python
Brian E Granger
Adding documentation to setup* files.
r1239 """Wrapper to run setup.py using setuptools."""
vivainio
Separate eggsetup.py that handles scripts installation in the egg...
r138
vivainio
changed setup to support easy_install ipython==dev
r173 import sys
vivainio
Separate eggsetup.py that handles scripts installation in the egg...
r138
vivainio
changed setup to support easy_install ipython==dev
r173 # now, import setuptools and call the actual setup
import setuptools
execfile('setup.py')
vivainio
Make the egg as minimal as possible, no docs, examples etc.
r139
vivainio
changed setup to support easy_install ipython==dev
r173 # clean up the junk left around by setuptools
vivainio
Joergens patches for Latex char escaping and eggsetup.py develop
r211 if "develop" not in sys.argv:
os.system('rm -rf ipython.egg-info build')