[issue17910] Usage error in multiprocessing documentation
New submission from Andriy Mysyk: "As mentioned above, when doing concurrent programming it is usually best to avoid using shared state as far as possible" should say "as much as possible" in multiprocessing.rst. ---------- assignee: docs@python components: Documentation messages: 188461 nosy: amysyk, docs@python priority: normal severity: normal status: open title: Usage error in multiprocessing documentation type: enhancement versions: Python 3.4 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue17910> _______________________________________
Andriy Mysyk added the comment: patch attached ---------- keywords: +patch Added file: http://bugs.python.org/file30142/issue17910.patch _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue17910> _______________________________________
Richard Oudkerk added the comment: I don't see any difference in meaning: http://idioms.thefreedictionary.com/as+far+as+possible ---------- nosy: +sbt _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue17910> _______________________________________
Andriy Mysyk added the comment: I found the use of "as far" (as opposed to "as much") but Richard has a good point. Let's close the issue. ---------- resolution: -> works for me status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue17910> _______________________________________
participants (2)
-
Andriy Mysyk -
Richard Oudkerk