##// END OF EJS Templates
add startup files to docs
MinRK -
Show More
@@ -358,6 +358,35 b' you create profiles with the name of one of our shipped profiles, these config'
358 files will be copied over instead of starting with the automatically generated
358 files will be copied over instead of starting with the automatically generated
359 config files.
359 config files.
360
360
361 Security Files
362 --------------
363
364 If you are using the notebook, qtconsole, or parallel code, IPython stores
365 connection information in small JSON files in the active profile's security
366 directory. This directory is made private, so only you can see the files inside. If
367 you need to move connection files around to other computers, this is where they will
368 be. If you want your code to be able to open security files by name, we have a
369 convenience function :func:`IPython.utils.path.get_security_file`, which will return
370 the absolute path to a security file from its filename and [optionally] profile
371 name.
372
373 Startup Files
374 -------------
375
376 If you want some code to be run at the beginning of every IPython session with a
377 particular profile, the easiest way is to add Python (.py) or IPython (.ipy) scripts
378 to your :file:`<profile>/startup` directory. Files in this directory will always be
379 executed as soon as the IPython shell is constructed, and before any other code or
380 scripts you have specified. If you have multiple files in the startup directory,
381 they will be run in lexicographical order, so you can control the ordering by adding
382 a '00-' prefix.
383
384 .. note::
385
386 Automatic startup files are new in IPython 0.12. Use the
387 InteractiveShellApp.exec_files configurable for similar behavior in 0.11.
388
389
361 .. _commandline:
390 .. _commandline:
362
391
363 Command-line arguments
392 Command-line arguments
@@ -142,4 +142,19 b' Profiles allow you to use IPython for different tasks, keeping separate config'
142 files and history for each one. More details in :ref:`the profiles section
142 files and history for each one. More details in :ref:`the profiles section
143 <profiles>`.
143 <profiles>`.
144
144
145 Startup Files
146 -------------
147
148 If you want some code to be run at the beginning of every IPython session, the
149 easiest way is to add Python (.py) or IPython (.ipy) scripts to your
150 :file:`<profile>/startup` directory. Files in this directory will always be executed
151 as soon as the IPython shell is constructed, and before any other code or scripts
152 you have specified. If you have multiple files in the startup directory, they will
153 be run in lexicographical order, so you can control the ordering by adding a '00-'
154 prefix.
155
156 .. note::
157
158 Automatic startup files are new in IPython 0.12. Use the
159 InteractiveShellApp.exec_files configurable for similar behavior in 0.11.
145
160
General Comments 0
You need to be logged in to leave comments. Login now