[Modeling-users] Python 2.3 and booleans

[Yannick G. <ygi...@yg...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,=20
  we just upgraded to Python 2.3.  As you probably know, Python 2.3
now has a boolean type so repr(a =3D=3D b) is no longer 0 or 1 but True or
=46alse.

We use some int(1) in our database to represent booleans but now all
our queries involving those fields are broken.

This is absolutely not a Modeling problem but I think that I can use
Modeling to reconvert those values just before the query.  That would
solve quite a lot of work here.

Any of you guys had the same problem when switching to Python 2.3 ?

Should I tweak Modeling to make the conversion automatically ?  Can it
break anything somewhere else ?

And absolutely unrelated to this problem, I've been using GNU Arch
lately instead of CVS.  It features GPG signed commits and ease
maintaining branches in synch.  If Modeling used Arch, we could make
the changes to automate booleans conversions in our branch and still
stay up to date with the main branch in case someone else would like
to have this particular feature and Sebastian find our code too ugly
to be merged yet...

 ; )

Enough propaganda, thanks for your time guys !

=2D --=20
Yannick Gingras                                "please call it ``GNU/Linux'=
'"
Coder for OBB : Officious Billowing Bailey             -- Richard M. Stallm=
an
http://OpenBeatBox.org

=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAfyG1ZJ8/OobqizMRAvk8AKDojHEvO8hdhLmk1xMtKfZMn4aKxwCeIhq9
quoHiRK/W5PBstlw9qs+DOE=3D
=3Dk51v
=2D----END PGP SIGNATURE-----