diff options
| author | Fred Drake <fdrake@acm.org> | 1999-07-06 21:00:18 (GMT) |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 1999-07-06 21:00:18 (GMT) |
| commit | 6166b871a24a7f983e0c48aaac264fef7c420738 (patch) | |
| tree | 9f5c54e7955613853498fa72670797ba8ea53ed2 | |
| parent | d5dfe984e7a20369d1529f8c80bebde0e93aaff2 (diff) | |
| download | cpython-6166b871a24a7f983e0c48aaac264fef7c420738.zip cpython-6166b871a24a7f983e0c48aaac264fef7c420738.tar.gz cpython-6166b871a24a7f983e0c48aaac264fef7c420738.tar.bz2 | |
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 2727b4b..5a57146 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 |