On 5 Mar, 09:46 am, [email protected] wrote: >That looks awesome. > >I can't find a license for it.
The code was already MIT licensed. It's more redundantly so, now. Jean-Paul I'm publishing some third-party helpers for >twisted's amp implementation as I need them myself (presumably I'll >make a >formal release announcement at the Pycon sprints). Do you mind if I >copy >this code? I can't seem to find a license. (txampext is ISC-licensed, >which >I assume is congruent to your sensibilities :)) > > >On Mon, Mar 4, 2013 at 5:17 PM, <[email protected]> wrote: >>On 03:34 pm, [email protected] wrote: >> >Hi, >> > >> > >> >I have no issue writing AMP responders TTD-edly, they work pretty >>much >> >the >> >way any other code would. However, I did notice that the only way I'd >> >notice if my Command definitions themselves were broken were if my >> >functional tests start failing. >> >>Chris and I wrote all the AMP-using code for game TDD. See >>game/test/test_network.py in lp:game. >> >>Jean-Paul >> >It would be nice if I could write unit test driven Command >> >specifications, >> >as well. >> > >> >The quickest I could come up with was to call >> >makeArguments/makeResponse >> >with a few known-good/known-bad dictionaries, and see if it blows up. >> >Is >> >there a smarter way to do it? >> > >> >-- >> >cheers >> >lvh >> >>_______________________________________________ >>Twisted-Python mailing list >>[email protected] >>http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > > > >-- >cheers >lvh _______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
