On Wed, May 10, 2006 at 04:00:01PM -0600, Jonathan Ellis wrote:
| There are any number of projects that can provide warm fuzzy learning
| experiences, but given limited funds, it only makes sense to give
| priority to ones that will benefit other Python developers as well.
You dramatically understimate the quantity of work here I'm afraid,
Well, turning this into a pissing contest would be useless, but I think my qualifications for estimating this are at least as good as yours.
even starting /w what SQLAlchemy's code base, there is an entire
summer of work for a student: work that is quite valuable.
Well, that's what it comes down to, really: how valuable is this? I measure that by what I can accomplish if this proposal were done, compared to what I can accomplish without it. And sure, I would include time saved from good docs as "value" by this metric.
But I still come up with an awfully low value for this project. You're clearly a smart guy, and you're coming up with a vastly different answer. Since I haven't seen you around the list much, my guess is that this is some combination of (a) underestimation of the SA capabilities, (b) overestimation of the difficulty of using the SA "low level" facilities, or (c) simply a much much higher emphasis on having this be separate for the sake of separateness.
| SQLAlchemy has a working codebase; a formal spec would be nice, but not
| really necessary. So saying, "Well, let's see if we can accomplish the
| same thing with a different api which may or may not consume a lot of
| time conforming with the New Vision" is bassackwards.
You have obviously not been reading my posts.
Wow, from "can't we be friends" to this in one post. :)
Relax, dude. Is the alternative -- that I read them, but still disagree -- so unthinkable?
--
Jonathan Ellis
http://spyced.blogspot.com
