6.1 Why is the package named Candygram?

The name Candygram is actually an acronym for ``the Candygram Acronym Does Not Yield a Good Reference to Anything Meaningful.''

6.2 But wait, doesn't that spell CADNYGRAM?

Yes, you are quite observant. In order to form a compromise with the French acronym, which is CANYDGRAM, the Candygram committee standardized the official acronym as CANDYGRAM.

6.3 How do you pronounce Candygram?

This question produces an outrageous amount of heated debate. Some claim that you pronounce it with short A's, as in tomato, while others claim that you pronounce it with long A's, as in potato. Both sides, however, are completely wrong; the correct pronunciation for Candygram is ``throat warbler mangrove.''

6.4 Underneath it all, does the spawn() function create a process, a thread, or a microthread?

The short answer is that it creates a thread. In Erlang, the spawn() function creates a microthread but calls it a ``process''. Since Python does not yet support microthreads, the Candygram spawn() function creates a standard thread instead and likewise calls it a ``process''. Despite the terminology, no new operating system processes are ever created. Refer to the overview in section 2 for further explanation about the terminology.

6.5 How many processes can I spawn()?

Since Candygram's spawn() function creates a new thread, it depends on how many threads your operating system can reliably handle. Most operating systems can comfortably handle several dozen threads.

Future versions of Candygram may support microthreads, which would allow you to spawn thousands of processes. Logo