This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vajrasky
Recipients docs@python, gvanrossum, vajrasky
Date 2013-12-13.09:54:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I was reading the documentation about asyncio. Here is the introduction paragraph:


This module provides infrastructure for writing single-threaded concurrent
code using coroutines, multiplexing I/O access over sockets and other
resources, running network clients and servers, and other related primitives.
Here is a more detailed list of the package contents:

Then I read it like a novel. Then somewhere out of the blue, the Tulip word shows up.


Unlike the standard library :mod:`queue`, you can reliably know this Queue's
   size with :meth:`qsize`, since your single-threaded Tulip application won't
   be interrupted between calling :meth:`qsize` and doing an operation on the

The Tulip word breaks the flow of the story because we never introduce the Tulip word previously. There are two ways to handle this situation:
1. Introduce the Tulip word in the introduction and other parts consistently,
2. Remove the references to Tulip.

I suggest we take option 2 (users of Python 3.4 asyncio stdlib have no reason to know the word Tulip). Here is the patch.
Date User Action Args
2013-12-13 09:54:50vajraskysetrecipients: + vajrasky, gvanrossum, docs@python
2013-12-13 09:54:50vajraskysetmessageid: <>
2013-12-13 09:54:49vajraskylinkissue19971 messages
2013-12-13 09:54:49vajraskycreate