> I'm not a Django dev and have nothing to do with GSOC but wanted to
> make some comments on your proposal because I'm interested in it from
> an end-user's perspective.
At the risk of oversimplifying: when justifying a new feature in an
existing code base, an end-user perspective is just as imp
> While I'm not a decision maker in the Django community, that's where
> my concern would be: is this something you could finish in the time
> period.
That's my only real concern as well. That's how I knew my original
proposal was all sorts of misleading and/or muddled: the fact that
Malcolm aske
Sorry, one more thought. Told you I'm not scared of writing!
Regarding hand-rolling these processes: yes, that's easy to do. But
automatic data generation is part of the greater testing process that
production code needs to undergo. And when you hand-roll testing
processes on the fly, you have to
> The main part of your application is something I'll think about some
> more, but I'm not really sure what development effort is involved there.
To address this particular point a little more:
My original proposal was lean on details, which is entirely my fault.
To be honest, I've never partici
Malcolm,
Regarding model-level validation, apparently I'm bad at tracking down
information. I tried on a couple of occasions to search for
information on validation's progress and only found references to
discussions that weren't recorded therein. My mistake. I'm glad that's
already so far along;
I'm looking for feedback on my SoC application which I call
"Effortless Model Testing". EMT would add sample instance generation,
fuzz testing, and (if still necessary) model-level validation to
Django.
I have my ideas explained in detail on my web page:
http://sarcasticzombie.net
Anyone willin
