Show More
@@ -0,0 +1,48 b'' | |||
|
1 | .TH IPCLUSTER 1 "October 28, 2008" "" "" | |
|
2 | .SH NAME | |
|
3 | \fBipcluster \- IPython parallel computing cluster control tool | |
|
4 | .SH SYNOPSIS | |
|
5 | .nf | |
|
6 | .fam C | |
|
7 | \fBipcluster\fP {\fmpiexec,local,mpirun,pbs,ssh\fP} [\fIoptions\fP] | |
|
8 | .fam T | |
|
9 | .fi | |
|
10 | .SH DESCRIPTION | |
|
11 | ipcluster is a control tool for IPython's parallel computing functions. | |
|
12 | ||
|
13 | IPython cluster startup. This starts a controller and engines using various | |
|
14 | approaches. Use the IPYTHONDIR environment variable to change your IPython | |
|
15 | directory from the default of .ipython or _ipython. The log and security | |
|
16 | subdirectories of your IPython directory will be used by this script for log | |
|
17 | files and security files. | |
|
18 | .SH POSITIONAL ARGUMENTS | |
|
19 | ||
|
20 | The first positional argument should be one of: {mpiexec, local, mpirun, pbs, | |
|
21 | ssh}, which are the available cluster types. | |
|
22 | ||
|
23 | For detailed help on each, type "ipcluster TYPE --help". Briefly: | |
|
24 | ||
|
25 | local run a local cluster | |
|
26 | mpirun run a cluster using mpirun (mpiexec also works) | |
|
27 | mpiexec run a cluster using mpiexec (mpirun also works) | |
|
28 | pbs run a pbs cluster | |
|
29 | ssh run a cluster using ssh, should have ssh-keys setup | |
|
30 | .SH OPTIONS | |
|
31 | .TP | |
|
32 | .B | |
|
33 | \-h, \-\-help | |
|
34 | show help message and exit | |
|
35 | .SH EXAMPLE | |
|
36 | ipcluster local -n 4 | |
|
37 | ||
|
38 | This command will start 4 IPython engines on the local computer. | |
|
39 | .SH SEE ALSO | |
|
40 | .BR ipython(1), ipcontroller(1), ipengine(1) | |
|
41 | .br | |
|
42 | .SH AUTHOR | |
|
43 | \fBipcluster\fP is a tool that ships with IPython, created by | |
|
44 | the IPython Development Team. | |
|
45 | .PP | |
|
46 | This manual page was written by Stephan Peijnik <debian@sp.or.at>, | |
|
47 | for the Debian project (but may be used by others). Modified by Fernando Perez | |
|
48 | <Fernando.Perez@berkeley.edu> for inclusion in IPython. |
@@ -0,0 +1,87 b'' | |||
|
1 | .TH IPCONTROLLER 1 "October 29, 2008" "" "" | |
|
2 | .SH NAME | |
|
3 | \fBipcontroller \- IPython parallel computing controller control tool | |
|
4 | .SH SYNOPSIS | |
|
5 | .nf | |
|
6 | .fam C | |
|
7 | \fBipengine\fP [\fIoptions\fP] | |
|
8 | .fam T | |
|
9 | .fi | |
|
10 | .SH DESCRIPTION | |
|
11 | ipcontroller is a control tool for IPython's parallel computing functions. | |
|
12 | .SH OPTIONS | |
|
13 | .TP | |
|
14 | .B | |
|
15 | \-h, \-\-help | |
|
16 | show this help message and exit | |
|
17 | .TP | |
|
18 | .B | |
|
19 | \-\-client\-ip=CLIENT_IP | |
|
20 | the IP address or hostname the controller will listen on for | |
|
21 | client connections | |
|
22 | .TP | |
|
23 | .B | |
|
24 | \-\-client\-port=CLIENT_PORT | |
|
25 | the port the controller will listen on for client connections | |
|
26 | .TP | |
|
27 | .B | |
|
28 | \-\-client\-location=CLIENT_LOCATION | |
|
29 | hostname or ip for clients to connect to | |
|
30 | .TP | |
|
31 | .B | |
|
32 | \-x | |
|
33 | turn off all client security | |
|
34 | .TP | |
|
35 | .B | |
|
36 | \-\-client\-cert\-file=CLIENT_CERT_FILE | |
|
37 | file to store the client SSL certificate | |
|
38 | .TP | |
|
39 | .B | |
|
40 | \-\-task\-furl\-file=TASK_FURL_FILE | |
|
41 | file to store the FURL for task clients to connect with | |
|
42 | .TP | |
|
43 | .B | |
|
44 | \-\-multiengine\-furl\-file=MULTIENGINE_FURL_FILE | |
|
45 | file to store the FURL for multiengine clients to connect with | |
|
46 | .TP | |
|
47 | .B | |
|
48 | \-\-engine\-ip=ENGINE_IP | |
|
49 | the IP address or hostname the controller will listen on for engine connections | |
|
50 | .TP | |
|
51 | .B | |
|
52 | \-\-engine\-port=ENGINE_PORT | |
|
53 | the port the controller will listen on for engine connections | |
|
54 | .TP | |
|
55 | .B | |
|
56 | \-\-engine\-location=ENGINE_LOCATION | |
|
57 | the IP address or hostname for engine to connect to | |
|
58 | .TP | |
|
59 | .B | |
|
60 | \-y | |
|
61 | turn off all engine security | |
|
62 | .TP | |
|
63 | .B | |
|
64 | \-\-engine\-cert\-file=ENGINE_CERT_FILE | |
|
65 | file to store the engine SSL certificate | |
|
66 | .TP | |
|
67 | .B | |
|
68 | \-\-engine\-furl\-file=ENGINE_FURL_FILE | |
|
69 | file to store the FURL for engines to connect with | |
|
70 | .TP | |
|
71 | .B | |
|
72 | \-l LOGFILE, \-\-logfile=LOGFILE | |
|
73 | log file name (default is stdout) | |
|
74 | .TP | |
|
75 | .B | |
|
76 | \-r | |
|
77 | try to reuse all furl files | |
|
78 | .SH SEE ALSO | |
|
79 | .BR ipython(1), ipcluster(1), ipengine(1) | |
|
80 | .br | |
|
81 | .SH AUTHOR | |
|
82 | \fBipcontroller\fP is a tool that ships with IPython, created by | |
|
83 | the IPython Development Team. | |
|
84 | .PP | |
|
85 | This manual page was written by Stephan Peijnik <debian@sp.or.at>, | |
|
86 | for the Debian project (but may be used by others). Modified by Fernando Perez | |
|
87 | <Fernando.Perez@berkeley.edu> for inclusion in IPython. |
@@ -0,0 +1,38 b'' | |||
|
1 | .TH IPENGINE 1 "October 28, 2008" "" "" | |
|
2 | .SH NAME | |
|
3 | \fBipengine \- IPython parallel computing engine control tool | |
|
4 | .SH SYNOPSIS | |
|
5 | .nf | |
|
6 | .fam C | |
|
7 | \fBipengine\fP [\fIoptions\fP] | |
|
8 | .fam T | |
|
9 | .fi | |
|
10 | .SH DESCRIPTION | |
|
11 | ipengine is a control tool for IPython's parallel computing functions. | |
|
12 | .SH OPTIONS | |
|
13 | .TP | |
|
14 | .B | |
|
15 | \-h, \-\-help | |
|
16 | show this help message and exit | |
|
17 | .TP | |
|
18 | .B | |
|
19 | \-\-furl\-file=FURL_FILE | |
|
20 | The filename containing the FURL of the controller | |
|
21 | .TP | |
|
22 | .B | |
|
23 | \-\-mpi=MPI | |
|
24 | How to enable MPI (mpi4py, pytrilions, or empty string to disable) | |
|
25 | .TP | |
|
26 | .B | |
|
27 | \-l LOGFILE, \-\-logfile=LOGFILE | |
|
28 | log file name (defaults to stdout) | |
|
29 | .SH SEE ALSO | |
|
30 | .BR ipython(1), ipcluster(1), ipcontroller(1) | |
|
31 | .br | |
|
32 | .SH AUTHOR | |
|
33 | \fBipengine\fP is a tool that ships with IPython, created by | |
|
34 | the IPython Development Team. | |
|
35 | .PP | |
|
36 | This manual page was written by Stephan Peijnik <debian@sp.or.at>, | |
|
37 | for the Debian project (but may be used by others). Modified by Fernando Perez | |
|
38 | <Fernando.Perez@berkeley.edu> for inclusion in IPython. |
@@ -0,0 +1,25 b'' | |||
|
1 | .TH IPYTHON-WX 1 "October 29, 2008" "" "" | |
|
2 | .SH NAME | |
|
3 | \fBipython-wx \- Graphical frontend that embeds a multithreaded IPython Shell | |
|
4 | .SH SYNOPSIS | |
|
5 | .nf | |
|
6 | .fam C | |
|
7 | \fBipython-wx\fP | |
|
8 | .fam T | |
|
9 | .fi | |
|
10 | .SH DESCRIPTION | |
|
11 | ipython-wx is, compared to ipythonx, a more advanced graphical frontend | |
|
12 | to IPython. It is implemented using WxWidgets. | |
|
13 | .SH OPTIONS | |
|
14 | .TP | |
|
15 | .B | |
|
16 | ipython-wx does not accept any command line options. | |
|
17 | .SH SEE ALSO | |
|
18 | .BR ipython(1), ipythonx(1) | |
|
19 | .br | |
|
20 | .SH AUTHOR | |
|
21 | \fBipython-wx\fP is a tool that ships with IPython, created by | |
|
22 | the IPython Development Team. | |
|
23 | .PP | |
|
24 | This manual page was written by Stephan Peijnik <debian@sp.or.at>, | |
|
25 | for the Debian project (but may be used by others). |
@@ -0,0 +1,30 b'' | |||
|
1 | .TH IPYTHONX 1 "October 29, 2008" "" "" | |
|
2 | .SH NAME | |
|
3 | \fBipythonx \- Simple graphical frontend to IPython, using WxWidgets. | |
|
4 | .SH SYNOPSIS | |
|
5 | .nf | |
|
6 | .fam C | |
|
7 | \fBipengine\fP [\fIoptions\fP] | |
|
8 | .fam T | |
|
9 | .fi | |
|
10 | .SH DESCRIPTION | |
|
11 | ipythonx is a simple graphical frontend to IPython, using WxWidgets. | |
|
12 | .SH OPTIONS | |
|
13 | .TP | |
|
14 | .B | |
|
15 | \-h, \-\-help | |
|
16 | show this help message and exit | |
|
17 | .TP | |
|
18 | .B | |
|
19 | \-d, \-\-debug | |
|
20 | Enable debug messages for the wx frontend. | |
|
21 | look for config files and profiles in this directory | |
|
22 | .SH SEE ALSO | |
|
23 | .BR ipython(1), ipython-wx(1) | |
|
24 | .br | |
|
25 | .SH AUTHOR | |
|
26 | \fBipythonx\fP is a tool that ships with IPython, created by | |
|
27 | the IPython Development Team. | |
|
28 | .PP | |
|
29 | This manual page was written by Stephan Peijnik <debian@sp.or.at>, | |
|
30 | for the Debian project (but may be used by others). |
@@ -39,14 +39,11 b' irunner.py \\-\\-ipython \\-\\- \\-\\-interact script.ipy' | |||
|
39 | 39 | .SH SEE ALSO |
|
40 | 40 | .BR ipython(1) |
|
41 | 41 | .br |
|
42 | .SH BUGS | |
|
43 | The SAGE runner only works if you manually configure your SAGE | |
|
44 | copy to use 'colors NoColor' in the ipythonrc config file, since | |
|
45 | currently the prompt matching regexp does not identify color sequences. | |
|
46 | 42 | .SH AUTHOR |
|
47 | 43 | \fBirunner\fP is an extension of Ken Schutte <kschutte-AT-csail.mit.edu>'s |
|
48 | 44 | script contributed on the ipython-user list: |
|
49 | 45 | http://scipy.net/pipermail/ipython-user/2006-May/001705.html |
|
50 | 46 | .PP |
|
51 | This manual page was written by Bernd Zeimetz <bernd@bzed.de>, | |
|
52 |
|
|
|
47 | This manual page was written by Bernd Zeimetz <bernd@bzed.de>, for the Debian | |
|
48 | project (but may be used by others). Modified by Fernando Perez | |
|
49 | <Fernando.Perez@berkeley.edu> for inclusion in IPython. |
@@ -78,14 +78,38 b" if len(sys.argv) >= 2 and sys.argv[1] in ('sdist','bdist_rpm'):" | |||
|
78 | 78 | #('docs/magic.tex', |
|
79 | 79 | #['IPython/Magic.py'], |
|
80 | 80 | #"cd doc && ./update_magic.sh" ), |
|
81 | ||
|
81 | ||
|
82 | ('docs/man/ipcluster.1.gz', | |
|
83 | ['docs/man/ipcluster.1'], | |
|
84 | 'cd docs/man && gzip -9c ipcluster.1 > ipcluster.1.gz'), | |
|
85 | ||
|
86 | ('docs/man/ipcontroller.1.gz', | |
|
87 | ['docs/man/ipcontroller.1'], | |
|
88 | 'cd docs/man && gzip -9c ipcontroller.1 > ipcontroller.1.gz'), | |
|
89 | ||
|
90 | ('docs/man/ipengine.1.gz', | |
|
91 | ['docs/man/ipengine.1'], | |
|
92 | 'cd docs/man && gzip -9c ipengine.1 > ipengine.1.gz'), | |
|
93 | ||
|
82 | 94 | ('docs/man/ipython.1.gz', |
|
83 | 95 | ['docs/man/ipython.1'], |
|
84 |
|
|
|
96 | 'cd docs/man && gzip -9c ipython.1 > ipython.1.gz'), | |
|
97 | ||
|
98 | ('docs/man/ipython-wx.1.gz', | |
|
99 | ['docs/man/ipython-wx.1'], | |
|
100 | 'cd docs/man && gzip -9c ipython-wx.1 > ipython-wx.1.gz'), | |
|
101 | ||
|
102 | ('docs/man/ipythonx.1.gz', | |
|
103 | ['docs/man/ipythonx.1'], | |
|
104 | 'cd docs/man && gzip -9c ipythonx.1 > ipythonx.1.gz'), | |
|
105 | ||
|
106 | ('docs/man/irunner.1.gz', | |
|
107 | ['docs/man/irunner.1'], | |
|
108 | 'cd docs/man && gzip -9c irunner.1 > irunner.1.gz'), | |
|
85 | 109 | |
|
86 | 110 | ('docs/man/pycolor.1.gz', |
|
87 | 111 | ['docs/man/pycolor.1'], |
|
88 |
|
|
|
112 | 'cd docs/man && gzip -9c pycolor.1 > pycolor.1.gz'), | |
|
89 | 113 | ] |
|
90 | 114 | |
|
91 | 115 | # Only build the docs if sphinx is present |
@@ -212,6 +212,31 b' def find_data_files():' | |||
|
212 | 212 | |
|
213 | 213 | return data_files |
|
214 | 214 | |
|
215 | ||
|
216 | def make_man_update_target(manpage): | |
|
217 | """Return a target_update-compliant tuple for the given manpage. | |
|
218 | ||
|
219 | Parameters | |
|
220 | ---------- | |
|
221 | manpage : string | |
|
222 | Name of the manpage, must include the section number (trailing number). | |
|
223 | ||
|
224 | Example | |
|
225 | ------- | |
|
226 | ||
|
227 | >>> make_man_update_target('ipython.1') #doctest: +NORMALIZE_WHITESPACE | |
|
228 | ('docs/man/ipython.1.gz', | |
|
229 | ['docs/man/ipython.1'], | |
|
230 | 'cd docs/man && gzip -9c ipython.1 > ipython.1.gz') | |
|
231 | """ | |
|
232 | man_dir = pjoin('docs', 'man') | |
|
233 | manpage_gz = manpage + '.gz' | |
|
234 | manpath = pjoin(man_dir, manpage) | |
|
235 | manpath_gz = pjoin(man_dir, manpage_gz) | |
|
236 | gz_cmd = ( "cd %(man_dir)s && gzip -9c %(manpage)s > %(manpage_gz)s" % | |
|
237 | locals() ) | |
|
238 | return (manpath_gz, [manpath], gz_cmd) | |
|
239 | ||
|
215 | 240 | #--------------------------------------------------------------------------- |
|
216 | 241 | # Find scripts |
|
217 | 242 | #--------------------------------------------------------------------------- |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
|
1 | NO CONTENT: file was removed |
General Comments 0
You need to be logged in to leave comments.
Login now