Show More
@@ -1,141 +1,147 b'' | |||
|
1 | 1 | # -*- coding: utf-8 -*- |
|
2 | 2 | """Release data for the IPython project.""" |
|
3 | 3 | |
|
4 | 4 | #----------------------------------------------------------------------------- |
|
5 |
# Copyright (c) 2008-201 |
|
|
5 | # Copyright (c) 2008-2012, IPython Development Team. | |
|
6 | 6 | # Copyright (c) 2001-2007, Fernando Perez <fernando.perez@colorado.edu> |
|
7 | 7 | # Copyright (c) 2001, Janko Hauser <jhauser@zscout.de> |
|
8 | 8 | # Copyright (c) 2001, Nathaniel Gray <n8gray@caltech.edu> |
|
9 | 9 | # |
|
10 | 10 | # Distributed under the terms of the Modified BSD License. |
|
11 | 11 | # |
|
12 | 12 | # The full license is in the file COPYING.txt, distributed with this software. |
|
13 | 13 | #----------------------------------------------------------------------------- |
|
14 | 14 | |
|
15 | 15 | # Name of the package for release purposes. This is the name which labels |
|
16 | 16 | # the tarballs and RPMs made by distutils, so it's best to lowercase it. |
|
17 | 17 | name = 'ipython' |
|
18 | 18 | |
|
19 | 19 | # IPython version information. An empty _version_extra corresponds to a full |
|
20 | 20 | # release. 'dev' as a _version_extra string means this is a development |
|
21 | 21 | # version |
|
22 | 22 | _version_major = 0 |
|
23 | 23 | _version_minor = 13 |
|
24 | 24 | _version_micro = '' # use '' for first of series, number for 1 and above |
|
25 | 25 | _version_extra = 'dev' |
|
26 | 26 | #_version_extra = 'rc1' |
|
27 | 27 | #_version_extra = '' # Uncomment this for full releases |
|
28 | 28 | |
|
29 | 29 | # Construct full version string from these. |
|
30 | 30 | _ver = [_version_major, _version_minor] |
|
31 | 31 | if _version_micro: |
|
32 | 32 | _ver.append(_version_micro) |
|
33 | 33 | if _version_extra: |
|
34 | 34 | _ver.append(_version_extra) |
|
35 | 35 | |
|
36 | 36 | __version__ = '.'.join(map(str, _ver)) |
|
37 | 37 | |
|
38 | 38 | version = __version__ # backwards compatibility name |
|
39 | 39 | |
|
40 | 40 | description = "IPython: Productive Interactive Computing" |
|
41 | 41 | |
|
42 | 42 | long_description = \ |
|
43 | 43 | """ |
|
44 | 44 | IPython provides a rich toolkit to help you make the most out of using Python |
|
45 | 45 | interactively. Its main components are: |
|
46 | 46 | |
|
47 | 47 | * Powerful interactive Python shells (terminal- and Qt-based). |
|
48 | * A web-based interactive notebook environment with all shell features plus | |
|
49 | support for embedded figures, animations and rich media. | |
|
48 | 50 | * Support for interactive data visualization and use of GUI toolkits. |
|
49 | 51 | * Flexible, embeddable interpreters to load into your own projects. |
|
50 |
* |
|
|
52 | * A high-performance library for high level and interactive parallel computing | |
|
53 | that works in multicore systems, clusters, supercomputing and cloud scenarios. | |
|
51 | 54 | |
|
52 | 55 | The enhanced interactive Python shells have the following main features: |
|
53 | 56 | |
|
54 | 57 | * Comprehensive object introspection. |
|
55 | 58 | |
|
56 | 59 | * Input history, persistent across sessions. |
|
57 | 60 | |
|
58 | 61 | * Caching of output results during a session with automatically generated |
|
59 | 62 | references. |
|
60 | 63 | |
|
61 | * Readline based name completion. | |
|
64 | * Extensible tab completion, with support by default for completion of python | |
|
65 | variables and keywords, filenames and function keywords. | |
|
62 | 66 | |
|
63 | 67 | * Extensible system of 'magic' commands for controlling the environment and |
|
64 | 68 | performing many tasks related either to IPython or the operating system. |
|
65 | 69 | |
|
66 |
* |
|
|
67 | than changing $PYTHONSTARTUP environment variables every time). | |
|
70 | * A rich configuration system with easy switching between different setups | |
|
71 | (simpler than changing $PYTHONSTARTUP environment variables every time). | |
|
68 | 72 | |
|
69 | 73 | * Session logging and reloading. |
|
70 | 74 | |
|
71 | 75 | * Extensible syntax processing for special purpose situations. |
|
72 | 76 | |
|
73 | 77 | * Access to the system shell with user-extensible alias system. |
|
74 | 78 | |
|
75 |
* Easily embeddable in other Python programs and |
|
|
79 | * Easily embeddable in other Python programs and GUIs. | |
|
76 | 80 | |
|
77 | 81 | * Integrated access to the pdb debugger and the Python profiler. |
|
78 | 82 | |
|
79 | 83 | The parallel computing architecture has the following main features: |
|
80 | 84 | |
|
81 | 85 | * Quickly parallelize Python code from an interactive Python/IPython session. |
|
82 | 86 | |
|
83 | 87 | * A flexible and dynamic process model that be deployed on anything from |
|
84 | 88 | multicore workstations to supercomputers. |
|
85 | 89 | |
|
86 | 90 | * An architecture that supports many different styles of parallelism, from |
|
87 | 91 | message passing to task farming. |
|
88 | 92 | |
|
89 | 93 | * Both blocking and fully asynchronous interfaces. |
|
90 | 94 | |
|
91 | 95 | * High level APIs that enable many things to be parallelized in a few lines |
|
92 | 96 | of code. |
|
93 | 97 | |
|
94 | 98 | * Share live parallel jobs with other users securely. |
|
95 | 99 | |
|
96 | 100 | * Dynamically load balanced task farming system. |
|
97 | 101 | |
|
98 | 102 | * Robust error handling in parallel code. |
|
99 | 103 | |
|
100 | 104 | The latest development version is always available from IPython's `GitHub |
|
101 | 105 | site <http://github.com/ipython>`_. |
|
102 | 106 | """ |
|
103 | 107 | |
|
104 | 108 | license = 'BSD' |
|
105 | 109 | |
|
106 | 110 | authors = {'Fernando' : ('Fernando Perez','fperez.net@gmail.com'), |
|
107 | 111 | 'Janko' : ('Janko Hauser','jhauser@zscout.de'), |
|
108 | 112 | 'Nathan' : ('Nathaniel Gray','n8gray@caltech.edu'), |
|
109 | 113 | 'Ville' : ('Ville Vainio','vivainio@gmail.com'), |
|
110 | 114 | 'Brian' : ('Brian E Granger', 'ellisonbg@gmail.com'), |
|
111 | 'Min' : ('Min Ragan-Kelley', 'benjaminrk@gmail.com') | |
|
115 | 'Min' : ('Min Ragan-Kelley', 'benjaminrk@gmail.com'), | |
|
116 | 'Thomas' : ('Thomas A. Kluyver', 'takowl@gmail.com'), | |
|
112 | 117 | } |
|
113 | 118 | |
|
114 | 119 | author = 'The IPython Development Team' |
|
115 | 120 | |
|
116 | 121 | author_email = 'ipython-dev@scipy.org' |
|
117 | 122 | |
|
118 | 123 | url = 'http://ipython.org' |
|
119 | 124 | |
|
120 | 125 | # This will only be valid for actual releases sent to PyPI, but that's OK since |
|
121 | 126 | # those are the ones we want pip/easy_install to be able to find. |
|
122 | 127 | download_url = 'http://archive.ipython.org/release/%s' % version |
|
123 | 128 | |
|
124 | platforms = ['Linux','Mac OSX','Windows XP/2000/NT'] | |
|
129 | platforms = ['Linux','Mac OSX','Windows XP/2000/NT/Vista/7'] | |
|
125 | 130 | |
|
126 |
keywords = ['Interactive','Interpreter','Shell','Parallel','Distributed' |
|
|
131 | keywords = ['Interactive','Interpreter','Shell','Parallel','Distributed', | |
|
132 | 'Web-based computing', 'Qt console', 'Embedding'] | |
|
127 | 133 | |
|
128 | 134 | classifiers = [ |
|
129 | 135 | 'Intended Audience :: Developers', |
|
130 | 136 | 'Intended Audience :: Science/Research', |
|
131 | 137 | 'License :: OSI Approved :: BSD License', |
|
132 | 138 | 'Programming Language :: Python', |
|
133 | 139 | 'Programming Language :: Python :: 2', |
|
134 | 140 | 'Programming Language :: Python :: 2.6', |
|
135 | 141 | 'Programming Language :: Python :: 2.7', |
|
136 | 142 | 'Programming Language :: Python :: 3', |
|
137 | 143 | 'Programming Language :: Python :: 3.1', |
|
138 | 144 | 'Programming Language :: Python :: 3.2', |
|
139 | 145 | 'Topic :: System :: Distributed Computing', |
|
140 | 146 | 'Topic :: System :: Shells' |
|
141 | 147 | ] |
@@ -1,376 +1,376 b'' | |||
|
1 | 1 | Overview |
|
2 | 2 | ======== |
|
3 | 3 | |
|
4 | 4 | This document describes the steps required to install IPython. IPython is |
|
5 | 5 | organized into a number of subpackages, each of which has its own dependencies. |
|
6 | 6 | All of the subpackages come with IPython, so you don't need to download and |
|
7 | 7 | install them separately. However, to use a given subpackage, you will need to |
|
8 | 8 | install all of its dependencies. |
|
9 | 9 | |
|
10 | 10 | Please let us know if you have problems installing IPython or any of its |
|
11 | 11 | dependencies. Officially, IPython requires Python 2.6, 2.7, 3.1, or 3.2. |
|
12 | 12 | |
|
13 | 13 | .. warning:: |
|
14 | 14 | |
|
15 | 15 | Since version 0.11, IPython has a hard syntax dependency on 2.6, and will no |
|
16 | 16 | longer work on Python <= 2.5. You can find older versions of IPython which |
|
17 | 17 | supported Python <= 2.5 `here <http://archive.ipython.org/release/>`_ |
|
18 | 18 | |
|
19 | 19 | Some of the installation approaches use the :mod:`distribute` package and its |
|
20 | 20 | :command:`easy_install` command line program. In many scenarios, this provides |
|
21 | 21 | the most simple method of installing IPython and its dependencies. More |
|
22 | 22 | information about :mod:`distribute` can be found on its website. |
|
23 | 23 | |
|
24 | 24 | .. note:: |
|
25 | 25 | |
|
26 | 26 | On Windows, IPython has a hard dependency on :mod:`distribute`. We hope to |
|
27 | 27 | change this in the future, but for now on Windows, you *must* install |
|
28 | 28 | :mod:`distribute`. |
|
29 | 29 | |
|
30 | 30 | More general information about installing Python packages can be found in |
|
31 | 31 | `Python's documentation <http://docs.python.org>`_. |
|
32 | 32 | |
|
33 | 33 | |
|
34 | 34 | Quickstart |
|
35 | 35 | ========== |
|
36 | 36 | |
|
37 | 37 | If you have :mod:`distribute` installed and you are on OS X or Linux (not |
|
38 | 38 | Windows), the following will download and install IPython *and* the main |
|
39 | 39 | optional dependencies: |
|
40 | 40 | |
|
41 | 41 | .. code-block:: bash |
|
42 | 42 | |
|
43 | 43 | $ easy_install ipython[zmq,qtconsole,notebook,test] |
|
44 | 44 | |
|
45 | 45 | This will get: |
|
46 | 46 | |
|
47 | 47 | - pyzmq, needed for IPython's parallel computing features, qt console and |
|
48 | 48 | notebook. |
|
49 | 49 | - pygments, used by the Qt console for syntax highlighting. |
|
50 | 50 | - tornado, needed by the web-based notebook |
|
51 | 51 | - nose, used by the test suite. |
|
52 | 52 | |
|
53 | 53 | To run IPython's test suite, use the :command:`iptest` command: |
|
54 | 54 | |
|
55 | 55 | .. code-block:: bash |
|
56 | 56 | |
|
57 | 57 | $ iptest |
|
58 | 58 | |
|
59 | 59 | |
|
60 | 60 | Installing IPython itself |
|
61 | 61 | ========================= |
|
62 | 62 | |
|
63 | 63 | Given a properly built Python, the basic interactive IPython shell will work |
|
64 | 64 | with no external dependencies. However, some Python distributions |
|
65 | 65 | (particularly on Windows and OS X), don't come with a working :mod:`readline` |
|
66 | 66 | module. The IPython shell will work without :mod:`readline`, but will lack |
|
67 | 67 | many features that users depend on, such as tab completion and command line |
|
68 | 68 | editing. If you install IPython with :mod:`distribute`, (e.g. with |
|
69 | 69 | `easy_install`), then the appropriate :mod:`readline` for your platform will be |
|
70 | 70 | installed. See below for details of how to make sure you have a working |
|
71 | 71 | :mod:`readline`. |
|
72 | 72 | |
|
73 | 73 | Installation using easy_install |
|
74 | 74 | ------------------------------- |
|
75 | 75 | |
|
76 | 76 | If you have :mod:`distribute` installed, the easiest way of getting IPython is |
|
77 |
to simpl |
|
|
77 | to simply use :command:`easy_install`: | |
|
78 | 78 | |
|
79 | 79 | .. code-block:: bash |
|
80 | 80 | |
|
81 | 81 | $ easy_install ipython |
|
82 | 82 | |
|
83 | 83 | That's it. |
|
84 | 84 | |
|
85 | 85 | Installation from source |
|
86 | 86 | ------------------------ |
|
87 | 87 | |
|
88 | 88 | If you don't want to use :command:`easy_install`, or don't have it installed, |
|
89 | 89 | just grab the latest stable build of IPython from `here |
|
90 | 90 | <http://ipython.org/download.html>`_. Then do the following: |
|
91 | 91 | |
|
92 | 92 | .. code-block:: bash |
|
93 | 93 | |
|
94 | 94 | $ tar -xzf ipython.tar.gz |
|
95 | 95 | $ cd ipython |
|
96 | 96 | $ python setup.py install |
|
97 | 97 | |
|
98 | 98 | If you are installing to a location (like ``/usr/local``) that requires higher |
|
99 | 99 | permissions, you may need to run the last command with :command:`sudo`. |
|
100 | 100 | |
|
101 | 101 | Windows |
|
102 | 102 | ------- |
|
103 | 103 | |
|
104 | 104 | As mentioned above, on Windows, IPython requires :mod:`distribute`, and it also |
|
105 | 105 | requires the PyReadline library to properly support coloring and keyboard |
|
106 | 106 | management (features that the default windows console doesn't have). So on |
|
107 | 107 | Windows, the installation procedure is: |
|
108 | 108 | |
|
109 | 109 | 1. Install `distribute <http://pypi.python.org/pypi/distribute>`_. |
|
110 | 110 | |
|
111 | 111 | 2. Install `pyreadline <http://pypi.python.org/pypi/pyreadline>`_. You can use |
|
112 | 112 | the command ``easy_install pyreadline`` from a terminal, or the binary |
|
113 | 113 | installer appropriate for your platform from the PyPI page. |
|
114 | 114 | |
|
115 | 115 | 3. Install IPython itself, which you can download from `PyPI |
|
116 | 116 | <http://pypi.python.org/pypi/ipython>`_ or from `our site |
|
117 | 117 | <http://ipython.org/download.html>`_. Note that on Windows 7, you *must* |
|
118 | 118 | right-click and 'Run as administrator' for the Start menu shortcuts to be |
|
119 | 119 | created. |
|
120 | 120 | |
|
121 | 121 | IPython by default runs in a terminal window, but the normal terminal |
|
122 | 122 | application supplied by Microsoft Windows is very primitive. You may want to |
|
123 | 123 | download the excellent and free Console_ application instead, which is a far |
|
124 | 124 | superior tool. You can even configure Console to give you by default an |
|
125 | 125 | IPython tab, which is very convenient to create new IPython sessions directly |
|
126 | 126 | from the working terminal. |
|
127 | 127 | |
|
128 | 128 | .. _Console: http://sourceforge.net/projects/console |
|
129 | 129 | |
|
130 | 130 | |
|
131 | 131 | Installing the development version |
|
132 | 132 | ---------------------------------- |
|
133 | 133 | |
|
134 | 134 | It is also possible to install the development version of IPython from our |
|
135 | 135 | `Git <http://git-scm.com/>`_ source code repository. To do this you will |
|
136 | 136 | need to have Git installed on your system. Then just do: |
|
137 | 137 | |
|
138 | 138 | .. code-block:: bash |
|
139 | 139 | |
|
140 | 140 | $ git clone https://github.com/ipython/ipython.git |
|
141 | 141 | $ cd ipython |
|
142 | 142 | $ python setup.py install |
|
143 | 143 | |
|
144 | 144 | Some users want to be able to follow the development branch as it changes. If |
|
145 | 145 | you have :mod:`distribute` installed, this is easy. Simply replace the last |
|
146 | 146 | step by: |
|
147 | 147 | |
|
148 | 148 | .. code-block:: bash |
|
149 | 149 | |
|
150 | 150 | $ python setupegg.py develop |
|
151 | 151 | |
|
152 | 152 | This creates links in the right places and installs the command line script to |
|
153 | 153 | the appropriate places. Then, if you want to update your IPython at any time, |
|
154 | 154 | just do: |
|
155 | 155 | |
|
156 | 156 | .. code-block:: bash |
|
157 | 157 | |
|
158 | 158 | $ git pull |
|
159 | 159 | |
|
160 | 160 | |
|
161 | 161 | Basic optional dependencies |
|
162 | 162 | =========================== |
|
163 | 163 | |
|
164 | 164 | There are a number of basic optional dependencies that most users will want to |
|
165 | 165 | get. These are: |
|
166 | 166 | |
|
167 | 167 | * readline (for command line editing, tab completion, etc.) |
|
168 | 168 | * nose (to run the IPython test suite) |
|
169 | 169 | * pexpect (to use things like irunner) |
|
170 | 170 | |
|
171 | 171 | If you are comfortable installing these things yourself, have at it, otherwise |
|
172 | 172 | read on for more details. |
|
173 | 173 | |
|
174 | 174 | readline |
|
175 | 175 | -------- |
|
176 | 176 | |
|
177 | 177 | As indicated above, on Windows, PyReadline is a *mandatory* dependency. |
|
178 | 178 | PyReadline is a separate, Windows only implementation of readline that uses |
|
179 | 179 | native Windows calls through :mod:`ctypes`. The easiest way of installing |
|
180 | 180 | PyReadline is you use the binary installer available `here |
|
181 | 181 | <http://pypi.python.org/pypi/pyreadline>`_. |
|
182 | 182 | |
|
183 | 183 | On OSX, if you are using the built-in Python shipped by Apple, you will be |
|
184 | 184 | missing a full readline implementation as Apple ships instead a library called |
|
185 | 185 | ``libedit`` that provides only some of readline's functionality. While you may |
|
186 | 186 | find libedit sufficient, we have occasional reports of bugs with it and several |
|
187 | 187 | developers who use OS X as their main environment consider libedit unacceptable |
|
188 | 188 | for productive, regular use with IPython. |
|
189 | 189 | |
|
190 | 190 | Therefore, we *strongly* recommend that on OS X you get the full |
|
191 | 191 | :mod:`readline` module. We will *not* consider completion/history problems to |
|
192 | 192 | be bugs for IPython if you are using libedit. |
|
193 | 193 | |
|
194 | 194 | To get a working :mod:`readline` module, just do (with :mod:`distribute` |
|
195 | 195 | installed): |
|
196 | 196 | |
|
197 | 197 | .. code-block:: bash |
|
198 | 198 | |
|
199 | 199 | $ easy_install readline |
|
200 | 200 | |
|
201 | 201 | .. note:: |
|
202 | 202 | |
|
203 | 203 | Other Python distributions on OS X (such as fink, MacPorts and the official |
|
204 | 204 | python.org binaries) already have readline installed so you likely don't |
|
205 | 205 | have to do this step. |
|
206 | 206 | |
|
207 | 207 | When IPython is installed with :mod:`distribute`, (e.g. using the |
|
208 | 208 | ``easy_install`` command), readline is added as a dependency on OS X, and |
|
209 | 209 | PyReadline on Windows, and will be installed on your system. However, if you |
|
210 | 210 | do not use distribute, you may have to install one of these packages yourself. |
|
211 | 211 | |
|
212 | 212 | |
|
213 | 213 | nose |
|
214 | 214 | ---- |
|
215 | 215 | |
|
216 | 216 | To run the IPython test suite you will need the :mod:`nose` package. Nose |
|
217 | 217 | provides a great way of sniffing out and running all of the IPython tests. The |
|
218 | 218 | simplest way of getting nose, is to use :command:`easy_install`: |
|
219 | 219 | |
|
220 | 220 | .. code-block:: bash |
|
221 | 221 | |
|
222 | 222 | $ easy_install nose |
|
223 | 223 | |
|
224 | 224 | Another way of getting this is to do: |
|
225 | 225 | |
|
226 | 226 | .. code-block:: bash |
|
227 | 227 | |
|
228 | 228 | $ easy_install ipython[test] |
|
229 | 229 | |
|
230 | 230 | For more installation options, see the `nose website |
|
231 | 231 | <http://somethingaboutorange.com/mrl/projects/nose/>`_. |
|
232 | 232 | |
|
233 | 233 | Once you have nose installed, you can run IPython's test suite using the |
|
234 | 234 | iptest command: |
|
235 | 235 | |
|
236 | 236 | .. code-block:: bash |
|
237 | 237 | |
|
238 | 238 | $ iptest |
|
239 | 239 | |
|
240 | 240 | pexpect |
|
241 | 241 | ------- |
|
242 | 242 | |
|
243 | 243 | The pexpect_ package is used in IPython's :command:`irunner` script, as well as |
|
244 | 244 | for managing subprocesses. IPython now includes a version of pexpect in |
|
245 | 245 | :mod:`IPython.external`, but if you have installed pexpect, IPython will use |
|
246 | 246 | that instead. On Unix platforms (including OS X), just do: |
|
247 | 247 | |
|
248 | 248 | .. code-block:: bash |
|
249 | 249 | |
|
250 | 250 | $ easy_install pexpect |
|
251 | 251 | |
|
252 | 252 | Windows users are out of luck as pexpect does not run there. |
|
253 | 253 | |
|
254 | 254 | Dependencies for IPython.parallel (parallel computing) |
|
255 | 255 | ====================================================== |
|
256 | 256 | |
|
257 | 257 | :mod:`IPython.kernel` has been replaced by :mod:`IPython.parallel`, |
|
258 | 258 | which uses ZeroMQ for all communication. |
|
259 | 259 | |
|
260 | 260 | IPython.parallel provides a nice architecture for parallel computing, with a |
|
261 | 261 | focus on fluid interactive workflows. These features require just one package: |
|
262 | 262 | PyZMQ. See the next section for PyZMQ details. |
|
263 | 263 | |
|
264 | 264 | On a Unix style platform (including OS X), if you want to use |
|
265 | 265 | :mod:`distribute`, you can just do: |
|
266 | 266 | |
|
267 | 267 | .. code-block:: bash |
|
268 | 268 | |
|
269 | 269 | $ easy_install ipython[zmq] # will include pyzmq |
|
270 | 270 | |
|
271 | 271 | Security in IPython.parallel is provided by SSH tunnels. By default, Linux |
|
272 | 272 | and OSX clients will use the shell ssh command, but on Windows, we also |
|
273 | 273 | support tunneling with paramiko_. |
|
274 | 274 | |
|
275 | 275 | Dependencies for IPython.zmq |
|
276 | 276 | ============================ |
|
277 | 277 | |
|
278 | 278 | pyzmq |
|
279 | 279 | ----- |
|
280 | 280 | |
|
281 | 281 | IPython 0.11 introduced some new functionality, including a two-process |
|
282 | 282 | execution model using ZeroMQ_ for communication. The Python bindings to ZeroMQ |
|
283 | 283 | are found in the PyZMQ_ project, which is easy_install-able once you have |
|
284 | 284 | ZeroMQ installed. If you are on Python 2.6 or 2.7 on OSX, or 2.7 on Windows, |
|
285 | 285 | pyzmq has eggs that include ZeroMQ itself. |
|
286 | 286 | |
|
287 | 287 | IPython.zmq depends on pyzmq >= 2.1.4. |
|
288 | 288 | |
|
289 | 289 | Dependencies for the IPython QT console |
|
290 | 290 | ======================================= |
|
291 | 291 | |
|
292 | 292 | pyzmq |
|
293 | 293 | ----- |
|
294 | 294 | |
|
295 | 295 | Like the :mod:`IPython.parallel` package, the QT Console requires ZeroMQ and |
|
296 | 296 | PyZMQ. |
|
297 | 297 | |
|
298 | 298 | Qt |
|
299 | 299 | -- |
|
300 | 300 | |
|
301 | 301 | Also with 0.11, a new GUI was added using the work in :mod:`IPython.zmq`, which |
|
302 | 302 | can be launched with ``ipython qtconsole``. The GUI is built on Qt, and works |
|
303 | 303 | with either PyQt, which can be installed from the `PyQt website |
|
304 | 304 | <http://www.riverbankcomputing.co.uk/>`_, or `PySide |
|
305 | 305 | <http://www.pyside.org/>`_, from Nokia. |
|
306 | 306 | |
|
307 | 307 | pygments |
|
308 | 308 | -------- |
|
309 | 309 | |
|
310 | 310 | The syntax-highlighting in ``ipython qtconsole`` is done with the pygments_ |
|
311 | 311 | project, which is easy_install-able. |
|
312 | 312 | |
|
313 | 313 | .. _installnotebook: |
|
314 | 314 | |
|
315 | 315 | Dependencies for the IPython HTML notebook |
|
316 | 316 | ========================================== |
|
317 | 317 | |
|
318 | 318 | The IPython notebook is a notebook-style web interface to IPython and can be |
|
319 | 319 | started withe command ``ipython notebook``. |
|
320 | 320 | |
|
321 | 321 | pyzmq |
|
322 | 322 | ----- |
|
323 | 323 | |
|
324 | 324 | Like the :mod:`IPython.parallel` and :mod:`IPython.frontend.qt.console` |
|
325 | 325 | packages, the HTML notebook requires ZeroMQ and PyZMQ. |
|
326 | 326 | |
|
327 | 327 | Tornado |
|
328 | 328 | ------- |
|
329 | 329 | |
|
330 | 330 | The IPython notebook uses the Tornado_ project for its HTTP server. Tornado 2.1 |
|
331 | 331 | is required, in order to support current versions of browsers, due to an update |
|
332 | 332 | to the websocket protocol. |
|
333 | 333 | |
|
334 | 334 | |
|
335 | 335 | MathJax |
|
336 | 336 | ------- |
|
337 | 337 | |
|
338 | 338 | The IPython notebook uses the MathJax_ Javascript library for rendering LaTeX |
|
339 | 339 | in web browsers. Because MathJax is large, we don't include it with |
|
340 | 340 | IPython. Normally IPython will load MathJax from a CDN, but if you have a slow |
|
341 | 341 | network connection, or want to use LaTeX without an internet connection at all, |
|
342 | 342 | we do include a utility to aid in downloading MathJax and installing it into |
|
343 | 343 | the proper location:: |
|
344 | 344 | |
|
345 | 345 | from IPython.external.mathjax import install_mathjax |
|
346 | 346 | install_mathjax() |
|
347 | 347 | |
|
348 | 348 | This function does require write access to the IPython install directory, so if |
|
349 | 349 | you have a system-wide Python install, it may need to be done from a ``sudo |
|
350 | 350 | python`` session. |
|
351 | 351 | |
|
352 | 352 | Browser Compatibility |
|
353 | 353 | --------------------- |
|
354 | 354 | |
|
355 | 355 | The notebook uses WebSockets and the flexible box model. These features are |
|
356 | 356 | available in the following browsers: |
|
357 | 357 | |
|
358 | 358 | * Chrome |
|
359 | 359 | * Safari |
|
360 | 360 | * Firefox 6 and above |
|
361 | 361 | * Firefox 4 and 5: These browsers have WebSocket support, but it is disabled by |
|
362 | 362 | default. If you're unable to upgrade, you can enable it by entering ``about:config`` |
|
363 | 363 | in the URL bar and then setting ``network.websocket.enabled`` and |
|
364 | 364 | ``network.websocket.override-security-block`` to ``true``. |
|
365 | 365 | |
|
366 | 366 | Internet Explorer 9 does not support WebSockets or the flexible box model, but |
|
367 | 367 | these features should appear in Internet Explorer 10. |
|
368 | 368 | |
|
369 | 369 | |
|
370 | 370 | .. _ZeroMQ: http://www.zeromq.org |
|
371 | 371 | .. _PyZMQ: https://github.com/zeromq/pyzmq |
|
372 | 372 | .. _paramiko: https://github.com/robey/paramiko |
|
373 | 373 | .. _pygments: http://pygments.org |
|
374 | 374 | .. _pexpect: http://www.noah.org/wiki/Pexpect |
|
375 | 375 | .. _Tornado: http://www.tornadoweb.org |
|
376 | 376 | .. _MathJax: http://www.mathjax.org |
General Comments 0
You need to be logged in to leave comments.
Login now