Re: [SQLObject] ezSqlObject convenience wrapper
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Brad B. <br...@bb...> - 2004-03-08 19:11:55
|
On Monday, March 8, 2004, at 08:50 AM, jws...@ra... wrote: >> This debate is becoming a pointless "yes it is", "no it isn't" sort of >> thing though, and I can see now I won't be able to make headway on my >> point, but my logic still stands. If everybody approached this >> situation in the same way (e.g. Daniel with inheritance, Sidnei with >> CASCADE and such), we'd have five or six "wrapper" packages like this >> is no time. > > One would hope that these extension would be test beds for new ideas > and if > worthwhile, would eventually be mainstreamed. If there were multiple > independent code forks, that should probably be interpreted as > impatience > with the development speed of the main code. Having too many people > contributing code is a problem every project should wish for. It's not impatience with the development speed (there were no such complaints to any of us with checkin access or to the list, and let's face it, there's only a couple of people actively contributing to the bleeding edge stuff, there's nothing particularly overwhelming to deal with here), it's just a mistake in choosing to put it another module when it really belongs in the main codebase (or, more likely, in a branch off the main codebase so that people could try it out and discuss before merging the branch, or the useful bits of it into HEAD.) I cannot speak for Ian obviously, though I have a pretty good hunch that if somebody sent him a big patch for SQLObject that looked anywhere near mildly sane, he'd either a.) merge it himself, or b.) offer checkin access, with the specification that it be checked in on a branch (which, for anyone who floats around the CVS repositories of Open Source projects knows that using branches for this kind of thing is standard procedure. Yes, I know, SQLObject is using svn now, but same idea.) To repeat, people like David are golden to SQLObject, and to any such Open Source project to which they contribute their volunteer efforts. It's great to see new contributions. All I'm saying is that doing it this way makes it much more hassle (prohibitively so, in fact) than it needs to be to try out new possible SQLObject features. -- Brad Bollenbach |