Show More
1 | NO CONTENT: modified file |
|
NO CONTENT: modified file |
@@ -1,525 +1,524 b'' | |||||
1 | # -*- coding: utf-8 -*- |
|
1 | # -*- coding: utf-8 -*- | |
2 | """Usage information for the main IPython applications. |
|
2 | """Usage information for the main IPython applications. | |
3 | """ |
|
3 | """ | |
4 | #----------------------------------------------------------------------------- |
|
4 | #----------------------------------------------------------------------------- | |
5 | # Copyright (C) 2008-2010 The IPython Development Team |
|
5 | # Copyright (C) 2008-2010 The IPython Development Team | |
6 | # Copyright (C) 2001-2007 Fernando Perez. <fperez@colorado.edu> |
|
6 | # Copyright (C) 2001-2007 Fernando Perez. <fperez@colorado.edu> | |
7 | # |
|
7 | # | |
8 | # Distributed under the terms of the BSD License. The full license is in |
|
8 | # Distributed under the terms of the BSD License. The full license is in | |
9 | # the file COPYING, distributed as part of this software. |
|
9 | # the file COPYING, distributed as part of this software. | |
10 | #----------------------------------------------------------------------------- |
|
10 | #----------------------------------------------------------------------------- | |
11 |
|
11 | |||
12 | import sys |
|
12 | import sys | |
13 | from IPython.core import release |
|
13 | from IPython.core import release | |
14 |
|
14 | |||
15 | cl_usage = """\ |
|
15 | cl_usage = """\ | |
16 | ========= |
|
16 | ========= | |
17 | IPython |
|
17 | IPython | |
18 | ========= |
|
18 | ========= | |
19 |
|
19 | |||
20 | Tools for Interactive Computing in Python |
|
20 | Tools for Interactive Computing in Python | |
21 | ========================================= |
|
21 | ========================================= | |
22 |
|
22 | |||
23 | A Python shell with automatic history (input and output), dynamic object |
|
23 | A Python shell with automatic history (input and output), dynamic object | |
24 | introspection, easier configuration, command completion, access to the |
|
24 | introspection, easier configuration, command completion, access to the | |
25 | system shell and more. IPython can also be embedded in running programs. |
|
25 | system shell and more. IPython can also be embedded in running programs. | |
26 |
|
26 | |||
27 |
|
27 | |||
28 | Usage |
|
28 | Usage | |
29 | ----- |
|
|||
30 |
|
29 | |||
31 | ipython [subcommand] [options] [files] |
|
30 | ipython [subcommand] [options] [files] | |
32 |
|
31 | |||
33 | If invoked with no options, it executes all the files listed in sequence |
|
32 | If invoked with no options, it executes all the files listed in sequence | |
34 | and exits, use -i to enter interactive mode after running the files. Files |
|
33 | and exits, use -i to enter interactive mode after running the files. Files | |
35 | ending in .py will be treated as normal Python, but files ending in .ipy |
|
34 | ending in .py will be treated as normal Python, but files ending in .ipy | |
36 | can contain special IPython syntax (magic commands, shell expansions, etc.) |
|
35 | can contain special IPython syntax (magic commands, shell expansions, etc.) | |
37 |
|
36 | |||
38 | Almost all configuration in IPython is available via the command-line. Do |
|
37 | Almost all configuration in IPython is available via the command-line. Do | |
39 | `ipython --help-all` to see all available options. For persistent |
|
38 | `ipython --help-all` to see all available options. For persistent | |
40 | configuration, look into your `ipython_config.py` configuration file for |
|
39 | configuration, look into your `ipython_config.py` configuration file for | |
41 | details. |
|
40 | details. | |
42 |
|
41 | |||
43 | This file is typically installed in the `IPYTHON_DIR` directory, and there |
|
42 | This file is typically installed in the `IPYTHON_DIR` directory, and there | |
44 | is a separate configuration directory for each profile. The default profile |
|
43 | is a separate configuration directory for each profile. The default profile | |
45 | directory will be located in $IPYTHON_DIR/profile_default. For Linux users, |
|
44 | directory will be located in $IPYTHON_DIR/profile_default. For Linux users, | |
46 | IPYTHON_DIR defaults to `$HOME/.config/ipython`, and for other Unix systems |
|
45 | IPYTHON_DIR defaults to `$HOME/.config/ipython`, and for other Unix systems | |
47 | to `$HOME/.ipython`. For Windows users, $HOME resolves to C:\\Documents |
|
46 | to `$HOME/.ipython`. For Windows users, $HOME resolves to C:\\Documents | |
48 | and Settings\\YourUserName in most instances. |
|
47 | and Settings\\YourUserName in most instances. | |
49 |
|
48 | |||
50 | To initialize a profile with the default configuration file, do:: |
|
49 | To initialize a profile with the default configuration file, do:: | |
51 |
|
50 | |||
52 | $> ipython profile create |
|
51 | $> ipython profile create | |
53 |
|
52 | |||
54 | and start editing `IPYTHON_DIR/profile_default/ipython_config.py` |
|
53 | and start editing `IPYTHON_DIR/profile_default/ipython_config.py` | |
55 |
|
54 | |||
56 | In IPython's documentation, we will refer to this directory as |
|
55 | In IPython's documentation, we will refer to this directory as | |
57 | `IPYTHON_DIR`, you can change its default location by creating an |
|
56 | `IPYTHON_DIR`, you can change its default location by creating an | |
58 | environment variable with this name and setting it to the desired path. |
|
57 | environment variable with this name and setting it to the desired path. | |
59 |
|
58 | |||
60 | For more information, see the manual available in HTML and PDF in your |
|
59 | For more information, see the manual available in HTML and PDF in your | |
61 | installation, or online at http://ipython.org/documentation.html. |
|
60 | installation, or online at http://ipython.org/documentation.html. | |
62 | """ |
|
61 | """ | |
63 |
|
62 | |||
64 | interactive_usage = """ |
|
63 | interactive_usage = """ | |
65 | IPython -- An enhanced Interactive Python |
|
64 | IPython -- An enhanced Interactive Python | |
66 | ========================================= |
|
65 | ========================================= | |
67 |
|
66 | |||
68 | IPython offers a combination of convenient shell features, special commands |
|
67 | IPython offers a combination of convenient shell features, special commands | |
69 | and a history mechanism for both input (command history) and output (results |
|
68 | and a history mechanism for both input (command history) and output (results | |
70 | caching, similar to Mathematica). It is intended to be a fully compatible |
|
69 | caching, similar to Mathematica). It is intended to be a fully compatible | |
71 | replacement for the standard Python interpreter, while offering vastly |
|
70 | replacement for the standard Python interpreter, while offering vastly | |
72 | improved functionality and flexibility. |
|
71 | improved functionality and flexibility. | |
73 |
|
72 | |||
74 | At your system command line, type 'ipython -h' to see the command line |
|
73 | At your system command line, type 'ipython -h' to see the command line | |
75 | options available. This document only describes interactive features. |
|
74 | options available. This document only describes interactive features. | |
76 |
|
75 | |||
77 | MAIN FEATURES |
|
76 | MAIN FEATURES | |
78 |
|
77 | |||
79 | * Access to the standard Python help. As of Python 2.1, a help system is |
|
78 | * Access to the standard Python help. As of Python 2.1, a help system is | |
80 | available with access to object docstrings and the Python manuals. Simply |
|
79 | available with access to object docstrings and the Python manuals. Simply | |
81 | type 'help' (no quotes) to access it. |
|
80 | type 'help' (no quotes) to access it. | |
82 |
|
81 | |||
83 | * Magic commands: type %magic for information on the magic subsystem. |
|
82 | * Magic commands: type %magic for information on the magic subsystem. | |
84 |
|
83 | |||
85 | * System command aliases, via the %alias command or the ipythonrc config file. |
|
84 | * System command aliases, via the %alias command or the ipythonrc config file. | |
86 |
|
85 | |||
87 | * Dynamic object information: |
|
86 | * Dynamic object information: | |
88 |
|
87 | |||
89 | Typing ?word or word? prints detailed information about an object. If |
|
88 | Typing ?word or word? prints detailed information about an object. If | |
90 | certain strings in the object are too long (docstrings, code, etc.) they get |
|
89 | certain strings in the object are too long (docstrings, code, etc.) they get | |
91 | snipped in the center for brevity. |
|
90 | snipped in the center for brevity. | |
92 |
|
91 | |||
93 | Typing ??word or word?? gives access to the full information without |
|
92 | Typing ??word or word?? gives access to the full information without | |
94 | snipping long strings. Long strings are sent to the screen through the less |
|
93 | snipping long strings. Long strings are sent to the screen through the less | |
95 | pager if longer than the screen, printed otherwise. |
|
94 | pager if longer than the screen, printed otherwise. | |
96 |
|
95 | |||
97 | The ?/?? system gives access to the full source code for any object (if |
|
96 | The ?/?? system gives access to the full source code for any object (if | |
98 | available), shows function prototypes and other useful information. |
|
97 | available), shows function prototypes and other useful information. | |
99 |
|
98 | |||
100 | If you just want to see an object's docstring, type '%pdoc object' (without |
|
99 | If you just want to see an object's docstring, type '%pdoc object' (without | |
101 | quotes, and without % if you have automagic on). |
|
100 | quotes, and without % if you have automagic on). | |
102 |
|
101 | |||
103 | Both %pdoc and ?/?? give you access to documentation even on things which are |
|
102 | Both %pdoc and ?/?? give you access to documentation even on things which are | |
104 | not explicitely defined. Try for example typing {}.get? or after import os, |
|
103 | not explicitely defined. Try for example typing {}.get? or after import os, | |
105 | type os.path.abspath??. The magic functions %pdef, %source and %file operate |
|
104 | type os.path.abspath??. The magic functions %pdef, %source and %file operate | |
106 | similarly. |
|
105 | similarly. | |
107 |
|
106 | |||
108 | * Completion in the local namespace, by typing TAB at the prompt. |
|
107 | * Completion in the local namespace, by typing TAB at the prompt. | |
109 |
|
108 | |||
110 | At any time, hitting tab will complete any available python commands or |
|
109 | At any time, hitting tab will complete any available python commands or | |
111 | variable names, and show you a list of the possible completions if there's |
|
110 | variable names, and show you a list of the possible completions if there's | |
112 | no unambiguous one. It will also complete filenames in the current directory. |
|
111 | no unambiguous one. It will also complete filenames in the current directory. | |
113 |
|
112 | |||
114 | This feature requires the readline and rlcomplete modules, so it won't work |
|
113 | This feature requires the readline and rlcomplete modules, so it won't work | |
115 | if your Python lacks readline support (such as under Windows). |
|
114 | if your Python lacks readline support (such as under Windows). | |
116 |
|
115 | |||
117 | * Search previous command history in two ways (also requires readline): |
|
116 | * Search previous command history in two ways (also requires readline): | |
118 |
|
117 | |||
119 | - Start typing, and then use Ctrl-p (previous,up) and Ctrl-n (next,down) to |
|
118 | - Start typing, and then use Ctrl-p (previous,up) and Ctrl-n (next,down) to | |
120 | search through only the history items that match what you've typed so |
|
119 | search through only the history items that match what you've typed so | |
121 | far. If you use Ctrl-p/Ctrl-n at a blank prompt, they just behave like |
|
120 | far. If you use Ctrl-p/Ctrl-n at a blank prompt, they just behave like | |
122 | normal arrow keys. |
|
121 | normal arrow keys. | |
123 |
|
122 | |||
124 | - Hit Ctrl-r: opens a search prompt. Begin typing and the system searches |
|
123 | - Hit Ctrl-r: opens a search prompt. Begin typing and the system searches | |
125 | your history for lines that match what you've typed so far, completing as |
|
124 | your history for lines that match what you've typed so far, completing as | |
126 | much as it can. |
|
125 | much as it can. | |
127 |
|
126 | |||
128 | - %hist: search history by index (this does *not* require readline). |
|
127 | - %hist: search history by index (this does *not* require readline). | |
129 |
|
128 | |||
130 | * Persistent command history across sessions. |
|
129 | * Persistent command history across sessions. | |
131 |
|
130 | |||
132 | * Logging of input with the ability to save and restore a working session. |
|
131 | * Logging of input with the ability to save and restore a working session. | |
133 |
|
132 | |||
134 | * System escape with !. Typing !ls will run 'ls' in the current directory. |
|
133 | * System escape with !. Typing !ls will run 'ls' in the current directory. | |
135 |
|
134 | |||
136 | * The reload command does a 'deep' reload of a module: changes made to the |
|
135 | * The reload command does a 'deep' reload of a module: changes made to the | |
137 | module since you imported will actually be available without having to exit. |
|
136 | module since you imported will actually be available without having to exit. | |
138 |
|
137 | |||
139 | * Verbose and colored exception traceback printouts. See the magic xmode and |
|
138 | * Verbose and colored exception traceback printouts. See the magic xmode and | |
140 | xcolor functions for details (just type %magic). |
|
139 | xcolor functions for details (just type %magic). | |
141 |
|
140 | |||
142 | * Input caching system: |
|
141 | * Input caching system: | |
143 |
|
142 | |||
144 | IPython offers numbered prompts (In/Out) with input and output caching. All |
|
143 | IPython offers numbered prompts (In/Out) with input and output caching. All | |
145 | input is saved and can be retrieved as variables (besides the usual arrow |
|
144 | input is saved and can be retrieved as variables (besides the usual arrow | |
146 | key recall). |
|
145 | key recall). | |
147 |
|
146 | |||
148 | The following GLOBAL variables always exist (so don't overwrite them!): |
|
147 | The following GLOBAL variables always exist (so don't overwrite them!): | |
149 | _i: stores previous input. |
|
148 | _i: stores previous input. | |
150 | _ii: next previous. |
|
149 | _ii: next previous. | |
151 | _iii: next-next previous. |
|
150 | _iii: next-next previous. | |
152 | _ih : a list of all input _ih[n] is the input from line n. |
|
151 | _ih : a list of all input _ih[n] is the input from line n. | |
153 |
|
152 | |||
154 | Additionally, global variables named _i<n> are dynamically created (<n> |
|
153 | Additionally, global variables named _i<n> are dynamically created (<n> | |
155 | being the prompt counter), such that _i<n> == _ih[<n>] |
|
154 | being the prompt counter), such that _i<n> == _ih[<n>] | |
156 |
|
155 | |||
157 | For example, what you typed at prompt 14 is available as _i14 and _ih[14]. |
|
156 | For example, what you typed at prompt 14 is available as _i14 and _ih[14]. | |
158 |
|
157 | |||
159 | You can create macros which contain multiple input lines from this history, |
|
158 | You can create macros which contain multiple input lines from this history, | |
160 | for later re-execution, with the %macro function. |
|
159 | for later re-execution, with the %macro function. | |
161 |
|
160 | |||
162 | The history function %hist allows you to see any part of your input history |
|
161 | The history function %hist allows you to see any part of your input history | |
163 | by printing a range of the _i variables. Note that inputs which contain |
|
162 | by printing a range of the _i variables. Note that inputs which contain | |
164 | magic functions (%) appear in the history with a prepended comment. This is |
|
163 | magic functions (%) appear in the history with a prepended comment. This is | |
165 | because they aren't really valid Python code, so you can't exec them. |
|
164 | because they aren't really valid Python code, so you can't exec them. | |
166 |
|
165 | |||
167 | * Output caching system: |
|
166 | * Output caching system: | |
168 |
|
167 | |||
169 | For output that is returned from actions, a system similar to the input |
|
168 | For output that is returned from actions, a system similar to the input | |
170 | cache exists but using _ instead of _i. Only actions that produce a result |
|
169 | cache exists but using _ instead of _i. Only actions that produce a result | |
171 | (NOT assignments, for example) are cached. If you are familiar with |
|
170 | (NOT assignments, for example) are cached. If you are familiar with | |
172 | Mathematica, IPython's _ variables behave exactly like Mathematica's % |
|
171 | Mathematica, IPython's _ variables behave exactly like Mathematica's % | |
173 | variables. |
|
172 | variables. | |
174 |
|
173 | |||
175 | The following GLOBAL variables always exist (so don't overwrite them!): |
|
174 | The following GLOBAL variables always exist (so don't overwrite them!): | |
176 | _ (one underscore): previous output. |
|
175 | _ (one underscore): previous output. | |
177 | __ (two underscores): next previous. |
|
176 | __ (two underscores): next previous. | |
178 | ___ (three underscores): next-next previous. |
|
177 | ___ (three underscores): next-next previous. | |
179 |
|
178 | |||
180 | Global variables named _<n> are dynamically created (<n> being the prompt |
|
179 | Global variables named _<n> are dynamically created (<n> being the prompt | |
181 | counter), such that the result of output <n> is always available as _<n>. |
|
180 | counter), such that the result of output <n> is always available as _<n>. | |
182 |
|
181 | |||
183 | Finally, a global dictionary named _oh exists with entries for all lines |
|
182 | Finally, a global dictionary named _oh exists with entries for all lines | |
184 | which generated output. |
|
183 | which generated output. | |
185 |
|
184 | |||
186 | * Directory history: |
|
185 | * Directory history: | |
187 |
|
186 | |||
188 | Your history of visited directories is kept in the global list _dh, and the |
|
187 | Your history of visited directories is kept in the global list _dh, and the | |
189 | magic %cd command can be used to go to any entry in that list. |
|
188 | magic %cd command can be used to go to any entry in that list. | |
190 |
|
189 | |||
191 | * Auto-parentheses and auto-quotes (adapted from Nathan Gray's LazyPython) |
|
190 | * Auto-parentheses and auto-quotes (adapted from Nathan Gray's LazyPython) | |
192 |
|
191 | |||
193 | 1. Auto-parentheses |
|
192 | 1. Auto-parentheses | |
194 | Callable objects (i.e. functions, methods, etc) can be invoked like |
|
193 | Callable objects (i.e. functions, methods, etc) can be invoked like | |
195 | this (notice the commas between the arguments): |
|
194 | this (notice the commas between the arguments): | |
196 | >>> callable_ob arg1, arg2, arg3 |
|
195 | >>> callable_ob arg1, arg2, arg3 | |
197 | and the input will be translated to this: |
|
196 | and the input will be translated to this: | |
198 | --> callable_ob(arg1, arg2, arg3) |
|
197 | --> callable_ob(arg1, arg2, arg3) | |
199 | You can force auto-parentheses by using '/' as the first character |
|
198 | You can force auto-parentheses by using '/' as the first character | |
200 | of a line. For example: |
|
199 | of a line. For example: | |
201 | >>> /globals # becomes 'globals()' |
|
200 | >>> /globals # becomes 'globals()' | |
202 | Note that the '/' MUST be the first character on the line! This |
|
201 | Note that the '/' MUST be the first character on the line! This | |
203 | won't work: |
|
202 | won't work: | |
204 | >>> print /globals # syntax error |
|
203 | >>> print /globals # syntax error | |
205 |
|
204 | |||
206 | In most cases the automatic algorithm should work, so you should |
|
205 | In most cases the automatic algorithm should work, so you should | |
207 | rarely need to explicitly invoke /. One notable exception is if you |
|
206 | rarely need to explicitly invoke /. One notable exception is if you | |
208 | are trying to call a function with a list of tuples as arguments (the |
|
207 | are trying to call a function with a list of tuples as arguments (the | |
209 | parenthesis will confuse IPython): |
|
208 | parenthesis will confuse IPython): | |
210 | In [1]: zip (1,2,3),(4,5,6) # won't work |
|
209 | In [1]: zip (1,2,3),(4,5,6) # won't work | |
211 | but this will work: |
|
210 | but this will work: | |
212 | In [2]: /zip (1,2,3),(4,5,6) |
|
211 | In [2]: /zip (1,2,3),(4,5,6) | |
213 | ------> zip ((1,2,3),(4,5,6)) |
|
212 | ------> zip ((1,2,3),(4,5,6)) | |
214 | Out[2]= [(1, 4), (2, 5), (3, 6)] |
|
213 | Out[2]= [(1, 4), (2, 5), (3, 6)] | |
215 |
|
214 | |||
216 | IPython tells you that it has altered your command line by |
|
215 | IPython tells you that it has altered your command line by | |
217 | displaying the new command line preceded by -->. e.g.: |
|
216 | displaying the new command line preceded by -->. e.g.: | |
218 | In [18]: callable list |
|
217 | In [18]: callable list | |
219 | -------> callable (list) |
|
218 | -------> callable (list) | |
220 |
|
219 | |||
221 | 2. Auto-Quoting |
|
220 | 2. Auto-Quoting | |
222 | You can force auto-quoting of a function's arguments by using ',' as |
|
221 | You can force auto-quoting of a function's arguments by using ',' as | |
223 | the first character of a line. For example: |
|
222 | the first character of a line. For example: | |
224 | >>> ,my_function /home/me # becomes my_function("/home/me") |
|
223 | >>> ,my_function /home/me # becomes my_function("/home/me") | |
225 |
|
224 | |||
226 | If you use ';' instead, the whole argument is quoted as a single |
|
225 | If you use ';' instead, the whole argument is quoted as a single | |
227 | string (while ',' splits on whitespace): |
|
226 | string (while ',' splits on whitespace): | |
228 | >>> ,my_function a b c # becomes my_function("a","b","c") |
|
227 | >>> ,my_function a b c # becomes my_function("a","b","c") | |
229 | >>> ;my_function a b c # becomes my_function("a b c") |
|
228 | >>> ;my_function a b c # becomes my_function("a b c") | |
230 |
|
229 | |||
231 | Note that the ',' MUST be the first character on the line! This |
|
230 | Note that the ',' MUST be the first character on the line! This | |
232 | won't work: |
|
231 | won't work: | |
233 | >>> x = ,my_function /home/me # syntax error |
|
232 | >>> x = ,my_function /home/me # syntax error | |
234 | """ |
|
233 | """ | |
235 |
|
234 | |||
236 | interactive_usage_min = """\ |
|
235 | interactive_usage_min = """\ | |
237 | An enhanced console for Python. |
|
236 | An enhanced console for Python. | |
238 | Some of its features are: |
|
237 | Some of its features are: | |
239 | - Readline support if the readline library is present. |
|
238 | - Readline support if the readline library is present. | |
240 | - Tab completion in the local namespace. |
|
239 | - Tab completion in the local namespace. | |
241 | - Logging of input, see command-line options. |
|
240 | - Logging of input, see command-line options. | |
242 | - System shell escape via ! , eg !ls. |
|
241 | - System shell escape via ! , eg !ls. | |
243 | - Magic commands, starting with a % (like %ls, %pwd, %cd, etc.) |
|
242 | - Magic commands, starting with a % (like %ls, %pwd, %cd, etc.) | |
244 | - Keeps track of locally defined variables via %who, %whos. |
|
243 | - Keeps track of locally defined variables via %who, %whos. | |
245 | - Show object information with a ? eg ?x or x? (use ?? for more info). |
|
244 | - Show object information with a ? eg ?x or x? (use ?? for more info). | |
246 | """ |
|
245 | """ | |
247 |
|
246 | |||
248 | quick_reference = r""" |
|
247 | quick_reference = r""" | |
249 | IPython -- An enhanced Interactive Python - Quick Reference Card |
|
248 | IPython -- An enhanced Interactive Python - Quick Reference Card | |
250 | ================================================================ |
|
249 | ================================================================ | |
251 |
|
250 | |||
252 | obj?, obj?? : Get help, or more help for object (also works as |
|
251 | obj?, obj?? : Get help, or more help for object (also works as | |
253 | ?obj, ??obj). |
|
252 | ?obj, ??obj). | |
254 | ?foo.*abc* : List names in 'foo' containing 'abc' in them. |
|
253 | ?foo.*abc* : List names in 'foo' containing 'abc' in them. | |
255 | %magic : Information about IPython's 'magic' % functions. |
|
254 | %magic : Information about IPython's 'magic' % functions. | |
256 |
|
255 | |||
257 | Magic functions are prefixed by %, and typically take their arguments without |
|
256 | Magic functions are prefixed by %, and typically take their arguments without | |
258 | parentheses, quotes or even commas for convenience. |
|
257 | parentheses, quotes or even commas for convenience. | |
259 |
|
258 | |||
260 | Example magic function calls: |
|
259 | Example magic function calls: | |
261 |
|
260 | |||
262 | %alias d ls -F : 'd' is now an alias for 'ls -F' |
|
261 | %alias d ls -F : 'd' is now an alias for 'ls -F' | |
263 | alias d ls -F : Works if 'alias' not a python name |
|
262 | alias d ls -F : Works if 'alias' not a python name | |
264 | alist = %alias : Get list of aliases to 'alist' |
|
263 | alist = %alias : Get list of aliases to 'alist' | |
265 | cd /usr/share : Obvious. cd -<tab> to choose from visited dirs. |
|
264 | cd /usr/share : Obvious. cd -<tab> to choose from visited dirs. | |
266 | %cd?? : See help AND source for magic %cd |
|
265 | %cd?? : See help AND source for magic %cd | |
267 |
|
266 | |||
268 | System commands: |
|
267 | System commands: | |
269 |
|
268 | |||
270 | !cp a.txt b/ : System command escape, calls os.system() |
|
269 | !cp a.txt b/ : System command escape, calls os.system() | |
271 | cp a.txt b/ : after %rehashx, most system commands work without ! |
|
270 | cp a.txt b/ : after %rehashx, most system commands work without ! | |
272 | cp ${f}.txt $bar : Variable expansion in magics and system commands |
|
271 | cp ${f}.txt $bar : Variable expansion in magics and system commands | |
273 | files = !ls /usr : Capture sytem command output |
|
272 | files = !ls /usr : Capture sytem command output | |
274 | files.s, files.l, files.n: "a b c", ['a','b','c'], 'a\nb\nc' |
|
273 | files.s, files.l, files.n: "a b c", ['a','b','c'], 'a\nb\nc' | |
275 |
|
274 | |||
276 | History: |
|
275 | History: | |
277 |
|
276 | |||
278 | _i, _ii, _iii : Previous, next previous, next next previous input |
|
277 | _i, _ii, _iii : Previous, next previous, next next previous input | |
279 | _i4, _ih[2:5] : Input history line 4, lines 2-4 |
|
278 | _i4, _ih[2:5] : Input history line 4, lines 2-4 | |
280 | exec _i81 : Execute input history line #81 again |
|
279 | exec _i81 : Execute input history line #81 again | |
281 | %rep 81 : Edit input history line #81 |
|
280 | %rep 81 : Edit input history line #81 | |
282 | _, __, ___ : previous, next previous, next next previous output |
|
281 | _, __, ___ : previous, next previous, next next previous output | |
283 | _dh : Directory history |
|
282 | _dh : Directory history | |
284 | _oh : Output history |
|
283 | _oh : Output history | |
285 | %hist : Command history. '%hist -g foo' search history for 'foo' |
|
284 | %hist : Command history. '%hist -g foo' search history for 'foo' | |
286 |
|
285 | |||
287 | Autocall: |
|
286 | Autocall: | |
288 |
|
287 | |||
289 | f 1,2 : f(1,2) |
|
288 | f 1,2 : f(1,2) | |
290 | /f 1,2 : f(1,2) (forced autoparen) |
|
289 | /f 1,2 : f(1,2) (forced autoparen) | |
291 | ,f 1 2 : f("1","2") |
|
290 | ,f 1 2 : f("1","2") | |
292 | ;f 1 2 : f("1 2") |
|
291 | ;f 1 2 : f("1 2") | |
293 |
|
292 | |||
294 | Remember: TAB completion works in many contexts, not just file names |
|
293 | Remember: TAB completion works in many contexts, not just file names | |
295 | or python names. |
|
294 | or python names. | |
296 |
|
295 | |||
297 | The following magic functions are currently available: |
|
296 | The following magic functions are currently available: | |
298 |
|
297 | |||
299 | """ |
|
298 | """ | |
300 |
|
299 | |||
301 | gui_reference = """\ |
|
300 | gui_reference = """\ | |
302 | =============================== |
|
301 | =============================== | |
303 | The graphical IPython console |
|
302 | The graphical IPython console | |
304 | =============================== |
|
303 | =============================== | |
305 |
|
304 | |||
306 | This console is designed to emulate the look, feel and workflow of a terminal |
|
305 | This console is designed to emulate the look, feel and workflow of a terminal | |
307 | environment, while adding a number of enhancements that are simply not possible |
|
306 | environment, while adding a number of enhancements that are simply not possible | |
308 | in a real terminal, such as inline syntax highlighting, true multiline editing, |
|
307 | in a real terminal, such as inline syntax highlighting, true multiline editing, | |
309 | inline graphics and much more. |
|
308 | inline graphics and much more. | |
310 |
|
309 | |||
311 | This quick reference document contains the basic information you'll need to |
|
310 | This quick reference document contains the basic information you'll need to | |
312 | know to make the most efficient use of it. For the various command line |
|
311 | know to make the most efficient use of it. For the various command line | |
313 | options available at startup, type ``ipython qtconsole --help`` at the command line. |
|
312 | options available at startup, type ``ipython qtconsole --help`` at the command line. | |
314 |
|
313 | |||
315 |
|
314 | |||
316 | Multiline editing |
|
315 | Multiline editing | |
317 | ================= |
|
316 | ================= | |
318 |
|
317 | |||
319 | The graphical console is capable of true multiline editing, but it also tries |
|
318 | The graphical console is capable of true multiline editing, but it also tries | |
320 | to behave intuitively like a terminal when possible. If you are used to |
|
319 | to behave intuitively like a terminal when possible. If you are used to | |
321 | IPyhton's old terminal behavior, you should find the transition painless, and |
|
320 | IPyhton's old terminal behavior, you should find the transition painless, and | |
322 | once you learn a few basic keybindings it will be a much more efficient |
|
321 | once you learn a few basic keybindings it will be a much more efficient | |
323 | environment. |
|
322 | environment. | |
324 |
|
323 | |||
325 | For single expressions or indented blocks, the console behaves almost like the |
|
324 | For single expressions or indented blocks, the console behaves almost like the | |
326 | terminal IPython: single expressions are immediately evaluated, and indented |
|
325 | terminal IPython: single expressions are immediately evaluated, and indented | |
327 | blocks are evaluated once a single blank line is entered:: |
|
326 | blocks are evaluated once a single blank line is entered:: | |
328 |
|
327 | |||
329 | In [1]: print "Hello IPython!" # Enter was pressed at the end of the line |
|
328 | In [1]: print "Hello IPython!" # Enter was pressed at the end of the line | |
330 | Hello IPython! |
|
329 | Hello IPython! | |
331 |
|
330 | |||
332 | In [2]: for i in range(10): |
|
331 | In [2]: for i in range(10): | |
333 | ...: print i, |
|
332 | ...: print i, | |
334 | ...: |
|
333 | ...: | |
335 | 0 1 2 3 4 5 6 7 8 9 |
|
334 | 0 1 2 3 4 5 6 7 8 9 | |
336 |
|
335 | |||
337 | If you want to enter more than one expression in a single input block |
|
336 | If you want to enter more than one expression in a single input block | |
338 | (something not possible in the terminal), you can use ``Control-Enter`` at the |
|
337 | (something not possible in the terminal), you can use ``Control-Enter`` at the | |
339 | end of your first line instead of ``Enter``. At that point the console goes |
|
338 | end of your first line instead of ``Enter``. At that point the console goes | |
340 | into 'cell mode' and even if your inputs are not indented, it will continue |
|
339 | into 'cell mode' and even if your inputs are not indented, it will continue | |
341 | accepting arbitrarily many lines until either you enter an extra blank line or |
|
340 | accepting arbitrarily many lines until either you enter an extra blank line or | |
342 | you hit ``Shift-Enter`` (the key binding that forces execution). When a |
|
341 | you hit ``Shift-Enter`` (the key binding that forces execution). When a | |
343 | multiline cell is entered, IPython analyzes it and executes its code producing |
|
342 | multiline cell is entered, IPython analyzes it and executes its code producing | |
344 | an ``Out[n]`` prompt only for the last expression in it, while the rest of the |
|
343 | an ``Out[n]`` prompt only for the last expression in it, while the rest of the | |
345 | cell is executed as if it was a script. An example should clarify this:: |
|
344 | cell is executed as if it was a script. An example should clarify this:: | |
346 |
|
345 | |||
347 | In [3]: x=1 # Hit C-Enter here |
|
346 | In [3]: x=1 # Hit C-Enter here | |
348 | ...: y=2 # from now on, regular Enter is sufficient |
|
347 | ...: y=2 # from now on, regular Enter is sufficient | |
349 | ...: z=3 |
|
348 | ...: z=3 | |
350 | ...: x**2 # This does *not* produce an Out[] value |
|
349 | ...: x**2 # This does *not* produce an Out[] value | |
351 | ...: x+y+z # Only the last expression does |
|
350 | ...: x+y+z # Only the last expression does | |
352 | ...: |
|
351 | ...: | |
353 | Out[3]: 6 |
|
352 | Out[3]: 6 | |
354 |
|
353 | |||
355 | The behavior where an extra blank line forces execution is only active if you |
|
354 | The behavior where an extra blank line forces execution is only active if you | |
356 | are actually typing at the keyboard each line, and is meant to make it mimic |
|
355 | are actually typing at the keyboard each line, and is meant to make it mimic | |
357 | the IPython terminal behavior. If you paste a long chunk of input (for example |
|
356 | the IPython terminal behavior. If you paste a long chunk of input (for example | |
358 | a long script copied form an editor or web browser), it can contain arbitrarily |
|
357 | a long script copied form an editor or web browser), it can contain arbitrarily | |
359 | many intermediate blank lines and they won't cause any problems. As always, |
|
358 | many intermediate blank lines and they won't cause any problems. As always, | |
360 | you can then make it execute by appending a blank line *at the end* or hitting |
|
359 | you can then make it execute by appending a blank line *at the end* or hitting | |
361 | ``Shift-Enter`` anywhere within the cell. |
|
360 | ``Shift-Enter`` anywhere within the cell. | |
362 |
|
361 | |||
363 | With the up arrow key, you can retrieve previous blocks of input that contain |
|
362 | With the up arrow key, you can retrieve previous blocks of input that contain | |
364 | multiple lines. You can move inside of a multiline cell like you would in any |
|
363 | multiple lines. You can move inside of a multiline cell like you would in any | |
365 | text editor. When you want it executed, the simplest thing to do is to hit the |
|
364 | text editor. When you want it executed, the simplest thing to do is to hit the | |
366 | force execution key, ``Shift-Enter`` (though you can also navigate to the end |
|
365 | force execution key, ``Shift-Enter`` (though you can also navigate to the end | |
367 | and append a blank line by using ``Enter`` twice). |
|
366 | and append a blank line by using ``Enter`` twice). | |
368 |
|
367 | |||
369 | If you've edited a multiline cell and accidentally navigate out of it with the |
|
368 | If you've edited a multiline cell and accidentally navigate out of it with the | |
370 | up or down arrow keys, IPython will clear the cell and replace it with the |
|
369 | up or down arrow keys, IPython will clear the cell and replace it with the | |
371 | contents of the one above or below that you navigated to. If this was an |
|
370 | contents of the one above or below that you navigated to. If this was an | |
372 | accident and you want to retrieve the cell you were editing, use the Undo |
|
371 | accident and you want to retrieve the cell you were editing, use the Undo | |
373 | keybinding, ``Control-z``. |
|
372 | keybinding, ``Control-z``. | |
374 |
|
373 | |||
375 |
|
374 | |||
376 | Key bindings |
|
375 | Key bindings | |
377 | ============ |
|
376 | ============ | |
378 |
|
377 | |||
379 | The IPython console supports most of the basic Emacs line-oriented keybindings, |
|
378 | The IPython console supports most of the basic Emacs line-oriented keybindings, | |
380 | in addition to some of its own. |
|
379 | in addition to some of its own. | |
381 |
|
380 | |||
382 | The keybinding prefixes mean: |
|
381 | The keybinding prefixes mean: | |
383 |
|
382 | |||
384 | - ``C``: Control |
|
383 | - ``C``: Control | |
385 | - ``S``: Shift |
|
384 | - ``S``: Shift | |
386 | - ``M``: Meta (typically the Alt key) |
|
385 | - ``M``: Meta (typically the Alt key) | |
387 |
|
386 | |||
388 | The keybindings themselves are: |
|
387 | The keybindings themselves are: | |
389 |
|
388 | |||
390 | - ``Enter``: insert new line (may cause execution, see above). |
|
389 | - ``Enter``: insert new line (may cause execution, see above). | |
391 | - ``C-Enter``: force new line, *never* causes execution. |
|
390 | - ``C-Enter``: force new line, *never* causes execution. | |
392 | - ``S-Enter``: *force* execution regardless of where cursor is, no newline added. |
|
391 | - ``S-Enter``: *force* execution regardless of where cursor is, no newline added. | |
393 | - ``C-c``: copy highlighted text to clipboard (prompts are automatically stripped). |
|
392 | - ``C-c``: copy highlighted text to clipboard (prompts are automatically stripped). | |
394 | - ``C-S-c``: copy highlighted text to clipboard (prompts are not stripped). |
|
393 | - ``C-S-c``: copy highlighted text to clipboard (prompts are not stripped). | |
395 | - ``C-v``: paste text from clipboard. |
|
394 | - ``C-v``: paste text from clipboard. | |
396 | - ``C-z``: undo (retrieves lost text if you move out of a cell with the arrows). |
|
395 | - ``C-z``: undo (retrieves lost text if you move out of a cell with the arrows). | |
397 | - ``C-S-z``: redo. |
|
396 | - ``C-S-z``: redo. | |
398 | - ``C-o``: move to 'other' area, between pager and terminal. |
|
397 | - ``C-o``: move to 'other' area, between pager and terminal. | |
399 | - ``C-l``: clear terminal. |
|
398 | - ``C-l``: clear terminal. | |
400 | - ``C-a``: go to beginning of line. |
|
399 | - ``C-a``: go to beginning of line. | |
401 | - ``C-e``: go to end of line. |
|
400 | - ``C-e``: go to end of line. | |
402 | - ``C-k``: kill from cursor to the end of the line. |
|
401 | - ``C-k``: kill from cursor to the end of the line. | |
403 | - ``C-y``: yank (paste) |
|
402 | - ``C-y``: yank (paste) | |
404 | - ``C-p``: previous line (like up arrow) |
|
403 | - ``C-p``: previous line (like up arrow) | |
405 | - ``C-n``: next line (like down arrow) |
|
404 | - ``C-n``: next line (like down arrow) | |
406 | - ``C-f``: forward (like right arrow) |
|
405 | - ``C-f``: forward (like right arrow) | |
407 | - ``C-b``: back (like left arrow) |
|
406 | - ``C-b``: back (like left arrow) | |
408 | - ``C-d``: delete next character. |
|
407 | - ``C-d``: delete next character. | |
409 | - ``M-<``: move to the beginning of the input region. |
|
408 | - ``M-<``: move to the beginning of the input region. | |
410 | - ``M->``: move to the end of the input region. |
|
409 | - ``M->``: move to the end of the input region. | |
411 | - ``M-d``: delete next word. |
|
410 | - ``M-d``: delete next word. | |
412 | - ``M-Backspace``: delete previous word. |
|
411 | - ``M-Backspace``: delete previous word. | |
413 | - ``C-.``: force a kernel restart (a confirmation dialog appears). |
|
412 | - ``C-.``: force a kernel restart (a confirmation dialog appears). | |
414 | - ``C-+``: increase font size. |
|
413 | - ``C-+``: increase font size. | |
415 | - ``C--``: decrease font size. |
|
414 | - ``C--``: decrease font size. | |
416 |
|
415 | |||
417 | The IPython pager |
|
416 | The IPython pager | |
418 | ================= |
|
417 | ================= | |
419 |
|
418 | |||
420 | IPython will show long blocks of text from many sources using a builtin pager. |
|
419 | IPython will show long blocks of text from many sources using a builtin pager. | |
421 | You can control where this pager appears with the ``--paging`` command-line |
|
420 | You can control where this pager appears with the ``--paging`` command-line | |
422 | flag: |
|
421 | flag: | |
423 |
|
422 | |||
424 | - ``inside`` [default]: the pager is overlaid on top of the main terminal. You |
|
423 | - ``inside`` [default]: the pager is overlaid on top of the main terminal. You | |
425 | must quit the pager to get back to the terminal (similar to how a pager such |
|
424 | must quit the pager to get back to the terminal (similar to how a pager such | |
426 | as ``less`` or ``more`` works). |
|
425 | as ``less`` or ``more`` works). | |
427 |
|
426 | |||
428 | - ``vsplit``: the console is made double-tall, and the pager appears on the |
|
427 | - ``vsplit``: the console is made double-tall, and the pager appears on the | |
429 | bottom area when needed. You can view its contents while using the terminal. |
|
428 | bottom area when needed. You can view its contents while using the terminal. | |
430 |
|
429 | |||
431 | - ``hsplit``: the console is made double-wide, and the pager appears on the |
|
430 | - ``hsplit``: the console is made double-wide, and the pager appears on the | |
432 | right area when needed. You can view its contents while using the terminal. |
|
431 | right area when needed. You can view its contents while using the terminal. | |
433 |
|
432 | |||
434 | - ``none``: the console never pages output. |
|
433 | - ``none``: the console never pages output. | |
435 |
|
434 | |||
436 | If you use the vertical or horizontal paging modes, you can navigate between |
|
435 | If you use the vertical or horizontal paging modes, you can navigate between | |
437 | terminal and pager as follows: |
|
436 | terminal and pager as follows: | |
438 |
|
437 | |||
439 | - Tab key: goes from pager to terminal (but not the other way around). |
|
438 | - Tab key: goes from pager to terminal (but not the other way around). | |
440 | - Control-o: goes from one to another always. |
|
439 | - Control-o: goes from one to another always. | |
441 | - Mouse: click on either. |
|
440 | - Mouse: click on either. | |
442 |
|
441 | |||
443 | In all cases, the ``q`` or ``Escape`` keys quit the pager (when used with the |
|
442 | In all cases, the ``q`` or ``Escape`` keys quit the pager (when used with the | |
444 | focus on the pager area). |
|
443 | focus on the pager area). | |
445 |
|
444 | |||
446 | Running subprocesses |
|
445 | Running subprocesses | |
447 | ==================== |
|
446 | ==================== | |
448 |
|
447 | |||
449 | The graphical IPython console uses the ``pexpect`` module to run subprocesses |
|
448 | The graphical IPython console uses the ``pexpect`` module to run subprocesses | |
450 | when you type ``!command``. This has a number of advantages (true asynchronous |
|
449 | when you type ``!command``. This has a number of advantages (true asynchronous | |
451 | output from subprocesses as well as very robust termination of rogue |
|
450 | output from subprocesses as well as very robust termination of rogue | |
452 | subprocesses with ``Control-C``), as well as some limitations. The main |
|
451 | subprocesses with ``Control-C``), as well as some limitations. The main | |
453 | limitation is that you can *not* interact back with the subprocess, so anything |
|
452 | limitation is that you can *not* interact back with the subprocess, so anything | |
454 | that invokes a pager or expects you to type input into it will block and hang |
|
453 | that invokes a pager or expects you to type input into it will block and hang | |
455 | (you can kill it with ``Control-C``). |
|
454 | (you can kill it with ``Control-C``). | |
456 |
|
455 | |||
457 | We have provided as magics ``%less`` to page files (aliased to ``%more``), |
|
456 | We have provided as magics ``%less`` to page files (aliased to ``%more``), | |
458 | ``%clear`` to clear the terminal, and ``%man`` on Linux/OSX. These cover the |
|
457 | ``%clear`` to clear the terminal, and ``%man`` on Linux/OSX. These cover the | |
459 | most common commands you'd want to call in your subshell and that would cause |
|
458 | most common commands you'd want to call in your subshell and that would cause | |
460 | problems if invoked via ``!cmd``, but you need to be aware of this limitation. |
|
459 | problems if invoked via ``!cmd``, but you need to be aware of this limitation. | |
461 |
|
460 | |||
462 | Display |
|
461 | Display | |
463 | ======= |
|
462 | ======= | |
464 |
|
463 | |||
465 | The IPython console can now display objects in a variety of formats, including |
|
464 | The IPython console can now display objects in a variety of formats, including | |
466 | HTML, PNG and SVG. This is accomplished using the display functions in |
|
465 | HTML, PNG and SVG. This is accomplished using the display functions in | |
467 | ``IPython.core.display``:: |
|
466 | ``IPython.core.display``:: | |
468 |
|
467 | |||
469 | In [4]: from IPython.core.display import display, display_html |
|
468 | In [4]: from IPython.core.display import display, display_html | |
470 |
|
469 | |||
471 | In [5]: from IPython.core.display import display_png, display_svg |
|
470 | In [5]: from IPython.core.display import display_png, display_svg | |
472 |
|
471 | |||
473 | Python objects can simply be passed to these functions and the appropriate |
|
472 | Python objects can simply be passed to these functions and the appropriate | |
474 | representations will be displayed in the console as long as the objects know |
|
473 | representations will be displayed in the console as long as the objects know | |
475 | how to compute those representations. The easiest way of teaching objects how |
|
474 | how to compute those representations. The easiest way of teaching objects how | |
476 | to format themselves in various representations is to define special methods |
|
475 | to format themselves in various representations is to define special methods | |
477 | such as: ``_repr_html_``, ``_repr_svg_`` and ``_repr_png_``. IPython's display formatters |
|
476 | such as: ``_repr_html_``, ``_repr_svg_`` and ``_repr_png_``. IPython's display formatters | |
478 | can also be given custom formatter functions for various types:: |
|
477 | can also be given custom formatter functions for various types:: | |
479 |
|
478 | |||
480 | In [6]: ip = get_ipython() |
|
479 | In [6]: ip = get_ipython() | |
481 |
|
480 | |||
482 | In [7]: html_formatter = ip.display_formatter.formatters['text/html'] |
|
481 | In [7]: html_formatter = ip.display_formatter.formatters['text/html'] | |
483 |
|
482 | |||
484 | In [8]: html_formatter.for_type(Foo, foo_to_html) |
|
483 | In [8]: html_formatter.for_type(Foo, foo_to_html) | |
485 |
|
484 | |||
486 | For further details, see ``IPython.core.formatters``. |
|
485 | For further details, see ``IPython.core.formatters``. | |
487 |
|
486 | |||
488 | Inline matplotlib graphics |
|
487 | Inline matplotlib graphics | |
489 | ========================== |
|
488 | ========================== | |
490 |
|
489 | |||
491 | The IPython console is capable of displaying matplotlib figures inline, in SVG |
|
490 | The IPython console is capable of displaying matplotlib figures inline, in SVG | |
492 | or PNG format. If started with the ``pylab=inline``, then all figures are |
|
491 | or PNG format. If started with the ``pylab=inline``, then all figures are | |
493 | rendered inline automatically (PNG by default). If started with ``--pylab`` |
|
492 | rendered inline automatically (PNG by default). If started with ``--pylab`` | |
494 | or ``pylab=<your backend>``, then a GUI backend will be used, but IPython's |
|
493 | or ``pylab=<your backend>``, then a GUI backend will be used, but IPython's | |
495 | ``display()`` and ``getfigs()`` functions can be used to view plots inline:: |
|
494 | ``display()`` and ``getfigs()`` functions can be used to view plots inline:: | |
496 |
|
495 | |||
497 | In [9]: display(*getfigs()) # display all figures inline |
|
496 | In [9]: display(*getfigs()) # display all figures inline | |
498 |
|
497 | |||
499 | In[10]: display(*getfigs(1,2)) # display figures 1 and 2 inline |
|
498 | In[10]: display(*getfigs(1,2)) # display figures 1 and 2 inline | |
500 | """ |
|
499 | """ | |
501 |
|
500 | |||
502 |
|
501 | |||
503 | quick_guide = """\ |
|
502 | quick_guide = """\ | |
504 | ? -> Introduction and overview of IPython's features. |
|
503 | ? -> Introduction and overview of IPython's features. | |
505 | %quickref -> Quick reference. |
|
504 | %quickref -> Quick reference. | |
506 | help -> Python's own help system. |
|
505 | help -> Python's own help system. | |
507 | object? -> Details about 'object', use 'object??' for extra details. |
|
506 | object? -> Details about 'object', use 'object??' for extra details. | |
508 | """ |
|
507 | """ | |
509 |
|
508 | |||
510 | gui_note = """\ |
|
509 | gui_note = """\ | |
511 | %guiref -> A brief reference about the graphical user interface. |
|
510 | %guiref -> A brief reference about the graphical user interface. | |
512 | """ |
|
511 | """ | |
513 |
|
512 | |||
514 | default_banner_parts = [ |
|
513 | default_banner_parts = [ | |
515 | 'Python %s\n' % (sys.version.split('\n')[0],), |
|
514 | 'Python %s\n' % (sys.version.split('\n')[0],), | |
516 | 'Type "copyright", "credits" or "license" for more information.\n\n', |
|
515 | 'Type "copyright", "credits" or "license" for more information.\n\n', | |
517 | 'IPython %s -- An enhanced Interactive Python.\n' % (release.version,), |
|
516 | 'IPython %s -- An enhanced Interactive Python.\n' % (release.version,), | |
518 | quick_guide |
|
517 | quick_guide | |
519 | ] |
|
518 | ] | |
520 |
|
519 | |||
521 | default_gui_banner_parts = default_banner_parts + [gui_note] |
|
520 | default_gui_banner_parts = default_banner_parts + [gui_note] | |
522 |
|
521 | |||
523 | default_banner = ''.join(default_banner_parts) |
|
522 | default_banner = ''.join(default_banner_parts) | |
524 |
|
523 | |||
525 | default_gui_banner = ''.join(default_gui_banner_parts) |
|
524 | default_gui_banner = ''.join(default_gui_banner_parts) |
General Comments 0
You need to be logged in to leave comments.
Login now