On 5 Mar, 09:46 am, email@example.com wrote:
>That looks awesome.
>I can't find a license for it.
The code was already MIT licensed. It's more redundantly so, now.
I'm publishing some third-party helpers for
>twisted's amp implementation as I need them myself (presumably I'll
>formal release announcement at the Pycon sprints). Do you mind if I
>this code? I can't seem to find a license. (txampext is ISC-licensed,
>I assume is congruent to your sensibilities :))
>On Mon, Mar 4, 2013 at 5:17 PM, <firstname.lastname@example.org> wrote:
>>On 03:34 pm, email@example.com wrote:
>> >I have no issue writing AMP responders TTD-edly, they work pretty
>> >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.
>> >It would be nice if I could write unit test driven Command
>> >as well.
>> >The quickest I could come up with was to call
>> >with a few known-good/known-bad dictionaries, and see if it blows up.
>> >there a smarter way to do it?
>>Twisted-Python mailing list
Twisted-Python mailing list