|
4 | 4 | Overview of the IPython configuration system
|
5 | 5 | ============================================
|
6 | 6 |
|
7 |
| -This section describes the IPython configuration system. Starting with version |
8 |
| -0.11, IPython has a completely new configuration system that is quite |
9 |
| -different from the older :file:`ipythonrc` or :file:`ipy_user_conf.py` |
10 |
| -approaches. The new configuration system was designed from scratch to address |
11 |
| -the particular configuration needs of IPython. While there are many |
12 |
| -other excellent configuration systems out there, we found that none of them |
13 |
| -met our requirements. |
14 |
| - |
15 |
| -.. warning:: |
16 |
| - |
17 |
| - If you are upgrading to version 0.11 of IPython, you will need to migrate |
18 |
| - your old :file:`ipythonrc` or :file:`ipy_user_conf.py` configuration files |
19 |
| - to the new system. You may want to read the section on |
20 |
| - :ref:`configuring IPython <configuring_ipython>`. There are also some ideas |
21 |
| - `on the IPython wiki <http://wiki.ipython.org/Cookbook/Moving_config_to_IPython_0.11>`_ |
22 |
| - about this. |
23 |
| - |
24 |
| -The discussion that follows is focused on teaching users how to configure |
25 |
| -IPython to their liking. Developers who want to know more about how they |
26 |
| -can enable their objects to take advantage of the configuration system |
27 |
| -should consult our :ref:`developer guide <developer_guide>` |
| 7 | +This section describes the IPython configuration system. |
| 8 | + |
| 9 | +The following discussion is for users who want to configure |
| 10 | +IPython to their liking. Developers who want to know how they can |
| 11 | +enable their objects to take advantage of the configuration system |
| 12 | +should consult the :ref:`developer guide <developer_guide>` |
28 | 13 |
|
29 | 14 | The main concepts
|
30 | 15 | =================
|
@@ -399,18 +384,14 @@ name.
|
399 | 384 | Startup Files
|
400 | 385 | -------------
|
401 | 386 |
|
402 |
| -If you want some code to be run at the beginning of every IPython session with a |
403 |
| -particular profile, the easiest way is to add Python (.py) or IPython (.ipy) scripts |
404 |
| -to your :file:`<profile>/startup` directory. Files in this directory will always be |
405 |
| -executed as soon as the IPython shell is constructed, and before any other code or |
406 |
| -scripts you have specified. If you have multiple files in the startup directory, |
407 |
| -they will be run in lexicographical order, so you can control the ordering by adding |
408 |
| -a '00-' prefix. |
409 |
| - |
410 |
| -.. note:: |
411 |
| - |
412 |
| - Automatic startup files are new in IPython 0.12. Use the |
413 |
| - InteractiveShellApp.exec_files configurable for similar behavior in 0.11. |
| 387 | +If you want some code to be run at the beginning of every IPython session with |
| 388 | +a particular profile, the easiest way is to add Python (``.py``) or |
| 389 | +IPython (``.ipy``) scripts to your :file:`<profile>/startup` directory. Files |
| 390 | +in this directory will always be executed as soon as the IPython shell is |
| 391 | +constructed, and before any other code or scripts you have specified. If you |
| 392 | +have multiple files in the startup directory, they will be run in |
| 393 | +lexicographical order, so you can control the ordering by adding a '00-' |
| 394 | +prefix. |
414 | 395 |
|
415 | 396 |
|
416 | 397 | .. _commandline:
|
|
0 commit comments