diff options
| author | Fred Drake <fdrake@acm.org> | 1999-07-06 21:00:18 +0000 |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 1999-07-06 21:00:18 +0000 |
| commit | 9c05b63c65433d42bcd0e8ab5dcc674218468962 (patch) | |
| tree | fee658f1f6d2bd0839f065a54ba5e9e40b36db1b | |
| parent | 9ef1c2dd6f86001ba3b1d3f5c206844d7de1b20a (diff) | |
| download | cpython-9c05b63c65433d42bcd0e8ab5dcc674218468962.tar.gz | |
Missing space; reported by Robert Kern <kernr@ncifcrf.gov>.
| -rw-r--r-- | Doc/lib/libasyncore.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/lib/libasyncore.tex b/Doc/lib/libasyncore.tex index 2727b4b891..5a57146308 100644 --- a/Doc/lib/libasyncore.tex +++ b/Doc/lib/libasyncore.tex @@ -16,7 +16,7 @@ socket service clients and servers. There are only two ways to have a program on a single processor do ``more than one thing at a time.'' Multi-threaded programming is the simplest and most popular way to do it, but there is another very -different technique, that lets youhave nearly all the advantages of +different technique, that lets you have nearly all the advantages of multi-threading, without actually using multiple threads. It's really only practical if your program is largely I/O bound. If your program is CPU bound, then pre-emptive scheduled threads are probably what |