[Twisted-Python] documentation issue?
![](https://secure.gravatar.com/avatar/86ede4dcfd70d216048f9f5b1fdc6d45.jpg?s=120&d=mm&r=g)
Hi, I am working my way through "The Twisted Documentation" Jan 29, 2003 and found a problem with an example (or with me). At http://twistedmatrix.com/documents/howto/plugin it says: % mktap qotd Saving qotd application to qotd.tap... Saved. % twistd -f qotd.tap % nc localhost 8007 An apple a day keeps the doctor away. % kill `cat twistd.pid` The problem is when I run 'mktap qotd' I get the following error: Unknown command: qotd and then it prints the usage and options help. I am using python 2.2.1 and Twisted 1.0.3 Any help would be appreciated. Ray
![](https://secure.gravatar.com/avatar/8a47722ec9cfd9702f7abefaefa22482.jpg?s=120&d=mm&r=g)
[rprice@collegenet.com]
I got the same problem, then quickly figured out that I forgot to create an empty `__init.py__' file within the other files. But the real reason of this reply is for reporting that the documented: ----------------------------------------------------------------------> Saving qotd application to qotd.tap... Saved. ----------------------------------------------------------------------< lines are not given in response to calling `mktap'. Besides that detail, the example nicely works. Instead of amending the documentation to remove those two lines, maybe `mktap' could accept some `-v' option, server generic, for producing them, and be an opened door for any later other useful extra feedback? -- François Pinard http://www.iro.umontreal.ca/~pinard
![](https://secure.gravatar.com/avatar/8a47722ec9cfd9702f7abefaefa22482.jpg?s=120&d=mm&r=g)
[rprice@collegenet.com]
I got the same problem, then quickly figured out that I forgot to create an empty `__init.py__' file within the other files. But the real reason of this reply is for reporting that the documented: ----------------------------------------------------------------------> Saving qotd application to qotd.tap... Saved. ----------------------------------------------------------------------< lines are not given in response to calling `mktap'. Besides that detail, the example nicely works. Instead of amending the documentation to remove those two lines, maybe `mktap' could accept some `-v' option, server generic, for producing them, and be an opened door for any later other useful extra feedback? -- François Pinard http://www.iro.umontreal.ca/~pinard
participants (3)
-
Francois Pinard
-
Mario Ruggier
-
rprice@collegenet.com