[Twisted-Python] Error using mktap for ResourceTemplates
I'm getting an error with both the 1.0.0-1 Debian package (congrats on 1.0, BTW!...and many, many thanks for the up-to-date debs.) and current CVS when I try to use the mktap --processor flag suggested in doc/howto/resource-templates.html mktap web --processor=.rtl=twisted.web.script.ResourceTemplate 'NoneType' object has no attribute 'processors' Usage: mktap web [options]...etc. I'll look into it myself in the morning, but I wanted to see if anyone else had noticed this. Quixote/Twisted interaction possibilities look excellent to me! -- Ken Kennedy | http://www.kenzoid.com | kenzoid@io.com
On Wed, 23 Oct 2002 05:53:11 -0600, Bruce Mitchener <bruce@cubik.org> wrote:
It still shouldn't error. I've filed a bug in the SF tracker for this.
I just "fixed" this, using the existing idioms available used in mktap, but I noticed 2 other problems while doing so. - currently the only idiom for reporting this sort of simple error is "print 'foo'; sys.exit(2)". This isn't really optimal, since we're hopefully going to be using twisted.tap through a non-commandline interface at some point, and the failure should be a formattable, self-contained exception. - the help message for almost every "tap" script is quite long, and so it's very easy to lose the default error reporting. Perhaps it would be more useful in the common case to print exception/error information _after_ the help message, rather than before it, when there is a problem? Thoughts? -- | <`'> | Glyph Lefkowitz: Travelling Sorcerer | | < _/ > | Lead Developer, the Twisted project | | < ___/ > | http://www.twistedmatrix.com |
On Wed, 23 Oct 2002 05:53:11 -0600, Bruce Mitchener <bruce@cubik.org> wrote:
It still shouldn't error. I've filed a bug in the SF tracker for this.
I just "fixed" this, using the existing idioms available used in mktap, but I noticed 2 other problems while doing so. - currently the only idiom for reporting this sort of simple error is "print 'foo'; sys.exit(2)". This isn't really optimal, since we're hopefully going to be using twisted.tap through a non-commandline interface at some point, and the failure should be a formattable, self-contained exception. - the help message for almost every "tap" script is quite long, and so it's very easy to lose the default error reporting. Perhaps it would be more useful in the common case to print exception/error information _after_ the help message, rather than before it, when there is a problem? Thoughts? -- | <`'> | Glyph Lefkowitz: Travelling Sorcerer | | < _/ > | Lead Developer, the Twisted project | | < ___/ > | http://www.twistedmatrix.com |
participants (4)
-
Bruce Mitchener -
Glyph Lefkowitz -
kkennedy＠kenzoid.com -
Moshe Zadka