[IronPython] [Kamaelia-list] Kamaelia and IronPython (was: Hosting IronPython 2.X in .NET app)
dinov at exchange.microsoft.com
Fri Jul 20 08:29:12 PDT 2007
Generally what’s best for us is to get small test cases which demonstrate particular problems. Great examples of this are every single one of Seo’s bug reports.
We have occasionally picked up external Python libraries and their associated test suites (the best example of this I can think of is nzmath). Unfortunately when we do that we need to talk to lawyers, have them approve the license, and then we keep those files in a separate source repository from our primary one. The small individual test cases we can integrate back into our own test suite, add our own versions of the tests for more coverage, etc… and that’s much more flexible.
If they do have a test suite, or if you’re interested in contributing one, I could ping the lawyers, but Kamaelia’s license will at least make that an interesting talk for us ☺.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of M. David Peterson
Sent: Wednesday, July 18, 2007 8:23 PM
To: Discussion of IronPython
Cc: kamaelia-list at lists.sourceforge.net; Peter Fisk; ms at cerenity.org
Subject: Re: [IronPython] [Kamaelia-list] Kamaelia and IronPython (was: Hosting IronPython 2.X in .NET app)
On 7/18/07, Dino Viehland <dinov at exchange.microsoft.com<mailto:dinov at exchange.microsoft.com>> wrote:
Awesome, this will have to be fixed soon. I don't know that any of our PMs are tracking the list,
And if they were, I would question why in the hell that particular PM is getting in the way of progress! ;-)
it's more like "time to fix bugs, let's look at the list!" ☺.
Which makes the 16 votes this bug currently has that much more exciting! :D
To make this even better we've been running into some of our own issues w/ this which provide us w/ additional motivation to fix this.
I'm betting it won't make it into the next release (Alpha 3?), but hopefully the release after that.
All I hope for is that it gets fixed in time for the first beta such that it can be properly and thoroughly tested before the final release. Thanks for all of your efforts with this!
One thing: Would it be helpful if myself or someone else were to pull together a test suite composed of Axon/Kamaelia and all non-C API-based Kamaelia components? Not sure if providing external test suites is considered kosher, but if yes and it would be helpful, I'd be happy to put forth the effort.
Thanks everyone who voted for this.
I second the thanks. Thanks everyone! :D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | http://dev.aol.com/blog/3155
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users