On Wed, Sep 10, 2008 at 03:57:45PM +0300, Dan Pascu wrote:
> On Wednesday 10 September 2008, Oleg Broytmann wrote:
> > > The second fix is for incorrectly interpretted boolean values passed
> > > via arguments to connectionForURI or via dburi parameters.
> >
> > Why Boolean is a class and not just a function? It never creates any
> > instance of the class.
>
> No particular reason. I guess it comes from the habit of doing it that way
> because it looks more like a data type with a class. Of course a function
> would do just fine, but there is no big difference since with the class
> the __new__ method will do exactly what that function would do.
Ok, then. I don't care about it too much.
What I care is the following. If I release 0.9.8 and 0.10.3 the meaning
for URLs like '...?debug=0' would be different compared to previous
versions, so if a developer debugs a program against the newer version of
SQLObject and deploy against an older version this could lead to subtle
bugs. Isn't it a problem? The patch is not a bugfix but a small feature,
isn't it? Should we allow such changes of the API?
Python core developers would disallow such features - even small
features - but they are working on a project with much bigger scale. But
for SQLObject, and counting that the change is only about less significant
part of the DB URI API - I think it's mostly ok.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
