The bottom line is, participating in a project doesn't give you the right to bitch at the lead who is doing far more work than you. (Especially when the bugs you're complaining about are the direct results of features you requested yourself!) The sooner you figure that out, the more willing people will be to work with you.
Normally I'm not a fan of the proliferation of solutions to the same problem, but in this case I think it would be very instructive for you to go ahead and start your own ORM project like you said you would. Do let us know how that goes. :)
On 3/28/06, Florian Boesch <[EMAIL PROTECTED]> wrote:
I originally would've stayed on a stable version, except, it was bugged mainly
for oracle usage, so I *had* to move to the newer versions.
And don't you darn shove the "you lousy slack" up my arse. Do you have *any*
idea how hard it is to isolate a specific mal-behaving combination in a huge
model, extract and rewrite it so I can post it here?
And I didn't do one or two of those!
No Michael has no darn obligation, but the fact is that there is *no* other
usable ORM for oracle in python, and wouldn't there be one, strategically my
whole development would now be java and not python, which for multiple reasons
I don't want, I'm sure you can empathize.
But when you want me to stop thinking of testcases and just simply complain that
things are broken without providing a test-program, just tell me.
--
Jonathan Ellis
http://spyced.blogspot.com
